Logistics
In logistics the software is always behind reality. The truck has already left, the pallet has already moved, the scan happened four minutes ago in a yard with no signal. Systems that assume otherwise produce confident answers that are wrong.
Your data is a lagging, incomplete record
A consignment's state arrives from carrier APIs of varying honesty, driver devices that were offline, EDI messages in inconsistent dialects, and scans that occasionally happen out of order. Treating any of it as the authoritative present tense is the root of most logistics data problems.
What works is modelling events rather than current state — an append-only record of what was reported and when, with current position derived from it. That makes late and out-of-order arrivals a normal case instead of a corruption, and it means you can answer what you knew at the time, which is the question that matters in a dispute.
Where we work
Transport management
Planning, tendering and execution across carriers, including the exception handling that is most of the operational day.
Route optimisation
Constraint-aware routing that accounts for time windows, vehicle limits and driver hours, and degrades sensibly under a tight deadline.
Warehouse systems
Receiving, picking and inventory accuracy, designed for handheld use in cold, noisy places by people wearing gloves.
Track and trace
Shipment visibility that reconciles conflicting carrier reports rather than displaying whichever arrived last.
Freight settlement
Rating, audit and invoice reconciliation, where the disagreement is usually about which accessorial applied.
Carrier and EDI integration
Onboarding carriers whose interfaces range from a clean REST API to a fixed-width file at 2am.
Exceptions are the product
Almost every logistics interface is designed around the shipment that goes to plan, and almost every hour of operational effort goes to the ones that do not. A screen that shows a green path beautifully and buries the failed delivery three clicks deep has optimised for the wrong case.
We design the exception path first: what an operator sees when a scan is missing, a carrier contradicts itself, or an address will not geocode. Getting that right is worth more than any amount of dashboard polish, because it is where the labour actually is.
Event-sourced shipment state, so late data is normal rather than corrupting
Exception queues designed as the primary workflow, not an afterthought
Conflicting carrier reports reconciled with a visible, explainable rule
Offline-tolerant mobile capture, syncing without duplicate events
Time zones and daylight saving handled once, properly, at the boundary
Common questions
Practically, yes, though effort varies enormously. A modern REST API is days; a carrier with a bespoke EDI dialect and no sandbox is weeks, most of it spent discovering undocumented behaviour. We size each one individually rather than quoting an average that will be wrong in both directions.
Keep exploring.
Ready to start your project?
Get a free technical discovery call. We'll map the right team, stack, and timeline to match your goals — no obligation.