Purchase orders in, invoices and ship notices out — without re-keying anything.
Retailer purchase orders arrive as Sage 100 sales orders. Invoices, advance ship notices, and acknowledgements are generated from your Sage 100 records and validated against each retailer’s rules before they go out. ActionEDI builds and maintains the mapping in between.
Year 1 is $0. No credit card, no contract.
Most distributors running Sage 100 without integrated EDI settle into the same routine: a purchase order lands in a retailer portal or an inbox, someone keys it into Sage 100 as a sales order, then keys the invoice back out the other way. Every hop is a chance to transpose a quantity or miss a ship window.
The bill usually arrives as chargebacks rather than as labour. A late ASN, a carton label that does not match the shipment, or an invoice that will not tie back to the PO gets deducted from a payment weeks later — long after anyone can reconstruct why.
The X12 documents most retail trading partners require, and where each lands in Sage 100.
| Doc | Document | Direction | Sage 100 record | What happens |
|---|---|---|---|---|
| 850 | Purchase Order | Retailer → you | Sales Order | The retailer’s PO becomes a Sage 100 sales order with customer, items, pricing, ship-to, and dates already filled in — no one retypes it. |
| 855 | PO Acknowledgement | You → retailer | Sales Order | Confirms what you can actually ship — accepted, rejected, backordered, or changed lines — inside the window the retailer requires. |
| 856 | Advance Ship Notice | You → retailer | Shipment | Built from the Sage 100 shipment, carrying the carton and pallet hierarchy and the SSCC-18 numbers printed on the GS1-128 labels. |
| 810 | Invoice | You → retailer | Invoice | Generated from the Sage 100 invoice and validated against the retailer’s rules before transmission, rather than rejected days later. |
| 860 | PO Change | Retailer → you | Sales Order | Quantity, date, and line changes apply against the original sales order instead of arriving as an email nobody actions. |
| 997 | Functional Acknowledgement | Both ways | — | Proof a document arrived. A missing 997 is usually the first sign something has quietly stopped working. |
Running a different Sage product? Sage 50, Sage 200, Sage 300, Sage Intacct, and Sage X3 are covered on our general Sage EDI integration page.
Your team works in Sage 100. The EDI layer is ours to build, run, and fix.
Which retailers, which documents each requires, and how your Sage 100 installation is configured. You get a straight answer on fit within 24 hours — including if we are not right for you.
Each retailer tests and certifies separately, and each has its own quirks. Onboarding usually runs in weeks rather than months, scaling with the number of partners and documents.
Year 1 is free — unlimited volume, partners, and seats. Before it ends we quote Year 2 in writing from your real usage. If the number does not work, you walk.
Tell us your retailers and how Sage 100 is set up. Ramesh, our founder, replies within 24 hours with a straight answer on fit — including if we are not the right choice.
