EDI 850, 855, 856, and 810 — built in.
Trade with the chains and buying groups that require EDI without a separate EDI vendor. DistroLync OMS sends 850 purchase orders and takes back 855 acknowledgments, 856 ship notices, and 810 invoices — on the same orders they answer, with no rekeying and no per-document fees from us.
One system generates each document from the last.
- 850 — Purchase Order. Orders arrive from the portal, EDI, or a rep, each carrying its account’s contract pricing from the moment it lands.
- 855 — PO Acknowledgment. Confirmations flow back onto the same order, so exceptions surface before the truck is loaded.
- 856 — Advance Ship Notice. Ship notices generate from the pick and route, not a separate export.
- 810 — Invoice. Invoices generate from the stop’s final numbers as it closes, matching what actually came off the truck.
No separate EDI vendor. No per-document fees.
If you’ve been quoted a five-figure EDI project, talk to us first — EDI is part of DistroLync OMS, wired into the same orders, pricing, and invoices your warehouse already runs on. For a plain-English tour of the documents, read EDI 850 / 855 / 856 / 810 explained.
Which EDI documents does DistroLync OMS support?
The four a distribution house trades on: outbound 850 purchase orders to your suppliers, and inbound 855 purchase-order acknowledgments, 856 advance ship notices, and 810 invoices — all flowing back into the same orders they answer.
Do I need a separate EDI vendor or VAN?
No. EDI is built into DistroLync OMS, so trading with the chains and buying groups that require it does not need a bolt-on EDI provider or per-document fees from us.
How do chains and buying groups connect?
We map your trading partners once; from then on their documents flow straight onto your fulfillment board with the right account pricing already applied — no rekeying between a portal, EDI, and phone orders.