ASN accuracy and compliance
An Advance Ship Notice that reflects what was actually packed and shipped
An accurate ASN connects the customer's order with the physical shipment. It must communicate the correct items, quantities, packaging structure and shipment references within the trading partner's required timeframe. ECOM validates ASNs against partner rules, packing data, labels and deadlines to help prevent the errors that lead to receiving problems, shipment disputes and chargebacks.
At a glance
- Trading partner-specific ASN rules
- Packing hierarchy validation
- Order-to-shipment reconciliation
- Label reconciliation
- Quantity and unit-of-measure checks
- Shipment reference validation
What is an Advance Ship Notice (ASN)?
An Advance Ship Notice, the X12 856 or the EDIFACT DESADV, describes a shipment before it arrives, with the order, the pallets and cartons with their SSCCs, and the items and quantities in each. GS1 guidance recommends that ASN information match the actual goods and be received and processed before those goods arrive. Receiving partners use it to plan the dock, receive by scan and update inventory.
Outcomes
What you can expect
Fewer ASN errors
Rules, reconciliation and label checks help prevent the common errors that contribute to receiving problems and chargebacks.
Fewer shipment disputes
Notices that match what was packed and shipped, with an audit history of corrections, give you facts when a partner questions a shipment.
Deadlines met
Notices approaching or missing a customer's transmission deadline are flagged while there is still time to act.
Approach
How ECOM delivers it
-
Trading partner-specific ASN rules
Apply required fields, document structures, codes, and validation rules for each customer.
-
Packing hierarchy validation
Check shipment, order, pallet, carton, and item relationships against the required structure.
-
Order-to-shipment reconciliation
Compare shipped items and quantities with purchase orders and available packing confirmations.
-
Label reconciliation
Verify that SSCCs reported in the ASN correspond to the labeled shipping units.
-
Quantity and unit-of-measure checks
Identify discrepancies involving eaches, cases, packs, and configured conversion factors.
-
Shipment reference validation
Check purchase orders, tracking numbers, bills of lading, carrier identifiers, and shipping dates.
-
Deadline monitoring
Flag ASNs approaching or missing customer-specific transmission deadlines.
-
Acknowledgment and exception tracking
Track transmission and available responses, distinguishing delivery, technical acknowledgment, and business acceptance.
-
Controlled corrections
Support correction and resubmission according to the trading partner's procedures, with an audit history.
Learn the basics
What partners check in an ASN
This is general industry practice. Each partner's implementation guide sets the exact deadline, structure and data it requires, so always start from the partner's own guide.
Read the 856 ship notice guide-
Timing
Many partners require the ASN when the shipment leaves, or a set time before it arrives. A notice received after the truck is often treated as late.
-
Structure
The notice follows the partner's hierarchy, typically shipment, order, pack and item levels, in the order its guide defines.
-
Quantities and units
Every item and quantity matches what is in each carton, in the unit of measure and packaging level the partner ordered.
-
Carton SSCCs
Each pallet or carton SSCC in the notice matches the label on that unit, and no SSCC is repeated.
-
Order and location references
The purchase order number, ship-to location and, for cross-dock shipments, the final store match the order.
-
Carrier details
The carrier, bill of lading or tracking number and ship date match the actual shipment and the partner's routing rules.
Common problems
Why ASNs fail
Most ASN errors trace back to a few causes. Each has a fix at the source rather than at the dock.
How to prevent retail EDI chargebacks-
Built from the order, not the shipment
The notice repeats ordered quantities, so short or substituted shipments arrive with an ASN that does not match.
-
Sent in an end-of-day batch
Notices wait for a nightly run and reach the partner after the truck. Sending at shipment confirmation avoids it.
-
Labels printed from other data
Labels and notices come from different systems, so SSCCs differ and cartons cannot be received by scan.
-
Rejections nobody sees
A 997 or 824 reports a problem, but no one acts on it, so the same error repeats on the next shipment.
Where ECOM fits
Related ECOM products and services
These recorded capabilities of ECOM products and services support this workflow. Your configuration decides which apply.
-
PRISM-SCV
PRISM-SCV monitors response windows by trading partner and document type and identifies late or missing responses.
-
PRISM-WebEDI
PRISM-WebEDI lets partners without EDI systems create ship notices in a browser, with business-rule enforcement and UCC labels printed from the portal.
Documents and standards
Common transactions
The ASN sits in the middle of the order cycle. These are the documents it is checked against and the responses that show how it was received.
| Code | Document | What it does |
|---|---|---|
| 850 | Purchase Order | The order the ASN must reference, with its items, quantities and ship-to locations. |
| 856 | Ship Notice/Manifest | The Advance Ship Notice, with the shipment, order, pack and item levels of the shipment. |
| 997 | Functional Acknowledgment | The technical acknowledgment that the partner received the ASN and that it was syntactically valid. |
| 824 | Application Advice | Business acceptance or rejection, reporting ASNs the partner rejected or accepted with errors. |
| 810 | Invoice | Bills the quantities the ASN reported as shipped. |
Scenarios
Common scenarios
Retail distribution center shipments
Send ASNs that meet each retailer's timing and structure rules for store and distribution center deliveries.
Drop-ship and e-commerce orders
Confirm each consumer shipment with an accurate notice and tracking details within the partner's window.
Shipments from a 3PL
Reconcile the 3PL's packing confirmations with the order so the ASN matches what the warehouse actually shipped.
Frequently asked questions
Will this eliminate ASN chargebacks?
No one can promise that. Each partner sets its own rules and penalties. ECOM helps prevent common ASN errors by applying partner rules, reconciling the ASN with the order, labels and packing data, and flagging deadlines.
How soon must an ASN be sent?
It depends on the partner. Many retailers require it when the shipment leaves or a set time before it arrives. The partner's implementation or routing guide states the rule.
What is the difference between a 997 and an 824?
A 997 is a technical acknowledgment that the ASN was received and syntactically valid. An 824 reports business acceptance or rejection. A 997 alone does not mean the partner accepted the content.
Which functions will we have?
Available functions depend on the configured solution, connected data sources, and trading partner requirements. ECOM confirms the scope with you during discovery.
Review your ASNs before your partner does
Tell us which partners you ship to and send a sample ASN. An ECOM specialist will review it against the partner's requirements.