EDI (Electronic Data Interchange) is the structured exchange of business documents between trading partners — purchase orders, invoices, load tenders, and status updates — without re-keying. DotLinQ is an EDI platform with a VAN communication layer so you can receive partner EDI and generate X12 to send back in the same workspace.

DotLinQ is bidirectional EDI for transportation and retail. Receive trading-partner files over a VAN communication layer, validate and map them into the systems you already run, generate X12 from those same systems, and send it back with the same secure file transmission — same workspace, partners, maps, mailbox, and monitoring.

Is DotLinQ bidirectional?

Yes. Inbound pipelines receive, validate, unpack, map, and deliver into your ERP, WMS, TMS, or API. Outbound pipelines export from those systems, map, pack standards-compliant X12, and transmit to the trading partner. Both directions are first-class.

What is the Intelligent Mapping Engine?

DotLinQ’s Intelligent Mapping Engine auto-maps partner EDI samples into a canonical document model, then to your target schema. You review, version, and publish — the same map drives inbound and outbound.

Yes. DotLinQ includes a VAN communication layer for secure file transmission — receive partner files and send generated EDI back on the same mailbox. AS2, SFTP, and REST are how that layer talks to partners and your systems.

What EDI formats do you support?

X12 for transportation and retail / order-to-cash use cases.

Does the VAN layer support AS2?

Yes. The VAN communication layer supports AS2 — identity, receive URL, MDN URL, certificates, signing, encryption, MDN receipts, and an inbox. The same station can receive inbound files and transmit outbound EDI.

Does the VAN layer support SFTP?

Yes. SFTP and FTP are supported for partners who exchange files that way, on the same VAN communication layer as AS2.

Can DotLinQ connect to my ERP or WMS?

Yes, through the VAN layer and REST, and by mapping to the target schema your system already accepts — inbound deliver and outbound pickup. DotLinQ does not ship native ERP connectors.

Do you support SAP or Dynamics 365?

DotLinQ does not include a native SAP or Dynamics 365 connector. You can exchange data with those systems through the VAN layer and REST, and by mapping to the schema those systems accept.

Do you support healthcare EDI?

Not currently. DotLinQ is focused on transportation and retail / order-to-cash X12.

Does DotLinQ automatically generate 997s?

997 configuration is supported, but automatic generation and transmission is not currently a runtime feature.

Can failed EDI transactions be reprocessed?

Yes. Inspect the failed step and replay the transaction from there. You do not have to ask the partner to resend the file.

Can I schedule process flows?

Yes. Run on demand or on daily, weekly, monthly, and recurring interval schedules, with automatic retries and dead-letter handling.

When does DotLinQ launch?

DotLinQ launches October 30, 2026. Join the waitlist for early access invitations around launch. Public self-service signup is not available today.

EDI Platform · Transportation & Retail

Connect Every Dot.Automate Every Flow.

We do bidirectional EDI. Receive trading-partner files over our VAN communication layer, validate and map them into the systems you already run — then generate X12 and send it back with the same secure file transmission.

EDI
Inbound
Outbound
VAN layer
Map once
Monitor both

Early access · October 30, 2026

Days: —
Hours: —
Minutes: —
Seconds: —

Public self-service signup is not open yet.

Inbound

Receive and transform

Trading partner

1Receive
2Validate
3Unpack
4Map
5Deliver

ERP / WMS / TMS / API

Outbound

Generate and send

ERP / WMS / TMS / API

1Export
2Map
3Pack X12
4Transmit

Trading partner

Same partners. Same maps. Same monitor. Both directions.

Bidirectional EDI

Two directions.

Same partners, maps, and monitor.

Inbound consumes partner EDI. Outbound produces partner EDI. One workspace for both.

Inbound

Receive and transform

Partner EDI through the VAN communication layer. Validate. Unpack. Map. Deliver JSON, XML, or CSV into the ERP, WMS, TMS, or API you already run.

Receive
Validate
Unpack
Map
Deliver

Outbound

Generate and send

Pick up data from those same systems. Map it. Pack standards-compliant X12. Transmit the generated EDI file to the trading partner through the same VAN layer.

Export
Map
Pack X12
Transmit

Inbound and outbound are first-class. Not a one-way mailbox.

TransportRetailManufacturingDistribution3PLCarriersSuppliers

Trading partner connectivity

Same partners. Both directions.

Partners send documents in. You generate X12 and send it back. DotLinQ is the exchange layer in between — not another custom project per relationship.

Retailer

Carrier

Supplier

3PL

DotLinQ

ERP

WMS

TMS

API

The problem

Every new partner shouldn’t become another integration project.

You already know the work: receive the file, get it into your system, generate the reply, and know what happened. Many tools only land inbound files. The project starts over with every new relationship.

Slow onboarding

Each new retailer or carrier is a custom project — envelopes, certificates, maps, and a specialist on every ticket.

One-way tools

Many translators only land inbound files. You still need another stack to generate X12 and send it back.

Opaque failures

When a document fails between partner, folder, and ERP, the team finds out from the warehouse — not from the hop that broke.

Specialist bottleneck

Maps live on one laptop. Certificates, envelopes, and the mailbox are tribal knowledge. Replay means asking the partner to resend.

How it works

Connect the partner. Design both directions. Watch them run.

DotLinQ is bidirectional. One workspace both consumes partner EDI and produces partner EDI. Scroll the seven beats.

Document journey

Add the trading partner
Create the partnership
Stand up the VAN layer
Map once, use both ways
Draw both pipelines
Route what arrives unsolicited
Operate both directions

Carrier, retailer, 3PL, or supplier — identifiers, contacts, and the relationship you will run in both directions.

Five capabilities

One workspace for both directions

Connect, Studio, Validate, Flow, and Monitor are the same console — inbound receive and outbound send, from the first partner file to the failed step you replay.

DotLinQ Flow

Automate both directions: receive and send.

Inbound: receive, validate, unpack, map, deliver. Outbound: export, map, pack X12, transmit. Same schedules and replay.

Inbound

Receive
Validate
Unpack
Map
Deliver

Outbound

Export
Map
Pack X12
Transmit

DotLinQ Studio

Map once. Use inbound and outbound.

Intelligent Mapping Engine, canonical model, business rules, versioning, and publishing — the same map drives receive and send.

DotLinQ Connect

Connect every partner on one VAN layer.

Trading partners, partnerships, VAN communication layer, File Explorer, and dynamic routing.

DotLinQ Validate

Know the file is legal before you process it.

Partnership-aware X12 validation — envelopes, delimiters, control numbers, and syntax rules on inbound files.

Interchange valid

DotLinQ Monitor

See inbound and outbound, every hop, every failure.

Inbound Transactions and Outbound Transactions, file exchanges, processing steps, and reprocess from the failed step.

CompletedCompletedFailedReplay

The product

The actual console your team would run

Configuration, mapping, and monitoring — real DotLinQ product UI. Inbound receive and outbound send in the same workspace.

Build the inbound pipeline visually: receive, validate, unpack, map, convert, and deliver. Draw the outbound pipeline: export, map, pack X12, transmit. Schedule either. When a step fails, reprocess from there.

app.dotlinq.com · ConfigurationStep 01 of 03

DotLinQ Configuration Studio — visual process flow from inbound SFTP receive through validate, unpack, map, convert, and REST API import

DotLinQ Studio · Intelligent Mapping Engine

Intelligent mapping. Canonical by design.

DotLinQ’s Intelligent Mapping Engine auto-maps partner documents through a canonical model — so inbound and outbound flows share one published map.

Intelligent Mapping Engine

DotLinQ’s own engine proposes and builds maps — less blank-canvas work on every new trading partner.

Canonical by design

Partner EDI is normalized into a canonical document model, then mapped to the schema your systems already accept.

You stay in control

Review the proposed map, adjust business rules, version it, and publish when it’s ready for inbound and outbound flows.

Intelligent Mapping EngineAuto-map

Source

EDI 850

ISA / GS
BEG
N1 / N3
PO1 loop

Canonical

Engine

Purchase Order

OrderId
Party
ShipTo
LineItem

Target

Order API

order.id
customer
location
lines[]

Intelligent Mapping Engine
Auto-map
Canonical model
Visual
Versioned
Publishable
Reusable inbound & outbound

Start from an Intelligent Mapping Engine proposal, refine the draft until it’s right, then publish a version for your flows. Older versions stay available — you are not editing live production blindly.

DotLinQ Mapping Studio — Intelligent Mapping Engine from X12 source segments through a canonical document model into your target schema

Transaction lifecycle

Every document has a journey.

Inbound example: a 204 load tender does not disappear into a folder. You can see received, validated, mapped, delivered — and replay if a hop fails. Outbound transactions have the same operational depth.

Recovery

Replay. Don’t resend.

When a hop fails, inspect the step and reprocess from there. The partner does not have to send the file again.

Traditional

Ask the partner to resend

Partner sends file
Failure
Investigate
Ask partner to resend
Start again

DotLinQ

Replay. Don’t resend.

File received
Failure
Inspect failed step
Reprocess
Continue

VAN communication layer

A VAN layer for communication — secure file transmission, receive, and send.

DotLinQ includes a VAN communication layer. Partners send files into your mailbox. You generate X12 and send it back on the same layer. One communication surface for the relationship.

VAN layer

A communication layer between you and every trading partner — one mailbox for the relationship, not a protocol project per partner.

Secure receive

Inbound partner files land in your VAN mailbox. Validate, unpack, map, and deliver into the systems you already run.

Secure transmit

Generate X12 from those same systems and send it back to the trading partner over the same VAN communication layer.

Every file has a place.

Receive documents, organize them, route them, and let automated flows pick them up. File Explorer is the VAN mailbox for your trading partner network — inbound files land here, then routing and flows pick them up.

File Explorer

Every file has a place.

AS2 Inbox
Unrouted inbound files
01 · Receive
Transportation / 204
Routed by document content
02 · Route
Retail / 850
Purchase orders
03 · Route
Process Flows
Automated pickup
04 · Automate

