EDI compliance, as US retailers enforce it

What the mandate asks for, document by document

• The order, acknowledged in a window

  The purchase order arrives as an 850 and the retailer expects an 855 back inside their window, confirming what you will actually ship. Walmart, Kroger and Target each set their own clock, and the clock starts when their system sends, whether or not anyone on your side was watching.

• The ship notice, before the truck

  The 856 announces the shipment, structured the way the guideline demands, down to the pallet or the carton, and it has to arrive before the freight does. Arrive late or malformed and the guideline's deduction schedule applies.

• The invoice, matching the order

  The 810 has to reconcile against the order and the receipt. Quantity and price disagreements come back as short payments on the remittance advice, weeks after the shipment.

Where the money leaks

Enforcement is financial and it is quiet. A missed window becomes a chargeback code on a remittance advice weeks later, and accounts receivable writes it off as noise until somebody adds up three months of deduction lines.

Counting yours is a half-day exercise with the statements you already have, and it is the number that tells you whether this project pays for itself.

The codes, the causes and the counting method are laid out in the chargebacks and deductions guide.

We also maintain customer-specific pages for Walmart EDI requirements and Kroger EDI requirements. The Kroger page links to the programme material behind its claims.

Platform or direct

Your retailer's onboarding documents decide which routes are available. If they name a network, check its Odoo connection and who owns mapping, testing and failed transactions.

If the retailer permits a direct connection, compare the cost of running AS2 or SFTP yourself with the platform option. Transport, monitoring and support still need an owner.

What each route involves: SPS Commerce, TrueCommerce, Rithum, or direct over AS2 or SFTP.

What changes inside Odoo

The network moves the file. Inside Odoo, somebody decides which warehouse the order lands on, how the retailer's item numbers cross-reference to yours, what a consumer-level drop-ship order should become, and how a delivery turns into an 856 with the structure their guideline demands, before the truck leaves.

Some EDI providers also sell Odoo integration and managed mapping. Our role is to scope the Odoo workflow against your retailer's actual requirements, including the exception path when an order cannot be fulfilled as sent.

An order-flow example

This is a fictional example with sample item numbers. It describes a possible workflow, not a completed client project.

A retailer sends an 850 for 40 units of item R-174. The supplier calls the same product H-174 in Odoo, and only 28 units are available. The item cross-reference gets the order to the right product, but the shortage needs a person to resolve it before an acknowledgment goes back.

If the retailer allows a partial fill, the 855 can state what the supplier can ship under that retailer's rules. The 856 then reports what actually left the warehouse, and the 810 follows the agreed quantity. If partial fills are forbidden, the team needs a different response. The retailer's current guideline decides the branch; the integration should not guess.

A Requirement Check can identify the item mapping, response window and exception owner before anyone estimates the build. Start with your mandate.

Who does the work

ERPintegrators.com is a service line of Solvync Inc., an Odoo consultancy based in Calgary. We work remotely with US suppliers. We have no US office or endorsement from the retailers named here.

For work beyond retail EDI, see Solvync's Odoo integrations service.