IndustriesLogistics

The exception is the job

When everything moves as planned, nobody needs to be involved. The entire operational cost of a freight business sits in the shipments that do not, and in the phone calls asking about them.

$100-250

typical demurrage cost per container per day

FreightAmigo, 2025

5-7 days

typical free time on imports before demurrage begins

FreightAmigo

+20%

increase in dwell times from congestion and disruption

FreightAmigo, 2025

Hours

the window in which an exception is cheap to fix, not days

Operational reality

Where the time and revenue actually go

These are the specific, measured problems in logistics and freight. Not generic digital transformation.

01

Exceptions are found late, when they are expensive

Free time on an import container is typically five to seven days, and demurrage runs from roughly a hundred to two hundred and fifty dollars per container per day once it starts. The difference between catching a problem on day four and day eight is entirely a matter of whether anyone was watching.

02

Where is my shipment consumes the operations desk

The single highest volume enquiry in freight is a status request. The information exists in the carrier feed, the TMS and the customs system. It is a lookup, but it lands on a coordinator who is in the middle of solving an actual problem.

03

The documents are the freight

Bills of lading, packing lists, commercial invoices, certificates of origin and customs declarations. They arrive as PDFs, scans and photographs, in dozens of layouts, and a single mismatched field between two of them stops a container at a border.

04

Every carrier speaks a different dialect

Status codes, milestone definitions and event timing differ per carrier, so a unified view of a shipment requires reconciling sources that genuinely disagree about what has happened and when.

05

The knowledge lives with the long serving coordinator

Which customs broker to use for that lane, which carrier's ETA to distrust, what to do when a specific port throws a specific code. It is real expertise and it is almost entirely undocumented, which makes it a staffing risk.

06

Congestion has made the margins for error smaller

Dwell times have risen roughly 20 percent through congestion and disruption, which compresses the window in which an exception can still be fixed cheaply. The same process that worked in a calmer market now produces charges.

07

Quoting is slow because it is manual

A rate request requires checking lane rates, current surcharges, capacity and the customer's history. By the time a quote is produced the customer has often already accepted a faster one, and the faster one was not necessarily cheaper.

What we build for logistics teams

01

Proactive exception detection

Watches carrier feeds against the plan, detects the divergence when it happens rather than when someone notices, and raises it with the recommended action and the cost of doing nothing attached.

02

Track and trace answered from live systems

Status enquiries resolved against the actual carrier feed and TMS, in the customer's language, with the honest answer when carriers disagree rather than a confident one picked at random.

03

Document extraction and cross checking

Reads bills of lading, invoices, packing lists and declarations in whatever layout they arrive in, extracts the structured fields, and flags mismatches between documents before the container reaches a border rather than after.

04

Carrier milestone normalisation

Reconciles conflicting status codes and event definitions across carriers into one timeline, so a shipment has a single state rather than four competing ones.

05

Coordinator knowledge, written down and searchable

The lane specific and port specific knowledge that currently lives with two people, captured, cited and searchable, so a new coordinator is useful in weeks rather than in a year.

Two workflows, end to end

Illustrative composites, drawn from how these workflows actually run in each industry. Not named client engagements.

01Catching the exception while it is still cheap
The situation

A container discharges on a Friday. Free time is five days. The customs entry has not been filed because a commercial invoice value does not match the packing list.

What usually happens

Nobody notices until the broker chases on Wednesday. By the time the discrepancy is traced, corrected and refiled, free time has expired and demurrage is accruing daily on a container nobody can move.

What our system does

The mismatch is caught at document ingestion, before discharge, because the invoice and packing list were cross checked the moment both arrived. The coordinator gets one notification naming the two documents, the specific field, both values, and the deadline that is at risk with the daily cost attached. The correction is requested from the shipper the same day, and the entry is filed inside free time.

Steps the system took
01Documents cross checked on arrival, not at the border
02The specific conflicting field named, with both values
03The at risk deadline and its daily cost stated plainly
04Correction requested from the shipper immediately
05Coordinator decides the action, the system does the watching
02Taking the status calls off the desk
The situation

A customer emails on Tuesday morning asking where three shipments are, two of which have conflicting carrier milestones.

What usually happens

A coordinator opens the TMS, checks each shipment, opens two carrier portals to reconcile the conflicting events, and writes a reply. Twenty minutes, repeated across a queue, by the person who should be solving the exception from the previous scenario.

What our system does

The system answers from the live feed and the TMS, gives the current position and revised ETA for each shipment, and where carriers disagree it says so explicitly rather than picking one, flagging that shipment for a coordinator to confirm. The routine two resolve immediately. The genuinely uncertain one reaches a human with the conflict already laid out.

Steps the system took
01Answered from the carrier feed and TMS, not from a static record
02Conflicting carrier milestones surfaced rather than hidden
03Routine enquiries resolved without a coordinator
04The uncertain case escalated with the conflict already summarised
05The reply logged against the shipment record

Wired into the logistics stack you already run

Transport management

  • Descartes
  • project44
  • FourKites
  • MercuryGate
  • Shipwell

Carrier and visibility

  • Carrier EDI and API feeds
  • Port community systems
  • AIS tracking
  • Container milestones

Customs and documents

  • Customs filing systems
  • Bills of lading
  • Commercial invoices
  • Certificates of origin

Business systems

  • NetSuite
  • SAP
  • Salesforce
  • Zendesk
  • QuickBooks

Start with one logistics workflow

A 30 minute audit, no sales pitch. We map where automation can cut manual work and create measurable ROI across the tools you already use.