EDI 856: Advance Ship Notice (ASN) for Regulated Traceability
Understand how an advance ship notice connects shipment contents, physical handling units and lot records without confusing an exchange format with regulatory obligations.

On this page · 11 sections
- 1What an EDI 856 is—and what it does not establish
- 2The generic shipment–order–pack–item hierarchy
- 3Agree the partner mapping and physical-label connection
- 4ASN and FSMA 204: reference records, lot links and scope
- 5DSCSA transaction information: a separate scope check
- 6Follow the notice from shipment preparation to receipt
- 7Build a shipment-to-lot evidence model
- 8Three worked cases: mixed lots, split orders and corrections
- 9Integrate transport, validation and business responses
- 10Common failure modes and proportionate controls
- 11Implementation and review checklist before live exchange
How does EDI 856 apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What an EDI 856 is—and what it does not establish
EDI 856 is an electronic advance ship notice (ASN), also called a ship notice/manifest, used to tell a trading partner what is being shipped and how the shipment is organised. This is common operational usage, not a reproduction of an ASC X12 specification. The shipment–order–pack–item hierarchy used in this article is a generic business model, not a segment map or mandatory transaction structure.
| Term | Operational purpose | What it does not establish |
|---|---|---|
| EDI 856 | Electronically announce shipment contents and organisation. | What the recipient actually received. |
| ASN | Describe the broader business concept of an advance shipment notice. | A particular exchange format merely from the name. |
| Purchase order | Record what the buyer intends to purchase, including quantities. | What was shipped or received. |
| Packing list | Describe contents represented as packed for dispatch. | Independent confirmation of receipt. |
| Receiving record | Record observed quantities and findings at receipt. | Agreement with every ordered or announced quantity. |
An illustrative workflow compares intended purchase quantities on the order, announced shipment contents on the ASN, and observed receipt quantities on the goods receipt note. Keep these quantities distinct even when they match. If they differ, investigate the discrepancy rather than replacing one record with another; preserving each record’s meaning supports data integrity.
For regulated traceability, treat EDI 856 as an exchange option, not proof that a regulatory obligation has been satisfied. This article separates binding regulatory text, FDA explanatory material, proposed operating practices and software implementation choices. Its record comparisons are operating practices; any legal assessment needs the applicable product scope and underlying records, not simply the message’s name.
02The generic shipment–order–pack–item hierarchy
A useful way to understand an EDI 856 is to follow four business levels: shipment, order, pack and item. The hierarchy below is an explanatory model for organising shipment information, not a universally required layout or a statement of ASC X12 conformance rules.
- Shipment identifies the movement being announced. It provides the common context for the orders and physical contents included in that movement.
- Order links those contents to a commercial request. Keep the order-line reference where it is needed to distinguish which requested product an allocation fulfils.
- Pack identifies a physical grouping, such as a carton or pallet. In this model, it answers where the allocated contents sit, rather than merely restating an order total.
- Item describes the product and associated quantity. Retain the lot association at a sufficiently detailed level to distinguish the contents within each physical grouping.
Connect the levels without losing allocations
For an illustrative application design, shipment_id identifies the parent movement, and handling_unit_id identifies a physical grouping belonging to it. Each shipment_line_id identifies a shipped-content allocation linked to that shipment, its handling_unit_id and the relevant order_line_id. These are illustrative application field names, not prescribed EDI fields. The order relationship and physical containment relationship remain separately identifiable even when displayed as one hierarchy.
Use a proposed line-grain rule: keep product, lot, physical grouping, quantity and unit of measure together for each distinguishable allocation. An order line and a shipped-content line therefore need not have a one-to-one relationship. One ordered product can occupy several handling units or draw from several lots. A single product total would conceal those lot allocations. This distinction is useful when reviewing the output of batch picking.
Reconcile quantities on an explicit basis
Check totals across shipped-content lines and handling units only after units and any conversion basis are explicit. Cases and individual units are not directly additive; document the applicable pack size before comparing them. Sum each allocation once rather than adding parent totals to their children. This gives packing list verification a defined comparison basis: requested quantities, allocated contents and physical groupings can be compared without discarding lot detail.
03Agree the partner mapping and physical-label connection
Use a partner-mapping worksheet as an exchange agreement. These are proposed design questions, not a regulatory review list.
| Topic | Question to settle |
|---|---|
| Identifier meaning | What does each product, location and shipment reference identify? |
| Field ownership | Who maintains each value and approves changes? |
| Quantity units | Are quantities cases, individual units or mass? Which conversions apply? |
| Mixed lots | Can one physical handling unit contain multiple lots? How are allocations distinguished? |
| Handling-unit relationships | Can one lot appear in several handling units? How are parent–child units linked? |
| Transmission timing | Which shipment event triggers the notice, and what happens if dispatch changes? |
| Correction handling | How does a replacement identify the earlier notice and communicate changed values? |
Keep partner product and location references separate from internal product_id and location_id values. Document each cross-reference and its partner context; matching text alone does not establish matching identity.
For an illustrative physical-label connection, make the scanned label value resolve to a handling_unit_id, then to that shipment’s item-and-lot allocations. Test both lot questions above against this lookup. This connects the physical pack to bulk-to-pack traceability without prescribing label syntax or conformance rules.
Assign each mapping a version and retain that version’s association with every transmission. When changing a representation—such as an external product code or quantity format—test that it still resolves to the same underlying product, lot and quantity. Keep earlier versions interpretable rather than silently reinterpreting past notices.
04ASN and FSMA 204: reference records, lot links and scope
| Jurisdiction and product scope | Authority type | Supported connection to ASN data | Further scope check |
|---|---|---|---|
| FTL foods for U.S. consumption; domestic and foreign firms | FDA scope explanation; binding requirements in Subpart S | An advance shipping notice is an example of a reference document under Subpart S. | Check the food, activity and applicable exemptions. |
| Other product categories or jurisdictions | Applicable product and jurisdiction-specific requirements | No extension of this food-traceability mapping by analogy. | Review the applicable requirements separately. |
FDA's Food Traceability Rule overview discusses persons who manufacture, process, pack or hold foods on the Food Traceability List (FTL). Its scope explanation covers domestic and foreign firms producing food for U.S. consumption. Use that scope to frame the FSMA 204 assessment, rather than treating every food shipment as equivalent.
A reference document, not a complete shipping checklist
21 CFR 1.1310, definition of Reference document includes advance shipping notices among its examples. A reference document may contain some or all of the key data elements (KDEs) for a critical tracking event. This provides a specific connection between the ASN concept and traceability records; it does not establish EDI 856 as a mandated format.
The shipping obligation itself is in 21 CFR 1.1340. Paragraph (a) says that “For each traceability lot of a food on the Food Traceability List you ship, you must maintain records containing the following information and linking this information to the traceability lot”: the traceability lot code; the quantity and unit of measure; the product description; the location description for the immediate subsequent recipient (other than a transporter); the location description for the shipping location; the ship date; the location description for the traceability lot code source, or the traceability lot code source reference; and the reference document type and number. Paragraph (b) splits keep from provide: “You must provide (in electronic, paper, or other written form) the information in paragraphs (a)(1) through (7) of this section to the immediate subsequent recipient (other than a transporter) of each traceability lot that you ship.” The reference document type and number in (a)(8) is therefore kept but not on the list that must be passed on. Paragraph (c) limits scope: the section “does not apply to the shipment of a food that occurs before the food is initially packed (if the food is a raw agricultural commodity not obtained from a fishing vessel).”
| §1.1340(a) element | Keep | Provide to recipient | Where an ASN can carry it (proposed, non-exhaustive) |
|---|---|---|---|
| (1) Traceability lot code | Yes | Yes | Item-level lot attribute on each shipped-content line |
| (2) Quantity and unit of measure | Yes | Yes | Shipped quantity with explicit unit per lot line |
| (3) Product description | Yes | Yes | Item description or a mapped product reference resolvable to one |
| (4) Recipient location description | Yes | Yes | Ship-to party and address at shipment level |
| (5) Ship-from location description | Yes | Yes | Ship-from party and address at shipment level |
| (6) Ship date | Yes | Yes | Shipment date |
| (7) Lot code source location or reference | Yes | Yes | Lot-level party/location reference agreed with the partner |
| (8) Reference document type and number | Yes | Not required by (b) | The ASN's own document number, if the ASN is the reference document |
Preserve the connection to the traceability lot
FDA's Traceability Lot Code explanation describes the TLC as identifying a traceability lot uniquely within the assigning firm's records. FDA also explains that all KDEs, including the TLC, must link to the relevant traceability lot.
As a proposed operational design, map each relevant ASN value to its source record and lot association. Preserve the assigning-firm context rather than treating a code string as globally unique. For each mapped value, identify whether the notice carries it directly or whether it remains in a linked record. Review those links alongside the shipment's lot pedigree; this is a design approach, not an additional regulatory field list.
21 CFR 1.1315(a) requires persons subject to the subpart to establish and maintain a traceability plan. Keep the operational ASN mapping review distinct from the plan's legally required contents.
Timing: FDA's Compliance Date section states that FDA proposed extending the compliance date by 30 months to July 20, 2028. It separately reports congressional direction not to enforce the rule before that date and FDA's intention to comply. The proposal is not itself a final amendment; keep that distinction when reviewing the FSMA 204 proposed extension.
05DSCSA transaction information: a separate scope check
For a DSCSA-related exchange, check the current DSCSA text and FDA's DSCSA overview for applicable product, transaction and information scope. Use the DSCSA glossary for related terminology.
Keep two review questions separate: does the ASN represent the shipment contents, and does the proposed exchange address the applicable transaction-information requirements? Do not declare an ASN sufficient merely because it contains a product identifier, quantity or lot value. Do not carry the food-traceability mapping above into this review.
Use the following worksheet as an implementation aid, not a statutory field list. Create one row for each requirement identified through the scope review.
| Applicable requirement | Authoritative reference | Source business record | Candidate exchange field | Authorised review outcome |
|---|---|---|---|---|
| Requirement under review | Exact provision or guidance passage | Record and record identifier | Proposed field and meaning | Decision, rationale and reviewer |
Ask reviewers whether each proposed data element represents the intended business fact and remains connected to its source record. An identically named field is not a substitute for reviewing its meaning. Record unresolved differences rather than treating matching labels as acceptance evidence. This source-to-field check supports data integrity by design; the authorised reviewer records the mapping decision.
06Follow the notice from shipment preparation to receipt
Use this illustrative ASN lifecycle to connect each operational step with a retrievable evidence output. It is a proposed workflow, not a regulation-mandated sequence.
| Stage | Evidence output |
|---|---|
| Agree the partner mapping | Mapping version identifying the agreed exchange rules; link it to the configuration specification. |
| Assemble shipment facts | Shipment snapshot containing the facts selected for this particular notice version. |
| Reconcile physical allocations | Quantity reconciliation comparing allocated items, lots and quantities with the physical contents, using stated units. |
| Validate the notice | Validation result identifying the notice version, checks performed and unresolved exceptions. |
| Transmit an identified version | Transmitted payload reference linking the retained message to its version, destination and transmission event. |
| Review responses | Partner response linked to the transmitted version, with follow-up ownership for any exception. |
| Reconcile the eventual receipt | Receiving discrepancy record comparing reported receipt with the relevant shipment snapshot and documenting differences or agreement. |
Treat the shipment snapshot as the comparison baseline for that notice version. Evaluate later changes against it, record what changed and why, and identify any replacement notice separately. Do not silently rewrite what the recipient previously received.
Suggested ownership: warehouse staff establish physical contents; integration staff handle message processing; authorised business or quality personnel resolve matters within their assigned responsibilities. These are suggested roles, not mandated job titles. Assign an owner to unresolved exceptions so a technical retry does not substitute for a business decision. Approval and disposition remain with authorised people: successful message validation is not product release.
- Agree MappingDefine identifiers, units and partner expectations.
- Assemble contentsCapture shipment lines and physical groupings.
- Reconcile lotsCheck allocations against physical shipment quantities.
- Validate noticeRecord checks against the agreed mapping.
- Transmit VersionPreserve payload reference and transmission identity.
- Review responseRoute exceptions to their authorised owners.
- Reconcile receiptLink receiving observations and discrepancy resolutions.
07Build a shipment-to-lot evidence model
Use six linked entities to separate physical shipment facts from message history. The field names below are proposed database or integration fields—not standard EDI elements or a mandatory regulatory schema. This application-neutral design supports reconciliation and investigation; it does not define regulatory completeness.
| Entity | Illustrative fields |
|---|---|
| Shipment | shipment_id, ship_from_location_id, ship_to_location_id, shipped_at, source_record_id |
| Order allocation | allocation_id, shipment_id, order_id, order_line_id, shipment_line_id, allocated_quantity, uom |
| Handling unit | handling_unit_id, shipment_id, parent_handling_unit_id, label_value |
| Shipment line | shipment_line_id, shipment_id, handling_unit_id, product_id, lot_record_id, quantity, uom, source_record_id |
| Traceability lot | lot_record_id, lot_code, lot_code_assigner_id, source_record_id |
| Exchange record | transmission_id, shipment_id, mapping_version, sent_payload_reference, partner_response_reference, correction_of_transmission_id |
One shipment can link to multiple order allocations and handling units. Each shipment line identifies a product, one lot record, one handling unit, a quantity and its unit. Apply the hierarchy’s line-grain rule above. Use the allocation table to associate order demand with specific shipment lines and quantities, rather than placing several unrelated lot codes in one free-text field.
Keep business identifiers separate from transmission identifiers: shipment_id identifies the movement represented in this model; transmission_id identifies a particular exchange attempt or version. Exchange records identify communication versions without creating another physical shipment. A retry can therefore have a new transmission_id while retaining the same shipment_id and message_version.
Keep source_record_id resolvable to the operational record version used, and mapping_version resolvable to the transformation rules that produced the communication. Together, these links support reconstruction across MES–ERP integration and WMS–TMS integration, rather than relying on today’s source values or mapping.
Use sent_payload_reference to locate the actual transmitted representation, not a newly generated preview. An optional payload_hash can aid comparison with the retained payload; it is not proof of regulatory completeness or correctness. Preserve these references per exchange record so investigators can distinguish the underlying shipment, its source data and what was communicated.
Shipment
Identifies the announced physical movement.
- shipment_id
- ship_from_location_id
- ship_to_location_id
- shipped_at
- source_record_id
Order Allocation
Connects each shipped line to one order line; ordered quantity stays on the order.
- allocation_id
- shipment_id
- order_id
- order_line_id
- shipment_line_id
- allocated_quantity
- uom
Handling Unit
Connects physical groupings and label values.
- handling_unit_id
- shipment_id
- parent_handling_unit_id
- label_value
Shipment Line
Locates each product-and-lot quantity allocation.
- shipment_line_id
- shipment_id
- handling_unit_id
- product_id
- lot_record_id
- quantity
- uom
- source_record_id
Traceability Lot
Links lot identity to its source.
- lot_record_id
- lot_code
- lot_code_assigner_id
- source_record_id
Exchange Record
Preserves transmission identity and review evidence.
- transmission_id
- shipment_id
- mapping_version
- sent_payload_reference
- partner_response_reference
- correction_of_transmission_id
08Three worked cases: mixed lots, split orders and corrections
These hypothetical cases test quantity reconciliation and record relationships, not legal sufficiency. All identifiers are fictional. Each case assumes one product with the stated, fixed units-per-case conversion; cases and individual units are distinct quantities.
Case 1: Mixed lots across two handling units
Assume shipment EX-S1 contains 120 cases at 12 units per case. Lot A contributes 72 cases; lot B contributes 48 cases. The handling-unit allocation is:
| Handling unit | Lot A cases | Lot B cases | Total cases | Total units |
|---|---|---|---|---|
| H1 | 60 | 0 | 60 | 720 |
| H2 | 12 | 48 | 60 | 720 |
| Shipment | 72 | 48 | 120 | 1,440 |
Reconciliation: H1 plus H2 equals 60 + 60 = 120 cases. Lot A equals (60 + 12) × 12 = 864 units; lot B equals 48 × 12 = 576 units. Together, 864 + 576 = 1,440 units.
Control lesson: a shipment-level total of 1,440 units cannot identify which handling unit contains lot B. Preserve each handling-unit-to-lot allocation for later forward genealogy tracing, rather than retaining only the product total.
Case 2: One order, a partial first shipment
Assume order EX-O2 is for 180 cases at 6 units per case, with no cancellation or amendment. Its total is 180 × 6 = 1,080 units. The first shipment, EX-S2, contains 108 cases: 108 × 6 = 648 units. The unshipped balance is 180 − 108 = 72 cases, or 72 × 6 = 432 units.
Reconciliation: 108 + 72 = 180 cases, and 648 + 432 = 1,080 units. Control lesson: announce 648 units for EX-S2; keep the 432-unit order balance separate. Use explicit quantity labels and unit classifications so the order total is not mistaken for the dispatched quantity.
Case 3: Correcting a notice, not adding a shipment
Assume physical shipment EX-S3 contains 48 cases at 10 units per case: 480 units. Original transmission EX-T3-01 incorrectly announces 50 cases, or 500 units. Corrected transmission EX-T3-02 announces 480 units.
Retain both transmission references, identify EX-T3-02 as the correction, and link both to the same shipment_id, EX-S3. Whether the partner expects replacement, cancellation or another correction mechanism belongs in the partner agreement.
Reconciliation: 50 − 48 = 2 cases and 500 − 480 = 20 units of overstatement removed. Control lesson: reconcile the corrected notice to the unchanged 480-unit shipment; do not count the correction as a second physical shipment.
09Integrate transport, validation and business responses
One possible architecture connects four components: an operational shipment system holding shipment identity and content; a partner-specific mapping component translating that content into the agreed exchange; a transport adapter sending it; and a response store retaining returned messages and their interpretation. Treat this as a proposed engineering design, not a product capability. Define component ownership alongside the WMS–TMS integration.
Use three independent status fields, with meanings defined for this implementation:
- Transport outcome: pending, delivered to the agreed endpoint, or failed.
- Message validation: unchecked, passed agreed structural checks, or failed those checks.
- Recipient business review: awaiting review, accepted for processing, or unresolved business issue.
These are local definitions, not meanings assigned to standard acknowledgement transactions. For each response, retain its transmission reference, timestamp and interpreted status meaning. A generic success flag cannot distinguish delivery from validation or business acceptance. Document interpretation rules in the functional specification.
Tie retries to the existing business shipment identity while recording each exchange attempt separately. A retransmission does not, by itself, represent another physical shipment; use the correction-case approach above when content changes.
For recovery, suppose transport succeeds but the recipient reports an unresolved item identifier. Preserve both events: delivery remains successful while business review remains unresolved. Route the identifier mapping issue to its designated owner, retain the resolution, and link any subsequent exchange attempt to the same shipment.
10Common failure modes and proportionate controls
Use this proposed diagnostic checklist to assign targeted investigations. It is neither a ranking of incident frequency nor an agency-mandated review list; responsible roles below are suggested owners.
| Failure mode | Observable evidence | Proposed control | Responsible role |
|---|---|---|---|
| Unknown product cross-reference | Partner identifier has no matching product | Resolve the cross-reference against agreed product records | Master-data owner |
| Lot allocation detached from a shipment line | Allocation references no existing line | Repair the allocation with a documented correction | Shipping records owner |
| Mismatched quantity units | Notice and order use different units | Establish the unit basis before comparing quantities | Order-management owner |
| Label value resolving to the wrong handling unit | Scan retrieves another unit’s record | Investigate the label-to-record link | Warehouse supervisor |
| Missing partner response | No response linked to the notice | Investigate response status before deciding whether to resend | EDI support |
| Receipt quantity differing from the announced quantity | Receiving count differs on the same unit basis | Reconcile the physical discrepancy | Receiving supervisor |
For each exception, record issue_id (unique issue), affected_record_id (record involved), owner (accountable person), decision (action and rationale), resolution_reference (supporting correction or reconciliation), and closed_at (closure time). Closure should identify what was resolved and link the supporting record—not merely show that an alert disappeared. Use an audit trail review workflow to review documented corrections; authorised people decide disposition.
11Implementation and review checklist before live exchange
Use this proposed operational acceptance checklist before live exchange:
- Agree identifier mappings and document quantity units and conversions.
- Test lot allocations and physical label-to-record links, including the resulting lot relationships.
- Record the mapping version and retain an accessible representation of exactly what was transmitted.
- Document response meanings: what each response confirms and what remains unresolved.
- Assign exception owners and escalation routes.
- Record who accepted the mapping and who may approve later changes within the organisation’s authorised responsibilities; preserve those decisions in the audit trail.
Run the three worked cases—mixed lots, split orders and corrections—as acceptance tests. Add an unknown-identifier rejection and a physical receipt discrepancy. Retain expected results, actual results and exception dispositions. Success means correct shipment–order–pack–item–lot relationships and explainable quantity reconciliation, not merely a sent message.
Keep operational acceptance separate from the product- and jurisdiction-specific regulatory review discussed above. This checklist is not a complete FSMA 204, DSCSA or general compliance assessment.
Frequently asked questions
Q.Can one ASN cover several purchase orders going to the same destination?+
Treat this as a trading-partner mapping question: agree whether one ASN may reference multiple purchase orders before combining them. If permitted, preserve each order number and its association with the relevant items, quantities and handling units. A shared delivery address alone is not a sufficient grouping rule. Test a shipment containing the same item on two orders to confirm that receiving allocates quantities correctly. Use packing list verification to reconcile the physical load against those allocations.
Q.How should an ASN be interpreted when the buyer orders cases but the receiver counts individual units?+
Compare quantities only after establishing the item-specific conversion and the unit attached to each quantity. For example, assume an order and ASN both describe 12 cases, with 24 individual units per case: the expected receipt is 288 units. A count of 280 units then indicates an eight-unit difference, not an eight-case difference. Preserve the original case quantity alongside the converted count in the goods receipt note, and investigate mixed pack sizes or partial cases before accepting the comparison.
Q.How should returned goods be linked to the original shipment without confusing the two movements?+
Record the return as a separate movement with its own reference, date, direction and quantity, then link it to the original shipment and affected shipment lines. Preserve the original outbound record rather than changing it to describe the return. For a partial return, identify the particular items, lots and handling units involved; do not imply that the entire shipment came back. Use container status tracking to distinguish returned stock awaiting assessment from stock authorised for further use.
Q.How can receiving staff investigate a shipment when a physical handling-unit label cannot be read?+
Start with independent references: delivery paperwork, carrier reference, supplier, arrival details and any readable carton identifiers. Use these to locate candidate shipment records, then compare physical contents, quantities and lot markings with the ASN. Do not assign a handling-unit identity merely because one expected unit remains unmatched. Document the identification basis and unresolved differences through the receiving discrepancy process. Keep the affected goods distinguishable while an authorised person decides whether the identity is sufficiently established.
Q.What if two suppliers use the same lot-code text?+
Design matching so that identical lot-code text does not, by itself, merge two records. Retain the original code together with the product and the identity of the party that assigned it, where known; also preserve the supplier and shipment references. If one supplier is a distributor, investigate the originating lot identity rather than assuming the distributor created it. In lot pedigree searches, show this context beside the code so staff can distinguish separate lots from repeated deliveries.
Q.What evidence helps investigate an ASN sent to the wrong trading partner?+
Preserve the transmitted message, intended recipient, actual routing destination, transmission time, message identifier and any acknowledgements. Compare the destination against the partner configuration and order used when the message was generated. Separate evidence of technical delivery from evidence that a recipient processed the business content. Use the audit trail to investigate routing changes and manual interventions. Have the responsible team assess the disclosure and coordinate any correction or retransmission, retaining links between the original and corrective messages.
Q.How should a team assess a transaction-information request when its ASN only describes case-level contents?+
Start by identifying the products, transactions and information requested; do not assume case totals answer the request. FDA’s DSCSA overview describes electronic, interoperable tracing of certain prescription drugs at the package level. As an operational assessment, compare the request with the ASN and related records, including serialized unit tracking records where relevant. Document gaps and refer the response to the responsible regulatory team. Case-level contents alone should not be treated as proof that the requested information is complete.
Q.How can an older shipment be reconstructed after the partner mapping has changed?+
Retain the original message alongside its readable interpretation, the mapping version used at the time and the relevant historical item and partner references. Reconstruct the shipment using those historical definitions rather than silently applying today's mapping. Compare the result with dispatch and receipt records, and document any remaining ambiguity. Under change control, test whether mapping revisions alter the interpretation of older messages. Keep a later reprocessing result distinguishable from the record originally used to execute the shipment.
Primary sources
Explore this topic
EDI 856 sits inside this topic cluster in our glossary. Every neighbour is one click away.
Want to see how EDI 856 could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
