Improved Order Accuracy for SKU order creation in Anchanto Order Experience (OXM)

Overview

Anchanto Operations Experience (OXM) now helps improve shipment reliability, order value accuracy, and downstream financial consistency during SKU creation.

With this update, sellers are required to explicitly enter a Selling Price while creating SKUs or products, helping reduce shipment processing issues caused by unintended zero-value orders.

Sellers can still enter zero where required for scenarios such as gifts, samples, or reshipments, but the value must now be entered intentionally. This ensures more accurate order data, smoother carrier processing, and better operational control across fulfillment workflows.

Steps (UI and Bulk Workflows)

Steps for Creating or Editing a New SKU via the UI

1. Go to Products or Inventory section on the side navigation bar. Click + Add New Product located at the top-right corner of the listing screen.

2. Select the option to create a new SKU or product from the menu.
3. Fill in the product details as required, including core identification metadata fields. 
4. Locate the Selling Price field within the Base UOM pricing matrix section. Type your explicit selling price in the Selling Price field. If the SKU is a gift, sample, or reshipping item, enter 0 manually.

5. Enter a value in the Retail Price box and ensure it is equal to or more than the value typed in the Selling Price field. 

6. Click Add Product at the bottom of the form page to save your entry. 

Steps for Creating or Updating SKUs via Bulk Upload

1. Go to Products or Inventory section → Click the dropdown arrow next to the creation button and select Bulk Upload.
2. Click Download Bulk Products Template from the modal overlay popup box. 

3. Open the downloaded spreadsheet on your device and navigate to the data worksheet rows. 

4. Locate column AF, titled Selling price*. Note the asterisk character indicating its mandatory operational status. 
5. Populate the Selling price* column for every single active product row entry in your catalog sheet. For any intentional zero-value items, type 0 directly into the cell. 
6. Locate column AG, titled Retail price. Ensure no row entry contains a value lower than the corresponding selling price row. 
7. Save your completed spreadsheet file, then return to the OXM platform's Add Bulk Products interface modal box. 
8. Drag and drop your spreadsheet file into the target box or click Browse to select the file from your local storage. 
9. Click the Upload button to run platform verification and parse your catalog updates. 
10. Review the generated processing report to verify that all rows passed without validation rejections.

Important Points

• Where this applies : This validation rule applies exclusively when you create new SKUs or edit your existing SKUs going forward. 
• Existing Data Impact: Your current catalog is completely safe. There is no forced change or automatic data update. Existing SKUs carrying a zero selling price will remain completely unchanged and continue to operate normally. 
• Valid Zero-Value Use Cases: Entering zero (0) remains fully supported for specific workflows, such as gift shipments, promotional product samples, reshipping legs after a failed delivery, or return-to-origin flows. However, you must now type 0 into the box yourself. 
• Retail Price Rules: Retail price validation rules remain unchanged. The Retail Price must always be equal to or greater than the Selling Price. Note that a retail price of zero (0) is always allowed regardless of what your selling price is. 
• API Integration Changes: If your technical teams use the Open API for bulk product workflows, they must update their integration request payloads to define Selling Price as a required field to avoid system error responses. It is highly recommended to test updated payloads in a staging environment before pushing updates to production. 
• Template Layout Changes: Logistics and catalog management teams must stop using old saved files and download the updated version of the bulk template from the platform to avoid row-level verification failures.

Common errors: