Resolving KIT and Standalone Inventory Line Items Between Anchanto Operations Experience (OXM) and Anchanto Warehouse Management Systems(WMS)

OXM automatically resolves KIT SKUs into their underlying Inventory SKUs (ISKUs) during order submission to maintain accurate inventory alignment across downstream systems. Because Warehouse Management Systems (WMS) process orders strictly at the ISKU level, this resolution prevents data mismatches and reduces order push failures. It retains complete structural traceability by embedding specialized KIT references directly into each fulfilled line-item payload. 

Prerequisites: 

• Required User Roles/Permissions: Admin Portal access for 3PL operators or Customer Portal access for E-commerce sellers with existing Role-Based Access Control (RBAC) order creation and update privileges. 
• Essential System Configurations: A properly configured product master where active KIT SKUs are mapped to their respective component ISKUs. 
• Integration Rules & Constraints: Downstream WMS systems must handle order create, update, detail, and resync flows via B2B or B2C integration paths. The kit_sku field must always be present in the payload, even when it contains a null value. Note that historical orders are not backfilled with KIT references.

Creating an Order with a KIT SKU

1. Go to Orders → Click  Create New Order.
2. Go to the Add Products section → Click the Search By dropdown and select either SKU or Product. 
3. Click the Products field → Select the desired KIT SKU (e.g., OfflineKitByBulk001 (Offline KIT)) or a standalone ISKU from the populated list. 

4. Review the auto-populated component lines in the product grid to verify that all corresponding ISKUs, product names, and unique kit_sku mapping fields populate correctly. 

5. Click Submit → The system evaluates the configuration on the server side at submission time, replaces the KIT SKU with individual ISKU line items, attaches the parent bundle identifier within the kit_sku field, and routes the pure ISKU line payload to the WMS. 

Reviewing a Stored Order

1. Go to Orders → Click the specific Order Number you wish to inspect. 
2. Scroll to the Product Details section → The system displays the finalized order matrix populated strictly with individual ISKU lines. 
3. Locate the Kit SKU column header to verify the structural tracing status: 
   • Component lines derived from an ordered bundle display their originating parent bundle identifier (e.g., Bulkinvkit2705). 
   • Component lines added independently as standalone items populate this field value as null. 

Updating an Active Order

1. Go to Orders → Locate the target record, click the Actions menu on the right edge of the row, and click Edit.

1. Add, remove, or modify item line rows within the restriction boundaries allowed by your active order status and user permission model. 
2. If introducing a new bundle to the order layout, select the required KIT SKU normally. 
3. Click Save/Submit → OXM resolves the new bundle parameters on the server side, maps entries to their component ISKUs, injects is_kit and kit_sku context tracking variables against the lines, and transmits the clean updated layout payload to the WMS integration path. 

Managing WMS Resync Signals

1. When the WMS transmits execution details or triggers an order resync signal back to OXM, go to the Order Details interface screen of the target record. 
2. Check the Audit Logs or the Product Details matrix to review inbound data changes. 
3. Verify the updated database rows based on system processing and log rules:
   • If WMS returns a null value, OXM stores a literal null value without recalculating or overriding the baseline data model. 
   • If WMS transmits an unexpected or unknown KIT reference string, OXM stores the value exactly as received and logs an operational warning for system monitoring.

Note: