Direct answer: A controlled 3PL ASN receiving handoff requires more than sending shipment data. Freeze the physical load and active routing guide, submit the notice through the approved channel, capture technical and business acknowledgements, and block dispatch when the accepted version differs from the cargo. After delivery, reconcile shipped, delivered, received, quarantined and usable quantities before closing the inbound record.

This guide is for brands, importers and operations teams sending inventory into a US or Canadian third-party logistics warehouse. It does not prescribe an EDI map, appointment rule or chargeback. The 3PL agreement, routing guide and account implementation specification remain controlling.

Reviewed: 19 October 2026. X12 and GS1 US originals were reopened. Recheck current account documents after an operational change.

Key facts for a 3PL ASN receiving handoff

State Evidence to retain What it does not prove
Prepared Frozen order, item, carton and handling-unit ledger That the receiver has seen the notice
Transmitted Timestamp, control number or portal submission record That syntax or business content was accepted
Accepted Technical and business acknowledgement tied to a version That later load changes were approved
Delivered Appointment and carrier handoff evidence That every unit was identified or made usable
Closed Warehouse receipt and resolved discrepancy record Anything beyond the completion state in the agreement

X12 describes the 856 Ship Notice/Manifest as a transaction that can list shipment contents and related order, product, packaging, marking, carrier and configuration information at several levels. That capability does not create one universal customer map. The receiver still determines which fields, identifiers, hierarchy, code values and acknowledgements apply to the account.

Freeze the controlling documents and physical hierarchy

Start with the current service agreement, routing guide, implementation specification, portal instructions and facility addendum. Record each document’s title, version, effective date, source and confirming 3PL contact.

Build one hierarchy from inbound order or purchase order to shipment, handling unit, carton, item and quantity. Add lot, batch, serial, expiry or country-of-origin attributes only when the product and receiver require them. A flat SKU total may balance while individual cartons remain impossible to identify at the dock.

The origin team should use the carton-to-shipment reconciliation workflow before building the final notice. Finished cartons, not purchase-order estimates, should supply identifiers, quantities, dimensions and weight. The origin release gate should physically isolate blocked cartons so they cannot enter an accepted shipment by mistake.

Use receiver-approved party and handling-unit identifiers

If the receiver requires a Serial Shipping Container Code, follow its implementation instructions and licensing rules. GS1 US explains the SSCC as an identifier for a logistic unit. That definition does not make SSCC mandatory for every pallet, authorize a supplier to invent a number or allow an identifier to be reused while the first unit remains active.

For consolidated inventory, preserve factory and order traceability. The multi-supplier intake board assigns cutoffs and exceptions before one notice is created. Combining cartons must not erase source ownership or destination allocation.

Submit the ASN and capture each acknowledgement

Transmit through the approved EDI connection, API, portal or structured file route. Save the outgoing payload or export, transmission time, control number and integration environment. Then separate three possible responses: transport receipt, syntax acknowledgement and business acknowledgement. A file can reach the channel yet fail syntax; it can pass syntax yet fail because the order is closed, the destination is unknown or quantities exceed a rule.

X12’s supply-chain transaction flow places the 856 in the delivery process that advises a buyer about products being shipped against one or more purchase orders. It also shows that order, notice, invoice and payment are distinct records. A valid notice does not reopen a closed order or replace a commercial document.

Run the five-point version-difference test

Immediately before dispatch, compare the accepted notice with the physical load and the current documents. Review five groups:

  1. Order: Is the inbound or purchase order still open for the destination and quantities?
  2. Identity: Do shipment, pallet, carton and item identifiers match the labels on the cargo?
  3. Quantity: Do item, carton and handling-unit totals reconcile without unexplained overage or shortage?
  4. Movement: Do carrier, route, appointment and expected-arrival references remain current?
  5. Version: Can the team identify the exact notice the receiver accepted and every later change?

Place a release hold on unknown orders, duplicate handling-unit identifiers, rejected notices, unreadable labels, unresolved quantity differences, changed destinations or missing required appointments. A transport cutoff is not a reason to ship data the receiver cannot use.

Control amendments after acceptance

