Delivery Agent

The Delivery Agent owns the moment of the drop. Where the Route Agent decides the sequence of stops, the Delivery Agent runs what happens at each door — it broadcasts live ETAs to the outlet as the van moves, captures structured proof of delivery at the point of handover, and reconciles what was ordered against what actually arrived. Signatures, condition photos, crate and case counts, returns, refusals and short-ships are all captured as typed events rather than as paper or loose notes, so the delivery is closed out the instant the driver leaves the curb.

In the field it behaves as a working agent, not a tracking screen. It watches each route in flight and recalculates arrival windows as traffic, dwell time at prior stops and re-sequencing shift the plan, then pushes a fresh ETA to the receiving store so a manager is at the dock when the truck pulls in. When a delivery goes sideways — a locked store, a rejected pallet, a damaged case, a quantity that doesn't match the manifest — the Delivery Agent recognises the exception, prompts the driver for the right proof, and routes the discrepancy to the people who resolve it instead of letting it surface days later as a dispute. Because it consumes and emits on the same data model as the rest of the platform, the order, the route, the load and the proof all describe one shared object rather than four systems that have to be stitched together after the fact.

Once a drop is confirmed, the Delivery Agent closes the loop back through the route to market. Proof of delivery and any exceptions flow to the Settlement Agent so invoicing and claims start from clean, evidenced quantities; back to the Route Agent and the Inventory Agent so tomorrow's plan reflects what genuinely got delivered and what came back; and into the outlet's history so the next visit is briefed on what was short-shipped or refused. For direct store delivery, van sales and B2B fulfilment alike, it makes the delivery the system of record rather than the gap in it.