A full EDI engine — translation, transport, mapping and archive — built for the people who live with the consequences of a late document. Trade with retailers, carriers, brokers and 3PLs without adding a vendor between you and your data.
X12 · EDIFACT · AS2
Most EDI providers do the first two and leave you to solve the rest with spreadsheets and a data warehouse.
X12 and EDIFACT parsed into structured data and rebuilt in whatever shape the receiving system needs — JSON, XML, CSV or another EDI dialect. Hierarchical documents such as the 856 ASN are built to the retailer's own nesting rules, not a generic template.
AS2 with signed MDN receipts, SFTP with per-partner credentials and key rotation, REST for anyone modern, and signed webhooks for event-driven partners. Certificates are parsed, stored and monitored for expiry rather than left in an inbox.
A rules engine decides where each document goes: which partner, which trading relationship, which downstream system, which mailbox. Change a rule without touching a mapping, and without a support ticket.
Every transaction keeps its raw payload, the parsed version, the transformed output and the response — with timestamps, status and retry count. Six months later you can still answer exactly what was sent, when, and what came back.
Chargeback disputes, retailer audits and "we never received it" conversations all come down to evidence. Plenty of EDI services consume a document, hand you the contents once, and keep nothing you can query afterwards — so teams end up building a second archive alongside the service they already pay for.
We keep the whole lifecycle of every transaction as a first-class record, queryable from the interface. There is no separate warehouse to build, and no window after which the trail goes cold.
Mapping is where EDI actually lives. A partner changes a qualifier, adds a segment, or starts sending a field you have never seen — and the cost of that change is measured in how quickly someone can safely alter the map.
Templates are versioned, testable and documented. You can see what a map does before you change it, and prove it still works afterwards.
Retail and freight on the same platform — most providers make you choose, or charge you twice.
EDI is not a silo here. The same documents that arrive from a retailer create orders, drive warehouse work, book dock appointments and tender freight — without a middle step where somebody re-keys them.
The one with the strange qualifier, the nested ASN and the certification cycle nobody wants to own. That is the conversation worth having — not a slide deck.