Big-box retailers process large numbers of purchase orders, shipments, invoices, inventory updates, and product records. To manage that volume efficiently, retailers establish detailed requirements governing how suppliers exchange data, label shipments, schedule deliveries, acknowledge orders, and submit invoices.
Electronic data interchange, or EDI, is the system that connects many of these activities. It allows purchase orders, shipping notices, invoices, acknowledgments, and other documents to move between the retailer’s systems and the supplier’s systems in standardized electronic formats.
Retail EDI compliance, however, involves more than successfully transmitting a file. Suppliers must send the right document, with the right information, in the retailer’s required format and within the required timeframe. The electronic information must also match the products, cartons, pallets, quantities, and locations involved in the physical shipment.
A failure at any point can lead to rejected documents, receiving delays, invoice disputes, delayed payment, additional manual work, or retailer-assessed noncompliance charges. Major retailers publish vendor standards that can include transactional requirements, routing procedures, shipping instructions, labeling rules, and financial consequences for noncompliance.
Understanding these requirements, and building reliable processes around them, is essential for maintaining productive retail relationships.
What Is Retail EDI Compliance?
Retail EDI compliance means configuring and operating your EDI processes according to the requirements established by each retail trading partner.
Those requirements may define:
- Which EDI documents must be exchanged
- Which version of the EDI standard must be used
- Which fields are required within each document
- How products, locations, cartons, and orders must be identified
- When each document must be transmitted
- Which communication protocol must be used
- How documents must be acknowledged
- How shipping labels must be formatted
- How the advance ship notice must match the physical shipment
- How purchase order changes must be processed
- How errors and rejected transactions must be corrected
Although many North American retailers use X12 transaction sets, each retailer can create its own implementation guide or mapping specification.
Two retailers may both require an X12 856 Ship Notice/Manifest, commonly called an advance ship notice or ASN, but require different segments, qualifiers, identifiers, shipment structures, or transmission deadlines.
Therefore, supporting the correct X12 transaction set is only the beginning. The supplier must also comply with the retailer’s specific implementation of that transaction.
Why Big-Box Retailers Require EDI
Large retailers depend on automation to coordinate purchasing, fulfillment, transportation, warehouse receiving, inventory management, invoicing, and payment across extensive supplier networks.
EDI gives retailers and suppliers a standardized way to exchange structured business information without manually entering every purchase order or invoice.
The basic X12 supply chain flow can include item information, purchase orders, purchase order acknowledgments, shipping notices, invoices, and payment information. X12 identifies the 850 Purchase Order, 855 Purchase Order Acknowledgment, 856 Ship Notice/Manifest, 810 Invoice, and 820 Payment Order/Remittance Advice as core parts of this process.
When EDI data is accurate, retailers can use it to:
- Create orders in supplier systems
- Confirm whether products can be shipped
- Plan transportation and receiving capacity
- Identify incoming cartons and pallets
- Match shipments against open purchase orders
- Update inventory
- Validate invoices
- Schedule payments
- Investigate shortages or discrepancies
The system works only when the electronic documents accurately represent the underlying business activity.
An ASN stating that 100 units were shipped is not useful when the pallet contains 90 units. Likewise, a shipping label cannot support automated receiving when the identifier printed on the carton does not match the identifier transmitted in the ASN.
Common EDI Documents in Retail
The documents required will depend on the retailer, merchandise category, fulfillment model, and supplier relationship. However, the following transaction sets are commonly used in retail supply chains.
X12’s supply chain model explains how these documents support data alignment, ordering, delivery, invoicing, and payment. It also emphasizes the importance of the 997 Functional Acknowledgment for confirming that a transaction was received and usable.
Retailers may also require additional documents for warehouse activity, transportation, product data, receiving discrepancies, direct-to-consumer fulfillment, or specific merchandise categories.
The retailer’s current EDI implementation guide should always be treated as the governing specification.
The EDI 850 Purchase Order
The EDI 850 Purchase Order is typically the starting point of the retail order cycle.
It can communicate information such as:
- Purchase order number
- Order date
- Ship-to location
- Bill-to location
- Product identifiers
- Quantities
- Unit prices
- Requested shipping dates
- Requested delivery dates
- Packaging information
- Carrier or routing details
- Allowances and charges
- Cancellation dates
The supplier must be able to translate the incoming 850 into its order management or ERP system without losing required information.
Problems can occur when:
- The retailer’s item number does not match the supplier’s item number
- A ship-to location has not been configured
- The unit of measure is interpreted incorrectly
- A pack quantity is mistaken for an individual unit quantity
- The requested dates are not passed into the ERP
- Duplicate purchase orders are created
- Updated purchase orders overwrite valid order data incorrectly
X12 notes that the 850 can contain buyer and seller information, purchase order identifiers, pricing, packaging, carrier details, delivery scheduling requirements, and product data.
A compliant process must validate the order before it enters fulfillment
Purchase Order Changes
Retail purchase orders do not always remain unchanged between the original order and shipment.
A retailer may change:
- Quantities
- Products
- Ship-to locations
- Shipping windows
- Delivery dates
- Pricing
- Cancellation dates
- Transportation instructions
The EDI 860 Purchase Order Change can communicate buyer-initiated changes. The supplier may then use the EDI 865 Purchase Order Change Acknowledgment to accept, reject, or modify the requested change.
These documents must be processed carefully. If the warehouse ships from an outdated version of the purchase order, the physical shipment may no longer match the retailer’s current order.
The EDI process should preserve a clear history of the original purchase order and every subsequent change.
Why ASN Accuracy Matters
The ASN is not simply a notification that a truck has left the warehouse. It is an electronic representation of the actual shipment.
The retailer may compare the ASN against:
- The original purchase order
- The latest purchase order changes
- The barcode on each carton or pallet
- The products and quantities physically received
- The supplier’s invoice
An ASN can be considered noncompliant when:
- It is transmitted late
- It references the wrong purchase order
- It contains an incorrect ship-to location
- The carton count is inaccurate
- The item quantities do not match the shipment
- Carton identifiers are duplicated
- Products are assigned to the wrong cartons
- The barcode identifiers do not match the ASN
- The shipment hierarchy is structured incorrectly
- The retailer cannot connect the ASN to the physical delivery
Some retailer vendor guides expressly connect late or inaccurate ASNs with compliance assessments. Belk’s published vendor materials, for example, state that accurate ASN information must be transmitted when the carrier picks up the shipment and describe chargebacks for noncompliance.
The exact timing and content requirements will differ by retailer, so suppliers must validate each ASN against the relevant trading partner guide.
Functional and Application Acknowledgments
Sending an EDI document does not prove that the retailer successfully processed it.
Suppliers need to monitor acknowledgments and document statuses.
An EDI 997 Functional Acknowledgment can indicate whether an EDI transaction was received and structurally accepted or rejected. X12 describes the 997 as critical because it confirms receipt and whether the original transaction was usable by the receiving party.
Depending on the retailer and transaction, suppliers may also receive application-level messages identifying business errors.
A complete monitoring process should distinguish among:
- Document transmitted
- Document delivered
- Functional acknowledgment received
- Document structurally accepted
- Document rejected
- Document accepted with errors
- Business application processing completed
- Manual investigation required
Without this visibility, a supplier may believe that an ASN or invoice was accepted when it actually failed.
Frequently Asked Questions
What is retail EDI compliance?
Retail EDI compliance means exchanging electronic business documents according to a retailer’s technical and operational requirements. These requirements can cover transaction formats, required data, transmission timing, acknowledgments, shipping labels, ASNs, invoicing, and error handling.
Which EDI documents do big-box retailers require?
Requirements vary, but common documents include the EDI 850 Purchase Order, EDI 855 Purchase Order Acknowledgment, EDI 856 Advance Ship Notice, EDI 810 Invoice, EDI 820 Remittance Advice, EDI 846 Inventory Advice, and EDI 997 Functional Acknowledgment.
What is an ASN in retail?
An ASN is an advance ship notice, typically sent using the EDI 856 transaction set. It tells the retailer what is being shipped and may identify the purchase orders, cartons, pallets, products, quantities, carrier, and shipment identifiers involved.
When should an ASN be sent?
The retailer’s implementation guide determines the exact deadline. In general, the ASN must be transmitted according to the retailer’s required shipping event and early enough for the retailer to process it before receiving the physical shipment.
What is the difference between an ASN and a shipping label?
The ASN is an electronic document containing shipment information. The shipping label is attached to the physical carton or pallet. Identifiers on the label, such as an SSCC, may be included in the ASN so the retailer can connect the physical shipment with the electronic record.
What is an SSCC?
An SSCC, or Serial Shipping Container Code, is a unique GS1 identifier assigned to a logistics unit such as a carton or pallet. It can be encoded in a GS1-128 barcode and connected to shipment information in an ASN.
Can an EDI document be transmitted successfully but still be rejected?
Yes. A document may be delivered and pass structural validation but still fail the retailer’s business rules. Examples include an invalid purchase order number, incorrect item identifier, unrecognized ship-to location, quantity discrepancy, or duplicate invoice.
What causes retail EDI chargebacks?
Potential causes vary by retailer but can include late or inaccurate ASNs, invalid labels, routing violations, incorrect quantities, missing acknowledgments, invoice errors, or shipments made outside an authorized window. The retailer’s vendor agreement and compliance policy determine when charges apply.
Can a small supplier meet big-box EDI requirements?
Yes. Smaller suppliers may use a web-based EDI portal when transaction volume is limited. As volume increases, integrated or managed EDI services may provide greater automation and reduce repetitive manual entry.
Does EDI need to integrate with a warehouse management system?
Not in every implementation, but WMS integration can be particularly valuable for ASN and shipping label accuracy. It allows final carton, pallet, product, and quantity information to flow from warehouse execution into the outbound EDI document.
How can an EDI provider help with retail compliance?
An EDI provider can review retailer specifications, build maps, configure communications, manage testing, integrate business systems, monitor transactions, resolve errors, maintain maps, and help suppliers respond when retailer requirements change.
Our Company
Resources