What Is EDI?

EDI — Electronic Data Interchange — is the structured exchange of business documents between companies. Instead of emailing a PDF or typing a purchase order into someone else’s portal, partners send a machine-readable file: an X12 850, a 204 load tender, a 810 invoice, a 214 status update.

The point is not the acronym. The point is that two organizations can complete a commercial transaction without a person in the middle retyping it. That is why EDI still sits under transportation, retail, and order-to-cash networks decades after it was invented.

Retailers, carriers, 3PLs, and suppliers already run on EDI. A new partner often means a new document set, a new envelope, and a new mailbox. Miss the file and the truck does not move, the ASN is late, or the invoice is rejected.

Spreadsheets and portal logins do not replace that network. They hide it until volume, chargebacks, or a compliance deadline make the hidden work visible. An EDI platform exists to make the network operable.

Inbound EDI is receive: the partner sends a file, you validate it, unpack it, map it, and deliver JSON, XML, or CSV into the ERP, WMS, TMS, or API you already run.

Outbound EDI is send: you pick up data from those same systems, map it, pack standards-compliant X12, and transmit it back to the trading partner. If a product only receives, it is a mailbox. Bidirectional EDI treats generate-and-send as first-class.

A VAN (value-added network) is the communication layer for secure file transmission — receive inbound files and send outbound EDI on the same mailbox. Partners should not need a protocol project for every relationship.

DotLinQ includes a VAN communication layer. Under the hood it can talk AS2, SFTP, and REST. The public job of the layer is simple: get the file in, get the generated file out, with receipts and an inbox you can operate.

Connectivity is not enough. Production EDI also needs partnership-aware validation, visual mapping, inbound and outbound process flows, routing when a file lands unsolicited, and monitoring that shows the failed step — so you replay instead of asking the partner to resend.

DotLinQ is an EDI platform for transportation and retail built around that list: Connect, Studio, Validate, Flow, and Monitor in one workspace. X12 versions 4010, 5010, and 6040. Launch October 30, 2026.