eAdapter in Production: Architecture & Operations
You got eAdapter working. Now you own it in production — the middleware, the monitoring, and the 2am pages when messages stop flowing. This guide is the operations manual CargoWise never wrote.
For integration leads and consultants running eAdapter in production.
Get early accessLaunch discount for the wait list. One email when it ships, no spam.
Stop googling these
The Problems This Guide Solves
“CargoWise eAdapter outbound service only accepts one URL”
Every multi-system shop discovers this too late. The relay/fan-out architecture that fixes it, with queue and dead-letter design.
“eAdapter message sent but nothing appeared in CargoWise”
Async sends return a tracking UUID, not a status. Real status lives in the EDI Interchange nobody told you about — and you can poll it.
“CargoWise milestone completed but the EDI message never fired”
Workflow templates need an explicit Completion Trigger Action per milestone, or they silently do nothing.
“Can't update shipment fields after customs declaration commenced”
Field locking is by design. The front-loading and parallel-charge-record patterns that survive it.
“Jobs created via eAdapter are missing the defaults the UI applies”
API jobs skip the UI defaults engine entirely. How to rebuild it with precedence rules on your side.
What's inside
8 Chapters, Zero Filler
From the single-outbound-URL relay problem to replay harnesses — every chapter comes from documented production experience, not docs regurgitation.
Chapter 1 · Free preview
The Production Reality Check
What changes when eAdapter runs the business: async everything, status elsewhere, one outbound pipe. The eHub vs E2E vs eAdapter decision framework.
Chapter 2
The Single Outbound URL Problem & Relay Architecture
CW accepts exactly one SOAP endpoint. Relay and fan-out design: queue, dead-letter queue, per-consumer routing, idempotency, and replay.
Chapter 3
Message Status Visibility
SendStreamRequest returns a UUID, not a result. Polling the EDI Interchange, correlation IDs end-to-end, and alerting that catches "stopped flowing" before the customer does.
Chapter 4
Workflow Triggers & Milestones
Tasks vs milestones vs triggers. Completion Trigger Actions, the milestone→message→destination matrix worksheet, and the XUE vs XUS decision rule.
Chapter 5
Field Locking, Customs, and Data You Can’t Touch
What locks when a customs declaration commences. Front-loading patterns, parallel AR/AP charge records, and the amend-declaration route.
Chapter 6
The Defaults Gap & Hidden Fees
Why API-created jobs skip UI/org/UNLOCODE defaults and how to build your own defaults engine. DOM-CWAF automation fee mechanics and UTC date-field traps.
Chapter 7
Operating at the Edge
Request timeouts on every CW endpoint, beating serverless time limits by splitting syncs, retry budgets, and scheduled credential health checks.
Chapter 8
Test Environments, Fixtures, and Replay
A test-environment strategy that survives CW upgrades, version-controlled XML fixtures as your regression suite, and a replay harness for production messages.
Get first access
The guide is being written now. Join the list for early access and a launch discount.
Already own Vol. 1? You get first access automatically.