Grocery EDI for Snack Brands: Keep Case Counts and Advance Ship Notices Consistent

What this looks like in packaged food and snacks

A grocer orders 120 cases of a snack multipack. The warehouse sends 96 cases on the first truck and the remainder later. If the first shipment notice copies the purchase-order quantity, the retailer receives a document claiming goods that are not on that truck. The second shipment then becomes difficult to reconcile.

Records, ownership, and update rules

Work through the process

1. 01
   Confirm the grocery packing rules

   Obtain the partner’s required item identifiers, case hierarchy, location codes, and shipment notice timing. Do not assume another grocer’s successful mapping applies unchanged.
2. 02
   Resolve the order line

   Translate retailer case quantities using the approved crosswalk and retain the original unit. Reject an unknown item or case factor before creating downstream commitments.
3. 03
   Build from the truck’s contents

   Use the actual shipment record to construct the notice, including only the goods assigned to that shipment. Preserve the unshipped remainder for later fulfillment under the partner’s rules.
4. 04
   Reconcile after transmission

   Track validation and delivery independently from receiving results. A technically accepted notice still needs to match the physical quantities and later invoice evidence.
5. 05
   Ship 96 of 120 cases and inspect the ASN in Orderful's test stream

   Load a purchase order for 120 cases and record a first shipment of 96 cases in NetSuite. Generate the advance ship notice in Orderful's test stream and read its line quantity: it must say 96, with the remaining 24 still open on the order. A notice that reports 120 halts the rollout. Next, compare the retailer's case count on the purchase-order line with the internal units on the NetSuite shipment; they must reconcile through the mapped case definition. Then substitute a different pack for part of the load. The notice must not describe it as the ordered item until product operations confirms the mapping and commercial approval is on file.

Handle the exceptions explicitly

Warehouse substitutes a pack

Require an approved commercial and mapping decision before describing it as the ordered item.

Shipment is repacked after notice creation

Version and correct the affected document according to the partner’s process.

Same notice is replayed

Preserve its business identity and avoid creating a second apparent shipment.

What to verify before expanding

• Each shipment notice describes only the goods on its own shipment.
• Retailer case quantities reconcile to the approved internal units.
• Repacking after notice preparation triggers the partner's agreed correction process and preserves the earlier notice reference.
• Replaying the same notice leaves one shipment identity; it does not double the case count in reconciliation.

Technical references

• Orderful transaction model
• Stacksync NetSuite supported objects