CargoWise Integration Options Compared: eHub vs E2E vs eAdapter (2026)

Here is the least-told truth about CargoWise integration: the best eAdapter integration is often the one you don't build.

CargoWise (WiseTech Global's platform) offers three main integration paths. Teams routinely default to eAdapter because it's the one with "API" energy — and then discover they've signed up to own middleware, a relay service, retry queues, and monitoring, for a connection that a pre-built option would have handled.

If you only take one thing from this article: the default order of preference is eHub → E2E → eAdapter. Use the custom path only when the pre-built ones can't meet the need.

The three options, in one paragraph each

eHub is CargoWise's pre-built carrier connectivity: established connections to major ocean carriers, air carriers, and NVOCCs — some direct, some via service providers like INTTRA, CargoSmart, or Infor Nexus. CargoWise generates a Universal Shipment XML, sends it via eHub, and WiseTech maps it to each carrier's requirements. New connections to carriers not yet on the list are requested through an eRequest.

E2E Messaging is standardised message exchange over CargoWise's global network, between CargoWise users. It supports standard EDI formats (X12 850, 856, 315, EDIFACT equivalents) and — this is the part that matters — it can be activated without additional configuration or custom development when both parties run CargoWise. Messages are captured against the operational record, so you get an audit trail for free.

eAdapter is the custom integration interface: full flexibility, XML in and out, and full ownership of everything around it. It requires development resources — not "some scripting", but a real middleware layer you run in production.

The decision table

Two rules that prevent most integration messes:

1. Don't mix patterns without a strategy. Keep an integration strategy document mapping every trading partner to its option, and a registry that prevents duplicate flows. Mixing patterns ad hoc creates duplicated flows and inconsistent data.
2. Default to the simplest option that works. Pre-built connections need less maintenance than anything you own.

What each path actually costs

Nobody publishes a clean price list for CargoWise integration, so here is what's documented publicly as of mid-2026 — with sources, because unsourced cost claims are how integration budgets die.

Since 1 December 2025, CargoWise licensing runs on Value Packs: per-transaction pricing (~$19.95 for a full import container with inland leg, ~$9.95 for a standalone customs entry) with 216+ modules and unlimited users bundled. EDI/API connectivity is listed as included in the bundle — but the operational costs of each path are very different:

Two cost traps specific to eAdapter:

• The middleware is core infrastructure, not an afterthought. CargoWise users must host their own outbound service and middleware to manage queues, retries, transforms, and monitoring. Smaller forwarders underestimate this constantly and end up with fragile scripts that break in production.
• The automation fee shows up in your charge extracts. CargoWise posts a system-generated automation fee (DOM-CWAF) to every invoicing job — it can't be switched off. If you extract charges via eAdapter, it will appear in the charge list, and you need a deliberate strategy: pass it through to the customer as a disbursement, absorb it (filter it out of customer-facing data), or zero out the sell side via carefully constructed XML. Decide this as a business decision before building, not when the first confused customer invoice lands.

The knowledge barrier (and how teams actually learn eAdapter)

The eAdapter Developer Guide is not publicly available — WiseTech provides it only after a customer purchases the eAdaptor modules. Community knowledge is scattered thin across G2 reviews, LinkedIn, and consultant blogs; Reddit coverage of eAdapter is close to non-existent.

In practice, most teams learn the message mechanics from three open-source client libraries:

Commercial middleware exists too — Complect's eAdaptor Relay, Chain.io, Crossfire Integration — if you'd rather buy the relay layer than build it.

Whichever route you take: build at least one person's worth of internal eAdapter expertise, even if you use consultants. It dramatically reduces your dependency and response time when something breaks — and something will break, because eAdapter is asynchronous end to end and HTTP 200 does not mean your message succeeded.

If you do land on eAdapter: the five things waiting for you

Choosing eAdapter is choosing to operate it. These are the five failure modes that hit in year one:

1. The single outbound URL. One endpoint per instance — the moment a second system needs CargoWise data, you're building a relay.
2. Async everything. Sends return a tracking UUID, not a result. Status lives in the CW1 EDI Interchange, and you have to go get it.
3. Silent triggers. Workflow milestones can complete without ever sending a message unless Completion Trigger Actions are configured.
4. Field locking. Once a customs declaration commences, fields freeze — your updates silently stop applying.
5. The defaults gap. API-created jobs skip the UI's default population. Messages must be self-contained, or jobs arrive half-empty.

FAQ

Can I use E2E Messaging with a partner who doesn't run CargoWise? No — E2E is CargoWise-to-CargoWise. For a non-CW partner on standard EDI, you need eAdapter with an EDI transform, or a commercial EDI platform in between.

Does eAdapter use SOAP or plain HTTP? Both exist in the wild. The commonly documented interface is SOAP (eAdapterStreamedService.wsdl, SendStream), but instances also run plain HTTP+XML — no SOAP envelope, no GZIP, basic-auth header, raw XML body. Check how your instance is configured before writing a line of client code; assuming the wrong flavour costs days.

Is eAdapter included in CargoWise Value Packs? The modules are part of the bundled catalogue, but the Developer Guide remains gated behind the module purchase, and the infrastructure around eAdapter (middleware, relay, monitoring) is entirely your cost.

How many outbound endpoints can CargoWise push to? One. Exactly one outbound URL per instance. Everyone with more than one downstream system runs a relay — it's the single most load-bearing fact in eAdapter architecture.

This is the territory of eAdapter in Production (Vol 2) — Chapter 1 is the free preview, and the other seven chapters cover the five failure modes above in depth: the relay pattern, message status visibility, silent triggers, field locking, and the defaults gap. Start with Vol 1 ($99) → or join the Vol 2 waitlist →