Slotting and delivery promises, driver apps, proof of delivery and failed attempts.
3 questions in Logistics & Supply Chain.
A slot shown at checkout has to be a reservation against remaining route capacity measured in minutes rather than a count of orders, and the flow behind it needs an offline-tolerant driver app, proof of delivery sized to the risk, and a designed path for the attempt that fails.
Treat the device as a first-class writer rather than a cache: it generates its own identifiers, records two timestamps per event, and queues durably until the network returns. Every submission carries an idempotency key because retries are certain, and genuine contradictions go to a human.
A failed delivery attempt in last-mile logistics is a structured event, not just failed status. The system must capture the allowed outcome, proof, attempt budget, customer notification and next custody location so redelivery, pickup or return can proceed safely.