The warehouse and the office, looking at one number

One screen showing what goes out today, what is due back, what is already overdue, counts waiting to be accepted, and units sitting in maintenance. Every figure on it opens the list it counted, filtered exactly the way the number was worked out.

The load-out screen counts each line as it is loaded, so the booking holds both what was promised and what physically went. Loading short is recorded rather than argued about later, and the return reconciles against what left rather than against what was ordered.

It holds the van, the crew and the day for each run, and creates the collection run the moment a delivery is scheduled so a due-back date is never quietly forgotten. Booking the same vehicle or the same person twice in one day is refused unless somebody overrides it by name - though a morning drop and an afternoon pickup are an ordinary day, not a clash.

The conflicts screen lists every booking contending for those units, in the order they go out, with the size of each claim and the customer behind it. Knowing an item is short does not help; seeing whose orders are competing for it is what lets somebody decide.

Yes, for every quantity in the system. The audit log is filterable and paged, and an item's own history merges its adjustments with the bookings it went out on, so a single item's page tells you it went to a wedding and what came back, not only that a number changed.