Late changes happen when a supplier shorts a product, a carton fails inspection, pallets are rebuilt, the carrier changes or an appointment moves. Record the original value, revised value, physical reason, approver, affected files and required receiver response. Use the 3PL’s replace, cancel or amendment method; do not assume a second ASN silently supersedes the first.

Use a pre-dispatch release checklist

  • Active routing and implementation guides are identified by version and effective date.
  • The receiver’s inbound order is open and destination identity is confirmed.
  • Item, carton, handling-unit and total quantities match the finished cargo.
  • Labels use approved identifiers, placement and scan rules.
  • The notice was submitted before the current cutoff through the approved channel.
  • Technical and business acknowledgements are stored with the submitted version.
  • Every post-submission change has a documented receiver response.
  • Appointment, carrier and arrival references match the dispatch plan.
  • One named release authority can hold or release the load.
  • The receiving owner knows the evidence and state that will close the file.

Reconcile delivery, receipt and usable inventory

Track shipped, delivered, received, quarantined and usable quantities separately. Proof of delivery can show the carrier handoff, yet it cannot show that every carton was identified, counted, inspected and allocated. The warehouse receipt may also precede quality release or inventory availability.

Open a receiving exception for shortage, overage, damage, unidentified stock, lot or expiry conflict, label failure, wrong destination or quarantine. Link the affected order, ASN version, handling unit and quantity to timestamps, photos when appropriate, receiver evidence, origin evidence, owner and next decision. Keep financial claims separate from the inventory-correction record so a credit discussion cannot hide unresolved stock.

Close the file only when the completion signal named in the service agreement is reached and discrepancies are assigned or resolved. For some accounts that signal may be receipt posted; for others it may be inventory available. Record the actual cycle time without turning one shipment into a universal performance promise.

Limitations and shipment-specific review

This guide cannot determine the correct EDI version, segment map, barcode symbology, identifier license, label layout, notice deadline, appointment rule, pallet standard, receiving tolerance, chargeback or liability allocation for a particular account. These conclusions require the current 3PL documents and, where applicable, the receiver, integration provider or GS1 member organization.

For a shipment-specific plan, provide origin, destination warehouse, order references, products, cartons, pallets, dimensions, gross weight, cargo-ready date, required receipt date, routing-guide version, ASN channel and unresolved exceptions through the North America inbound plan form. Do not include passwords or unnecessary personal data.

Frequently asked questions

What information belongs in a 3PL ASN?

Use the receiver’s current implementation guide. Common data groups include sender and destination, purchase-order or transfer reference, shipment and carrier references, expected arrival, handling-unit hierarchy, product identifiers, quantities, and lot or expiry attributes when applicable.

Is a sent ASN the same as an accepted ASN?

No. A transmission receipt may show only that a file reached a channel. Syntax acceptance can differ from business acceptance, and neither proves that the physical load matches. Preserve each acknowledgement and the accepted version.

When should a 3PL ASN be corrected?

Correct it when a material field changes after submission, including order status, quantities, handling units, carrier, destination or expected arrival. Use the approved method and preserve the superseded version.

Is a packing list the same as an ASN?

No. A packing list is a shipment document; an ASN is structured advance data. They should reconcile, but one does not satisfy the other’s format, timing, identifier or acknowledgement requirements.

Does proof of delivery close a 3PL inbound?

Not by itself. It records a carrier handoff. The warehouse may later post shortage, damage, quarantine or unidentified stock. Close the file only at the agreed receiving completion state.

Should every pallet use an SSCC?

Only when the receiver requires or accepts it and the shipper is authorized to create compliant identifiers. Confirm generation, label, uniqueness and reuse rules before printing.

Official sources and change log

Source note: All four standards sources returned HTTP 200 on 19 October 2026. The HTTP response was checked today; receiver account documents remain the controlling source for account-specific changes. Receiver account documents were not public and must be checked for the shipment.

Change log, 19 October 2026: Added the acknowledgement-state matrix, five-point version-difference test, explicit dispatch holds, amendment evidence, receiving-close criteria and current source mappings. The page remains a 3PL ASN receiving handoff guide and does not expand into broad freight-forwarding intent.