EDI Connections sits between suppliers and the buyers they sell to. Partners with their own EDI systems connect directly. Partners without EDI log in to a web portal, fill in a form, and click Send. The platform turns that form into a standards-compliant EDI document for the supplier.
ISA*00*…*ZZ*ACMERETAIL*ZZ*NORTHWIND…~ GS*PO*ACMERETAIL*NORTHWIND*20261006…~ ST*850*0001~ BEG*00*SA*PO-10482**20261006~ N1*ST*Acme Store #212*92*212~ PO1*1*24*EA*12.50**VP*NW-1001~ PO1*2*10*CS*48.00**VP*NW-2040~ CTT*2~ SE*8*0001~
Our team sets up each connection and keeps it running.
Suppliers see every order from every partner in one place, however it arrived.
Partners trade with EDI suppliers through a website instead of EDI software.
We link a client to a partner and set up a lane for each document type, with its direction, EDI version, and test or production mode.
The platform reads each incoming file's envelope, matches it to the right client, partner and lane, and records every step.
EDI files and portal forms become the same order record. Every portal shows that record, so no one works from a copy.
Accepting, shipping and invoicing in a portal generates the matching EDI document: 997, 855, 856 or 810.
Every transmission is logged with its control numbers. You can see when acknowledgments come back, and resend if one is lost.
Many buyers are too small for a VAN, translation software and an EDI specialist, but their suppliers can only process EDI. The Trading Partner portal closes that gap. The partner uses a website, and the supplier receives standard EDI, the same as from any large retailer.
Once the client approves the partner, we set up the relationship and send an invitation link.
The partner registers their company, adds ship-to locations and users, and sees the client's item catalog.
A three-step form (header, line items, review) looks up items from the catalog, so lines match what the supplier sells.
Approve and Send are separate steps, so nothing reaches the supplier until someone sends it on purpose.
The platform builds an X12 or EDIFACT document using the supplier's interchange IDs, version, separators and control numbers, then logs the transmission.
The order goes to the supplier's systems over their usual connection, such as SFTP. It also appears in the Client portal.
The partner sees acknowledgments, order changes, shipments and invoices in the portal. Invoices that don't match the order are flagged.
The vendor accepts, rejects or changes each order line with a standard acknowledgment code. The client receives a PO acknowledgment.
Ship all or part of an order. The platform tracks remaining quantities and generates the ship notice with carrier and package details when the lane requires them.
Turn the shipped order into an invoice. Drafts can be saved and checked before sending, and the client receives a standard EDI invoice.
| Document | Partner without EDI | Client with EDI |
|---|---|---|
| 850Purchase order · ORDERS | Creates it in a three-step form, then approves and sends it. | Receives a standard 850, then reviews and accepts it in the portal. |
| 997Functional ack · CONTRL | Sees the order's transmission history: what was sent and when. | Acknowledgments are generated and matched to the original file automatically. |
| 855PO acknowledgment | Sees each line accepted, changed or rejected. As a vendor, sends one by acknowledging each line. | Sends one automatically on accepting an order, if the 855 lane is enabled. |
| 856Ship notice · DESADV | As a vendor, records a full or partial shipment with Ship PO. | Receives the ship notice. Order status changes to Shipped. |
| 810Invoice · INVOIC | Checks invoices against the order. As a vendor, sends one with Turn into Invoice. | Creates the invoice from the accepted order, or receives the vendor's invoice as EDI. |
Tell us who they are. We'll set up the connection, send the invitation, and run test orders before anything goes to production.