Personal Care Retail EDI: Match Retailer Item Numbers to Shades, Sizes, and Sets

What this looks like in personal care

A retailer orders a seasonal gift set under its own item number. The brand also sells the component products individually and the set changes next season. The EDI mapping needs the current approved set revision while preserving older orders, rather than treating the retailer item as a timeless alias for one component.

Records, ownership, and update rules

Work through the process

1. 01
   Approve the assortment mapping

   Review each retailer code against the intended consumer product and case configuration. Similar shade names or shared family codes should not bypass exact item validation.
2. 02
   Preserve set revisions

   Tie seasonal sets to approved components and effective dates. Before changing a mapping, inspect open orders and determine which version the retailer actually ordered.
3. 03
   Build documents from their owners

   Acknowledgments use the accepted commercial decision, shipment notices use actual packing evidence, and invoices use the finance-owned transaction. Keep the partner references consistent across the chain.
4. 04
   Test product exceptions

   Include wrong shade, changed set, partial shipment, and unknown retailer item cases. Confirm both technical acceptance and the business correctness of the mapped products.
5. 05
   Push last season's retailer code through the Orderful test stream

   In the Orderful test stream, submit a purchase order using a retailer item number from last season's gift set, now assigned to this season's set. The NetSuite sales order must show the current revision's components with its effective date, while last season's accepted orders under the same code keep their original components. If earlier orders now display the new set, the mapping has no effective dating and cannot go live. Ship the test order and raise the invoice. Compare the retailer's line number on the purchase order, the ship notice and the invoice: all three must match. A renumbered or dropped line means the partner reference is regenerated, not carried.

Handle the exceptions explicitly

Retailer reuses a seasonal code

Confirm the effective set definition instead of rewriting historical orders.

Warehouse proposes another shade

Require commercial approval and the partner-compliant representation.

Set ships in separate cartons

Preserve the actual shipment hierarchy required by the partner.

What to verify before expanding

• Every retailer item resolves to the intended shade, size, or set revision.
• The original partner line survives through shipment and invoice reconciliation.
• A reused seasonal retailer code preserves the historical set definition for already accepted orders.
• A proposed shade substitution requires the accepted commercial decision and partner-compliant representation before release.

Technical references

• Orderful transaction model
• Stacksync NetSuite supported objects