Household Products EDI: Connect Distributor Purchase Orders to Case-Level Shipments

What this looks like in household consumables

A distributor orders cases of refill pouches using its internal item number. The brand also sells multipacks online and stocks individual pouches. A technically valid EDI mapping that selects the online pack can produce the wrong physical quantity while preserving the order’s apparent product family.

Records, ownership, and update rules

Work through the process

1. 01
   Confirm the partner crosswalk

   Review each distributor item number, internal SKU, and case definition. Retain customer-specific configurations rather than applying the ecommerce pack to every channel.
2. 02
   Validate order meaning

   Check product, unit, quantity, and ship-to before accepting the ERP order. Hold unknown codes and inconsistent case quantities for the responsible owner.
3. 03
   Construct each document correctly

   Use accepted order decisions for acknowledgments, actual shipment evidence for notices, and finance records for invoices. Preserve partner references across the business chain.
4. 04
   Reconcile partial delivery

   Keep unshipped balances and later shipments visible. A delivered EDI file should not close an order whose physical remainder is still outstanding.
5. 05
   Send one distributor PO through Orderful and audit every quantity

   Run a distributor test purchase order through Orderful for its refill-pouch item number. In NetSuite, the order line should point to the distributor's case item, not the online multipack, in the case quantity the partner ordered. Ship part of the order and check the outbound ship notice: its quantity must equal the shipped cases, and the open balance in NetSuite must equal the remainder. Then have the distributor announce a new case count. Open orders under the old definition should be flagged for review, not restated. A line mapped to the multipack, a notice reporting the full order, or an old order silently reinterpreted stops the rollout.

Handle the exceptions explicitly

Distributor changes its case definition

Version the mapping and review open orders before applying the new factor.

Shipment includes mixed cases

Use the required item-level contents and partner hierarchy.

Document repeats after a retry

Preserve the business identity and avoid a second apparent order or shipment.

What to verify before expanding

• Distributor cases cannot silently inherit an ecommerce multipack definition.
• Outbound quantities match actual shipment evidence and remaining order balance.
• A distributor case-definition change preserves earlier order interpretation and flags open orders that require mapping review.
• Mixed cases retain item-level contents in the partner hierarchy instead of being represented by one average case factor.

Technical references

• Orderful transaction model
• Stacksync NetSuite supported objects