Both directions. One workspace.
Receive partner EDI into your systems, and generate X12 to send back — with the same partners, maps, mailbox and monitor.
See the platform- Receive
- Validate
- Unpack
- Map
- Deliver
- Export
- Map
- Pack X12
- Transmit
Bidirectional EDI for transportation and retail — now live. Receive partner files, map them into the systems you already run, and send X12 back — all from one workspace.
X12 4010 · 5010 · 6040 · AS2, SFTP & REST · Inbound and outbound
Built on Microsoft AzureBuilt for the trading-partner networks behind transportation and retail
Everything a trading-partner integration needs, in the order you’ll need it.
Receive partner EDI into your systems, and generate X12 to send back — with the same partners, maps, mailbox and monitor.
See the platformThe Intelligent Mapping Engine auto-maps partner EDI through a canonical model. You review, version and publish.
About mappingWhen a transaction fails, inspect the failed step and reprocess from there. The partner never sends it twice.
About replayAS2, SFTP and REST on one communication layer — secure receive, secure transmit, delivery receipts.
About the VAN layerA 204 goes to transportation, an 850 goes to retail — routing rules read the document, not just the sender.
About flowsEnvelopes, delimiters, control numbers and syntax are checked against the actual relationship — before anything runs.
About validationThe product
Real screens from DotLinQ — the same workspace your team would run for configuration, mapping and monitoring.
Receive, validate, unpack, map, convert and deliver — a visual process flow your team can read at a glance.

Five capabilities, one console — from the first partner file to the failed step you replay.
DotLinQ Connect
Trading partners, partnerships, VAN communication layer, File Explorer, and dynamic routing.
How it works
Connect the partner, design both directions, and watch them run. Seven steps, one workspace.
Carrier, retailer, 3PL, or supplier — identifiers, contacts, and the relationship you will run in both directions.
Inbound when they send to you, outbound when you generate and send to them. Upload a sample EDI file; DotLinQ proposes envelopes and delimiters.
A communication layer for secure file transmission. Receive inbound partner files and transmit outbound EDI on the same mailbox.
DotLinQ’s Intelligent Mapping Engine auto-maps partner EDI through a canonical document model to your ERP, WMS, TMS, or API shape. Publish a version. Inbound and outbound flows attach to it.
Inbound: receive → validate → unpack → map → deliver. Outbound: export → map → pack X12 → transmit. Schedule them. Replay failures.
VAN inbox and routing folders. Rules move matching documents to the folder an inbound flow is watching.
Inbound Transactions and Outbound Transactions, step preview, delivery receipts and transmission traces, reprocess from the failed step.
Transportation and retail X12, versions 4010, 5010, 6040 — inbound into the systems you run, outbound back to the partner.
Carriers · Brokers · 3PLs · Shippers
Load tenders, responses, shipment status, and freight invoices — inbound into the TMS or API you already run, and outbound X12 generated from those same systems.
Retailers · Suppliers · Manufacturers · Distributors
Purchase orders, acknowledgments, ASNs, invoices, and remittance — inbound into the order or ERP schema you already run, and outbound X12 generated to send back.
Load tenders, responses, shipment status, and freight invoices — mapped into the TMS or API you already run.
Order-to-cash X12 with retailers and suppliers: POs, ASNs, invoices, and inventory advice.
Onboard shippers, carriers, and retailers without a new integration project for each relationship — inbound and outbound.
Receive 204s, return 990s, publish 214s, and invoice on 210s from one workspace — inbound and outbound.
Accept purchase orders, send ASNs and invoices, and keep every inbound and outbound transaction visible.
Monitor
When a transaction fails, inspect the failed step and reprocess from there. You do not have to ask the partner to send the file again.
Traditional
DotLinQ
Plans
Every plan includes the complete DotLinQ platform. Choose the tier that matches how many transactions your network exchanges each month, and move up as it grows.
Up to 5,000
transactions per month
For teams starting out with EDI, or exchanging with a focused set of trading partners.
5,001–10,000
transactions per month
For growing operations adding partners and exchanging documents more often.
10,001–20,000
transactions per month
For mid-market organizations with expanding supplier and customer networks.
20,001–50,000
transactions per month
For high-volume operations running complex, multi-partner integration flows.
50,001–150,000
transactions per month
For enterprise throughput and national trading-partner networks.
No feature is held back for a higher tier.
A transaction is one business document received or sent, such as a load tender, status message or invoice (one X12 transaction set). An interchange carrying several documents counts each one, and reprocessing a document does not count it again. Volume is measured over a rolling 30 days.
Exchanging more than 150,000 transactions a month, or need something specific? Talk to us.
Enterprise infrastructure
DotLinQ runs on Microsoft Azure, the cloud that enterprises worldwide rely on for their most important systems. Your partner files, transactions and evidence are protected by the same infrastructure, security and reliability.
Sign-in through Microsoft Entra ID, with role-based access inside every workspace.
Your data is encrypted as it moves and while it is stored.
Each organization's partners, files and transactions are kept separate from every other customer.
Exchanged files are kept in write-once storage, backed by a ledger you can verify.
Managed infrastructure with automated backups, so work in progress is not lost.
Platform health is monitored, with automatic alerts when something needs attention.
Isolated workspaces, role-based access, and every artifact kept so failures can be inspected — not guessed at.
Operate from isolated workspaces rather than a shared catch-all environment.
Partner files and transaction artifacts stay in tenant storage.
Control who can configure partners, publish maps, and replay transactions.
Signing, encryption, and delivery receipts are part of the VAN layer — not a side system.
Keep step-level files so failures can be inspected and reprocessed.
Inbound, outbound, and file-exchange visibility for operations.
Formats, the VAN layer, ERP connections — and what DotLinQ doesn’t do yet.
Something else? support@dotlinq.com
Now live · October 30, 2026
Book a demo and walk inbound receive, outbound send, mapping, and the VAN layer — with your trading-partner stack in mind.
We're live
Launched Oct 30, 2026 · demos open now