Retail EDI for CPG Brands: Connect Purchase Orders, Acknowledgments, Shipments, and Invoices

What this looks like in consumer packaged goods

A CPG brand wins a retail account with several distribution centers. The first purchase order uses retailer item numbers and case quantities, while NetSuite stores internal SKUs and individual units. The retailer also expects shipment details that only exist after packing. Reusing the purchase-order quantity for every outbound document would misstate a partial shipment.

Records, ownership, and update rules

Work through the process

1. 01
   Confirm the partner agreement

   Collect the required transaction types, identifiers, location codes, validation rules, and test process. Different retailers can require different fields for the same document type, so partner requirements belong in the mapping contract.
2. 02
   Map the incoming order

   Resolve item and location references before creating an ERP transaction. Hold unknown codes or inconsistent packs for review and preserve the original document so corrections remain explainable.
3. 03
   Generate each response from its owner

   Build acknowledgment from the accepted order decision, shipment notice from warehouse evidence, and invoice from finance. Avoid copying one status across these documents simply because they share a purchase-order number.
4. 04
   Reconcile technical and business status

   Track validation, transmission, acknowledgment, and operational completion separately. A delivered file is not evidence that the retailer accepted the commercial content or that the warehouse shipped the goods.
5. 05
   Ship a partial order through Orderful's test stream first

   Process one retailer purchase order for two distribution centers on Orderful's test stream. Acknowledgment, ship notice and invoice must each carry the partner identifier and test flag; none may address the live relationship. Ship fewer cases than requested from NetSuite, then open the ship notice: its quantities must equal what was packed, and the balance must stay open on the NetSuite order. Send a revised purchase order from the test partner; the ERP order must wait until the revision is checked against shipped amounts. Stop the rollout if a document reached the live stream, if the ship notice repeated the ordered quantity, or if the revision overwrote shipped lines.

Handle the exceptions explicitly

Partner revises a purchase order

Evaluate the revision against accepted and shipped quantities before updating the ERP order.

Partial shipment

Report the actual shipment and preserve the remaining order balance under the partner’s rules.

Document passes syntax but item is wrong

Keep business mapping checks in the release gate; technical validity does not establish correct product identity.

What to verify before expanding

• Every outbound document uses the correct partner and live or test stream.
• Actual shipment quantities drive the shipment document, not the original requested amount.
• A replayed partner document retains its existing order and line references without creating additional accepted demand.
• A technically valid document with the wrong item mapping stops at business review before ERP application or shipment release.

Technical references

• Orderful transaction model
• Stacksync NetSuite supported objects