Territory · Substrate signal

01Acquisition harmonization.

Three deals in 18 months — KLG (June 2024), International Airfreight Associates (February 2025), Pentagon Freight Services (November 2025) — adding ~1,300 staff and 70+ offices. Master-data, customer-mapping, and exception-routing across mixed forwarding stacks.

Where Caddie sits

Above CargoWise + acquired-entity stacks.

Customers · SmartHub portal · vertical-specific shippers

↓

CADDIE · agentic execution · cross-stack reconciliation · exception orchestration

↓

CargoWise (JAS USA + Japan)

KLG legacy stack

International Airfreight Associates legacy

Pentagon legacy (1,200 staff)

Caddie reads across the heterogeneous post-acquisition stack, drafts cross-system actions, executes on operator approval with audit trail.

What we read

Three deals · the integration debt.

KLG · June 2024

Outdoor industry + omnichannel logistics. Adds operational footprint to JAS USA.

Holland & Knight

International Airfreight · Feb 2025

100 employees · 4 countries · perishables and time-critical air. Amsterdam / Rotterdam / Frankfurt.

PR Newswire

Pentagon · November 2025

1,200 employees · 65 offices · oil & gas / marine / projects. Largest JAS acquisition to date. Onboarding 1,300+ heads while harmonizing onto CargoWise is the operational substrate.

JAS press

What Enmovil delivers here

Three moves · one orchestration layer.

Cross-stack read

Reads across CargoWise + KLG + International Airfreight Associates + Pentagon legacy stacks into one shipment view.

Exception drafting

When an exception fires in one acquired entity, Caddie drafts the cross-system action for operator approval.

Audit trail per action

Every drafted + executed action carries data lineage — auditable for the new ownership during transformation.

Proof anchor

Where we have shipped this shape.

~1,300

Staff added in 18 months · the harmonization scale

4 stacks

Heterogeneous TMS instances · the cross-stack read surface

40% / 30%

Fewer client inquiries · faster exception resolution · global lead-logistics provider

For the conversation

Questions, fence, timeline.

Are KLG, International Airfreight Associates, and Pentagon being migrated onto a single CargoWise instance, or run as federated entities? What's the harmonization horizon?
How is master-data mismatch (customer codes, lane codes, charge codes) being managed across the four stacks today?
Where would a first-lane pilot land — one acquired entity's book, one trade lane, or one customer cohort?

We would touch

Cross-stack read across CargoWise + acquired-entity TMS.
Drafted cross-system action + operator approval + audit trail.
Exception orchestration across 4 stacks.
Conversational query into systems of record.

We would not

CargoWise replacement (WiseTech is sticky).
Acquired-entity TMS replacement (coexistence only).
SmartHub replacement (extension only).
Vertical-specific compliance tooling.

8-12 weeks · one cross-stack flow

First lane: one operational flow that traverses CargoWise + at least one acquired-entity legacy stack, instrumented with audit trail. Cloud-native CargoWise integration runs longer than legacy SAP.