EDI 856 – Advance Ship Notice (ASN) (X12 / V4010)

What is an EDI 856 (ASN)?

The EDI 856 Advance Ship Notice (ASN) is an electronic document that communicates detailed shipment information—including packaging, carrier, and item-level data—before goods arrive. It enables automated receiving, cross-docking, and inventory visibility across supply chain systems.
 

Transaction Identity Block

What is the EDI 856 used for?

EDI 856 is used to notify buyers of incoming shipments in advance. It provides hierarchical shipment data (shipment, order, pack, item), enabling warehouses to prepare labor, validate deliveries, and reduce receiving errors.

Who Uses the EDI 856?

Who sends the EDI 856?

Suppliers, manufacturers, and distribution centers send EDI 856 messages to retailers, warehouses, and logistics partners to communicate shipment details prior to delivery.

When is an ASN sent?

An EDI 856 ASN is sent after goods are shipped but before they arrive, ensuring receiving systems can process shipments efficiently and accurately.

When Is the EDI 856 Required?

EDI 856 is required:

• Before shipment arrival (critical timing requirement)  
• For retailer compliance programs (e.g., Walmart, Target)
• For cross-docking and automated receiving workflows 

Timing is essential; the ASN must arrive ahead of the physical shipment. 

Is the EDI 856 Mandated Under Regulation?

EDI 856 is not universally mandated but is:

• Required by major retailers
• Required for certain regulated industries (e.g., pharmaceuticals under DSCSA)
• Required in import/export compliance scenarios (e.g., ISF 10+2) 

Why do retailers require EDI 856 ASN?

Retailers require EDI 856 ASNs to automate receiving, enable cross-docking, and ensure shipments match purchase orders. ASN compliance reduces manual labor, improves inventory accuracy, and supports high-volume distribution operations

How do companies ensure ASN compliance?

Organizations ensure ASN compliance by validating shipment data against trading partner requirements, enforcing SSCC labeling standards, and monitoring ASN timing and accuracy through automated EDI platforms and integration systems.

What Standards and Frameworks Govern the EDI 856?

The EDI 856 Advance Ship Notice is governed by ANSI X12 standards (commonly version 4010) which define the structure, segments, and validation rules of the transaction. Industry adoption frequently incorporates GS1 standards, including SSCC (Serial Shipping Container Code) labeling for carton and pallet identification. Industry-specific requirements may also apply, including DSCSA in healthcare and retailer-specific routing guides. 

Regulatory and operational frameworks influence ASN implementation across industries. Healthcare supply chains align with DSCSA traceability requirements, while retail and grocery sectors enforce routing guides and compliance programs that mandate ASN accuracy, timing, and labeling standards. These frameworks ensure interoperability, traceability, and consistency across multi-enterprise supply chain networks.

How Does the EDI 856 Work in the Business Workflow?

The EDI 856 Advance Ship Notice (ASN) functions as the execution bridge between order fulfillment and physical receipt. It communicates shipment structure, contents, and logistics details before goods arrive, enabling downstream systems to prepare for receiving, validation, and inventory updates.

Upstream Transactions

Downstream Transactions

End-to-End Workflow Example

A typical EDI 856 workflow follows a structured order-to-cash lifecycle:

1. A buyer transmits an EDI 850 Purchase Order to the supplier
2. The supplier responds with an EDI 855 to confirm or modify the order
3. The supplier fulfills the order and prepares shipment
4. An EDI 856 ASN is generated and transmitted prior to shipment arrival
5. The receiving organization uses ASN data to prepare for inbound processing
6. Goods arrive and are validated against the ASN structure (SOPI)
7. The supplier issues an EDI 810 Invoice for payment
8. Optional EDI 214 messages provide shipment status during transit

Industry-Specific Workflow Variations

Business-Level Workflow (ASN Execution Perspective)

At the operational level, the EDI 856 enables synchronized execution across systems:

• Pre-receipt planning: Warehouse systems allocate dock doors, labor, and storage locations
• Shipment validation: ASN data is matched against purchase orders and expected quantities
• Automated receiving: Barcode scanning (SSCC/LPN) validates cartons and updates inventory
• Exception handling: Discrepancies trigger alerts for missing, damaged, or incorrect items
• Inventory synchronization: ERP and WMS systems update stock positions in real time

How Does the EDI 856 Work in order fulfillment?

The EDI 856 Advance Ship Notice connects order fulfillment to receiving by providing detailed shipment information before goods arrive. It enables automated receiving, validates shipments against purchase orders, and supports real-time inventory updates across ERP and warehouse systems.

Cross-Standard Canonical Mapping

What is the difference between EDI 856 and 810?

EDI 856 provides shipment details before delivery, while EDI 810 is the invoice sent after shipment. Together, they support the order-to-cash process by separating logistics visibility from financial settlement.

What is the difference between EDI 856 and 214?

EDI 856 describes planned shipment contents and structure, while EDI 214 provides real-time shipment status updates during transit. Together, they provide both pre-shipment visibility and in-transit tracking.

EDI 856 vs Associated Transactions Comparison

How does PartnerLinQ use the EDI 856?

PartnerLinQ transforms the EDI 856 from a static document into an execution-controlled supply chain event. The platform synchronizes ASN data across ERP, WMS, and TMS environments while enforcing trading partner compliance and routing guide adherence.

PartnerLinQ manages hierarchical shipment structures, including carton IDs, pallet IDs, SSCC labels, and SOPI relationships, ensuring that shipment data reflects the physical configuration of goods. This alignment enables automated receiving, cross-docking, and inventory reconciliation without manual intervention.

Execution-level visibility is applied at the transaction level. Each ASN is monitored for completeness, timeliness, and accuracy, enabling proactive exception management when discrepancies occur, such as missing SSCCs, invalid hierarchies, or late transmissions.

PartnerLinQ supports partner-by-partner onboarding and multi-network connectivity, allowing organizations to standardize ASN processes across diverse trading partner ecosystems. A canonical data model normalizes ASN structures across EDI and API interactions, reducing mapping complexity and enabling downstream analytics, automation, and decision intelligence.

PartnerLinQ enables scalable ASN execution through integrated B2B supplier integration and transportation integration workflows, supporting partner onboarding, SSCC compliance, and real-time shipment visibility across multi-enterprise networks.

Explore how these capabilities are delivered:

• PartnerLinQ Integration Solutions
• B2B Supplier Integration
• B2B Transportation Integration

Understand how these capabilities serve your needs:

• Unlocking the Power of Multi-Enterprise Supply Chain Business Networks with PartnerLinQ
• How EDI Logistics is Transforming Supply Chain Operations

Learn MORE about related transactions:

• EDI 850 - Purchase Order
• EDI 214 - Transportation Carrier Shipment Status Message
• Resources for EDI Professionals

Where Is the EDI 856 Used?

• Retail & Apparel - Store replenishment
• Grocery - Distribution centers
• Manufacturing - Supplier coordination
• Logistics - Shipment visibility
• Healthcare - Track-and-trace compliance

What Is the Purpose, Key Features, and Business Use Cases of the EDI 856?

Operational Purpose

Provide advance shipment visibility for receiving optimization. 

Key Features

• Hierarchical structure (SOPI)
• SSCC/LPN tracking
• Carrier and routing detail
• Item-level granularity 

Business Use Cases

• Cross-docking - Direct shipment to outbound
• Inventory pre-allocation - System updates before receipt
• Compliance labeling - Retail routing guides
• Traceability - Batch, lot, serial tracking

What Information Is Required in the EDI 856?

The EDI 856 Advance Ship Notice (ASN) requires a structured set of shipment identifiers, purchase order references, hierarchical structure (SOPI), packaging details (SSCC), carrier information, item-level data elements & quantities, and shipment dates that collectively describe the contents and configuration of a shipment prior to delivery. The information must align with trading partner requirements and reflect the physical structure of the shipment using hierarchical relationships. Data that enables automated receiving, ensures accurate inventory updates, compliant with trading partner requirements.

Quick Segment Reference

Required Segments

Optional Segments

Required Identifiers

Required Dates

Required Logistics and Transportation Data

Required Product and Quantity Data

Required Packaging and Hierarchical Data

The EDI 856 must reflect how goods are physically packed. SSCC values in the MAN segment must align with physical labels applied to cartons or pallets.

Service-Level or Line-Level Detail

The EDI 856 supports item-level granularity This enables precise receiving, validation, and inventory updates.

• Each item is identified individually (LIN)
• Quantities are defined per item (SN1)
• Packaging relationships are preserved through HL loops 

Summary Table of Key Segments

Data Accuracy and Validation Requirements

The effectiveness of the EDI 856 depends on strict data integrity:

• Shipment ID (BSN02) must be unique
• SSCC values must match physical labels
• HL hierarchy must be structurally valid
• Quantities must align with purchase order expectations
• Dates must reflect actual shipment timing 

Errors in these elements can result in rejected ASNs, receiving delays, or compliance penalties.

What Status and Reason Codes Are Used with the EDI 856?

The EDI 856 Advance Ship Notice (ASN) uses BSN01 status codes such as 00 (Original), 01 (Cancel), and 05 (Replace) to indicate the purpose, condition, and handling of the shipment notification, in short, to define how a shipment notice should be processed.  These codes are primarily communicated through the BSN (Beginning Segment for Ship Notice) and supporting segments such as REF and N9, segments to provide shipment references and exception detail enabling trading partners to interpret whether an ASN is original, updated, canceled, or replaced.

Status Codes (BSN01 – Transaction Set Purpose Code)

The BSN01 element defines the status or intent of the ASN and determines how the receiving system should process the transaction. The EDI 856 does not define a universally adopted shipment status element beyond BSN01. Additional context is typically conveyed through REF and N9 segments.

*“Change by refresh” (Cancel + Replace) is recommended. 

What is “Change by Refresh” in EDI 856?

Change by refresh is a best-practice method for updating an EDI 856 Advance Ship Notice (ASN) by first canceling the original transaction and then sending a corrected replacement. This approach ensures that receiving systems remove outdated shipment data before processing the updated ASN, preventing duplicates and data conflicts.

Why Change by Refresh Is Used

Change by refresh is preferred because most receiving systems:

• Do not reliably support partial updates
• Require a clean removal of prior shipment data
• Enforce strict validation on SSCC, PO, and hierarchy

By canceling first, the system avoids:

• Duplicate ASN errors
• Conflicting SSCC (carton) identifiers
• Inventory mismatches

Status Code Processing Logic

Receiving systems typically apply the following logic when Change by Refresh is used

1. BSN01 = 00 (Original) → Create shipment record
2. BSN01 = 01 (Cancel) → Remove existing record
3. BSN01 = 05 (Replace) → Overwrite existing record
4. Validate SSCC, PO, and hierarchy
5. Trigger receiving or exception workflows

Reason Codes (REF and N9 Segments)

EDI 856 does not define a universal set of reason codes; however, trading partners commonly use REF and N9 segments to communicate exception details and contextual information.

Common Exception and Reason Scenarios

Reason codes or references may indicate:

Industry-Specific Code Usage

Different industries extend ASN status and reason usage:

What are the Benefits of the 856?

The EDI 856 Advance Ship Notice (ASN) delivers operational, financial, and compliance benefits by providing advance visibility into shipment contents and structure. It enables organizations to align physical logistics with digital execution, improving receiving efficiency, inventory accuracy, and supply chain coordination.

Operational Benefits

EDI 856 improves execution across warehouse and distribution operations.

Financial Benefits

EDI 856 accelerates financial workflows, reduces cost inefficiencies, and reduced Days Sales Outstanding (DSO).

What is Days Sales Outstanding (DSO)?

Days Sales Outstanding (DSO) measures the average number of days it takes a company to collect payment after a sale has been made.

DSO Formula

DSO = (Accounts Receivable ÷ Total Credit Sales) × Number of Days

What Does DSO Tell You?

DSO tells you how long you are waiting for payment following a sale

• Low DSO → Faster collections, strong cash flow, lower interest costs (P*I*T)
• High DSO → Slow collections, potential cash flow issues, higher interest costs

Compliance Benefits

EDI 856 supports trading partner and regulatory requirements in DSCSA, GUDID, the FSMA Final Rule on Requirements for Additional Traceability Records, even U.S. Customs and Border Protection (CBP) Importer Security Filings (ISF - known as "10+2”).

Supply Chain Coordination Benefits

EDI 856 improves coordination across chain participants particularly when it comes to Retailer KPIs like supplier assessment, performance, ratings, and vendor score carding.

Exception Management Benefits

EDI 856 enables proactive identification of inventory and OOS (out of stock) risks and provides insight into the resolution of those issues downstream by identifying delivery issues and potential bottlenecks.

Can EDI 856 be automated?

Yes, EDI 856 can be fully automated using EDI platforms that integrate with ERP and WMS systems. Automation enables real-time shipment visibility, reduces manual errors, and ensures compliance with trading partner requirements.

What are the Benefits of Automating the EDI 856?

• Real-time ERP/WMS updates
• Automated dock scheduling
• Reduced labor costs
• Enhanced visibility and exception management 

Automation and Digital Transformation Benefits

EDI 856 plays a critical role in modernizing supply chain execution.

EDI 856 Technical Structure, Format, and Versions

The EDI 856 Advance Ship Notice (ASN) is a hierarchically structured transaction designed to represent the physical configuration of a shipment. Its technical design enables trading partners to exchange detailed shipment data in a standardized, machine-readable format that supports automation, validation, and interoperability across supply chain systems.

Structural Characteristics

The EDI 856 supports a flexible and scalable structure:

• Nested loops: Each HL segment can contain multiple child levels
• Multi-order support: One ASN can represent multiple purchase orders
• Multi-pack representation: Multiple cartons or pallets per order
• Item-level granularity: Detailed product identification and quantities 

This flexibility allows the ASN to scale from simple shipments to highly complex, multi-tiered logistics scenarios.

Hierarchical Loop Structure

The EDI 856 is built on the HL (Hierarchical Level) segment, which organizes shipment data into parent-child relationships that mirror how goods are physically packed.

The most common structure is SOPI (Shipment → Order → Pack → Item), though variations such as SOTPI (including pallet level) are widely used depending on industry requirements.

What is the structure of an EDI 856 ASN?

The EDI 856 typically uses a structure known as SOPI (Shipment, Order, Pack, Item). This structure mirrors how goods are physically packed, enabling systems to track shipments at multiple levels, from entire shipments down to individual items.

This structure allows receiving systems to process shipments exactly as they are packed, improving accuracy and enabling selective handling (e.g., cross-docking or recall isolation).

File Format and Delimiters

Using the following Production Delimiters on all EDI transmissions sent to Vendors, Carriers, Trading and Solution partners will enable consistent EDI parsing across trading partners:

• Segment Separator – hex 15 (NAK) or hex 7E (~)
• Element separator – hex 7C (|) or hex 2A (*)
• Sub-element Separator – hex 3E (>)

What are the Limitations of the 856?

The EDI 856 Advance Ship Notice is highly effective but has several limitations that organizations must manage. 

1. Variations in trading partner implementation guides often require custom mappings, increasing integration effort and maintenance overhead. T
2. Data accuracy is essential, since errors in SSCC labeling, quantities, or hierarchy can propagate downstream into inventory discrepancies and financial disputes.
3. Timing sensitivity is critical, as late or inaccurate ASNs can lead to receiving delays, chargebacks, or rejected shipments.
4. The complexities of the SOPI structure can be difficult to implement and maintain, especially with complex shipments.
5. The 856 is also batch-oriented rather than real-time, limiting responsiveness compared to API-based models. 

Version Standards

EDI 856 is defined by ANSI X12 standards, with multiple versions in used despite newer versions.

Version Differences

ANSI X12 v4010 remains dominant due to widespread trading partner compatibility. Companion guides often define implementation-specific requirements, common X12 EDI versions include:

• X12 4010 and 5010 widely adopted across industries
• Companion guides define implementation specifics
• Industry-specific subsets (UCS, GS1)
• V4010 most common

Version Constraints

Companion guides define implementation practices and there are differences across trading partner guides.

Industry-Specific Implementation Variations

Different industries apply the EDI 856 structure in distinct ways:

These variations are typically defined in trading partner implementation guides.

Transmission and Integration

EDI 856 transactions are transmitted through standardized communication protocols:

• AS2         Secure, real-time internet transmission
• VAN        Managed EDI network services
• SFTP      Secure file transfer

Integration occurs across:

• ERP systems (order management)
• WMS systems (warehouse operations)
• TMS systems (transportation execution) 

Operational Dependencies and Timing

The effectiveness of the EDI 856 depends on timing and data accuracy:

• ASN must be transmitted before physical delivery
• Late ASN = receiving failures
• Shipment identifiers (BSN02) must be unique and consistent
• SSCC labels must match transmitted MAN segment values
• Hierarchical relationships (HL loops) must be structurally valid

Failure in any of these areas can result in receiving delays, compliance violations, or rejected shipments.

Are Implementation Guidelines and Sample Files Available for the X12 EDI 856?

Yes. PartnerLinQ provides sample transactions and implementation guides. EDI 856 implementation guides illustrate both inbound and outbound flows, segment layouts, and valid data examples and support testing and partner onboarding. 

Companion Guides

Trading partners frequently publish X12 EDI 856 implementation guidelines defining segment usage and validation rules. Customized specification documents for use in on boarding and technical development are available through PartnerLinQ Support and Guideline Management.

What does an EDI 856 example look like?

An EDI 856 example includes a BSN shipment header, HL hierarchical loops (Shipment, Order, Pack, Item), carrier details, SSCC carton identifiers, and item-level quantities. It provides advance shipment visibility and enables automated receiving before goods arrive.

EDI 856 Example File (X12 Sample)

ISA*00*          *00*          *ZZ*SENDERID      *ZZ*RECEIVERID    *240101*1200*U*00401*000000001*0*T*:~
GS*SH*SENDERID*RECEIVERID*20240101*1200*1*X*004010~
ST*856*0001~
BSN*00*SHIP12345*20240101*1200*0001~
HL*1**S~
TD1*CTN*10****G*500*LB~
TD5**2*UPSN*U*UPS~
REF*BM*BOL123456~
DTM*011*20240101~
N1*SF*Supplier Company*92*10001~
N1*ST*Buyer Distribution Center*92*20002~
HL*2*1*O~
PRF*PO123456~
HL*3*2*P~
MAN*GM*000123456789012345~
HL*4*3*I~
LIN*1*UP*012345678905~
SN1*1*100*EA~
CTT*4~
SE*16*0001~
GE*1*1~
IEA*1*000000001~
  

Annotated EDI 856 Example

Hierarchical Structure (SOPI Example)

This SOPI structure mirrors how goods are physically packed.

Key Characteristics of an EDI 856 Example

• Includes shipment-level data (carrier, dates, references)
• Links to purchase orders (PRF)
• Identifies cartons/pallets (MAN with SSCC)
• Provides item-level detail (LIN/SN1)
• Uses HL loops to define relationships 

What are the most common EDI 856 mistakes?

Common EDI 856 errors include missing hierarchical loops (HL), incorrect SSCC labels, mismatched purchase order numbers, and late ASN transmission. These issues can cause receiving delays, compliance penalties, and rejected shipments.

What are the more common EDI errors and rejection scenarios?

What are the Basic Questions for EDI Integration with the 856?

1. Are there Samples and Specs available?
2. What is the general direction of the transaction?
3. Are inbound or outbound orders required?
4. Are AS2, VAN, or SFTP connections used?
5. Are more than one trading partner exchanging the [Transaction ID]?
6. Are there other interested parties?
7. What trading partner requirements apply?
8. What version is supported?
9. What other transactions might these interested parties be a party to?
10. What response to the [Transaction ID] is expected or sent?
11. Is a response to [Transaction ID] a timed event?  Are notifications involved/needed?
12. What system generates the response?
13. What response time is contractually required?
14. Are there samples and specs of the response transaction available?
15. Are change orders supported?
16. What validation rules apply?
17. How are changes to the [Transaction ID] business message managed today?
18. Is there automation? (an internal systems trigger) or are [Transaction ID] business message transactions triggered manually?
19. How is automation managed (manual vs. system-triggered)?
20. Are responses and changes automatically triggered? (an internal systems trigger)
21. Are alerting systems configured for missed response deadlines?
22. Do transactions require human intervention?
23. What systems generate or consume the transaction?
24. How are changes to the business message managed today?
25. How are one-time addresses handled in ERP?
26. Are SKU or UPC identifiers used?
27. What identifiers are required (SKU, UPC, GTIN)?
28. What testing process is required?
29. What validation rules must be applied?

What are the Best Practices for using the 856?

What Transactions are associated with the 856?

People Also Ask

What is the difference between ASN and EDI 856?

ASN (Advance Ship Notice) is the business concept, while EDI 856 is the standardized electronic format used to transmit it. In practice, the terms are often used interchangeably, but EDI 856 specifically refers to the ANSI X12 transaction set.

What is ASN in warehouse operations?

In warehouse operations, an ASN (Advance Ship Notice) provides advance visibility into incoming shipments, allowing facilities to schedule labor, assign dock doors, and pre-receive inventory before goods physically arrive.

What is the difference between ASN and packing list?

An ASN is an electronic document sent in advance of shipment, while a packing list is a physical document included with the shipment. The ASN enables automated receiving, while the packing list supports manual verification.

What is ASN in logistics?

In logistics, an ASN is used to communicate shipment details between trading partners, improving coordination, tracking, and receiving efficiency across transportation and distribution networks. 

When should an EDI 856 be sent?

An EDI 856 should be sent immediately after shipment departure but before goods arrive at the destination. Timing is critical late ASNs can cause receiving delays, compliance violations, and rejected shipments.

What information is included in an EDI 856?

An EDI 856 includes shipment identifiers, purchase order references, carrier details, packaging hierarchy (shipment, order, pack, item), item quantities, SSCC labels, and delivery dates. This structured data enables accurate tracking and automated receiving processes.

What standards support EDI 856 compliance?

EDI 856 compliance is supported by ANSI X12 standards, GS1 labeling requirements such as SSCC, and industry-specific frameworks including DSCSA in healthcare and retailer routing guides in retail and grocery supply chains.

What is the SOPI structure in EDI 856?

SOPI stands for Shipment, Order, Pack, Item, which defines the structure of a typical ASN, a structure that represents how goods are physically packed, allowing systems to track shipments at multiple levels for accuracy and traceability.

What is the HL segment in EDI 856?

The HL (Hierarchical Level) segment defines the structure of the ASN by linking shipment, order, pack, and item levels. It is essential for organizing shipment data and enabling systems to interpret relationships between different packaging levels.

What is an SSCC in EDI 856?

SSCC (Serial Shipping Container Code) is a unique identifier assigned to cartons or pallets. In an EDI 856, SSCC values are transmitted to enable barcode scanning, automated receiving, and precise tracking of shipment units.

Why is EDI 856 important in supply chains?

EDI 856 improves supply chain efficiency by providing advance visibility into shipments. It reduces receiving errors, supports cross-docking, accelerates inventory updates, and ensures compliance with retailer and logistics requirements.

What happens if an ASN is late or missing?

A late or missing ASN can result in shipment delays, manual receiving processes, compliance penalties, and rejected deliveries. Many retailers require ASNs as part of their routing guides, making timely transmission critical.

How does EDI 856 support warehouse operations?

EDI 856 enables warehouses to prepare labor, allocate dock space, prepare ‘put-away’ locations update cross docking plans and pre-receive inventory. The detailed shipment structure allows for faster unloading, reduced manual checks, and improved accuracy during receiving.

Can EDI 856 be automated?

Yes, the EDI 856 can be automated using integration platforms connected to ERP and WMS systems. Automation of the ASN in this way reduces manual errors, ensures timely delivery, and enables real-time visibility across supply chain operations.

How does EDI 856 integrate with ERP and WMS systems?

EDI 856 integrates with ERP and WMS systems by automatically updating shipment, inventory, and receiving data. This integration eliminates manual entry, improves accuracy, and enables real-time synchronization across systems.

What industries use EDI 856?

EDI 856 is widely used in retail, grocery, manufacturing, logistics, healthcare, and distribution industries. Any industry that requires advance shipment visibility and automated receiving processes benefits from ASN implementation.

What triggers an EDI 856 transaction?

An EDI 856 is triggered when goods are shipped or have been prepared for shipment  and is typically generated after the picking processes have been completed, the truck has been loaded and the doors or the trailer have been closed (i.e., ‘close load’ function)..

Can an EDI 856 be corrected or updated?

Yes, EDI 856 transactions can be corrected using cancellation (BSN01 = 01) and replacement (BSN01 = 05) methods. This “change by refresh” approach ensures accurate shipment data while avoiding duplicate ASN issues.

What is “Change by Refresh” in EDI 856?

Change by refresh is a best-practice method for updating an EDI transaction by first canceling the original transaction and then sending a corrected replacement. This approach ensures the receiving systems has been advised to cancel or remove the outdated data before processing the updated document thus preventing duplicates and data conflicts.

What comes after EDI 856 in the workflow?

After EDI 856, the supplier typically sends an EDI 810 invoice, while carriers may send EDI 214 shipment status updates. The buyer then completes receiving and inventory reconciliation processes.

FAQs

What is an EDI 856?

EDI 856 is an Advance Ship Notice that communicates shipment details before goods arrive, enabling automated receiving and inventory updates.

What is SOPI in EDI 856?

SOPI stands for Shipment, Order, Pack, Item — It describe the typical structure of an ASN of which there are a few.

Why is the EDI 856 important?

The 856 enables faster receiving, reduces errors, and ensures compliance with trading partner requirements.

When should an ASN be sent?

It must be sent before the shipment arrives at the destination to be useful/effective.

Footnotes

1. PartnerLinQ EDI 856 Specification (V4010)
2. EDI 856 Overview Content
3. Sample ASN Files