Dock Optimizer + EDI — X12 documents wired to the load board.
Inbound 204 load tenders create Dock Optimizer Load records automatically. Outbound 214 status updates, 210 invoices, and 990 responses transmit on load milestones — without a legacy VAN project and without manual re-entry.
Per-trading-partner configuration. Swappable transport layer. The X12 documents brokers and shippers actually exchange, mapped directly to Dock Optimizer's load lifecycle.
Supported X12 documents
Four X12 transaction sets cover the core load lifecycle — tender, accept, track, and invoice. These are the documents brokers and shippers actually need exchanged; nothing more, nothing less.
Received via HTTP and mapped directly into a Dock Optimizer Load record. Triggers the scheduling and dock assignment workflow.
Sent automatically as the load moves through pickup, transit, and delivery milestones — keeping trading partners' systems current without manual status calls.
Generated from the load record and transmitted to the broker or shipper for payment processing — without manual data re-entry.
Accept or decline response sent back after a 204 is received — completing the tender loop within your configured SLA window.
What the EDI integration gives you
EDI has a reputation for being a multi-month professional services engagement. Dock Optimizer's approach is different: per-trading-partner configuration through the Integration Hub, a swappable transport layer that fits what your partners already use, and only the documents that matter to the load lifecycle.
- Inbound load tenders land as Load records: When a broker or shipper sends a 204, it arrives via HTTP and is mapped directly into a Dock Optimizer Load. No manual entry, no copy-paste from an email. The load is in the system and schedulable immediately.
- Status updates go out automatically: 214 shipment status messages transmit on configured load milestones — pickup, in transit, delivered. Trading partners' TMS and visibility tools stay current without a phone call or email status check.
- Invoicing without re-entry: 210 freight invoices are generated from the load record and transmitted to the broker or shipper. The data that's already in the system becomes the invoice — no separate billing entry.
- Tender responses close the loop: 990 responses (accept or decline) are sent back after a 204 is received. The tender cycle completes within your SLA window without manual intervention.
- Transport layer is swappable: Route through a managed EDI provider, AS2, SFTP, or an HTTP endpoint — or your existing VAN gateway. Partners' current EDI infrastructure is accommodated, not replaced.
- Per-partner configuration: Each trading partner gets its own document mappings, transport settings, and credential scope. One partner's configuration doesn't affect another's.
Setup outline
The Integration Hub walks you through each step. Most trading-partner setups complete in a single session.
Open the EDI connector in Dock Optimizer's Integration Hub and create a trading-partner profile. Give it a name, ISA qualifier, and any partner-specific settings.
Choose your transport layer: managed EDI provider (AS2, SFTP, or HTTP endpoint), direct trading-partner connection, or your existing VAN gateway. Dock Optimizer accommodates what your partners already use.
Map X12 segment fields to Dock Optimizer Load and appointment fields. Pre-built mappings cover the most common 204 and 214 configurations — most setups need only minor field adjustments.
Send a test 204 load tender through the configured transport. Verify the Load record is created correctly in Dock Optimizer. Test the outbound 990 response back to the trading partner.
Flip the trading-partner connection to production. Inbound 204s create Load records automatically. Outbound 214s, 210s, and 990s transmit on the configured triggers. Health is monitored in the Integration Hub dashboard.
Security and monitoring
Trading-partner credentials are encrypted at rest. Connector scope is per-partner — one partner's credentials cannot access another's data. Outbound calls are SSRF-guarded. Every configuration change is logged in the Integration Hub audit trail with rollback available to any prior version.
FAQ
What EDI documents does Dock Optimizer support?
Dock Optimizer handles X12 EDI documents around the load lifecycle: outbound 214 (shipment status update), 210 (freight invoice), and 990 (load-tender response); and inbound 204 (load tender), which is received via HTTP and mapped directly into a Load record.
Do I need a VAN (value-added network) to use EDI with Dock Optimizer?
No. The transport layer is swappable — you can route through a managed EDI provider, a direct trading-partner connection, or your existing gateway. Partners' existing EDI setups are accommodated rather than replaced.
How is EDI configured in Dock Optimizer?
EDI is configured per trading partner through the Dock Optimizer Integration Hub. Each partner gets its own document mappings, transport settings, and credential scope. A connection test is built into the setup wizard.
What happens when a 204 load tender arrives?
Inbound 204 load tenders are received via HTTP and mapped directly into a Load record in Dock Optimizer. From there the load follows normal scheduling and dock assignment workflows. A 990 response (accept or decline) is sent back to the trading partner.