Integrations

Customs Gateways

National single windows, AEO filings, and the hold that has to reach the planner.

Overview

Customs Gateways in one paragraph.

Anchora files to the national customs gateway in the message format it expects, tracks the response, and propagates a hold into the berth and yard plan as a constraint rather than as a notification.

Adapters exist for the single-window deployments in the countries where we run today. A new country is a scoped integration, typically three to five weeks, and the message mapping is documented before we write code.

6
Live gateways
3–5 weeks
New country
Hold
Becomes a constraint
IMDG
Declarations included

Coverage

What we integrate with today.

If your system is not listed, it is a scoped integration, not a refusal.

GatewayDirectionNotes
Netherlands (Portbase / DMF)Read and writeAEO filings and manifest amendments
Greece (ICISnet)Read and writeIncluding IMDG declarations
Sweden (Tullverket)Read and writeImport and export declarations
UAE (Dubai Trade)Read and writeMirsal 2 message set
Romania, Lithuania, LatviaRead and writeNational single-window adapters
New countryScopedThree to five weeks, mapping documented first

Next step

Talk to a senior solutions engineer.

Your first call is with an engineer, not a sales-development representative.