How Cronwell works alongside EDI (850/855/856)
Updated August 2026
EDI for your largest trading partners is the right choice, and Cronwell does not replace it. The question EDI never answered is the rest of the supplier base — the two hundred suppliers who will never justify an integration project — and that is the part Cronwell covers.
The five EDI message types
EDI messages follow a shared standard — in North America, ANSI X12 — and five of its message types carry the whole PO conversation. The table shows each one, and what carries the same message today when a supplier is not on EDI: an email.
| Document | What it says | Without EDI, this arrives as |
|---|---|---|
| 850 — Purchase Order | The buyer’s order: lines, quantities, prices, dates | A PDF attached to an email |
| 855 — PO Acknowledgment | The seller’s answer, line by line: accept, reject, or accept with changes | A reply — “all good except line 3, that ships the 23rd” — or silence |
| 856 — Advance Ship Notice | What is physically shipping, with tracking, before it arrives | A forwarded carrier email, a PDF packing list, or nothing |
| 860 — PO Change (buyer) | The buyer changes the order: quantity, date, destination | An email the buyer writes and then chases |
| 865 — PO Change Ack (seller) | The seller accepts, rejects, or proposes changes | A reply in whatever words the supplier chooses |
Why the long tail never gets on EDI
Onboarding one trading partner onto EDI is a project: mapping, testing, and maintenance on both sides. EDI vendors’ own pricing guides put setup at close to $2,500 per partner, and can run higher; in a Cleo-commissioned survey, 63% of IT decision-makers said EDI onboarding takes too long.
The project is also bigger than the invoice suggests. X12 has been through decades of releases, and most trading partners freeze on whichever version they implemented years ago. On top of the version, each partner publishes its own implementation guide: which segments it requires, which codes it accepts, where it deviates from the base standard. So “standard” EDI is really a per-partner dialect; the mapping is built to that guide, tested in both directions on the partner’s schedule, and rebuilt when either side changes fields or systems.
And the messages themselves are rigid by design. A document carries exactly what its segments define. A reply like “yes, but 600 now and 200 next week, and the price moved” has no clean segment to live in. The partial answers, questions, and negotiations always fall back to email, even between connected partners. EDI solves transmission for a set of structured messages. It does not work for the conversation.
So even EDI-mature organizations run a split book. An Esker white paper is unusually candid: most companies accept email orders as a necessary evil, and even in the best situations, large organizations often have 20 to 30 percent of their orders coming in by email. The top of your supplier base is structured; the tail never will be.
Running EDI and email side by side
The working pattern we see at mid-market manufacturers:
- If you already run EDI, keep it. Your highest-volume partners exchange 850/855/856 through Cleo, SPS Commerce, or your ERP’s native EDI. Nothing changes.
- Everything that happens in email, Cronwell handles. For every supplier who answers by email, the agent reads the reply — the informal 855, the free-text 865 — parses it, attaches it to the PO line as evidence, and a buyer approves the update into the record.
- One record either way. Line status, days since sent, promised dates, and shipping notices land in the same PO record and write back to the ERP with approval.
How Cronwell works alongside EDIs.
Common questions
Do we have to move EDI suppliers to email?
No. You can simply leave EDI exactly where it works. Cronwell exists for the suppliers who were never on it.
Can Cronwell read an 855 or 856 feed?
The record reconciles with your ERP, which is where EDI documents land today — so EDI-side status arrives in the record through the ERP connection rather than a second EDI integration.
What if a supplier sends a PDF instead of writing in the thread?
The agent reads attachments with the email and compares them against the PO before proposing the update.
Bring your channel split and your open-PO line count — sizing the email share takes 30 minutes, and the calculator does the labor floor in two.
Sources — X12 transaction-set references for 850/855/856/860/865 and the release history — stedi.com · Esker white paper on sales order processing (20–30% of orders by fax/email at EDI-mature organizations; vendor source) · Orderful EDI pricing guide and SignalEDI cost guide ($750–$2,500 typical per-partner setup; vendor sources) · Cleo-commissioned onboarding survey (63%; vendor source). Vendor-published figures are labeled as such. More: SourceDay alternatives · security at Cronwell.