Logistics automation solutions

We automate the exception-heavy middle of freight forwarding: WISMO traffic, milestone and POD chasing, customs data capture, carrier invoice reconciliation, demurrage watch. It is all built around the TMS you already run — CargoWise, BoxTop, Magaya — reading the job file rather than replacing it. Your operators keep the judgement calls; the five-tab lookups go.

Use cases

• Answers WISMO emails from live TMS milestones and carrier tracking instead of an operator opening five tabs
• Extracts commercial invoice and packing list data into draft CDS entries, tariff codes flagged for broker review
• Watches carrier schedules for rolled sailings, updates ETAs in the TMS and pre-alerts affected customers
• Reconciles carrier invoices against quoted rates and D&D terms, routing mismatches to the exceptions queue
• Chases hauliers for PODs and delivery confirmations so job files close without an operator on the phone
• Builds pre-alerts and arrival notices from HBL and manifest data already sitting in the job file
• Tracks free time per container and warns the desk before demurrage and quay rent start accruing
• Creates GMRs in GVMS and checks T1 transits are discharged so guarantees do not sit open

Common workflow problems

• The WISMO inbox eats the morning while operators answer questions the TMS could answer itself.
• You learn a booking was rolled from the customer's email, not the carrier's schedule change.
• Carrier invoices land with D&D charges nobody can match to the quote, and the dispute window quietly closes.
• CDS entries wait on commodity codes because the commercial invoice arrived as a scanned PDF at 17:40.
• Job files sit open for weeks waiting on PODs, so WIP accruals and job profitability are guesswork until month-end.

How we help

• We connect to your TMS through supported routes — eAdaptor for CargoWise, APIs for BoxTop and Magaya — plus carrier EDI and tracking feeds.
• Customer-facing answers are grounded in the job file and live milestones, with the source attached, so the desk can stand behind them.
• Extracted entry data is validated against tariff and procedure-code rules, and low-confidence fields queue for a human before anything files.
• Exceptions escalate with the whole picture — thread, job file, carrier correspondence — to a named operator, not a shared inbox.
• Everything runs on EU-hosted infrastructure, segregated per client and never used to train shared models, with every action logged for your AEO and GDPR obligations.

Systems we work with in this sector

We build around your existing stack: CargoWise, BoxTop or Magaya as TMS; ASM Sequoia or Descartes filing into CDS and NCTS; port community systems such as Destin8 and Portbase; container tracking feeds like Vizion.

Frequently asked questions

Customs data, rate cards and our customers' commercial invoices would flow through this. How is that handled?

Everything runs on EU-hosted infrastructure under a data processing agreement, segregated per client and never used to train shared models. Automations see only the job data they need, and every read and write is logged — a trail your AEO record-keeping can point to. Rates and customer terms stay inside your boundary.

We live in CargoWise with years of custom workflows and reports. Does this mean re-platforming?

No — we integrate through eAdaptor and the CargoWise APIs, or the equivalent on BoxTop, Magaya and Riege Scope, reading the job file where it already lives. Milestones, documents and events write back through supported interfaces, so your workflows, triggers and reports keep working. Where a partner system has no API, we work with structured exports and EDI.

Will it classify goods and submit declarations by itself?

No, and we would not build it that way. Tariff classification and declaration submission carry legal liability, so a competent person reviews and submits — and dangerous goods documentation we leave alone entirely. The automation earns its keep on capture, validation and drafting; the entry clerk's judgement stays in the loop.

Where does a forwarder usually start?

The WISMO inbox or carrier invoice reconciliation — high volume, low risk, easy to judge honestly. We deploy against one desk or one trade lane, ground it in your TMS data, and you watch the exception queue rather than a slide deck. If it earns a second desk, extend it; no per-seat licensing pushes you to go big early.

Relevant ways we support this sector

• Business Automation Solutions — Practical automation built around the way your business already works.
• Software Development — Any software, any tool, any commercial format — built to own, white-labelled under your brand, or run as your product.
• Process Audits — Find where time, accuracy, and money are being lost before building anything.

Discuss this industry: [email protected]