The starting point
Web EDI, and when to stop
Web EDI is a browser portal. Your customer's orders appear in it, you click each one, and you type your acknowledgments, ship notices and invoices into its forms. To the retailer you are fully EDI compliant.
Inside your building, somebody keys every one of those orders into your system a second time. Web EDI is where many suppliers start. The question this page answers is when it stops being the cheap option.
On this page
What web EDI actually is
The networks that carry retail documents, SPS Commerce and TrueCommerce among them, offer a portal tier: the documents flow through their pipes and stop at a screen. The retailer sees a compliant trading partner answering inside its windows. Nothing arrives in your ERP, because the portal is the endpoint.
So the mandate is satisfied, and the work has moved. Orders are read off one screen and typed into another, in both directions, for every document the programme requires.
When it is the right answer
A handful of orders a week
At low volume the keying stays an annoyance. A portal subscription is cheap, it stands up in days, and it buys time to see whether the retail relationship grows before anything is built.
One customer, few documents
A single mandate asking for orders and invoices is a light load. The arithmetic changes when the programme adds ship notices, because an 856 typed into a form has to describe physical packing a screen cannot see.
A trial relationship
A first purchase order from a new retailer proves nothing yet. Starting on the portal and integrating once the volume is real is a defensible sequence, run deliberately.
The signs you have outgrown it
The keying starts consuming a person. Orders wait in the portal until somebody has time, requested dates get closer while they wait, and rekeying introduces the typos the documents were invented to remove. The 856 becomes the breaking point, because typing a packing hierarchy into a web form, accurately, before the truck leaves, does not survive contact with a busy dock.
The tell that costs money is on the remittance advice: deduction lines for late acknowledgments and ship notices that were sitting in somebody's keying queue. When those appear, the portal has become the expensive option wearing the cheap option's price tag.
What integration changes
The same network, the same mandate, the same documents. The difference is the endpoint: documents land in Odoo as sales orders instead of stopping at a screen, and your acknowledgments, ship notices and invoices leave from the records Odoo already keeps. The portal keying, both directions of it, is the part that disappears.
Your customer notices nothing except the windows being met. That is the point.
What the platform routes involve: SPS Commerce and TrueCommerce. What the deduction lines cost: chargebacks and deductions. The documents themselves: the X12 catalog.
Count your portal hours first
The Requirement Check takes two answers: who mandated you and where you stand today. You get back a plain readout of which documents that customer asks for and what has to change inside your Odoo. It is free and it commits you to nothing.
Book a 30-minute call