Retail and eCommerce

Retail EDI for accurate ASNs, compliant labels and fewer chargebacks

Retailers run their supply chains on precise documents, labels and timing, and they deduct for mistakes. ECOM connects suppliers to retail customers through EDI, API and WebEDI, builds ship notices and labels from the same shipment data, and helps teams trace each chargeback to its cause.

Talk to an EDI/API Expert Request a Demo

Summary: Retail

  • Retailers run on precise documents, labels and timing, and they deduct for mistakes, so wrong ASNs and labels become chargebacks.
  • For suppliers to store retailers, drop-ship and marketplace sellers, and retailers running vendor programs.
  • ECOM connects you through EDI, API and WebEDI, builds ASNs and labels from the same shipment data and traces chargebacks to causes.
  • Typical documents: 850 order, 855, 860 change, 856 ASN, 810 invoice, 846, 852, 820, 754 routing; ERP, WMS, carrier systems.
  • Talk to an EDI/API Expert: bring one retailer's implementation guide, a recent chargeback report or a document that keeps failing.
A retail store operations manager scans a carton with a handheld barcode scanner between shelves of boxed stock in a bright store stockroom.

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 send the purchase orders. Every vendor, including small ones without EDI systems, returns acknowledgments, ship notices and invoices as the program requires.

How the workflow runs

From purchase order to payment, with the checkpoints retailers enforce

A typical store replenishment cycle. The retailer sends the order; the supplier returns an acknowledgment, ship notice and invoice. Drop-ship and marketplace programs follow similar steps with their own documents and timing.

  1. 850Purchase orderRetailer to supplier
  2. 855AcknowledgmentSupplier confirms lines, quantities and dates
  3. 856Ship notice and labelsSent before the shipment arrivesSSCC on each GS1-128 label matches the 856
  4. 810InvoiceMatches order and receiptPrices and quantities reconcile
  5. 820Payment and deductionsRemittance shows what was deductedDeductions traced to their cause
Typical X12 workflow. Each trading partner's implementation guide defines its own documents, versions and timing.
  1. 01

    Receive and acknowledge the order

    The retailer's 850 purchase order becomes a sales order in your ERP. Your 997 or 999 is a technical acknowledgment: it shows the file arrived and could be read. The 855 is business acceptance: it tells the retailer whether you accept, change or reject the lines, quantities and dates, where the retailer requires it.

  2. 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.

  3. 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.

  4. 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.

  5. 05

    Reconcile payment and deductions

    The retailer's 820 remittance or portal shows what was paid and deducted. Each deduction is traced to the order, ASN, label or invoice that caused it.

  6. 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

01

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.

02

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.

03

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.

04

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.

05

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-API Gateway

    Order, inventory and shipment connections by API for marketplaces, drop-ship programs and retailers that offer APIs alongside EDI.

  • PRISM UniChannel

    Drop-ship and unified commerce for suppliers selling through retailers and online channels, with pay-by-scan support.

  • PRISM Reconcile360

    Matching of remittance advice, bank deposits and open invoices, with short payments and unmatched deductions flagged for review.

  • 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.

SystemWhat flowsWhat to plan for
ERPPurchase 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 WMSPick 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 systemsCarrier, 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 platformsDrop-ship orders, inventory feeds and shipment confirmations.Feed frequency follows each program's requirements, by EDI or API.

Retail and eCommerce

Supplier compliance here, online selling on the eCommerce page

This page covers selling to retailers under their supplier programs. Selling directly to consumers through storefronts and marketplaces is a different set of workflows.

Implementation

What to plan for in a retail EDI project

Most retail EDI delays come from data and testing, not from the translation itself.

Assess your EDI environment before adding retailers
  • 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.

Retail segments

How requirements differ by type of retailer

The same documents run under very different programs. Start from the retailer’s own guide and the segment it belongs to.

Documents and standards

Common transactions

Common X12 documents in retail supply chains. Each retailer specifies its own set and versions.

