Logistics platforms, built for the exception rather than the parcel.

Network model: nodes, lanes and service levels

What your network physically is, before any software describes it. Origin and destination points, the hubs between them, which lanes you operate yourself and which you buy, and the service levels you sell against each. A platform that models a delivery as a straight line from sender to receiver cannot express a hub, a consolidation or a subcontracted leg.

Service levels are commitments with money attached. Same-day, next-day and economy are different promises with different costs and different consequences when missed, and if your contracts carry service credits then the platform is measuring your own liability.

The output is a network model that expresses legs, handovers and the party responsible at each point.

Consignment, custody and the handover record

Every movement of goods is a chain of custody, and every handover is a transfer of liability. Who held the consignment, from when, in what condition, and who accepted it next are the facts that decide a damage claim months later. Software that records location without recording custody answers the interesting question and misses the expensive one.

The consignment model itself needs care. A shipment can be one parcel or a pallet of many, can be split across vehicles, consolidated with others, and partially delivered. Modelling it as a single trackable object breaks the first time a pallet is broken down.

Proof of delivery is the end of the chain and it is evidence rather than a status. A signature, a photograph, a name, a time and a place, retained for as long as a claim can be raised.

Routing, capacity and dispatch

Routing in logistics is a constrained optimization rather than a shortest-path lookup. Vehicle capacity by weight and volume, driver hours, time windows agreed with receivers, loading sequence so the first drop is not at the back, and vehicle restrictions on certain roads all constrain the answer simultaneously.

Address quality is the constraint nobody budgets for and it dominates real-world performance. Incomplete addresses, informal addressing in many markets, and delivery points that differ from the postal address are the leading cause of failed first attempts, and geocoding alone does not solve it. Captured delivery points, learned from successful deliveries, do far more.

Dispatch has to survive the day changing: a vehicle breaks down, a receiver closes early, a driver calls in sick, and the plan made at six is wrong by ten.

Exceptions, and why they are the product

This is the phase that decides whether your operations team scales with volume or with headcount. Every exception needs a reason code that is specific enough to act on, a decision about what happens next, a notification to whoever is waiting, and a record that survives into a claim or a credit.

Generic reason codes are the common failure. "Delivery failed" tells nobody anything. "Receiver absent, second attempt", "address not found", "refused on condition" and "access denied at site" lead to four different actions, and a platform that cannot distinguish them cannot automate any of them.

Exception handling is also where customer experience is actually decided. Nobody remembers a parcel that arrived; everybody remembers how the failure was handled.

Rating, billing and carrier invoice reconciliation

Rating is deceptively hard. A price depends on weight, dimensional weight, zone, service level, fuel surcharge, residential or commercial delivery, and a contract that may differ per customer. Getting it wrong at quote time means either losing money on every consignment or losing the customer.

If you buy capacity from carriers, their invoices will disagree with your expectation, routinely and in their favour. Reweighs, reclassified surcharges and accessorial charges you did not anticipate are normal. Automated invoice reconciliation against expected cost per consignment is where operators recover margin they did not know they were losing.

Service credits close the loop: if a missed commitment triggers a credit, the platform must know it happened without a customer having to claim it.

Documentation, customs and cross-border

Crossing a border turns a delivery into a documentation exercise. Commercial invoices, classification codes, declared values, restricted goods and duty treatment all attach to the consignment, and an error holds goods rather than producing an error message.

Duty and tax treatment is a commercial decision with a customer-experience consequence: charged at checkout or collected on delivery. The second is cheaper to build and produces refused deliveries from customers surprised by a bill at the door.

Launch and day two

One lane or one depot, running real consignments alongside whatever you use today, because logistics failures are physical and a parallel period is the only way to find them without goods going missing.

Day two is the first billing cycle and the first claims, both of which arrive weeks after the first deliveries and test parts of the platform that launch does not. Sixty days of dedicated support, six months of priority bug resolution, twelve months of updates.