Skip to content

Beverage EDI: Reconcile Pallet Shipments, Advance Ship Notices, and Distributor Receipts

The advance ship notice describes the mixed pallet the warehouse loaded, not the pallet count on the order, and a distributor receipt is matched to it rather than replaced by it.

Author
Alexis Favre · Co-Founder & CTO
Published
Read time
5 min read
Beverage EDI: Reconcile Pallet Shipments, Advance Ship Notices, and Distributor Receipts
APP TIPS

The operating decision

Beverage EDI should connect the distributor order to actual pallet and case contents, shipment notices, and later receipts. Preserve product-specific pallet configurations and destination identifiers. Build the outgoing document from warehouse-confirmed contents and validate it against the partner’s requirements before treating technical delivery as complete.

Explore the complete beverages integration and automation hub for the systems and processes around this guide.

Summary card: Beverage EDI ship notices from NetSuite through Orderful

What this looks like in beverages

A distributor orders a full pallet plus loose cases of another flavor. The warehouse builds a mixed pallet for the final shipment. A notice based on the original order’s pallet count would not describe the physical shipment, making receiving and later shortage investigation difficult even if the file passes syntax checks.

Records, ownership, and update rules

RecordOwnerOperating rule
Distributor order lineCustomer operationsRetain partner item, unit, quantity, destination, and requested date.
Pallet contentsWarehouseOwn the actual item and case relationships for each shipped pallet or handling unit.
Shipment noticeIntegration operationsBuild the partner-required hierarchy from confirmed shipment evidence.
Distributor receiptAccounts receivablePreserve received quantities and references separately from the transmitted notice.
Record ownership diagram: Distributor order line, Pallet contents, Shipment notice
Define the record owner and the rule before enabling updates.

Work through the process

  1. 01
    Confirm the handling-unit rules
    Review how the partner expects pallets, cartons, item lines, and identifiers represented. A mixed pallet may require a different hierarchy from a full single-item pallet.
  2. 02
    Use actual packing evidence
    Collect the final warehouse contents after approved repacking. Keep partial pallets and loose cases explicit rather than converting every handling unit into a standard pallet quantity.
  3. 03
    Validate the business totals
    Reconcile shipment notice lines to actual cases and the remaining order balance. Compare destination and item identifiers as well as document syntax.
  4. 04
    Track the receiving outcome
    Attach later receipt evidence and keep discrepancies open for operations or finance review. The notice describes what was shipped; it does not establish what the distributor accepted.
  5. 05
    Send a mixed-pallet ASN to the Orderful test stream before go-live
    Ship a test order as one full pallet plus a mixed pallet holding two flavors. Generate the notice from the warehouse's confirmed contents in NetSuite and send it to the distributor's test stream in Orderful. The mixed pallet must appear with an item line and case count per flavor under its own handling unit, and the totals must equal the shipped cases and the balance left on the order line. Then repack the mixed pallet after the draft exists and regenerate. Stop the rollout if the mixed pallet arrives as one averaged line, if totals disagree with the shipment or order balance, or if the first draft goes out unchanged.
5-step operating sequence: Beverage EDI ship notices from NetSuite through Orderful
Follow the operating sequence; unresolved exceptions return to a responsible reviewer.

Handle the exceptions explicitly

Pallet is rebuilt after document preparation

Regenerate or correct the affected notice under the partner’s process before relying on it.

Receipt reports only a pallet total

Request the needed item detail before resolving a line-level shortage.

Loose cases are omitted

Block release until the document describes the complete actual shipment.

What to verify before expanding

  • Mixed pallets preserve their item-level case contents.
  • Notice totals reconcile to the actual shipment and remaining order quantities.
  • Loose cases and partial pallets appear in the shipment contents instead of disappearing behind a whole-pallet total.
  • A pallet-only distributor receipt leaves line-level shortages unresolved until the necessary item detail is obtained.
Book a demo for beverages integration and automation

Connect this process to the rest of your operation

Explore Stacksync EDI and scope the records and actions against your actual systems. Book a demo with a real distributor order line example and the exception your team handles most often, for example pallet is rebuilt after document preparation.

The shared architecture guide covers record matching, ownership, and recovery across systems.

Technical references

Book a demo for beverages integration and automation

FAQ

Frequently asked questions

Can all pallets use the same conversion factor?
No. Product, loading configuration, and partial or mixed contents determine the case quantities on each pallet, and the distributor's receiving team counts what is on the truck, not what a factor predicts. Use the approved configuration for that product and the shipment-specific packing evidence. A notice that leans on one factor passes the syntax check and still misdescribes the load, which surfaces later as a phantom shortage.
Does a 997 acknowledgment from Orderful mean the distributor accepted the shipment?
No. The acknowledgment confirms the distributor's EDI system received a well-formed document; it says nothing about whether the pallets arrived, were counted, or were accepted. Commercial acceptance shows up later in the receipt data and in any discrepancy the distributor raises. Treat the acknowledgment as the end of the transport step, and keep the order open in NetSuite until receiving evidence closes the quantity.
When is it safe to move the ASN from the test stream to live?
Once three things hold: each distributor location carries the partner's own identifier on its NetSuite ship-to record, each sellable item carries the partner item reference, and the warehouse records final pallet contents after repacking rather than before. Run real shipments through the Orderful test stream against the partner's validation guideline until they pass without manual edits, then switch. Skip any of these and the first production notice tends to fail on identifiers rather than syntax.

About the author

Alexis Favre
Alexis Favre
Co-Founder & CTO

Alexis Favre is the Co-Founder and CTO of Stacksync (YC W24), the first real-time and two-way sync for enterprise data at scale. Alexis is a Y Combinator alumni with expertise in large scale data engineering.

All posts by Alexis Favre

About Stacksync

Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing.

Coworkers laughing in front of a laptop in a casual office setting

You just read how it should work.
See it run on your own data.