CodeDocumentWhat it does
850Purchase OrderThe retailer orders merchandise.
855Purchase Order AcknowledgmentThe supplier confirms the order.
860Purchase Order ChangeThe retailer changes an order.
856Advance Ship NoticeDescribes the shipment, packs and items before arrival.
810InvoiceBills the retailer for what shipped.
846Inventory Inquiry/AdviceShares inventory availability.
852Product Activity DataShares store sales and inventory data.
820Payment Order/Remittance AdviceExplains payments and deductions.
754Routing InstructionsProvides shipment routing details where used.

Scenarios

Typical integration scenarios

A new national retailer goes live

Problem: the retailer's guide sets its own ASN structure, labels and timing, and testing can slip. ECOM maps and tests orders, acknowledgments, ASNs and invoices against the retailer's current guide and builds labels from the same carton data. Benefit: the supplier goes live without disrupting existing customers.

A mismatched label triggers a chargeback

Problem: the SSCC on a carton does not match the ASN, the retailer receives manually and deducts. ECOM builds the ASN and label from the same data, validates before sending and traces each deduction to its cause. Benefit: fewer repeat chargebacks and a clear record for disputes.

A drop-ship program needs fast inventory and tracking

Problem: shoppers order what the supplier cannot ship. ECOM connects inventory feeds, orders and tracking by EDI or API, with UniChannel for drop-ship and unified commerce where it fits. Benefit: inventory the retailer can trust and shipments confirmed on time.

A payment arrives short

Problem: remittance and deposit do not agree with the invoices and the cause is unclear. Reconcile360 matches remittance advice, deposits and open invoices and flags short payments and unmatched deductions for review. Benefit: the team starts from matched records, not from the bank statement.

A retailer enables small vendors

Problem: vendors without EDI cannot meet the program. WebEDI lets them receive the retailer's orders and return acknowledgments, ASNs, labels and invoices in a browser. Benefit: more vendors comply, with a path to integrated EDI as volume grows.

Trading partners

Retail partners we connect with

Examples of retail trading partners ECOM can connect your business with.

See all 57 retail partners

Logos are trademarks of their respective owners. Their display does not imply endorsement of ECOM Specialist.

Case studies

Where ECOM provides these services today

Anonymous profiles of ECOM customers in this industry, each showing the services ECOM provides and how the work is set up.

  • Live-plant supplier selling through retail and online channels

    How a live-plant supplier keeps seasonal inventory, retail channels and the ERP in step

    Seasonal, perishable inventory across retail and online channels, with UniChannel, ERP, API Gateway and Reconcile360.

    PRISM UniChannel · Reconcile360 · API Gateway · Complete ERP solutions

    Read the profile
  • Consumer equipment and supplies company

    Meeting retailer compliance requirements while bringing suppliers into one portal

    Retailer EDI compliance and a Supplier Portal for a consumer equipment company that sells through large retailers.

    EDI operations · API Gateway · Supplier Portal (PRISM-WebEDI)

    Read the profile
  • Household appliance manufacturer

    Serving national retailers, regional dealers and builders from one managed process

    One managed process for retailer EDI, dealer browser access and settlement review at an appliance manufacturer.

    EDI operations · API Gateway · WebEDI · Reconcile360

    Read the profile

All case studies

Frequently asked questions

What is the difference between a 997 or 999 and an 855?

The 997 and 999 are technical acknowledgments: they confirm that an EDI file was received and could be read, or report syntax errors. The 855 is business acceptance of a purchase order, where the retailer requires it. A file can be acknowledged technically and still be rejected on the business side, so each is monitored on its own.

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.

Where do I find a retailer’s EDI requirements?

Most large retailers publish a vendor or supplier guide, usually behind a vendor portal. The retailer guides in our directory summarize publicly available requirements; your retailer’s own guide is the authority.

Is retail EDI the same as consumer goods EDI?

The documents are the same, but the focus differs. This page is about meeting each retailer’s program. The consumer goods page is about the brand behind many retailers, including warehouses, deductions and online channels.

How to get started

Tell us who you trade with and what you run

  1. Send the basics. Your trading partners, the documents they require, your ERP or other systems, and any deadline.
  2. We review the requirements. An ECOM specialist looks at the partner programs, document formats and connections involved.
  3. You decide how to proceed. We outline the options, including managed services or software, for you to compare.

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.