Retailers can configure required system and custom fields necessary to generate a SKU. This article explains how a buyer can then populate data in these fields and send a request to their system to generate a new SKU.
Once a product has passed through costing analysis and approvals, buyers need to assign relevant retail data attributes for the product such as Merchandising Hierarchy, Description, Marketing Code, Defect handling, etc. before a SKU can be created. This enables the retailer to populate their own systems with all the required data necessary to create a SKU and distribute the product into their systems.
Follow the below steps to populate Retail data and submit a SKU request:
Step 1 : Navigate to Products > Linesheet then click on a specific Product to open the Product detail page and go to Retail Data tab.
Step 2: Retail Pricing > Values in these fields can be completed in two ways: either manually in the Linesheet OR automatically via API depending on your company's setup.
🔍 For more information about how these fields can be populated automatically please see SKU Integration documentation
Step 3: Merchandising Hierarchy> Assign the relevant Merchandising Hierarchy from the dropdown list.
Step 4: Specifications > Values in these fields can be completed in two ways: either manually in the Linesheet OR automatically via API depending on your company's set up.
- SKU: if your company is using Request SKU function then leave this field blank.
- Master SKU: if your company is using Request SKU function then leave this field blank.
- Atelier Code is a system field and cannot be edited.
- Purchase Method is a system field and cannot be edited.
- Purchase Method Status will be updated via SKU Integration and can not be edited.
- Description can be completed either manually in the Linesheet OR automatically via API depending on your company's set up.
Step 5 : Custom Fields > Populate values in Custom fields. The Save Data CTA will be disabled until all required fields are complete (required fields are indicated with a red asterisk*). Once all required fields are complete and data is saved, click on the REQUEST SKU button. 
📔 Note:
- Custom fields can be 2 types: type in or drop-down.
- Drop down values are configured by your Integration team for you to choose from at a Product level. If you don't see the value you need in the list, please contact your Integration team.
- Learn more about how these Custom fields are set up by your Integration team and their behaviour on Retail data Management documentation.
⚠️ All fields marked with * are required fields to generate a SKU in your system hence need to complete before you can submit your SKU request.
Step 6: Once The SKU request has been made, you will be unable to edit the product, and the REQUEST SKU is now disabled (grey). While the product is in a pending status, all fields will be locked (indicated by the padlock icon) until a SKU has been returned to Loupe.
Step 7 : Once a SKU is received successfully from your systems, you will receive a notification and the new SKU Code will be visible on Linesheet and on the Product page, Retail Data tab.
📔 Notes: Post SKU Behaviour:
- Loupe enables your Integration team to define which fields should be controlled by your internal systems versus which fields should control your internal systems from Loupe, after a SKU has been applied.
- Values in fields displaying a padlock icon can only be edited in your internal systems. Loupe can only receive the updated value via API.
- Values in fields that do not display a padlock can be edited in Loupe and your systems will be updated automatically via BoM Export API.
💡 Tips: Cancel SKU Request
For any reason if you need to cancel your submitted SKU request, please contact your IT team so they can remove the request for you via our SKU Error API.