Warehouse, fleet and documentation joined up, so a shipment has one status

One record, one status

The defining problem in logistics IT is not capability. It is reconciliation. The warehouse system says dispatched, the accounts system says not invoiced, the customer service spreadsheet says awaiting documents, and all three are partly right.

The fix is unglamorous: one system of record per fact, with the others reading from it rather than keeping their own copy. Deciding which system owns which fact is most of the work, and it is a business decision more than a technical one.

Offline-first, not offline-tolerant

A warehouse has dead zones. A truck spends hours without signal. Any app that needs connectivity to record an event will be worked around, and the workaround is paper.

So we build the other way: capture locally, queue, sync when a connection appears, resolve conflicts explicitly. The driver never waits for a signal bar, which is the only reason the app gets used.

Documentation is where the hours go

Commercial invoice, packing list, certificate of origin, customs declaration: mostly the same data, retyped per document, per consignment, by someone senior enough to know the rules.

Generated from the shipment record instead, with the exceptions flagged for a human, this is often the single highest-return automation available to a trading business.