Release status
Released
Gate appointment in
08:42
Free storage ends
3d
What this means
The container is released and the gate slot is confirmed. Dispatch a truck before the window closes or storage charges start in three days.
Built for the decision, not the dashboard.
Release-first tracking
Release status and the gate-appointment countdown are the headline, not a map pin. It is the number your agent phones about.
Push, not pull
The moment a terminal, carrier or customs event lands, the parties who care are notified — in-app and on WhatsApp.
Decision translation
Every shipment carries a plain-language 'what this means' card: the next action, who owns it, and the cost of waiting.
Chain of custody
Collection slots are accepted and completed by a named driver, closing the last mile the rest of the market leaves open.
Demurrage clock
Free-storage deadlines are tracked per container so the detention bill stops being a surprise at month end.
Signed integrations
HMAC-signed inbound webhooks per industry and a keyed read API, so partner systems plug in without a data-entry team.
Documents that read themselves.
Bills of lading, commercial invoices, packing lists, SAD500 declarations and release orders go in as text. Structured shipment data comes out — container and BL numbers, parties, ports, HS codes, customs values, free-time expiry — cross-checked against the shipment on file, with every discrepancy that will stop the container flagged before the terminal finds it.
Extract
One parser for every trade document type. Fields land straight on the shipment record instead of being re-keyed three times by three parties.
Reconcile
BL against invoice against declaration. Mismatched container numbers, missing HS codes and unclassified goods surface as critical flags with the action to take.
Escalate
A critical flag marks the document for review and feeds the alert engine, so the clearing agent hears about it days before demurrage starts.
Extraction is assistive. Rules decide release status — never the model.
The ecosystem. Connected.
CARGOPULSE bridges disparate legacy systems with standardised, signed telemetry.
Shipping Lines
Carrier APIs and EDI translated into one event stream: load, sail, transhipment, discharge, ETA change.
Port Terminals
Navis-grade stack, release and gate telemetry, plus yard occupancy and berth-wait context.
Customs & Agents
Declaration acknowledgements, stops, inspections and release — matched to the right container automatically.
Cargo Owners & Drivers
One answer to the only question that matters: can I collect it, and when. Drivers accept the slot in-app.
One endpoint per industry.
Every partner pushes into a signed webhook scoped to their role. Cargo owners read back through a keyed API. No spreadsheets, no re-keying.
| Industry | Method | Endpoint |
|---|---|---|
| Shipping line | POST | /api/public/integrations/shipping-line |
| Port terminal | POST | /api/public/integrations/terminal |
| Customs & declaration | POST | /api/public/integrations/customs |
| Transport & drivers | POST | /api/public/integrations/transport |
| Cargo owner (read) | GET | /api/public/shipments/{reference} |