Bidirectional EDI for transportation and retail. 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 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
Every plan runs the whole platform — inbound and outbound, AS2, SFTP and REST. Built for carriers, 3PLs and retail suppliers alike — plans are sized by how many trading partners you connect, with room for the loads and orders they send.
Carriers with their core shippers, or suppliers with their key retailers.
Regional carriers, 3PLs and suppliers selling into multiple retail chains.
National carriers, brokers, multi-site 3PLs and large brands or distributors.
For networks beyond 150 partners or with specific requirements.
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
Product launch · October 30, 2026
Join the waitlist for early access. We’ll invite teams around launch, starting with transportation and retail networks.