DotLinQ does not ship native ERP connectors. You map to the target schema your system accepts and deliver into those systems over REST or the VAN layer.

Dynamic routing

Route documents by what’s inside them.

Inspect the file and send a 204 to transportation, an 850 to retail, a 214 to shipment status — not only by who sent it.

AS2 Inbox

Unrouted files

Inspect document

Route by X12 content

204

Transportation Flow

Motor Carrier Load Tender

850

Retail Flow

Purchase Order

214

Shipment Status Flow

Carrier Shipment Status

VAN layer

Secure file transmission, without the infrastructure headache.

A VAN communication layer for receive and send — identity, certificates, receipts, and a mailbox. The station in the console is how that layer is configured.

AS2 Station

Workspace identity

Connected

AS2 ID: DOTLINQ_AS2
Receive URL: https://as2.dotlinq.com/receive
MDN URL: https://as2.dotlinq.com/mdn
Certificate: workspace-as2.cer
Expiry: 12 months
Partner: Ready to bind

VAN identity

A station identity your partners can address on the communication layer.

Secure receive

Inbound files land over encrypted transmission, with receipts when the partner requires them.

Certificates

Signing and encryption without a separate communications stack.

Delivery receipts

Proof of delivery on the same layer that received the file.

VAN mailbox

Inbound files land in one place, including unrouted files.

Secure transmit

The same layer sends generated X12 back to the trading partner.

DotLinQ Flow

Automate both directions: receive and send.

Inbound: receive → validate → unpack → map → deliver. Outbound: export → map → pack X12 → transmit. When something fails, you don’t start over.

Load the partner file from the VAN mailbox or storage.

Visual pipeline
On-demand runs
Daily, weekly, monthly schedules
Recurring intervals
Automatic retries
Dead-letter handling
Step-level artifacts
Reprocessing

DotLinQ Monitor

Know where every inbound and outbound document stands.

Inbound Transactions and Outbound Transactions. Received. Processing. Completed. Failed. See the hop, then reprocess from there.

Replay. Don’t resend.

Transaction received ✓
Validate ✓
Unpack ✓
Map ✕
Reprocess

DotLinQ Monitoring Studio — inbound transaction with step-level status from load through validate, packing, mapping, conversion, and import

Transaction status

Inbound and outbound in one console.

Processing steps

See which hop succeeded and which failed.

File preview

Inspect the document without leaving Monitor.

Transmission receipts

VAN evidence next to the transaction.

Errors

The failed step, not a mystery folder.

Reprocessing

Replay from the failed step. Don’t start over.

Supported EDI documents

X12 for the documents your business actually exchanges

Transportation and retail / order-to-cash — named by how teams use them, not a wall of transaction numbers.

204Motor Carrier Load Tender
990Response to a Load Tender
214Transportation Carrier Shipment Status
210Motor Carrier Freight Details and Invoice
211Motor Carrier Bill of Lading
997Functional Acknowledgment

Supported X12 versions: 4010 · 5010 · 6040

Industries

Built around the documents your business actually exchanges.

Transportation and retail / order-to-cash. X12 4010 · 5010 · 6040. A modern exchange layer — not a generic iPaaS.

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.

204Load Tender
990Response
214Status
210Invoice

Teams

Built for the people who keep commerce moving.

Same platform. Different jobs — onboarding, mapping, operations, and IT standardization.

EDI Manager

Onboard the next partner without another integration project.

Start from a real sample file. Configure the partnership, publish the map, attach the flow, and watch the first transactions in Monitor.

Plans

Flexible capacity for teams at every stage. Plan details and availability will be announced after launch. Public self-service signup is not available yet.

Capacity

Free

For exploring the platform.

3 Trading Partners
5 Partnerships
5 Process Flows
5 Mapping Projects
1 GB Storage
1,000 Transactions / 30 days

Growing networks

Growth

For growing partner networks.

25 Trading Partners
100 Partnerships
100 Process Flows
100 Mapping Projects
50 GB Storage
350,000 Transactions / 30 days

Capacity

Enterprise

For larger integration environments.

Unlimited trading partners
Unlimited partnerships
Unlimited process flows
Unlimited mapping projects
Unlimited platform-imposed storage
Unlimited platform-imposed transactions

Capacity

Custom

For organizations with specific requirements.

Agreed trading partners
Agreed partnerships
Agreed process flows
Agreed mapping projects
Agreed storage
Agreed transaction volume

Architecture

Built as a multi-tenant operations workspace

What DotLinQ actually provides today — not certifications we have not announced.

Multi-tenant workspaces

Operate from isolated workspaces rather than a shared catch-all environment.

Isolated tenant storage

Partner files and transaction artifacts stay in tenant storage.

Role-based access

Control who can configure partners, publish maps, and replay transactions.

Certificates & VAN

Signing, encryption, and delivery receipts are part of the VAN layer — not a side system.

Transaction artifacts

Keep step-level files so failures can be inspected and reprocessed.

Platform monitoring

Inbound, outbound, and file-exchange visibility for operations.

FAQ

Straight answers

Formats, VAN layer, ERP connections, and what DotLinQ does not do yet.

Product launch · October 30, 2026