Retail and eCommerce
Retail EDI that ships on time, labels correctly and gets paid in full
Retailers run their supply chains on precise documents, labels and timing, and they deduct for mistakes. ECOM connects suppliers to their retail customers through EDI, WebEDI and document automation, builds ship notices and labels from the same shipment data, and helps teams find and fix the causes of chargebacks.
What is retail EDI?
Retail EDI is the electronic exchange of purchase orders, acknowledgments, advance ship notices, invoices, inventory and sales data between retailers and their suppliers, usually in ANSI X12. Each retailer publishes implementation guides that set the documents, versions, fields and timing it requires, along with carton labeling and routing rules. Because receiving, payment and supplier scorecards depend on these documents, accuracy and timing matter as much as connectivity.
Who it's for
Different roles, different workflows
-
Suppliers to store retailers
Brands and manufacturers shipping to retail distribution centers and stores. Every retailer has its own implementation guide, and receiving depends on an accurate ASN and matching carton labels.
-
Drop-ship and marketplace sellers
Suppliers who ship online orders directly to consumers for a retailer's website, or sell through marketplaces. Inventory feeds and shipment confirmations must be fast and accurate.
-
Retailers running vendor programs
Retailers and distributors who need every vendor, including small ones without EDI systems, to send compliant orders, ship notices and invoices.
How the workflow runs
From purchase order to payment, with the checkpoints retailers enforce
A typical store replenishment cycle. Drop-ship and marketplace programs follow similar steps with their own documents and timing, which the retailer's guide defines.
- 850Purchase orderRetailer to supplier
- 855AcknowledgmentSupplier confirms lines, quantities and dates
- 856Ship notice and labelsSent before the shipment arrivesSSCC on each GS1-128 label matches the 856
- 810InvoiceMatches order and receiptPrices and quantities reconcile
- 820Payment and deductionsRemittance shows what was deductedDeductions traced to their cause
- 01
Receive and acknowledge the order
The 850 purchase order becomes a sales order in your ERP. A 997 confirms receipt, and an 855 confirms lines, quantities and dates where the retailer requires it.
- 02
Pick, pack and label
Cartons and pallets are labeled with GS1-128 labels. Each label's SSCC must match the carton or pallet in the ship notice exactly.
- 03
Send the ASN before the shipment arrives
The 856 describes the shipment, orders, packs and items in the hierarchy the retailer requires, with carrier and bill of lading references, inside the retailer's timing window.
- 04
Invoice what was shipped
The 810 matches the order and the ASN on items, quantities, prices and allowances, so it can be paid without manual review.
- 05
Reconcile payment and deductions
The 820 remittance or the retailer's portal shows what was paid and deducted. Each deduction is traced to the order, ASN, label or invoice that caused it.
- 06
Keep inventory current where required
Drop-ship and marketplace programs expect 846 inventory feeds often enough that shoppers never order what you cannot ship.
Challenges
Integration challenges in retail
Every retailer's rules are different
Versions, required fields, ASN structures, label formats and timing windows vary by retailer, so one generic map does not fit all of them.
ASN accuracy and timing
An ASN that arrives late or does not match what was physically shipped disrupts receiving and is one of the most common reasons for deductions.
Labels that do not match the ASN
When the SSCC on a carton label differs from the ASN, the retailer cannot receive the carton electronically and may charge for manual handling.
Master data drift
Item identifiers, pack quantities and retailer item numbers that differ between your ERP and the retailer's catalog cause rejected orders and invoices.
Deductions that nobody can explain
Deductions arrive weeks later in remittances or portals, often without enough detail to dispute them or to fix the cause.
How we help
How ECOM supports retail companies
-
Retailer onboarding and certification
Specifications, connectivity, test documents, scenario testing with the retailer and go-live support for each new retail customer.
-
Retailer-specific maps
Purchase orders, acknowledgments, ASNs and invoices mapped to each retailer's implementation guide and connected to your ERP and warehouse systems.
-
ASNs and labels from the same data
GS1-128 carton and pallet labels and the 856 are generated from the same shipment and carton data, so SSCCs and contents match.
-
Validation before sending
Retailer-specific rules check documents for required values, references and structure before they leave your systems.
-
Chargeback detection and prevention
Deductions are captured and traced to their cause, and the controls that prevent the recurring ones are put in place.
-
Options for smaller suppliers
Suppliers without EDI systems can exchange retail documents and print labels in a browser with PRISM-WebEDI.
PRISM products
Which PRISM products apply
Each partner connects in the way it can support. These products cover the connections and visibility this industry needs most.
-
PRISM-EDI
System-to-system exchange of X12 documents with retailers over AS2, SFTP or a VAN, translated to and from your ERP and warehouse systems.
-
PRISM-WebEDI
Browser-based purchase orders, acknowledgments, ASNs and invoices for suppliers without EDI systems, with UCC labels and bills of lading.
-
PRISM-SmartConvert
Orders and documents that arrive as PDFs or emails, for example from smaller retail customers, converted into ERP-ready data.
-
PRISM-SCV
Monitoring of acknowledgments, ASN timing and exceptions, so problems are visible before a retailer reports them.
Systems integration
What retail EDI connects to
Retail compliance depends on data from several systems. Integration covers each of them, not only the EDI translator.
| System | What flows | What to plan for |
|---|---|---|
| ERP | Purchase orders become sales orders; shipments and invoices produce ASNs and 810 invoices. | Retailer item numbers, customer locations and pricing cross-references maintained in one place. |
| Warehouse or WMS | Pick and pack results, carton contents and SSCCs for labels and the ASN. | Labels and ASNs built from the same carton data; packing done by a 3PL needs the same rules. |
| Shipping and carrier systems | Carrier, tracking and bill of lading references for the ASN. | The retailer's routing guide decides carriers and appointments; routing requests may be required. |
| Commerce and marketplace platforms | Drop-ship orders, inventory feeds and shipment confirmations. | Feed frequency follows each program's requirements, by EDI or API. |
Implementation
What to plan for in a retail EDI project
Most retail EDI delays come from data and testing, not from the translation itself.
-
Start from the retailer's current guide
Requirements change. Maps and labels are built and tested against the version the retailer publishes today, not a copy from a previous project.
-
Clean up item and location data first
GTINs, retailer item numbers, pack quantities and ship-to locations must match the retailer's records before testing begins.
-
Decide where labels are printed
Your warehouse, a 3PL or a co-packer can print labels, but the SSCCs must reach the ASN either way.
-
Plan the retailer's testing and certification
Many retailers test documents and labels before allowing production orders. The timeline depends partly on the retailer.
Documents and standards
Common transactions
Common X12 documents in retail supply chains. Each retailer specifies its own set and versions.
| Code | Document | What it does |
|---|---|---|
| 850 | Purchase Order | The retailer orders merchandise. |
| 855 | Purchase Order Acknowledgment | The supplier confirms the order. |
| 860 | Purchase Order Change | The retailer changes an order. |
| 856 | Advance Ship Notice | Describes the shipment |
| 810 | Invoice | Bills the retailer for what shipped. |
| 846 | Inventory Inquiry/Advice | Shares inventory availability. |
| 852 | Product Activity Data | Shares store sales and inventory data. |
| 820 | Payment Order/Remittance Advice | Explains payments and deductions. |
| 754 | Routing Instructions | Provides shipment routing details where used. |
Scenarios
Typical integration scenarios
Supplier adding a national retailer
Meet a new retailer's requirements for orders, ASNs, labels and invoices without disrupting existing customers.
Supplier with many retail customers
Manage several retailers' variations of the same documents from one integrated process and one view of exceptions.
Retailer enabling small vendors
Bring vendors without EDI systems onto compliant orders, ASNs and invoices through a browser.
Trading partners
Retail partners we connect with
Examples of retail trading partners ECOM can connect your business with.
Logos are trademarks of their respective owners. Their display does not imply endorsement of ECOM Specialist.
Frequently asked questions
Why do retailers require the ASN before the shipment arrives?
Retailers use the 856 to plan receiving and to receive cartons by scanning their labels. If the ASN is late or does not match the cartons, receiving becomes manual, which is why many retailers deduct for it.
What causes most retail EDI chargebacks?
Late or inaccurate ASNs, labels whose SSCC does not match the ASN, missing acknowledgments, invoice discrepancies and routing violations. Each retailer defines its own rules and fees.
Can ECOM eliminate chargebacks?
No process can promise that. ECOM helps you detect deductions, trace each one to its cause and put controls in place that prevent the recurring ones.
Can small suppliers meet retail EDI requirements without integrating their ERP?
Yes. PRISM-WebEDI lets suppliers exchange purchase orders, acknowledgments, ASNs and invoices and print labels in a browser, with a path to integrated EDI as volume grows.
Does ECOM have ready-made maps for specific retailers?
ECOM maintains reusable templates for common retail documents. Whether one applies to your retailer is confirmed during scoping, and every map is validated against the retailer's current guide.
Bring us one retailer's requirements
Share a retailer's implementation guide, a recent chargeback report or a document that keeps failing. An ECOM specialist will review it with you and explain the options.