Territory · Substrate signal
JAS publicly says they're investing in "digital tools and customs platforms to automate data validation and submission." HTS suggestion + pre-validation + Customs filing exception routing = straight Caddie surface.
The customs loop
What we read
"Investing in digital tools and customs platforms to automate data validation and submission." The mandate is named; the vendor / approach is not.
CargoWise extension to ICS2 (European e-commerce compliance) confirmed. The validation + filing layer above CargoWise is the wedge.
Plain-English query → cross-system read → drafted action → writeback in 90 minutes. Same engine handles HTS suggestion + ICS2 validation + filing exception.
Enmovil deployment baseline · Fortune 500 manufacturer
What Enmovil delivers here
AI-suggested HTS classification with confidence score + reasoning + audit trail · broker validates and approves.
Document pre-validation against ICS2 / AMS / Customs rules + carrier requirements · catches errors before filing.
When a filing fails or gets queried, Caddie routes the exception with full context to the responsible broker for one-tap resolution.
Proof anchor
90 min
Cross-system query → SAP writeback · Fortune 500 manufacturer · same engine
40 → 5 min
Manual reports compressed · same deployment
~99%
Estimated delivery accuracy across multimodal deployments
For the conversation
We would touch
We would not
First lane: one trade lane (e.g., Asia → US air freight) instrumented for HTS suggestion + ICS2 validation + filing exception routing, with broker-validation feedback loop.