Template, not built for a specific business

A promised collection window that nobody can check isn't a promise, it's a guess

Businesses that promise to collect a delivered item, container, or unit by a certain date often run that promise entirely on memory and phone calls: no reference number at booking, no shared view of which jobs are approaching or past their promised window, and a customer's only way to check is to call in and be told "it's not allocated." And if a charge beyond the original quoted price comes up after the fact, it can reach an invoice before the customer ever agreed to it. This page shows one small, working tool that closes both gaps: every order gets a reference number and a locked, visible collection window the moment it's booked, a dispatch queue flags any order approaching or past that window automatically, sorted most-overdue-first, a no-login customer lookup shows the same status without a phone call, and any charge beyond the original quote is itemized and held until the customer explicitly acknowledges it, before it is ever billed.

Everything below is fictional. When this gets built for a real business, the order queue reads from whatever already takes bookings (a phone log, a spreadsheet, a booking form), and the charge-authorization gate sits in front of whatever system already invoices customers, it does not replace either one.

Log a new order

A real build gives this same locked window to the customer the moment they book, not only to staff.

Orders, most-overdue-first

Check your order

Try REF-1001, REF-1002, REF-1003, REF-1004 or REF-1005 from the dispatch queue's sample orders.

How this gets built for real

The reference number is handed out the moment a real order is booked. A real build reads from whatever already takes the booking (phone, a form, a POS) instead of inventing a second system.
The collection window is a real commitment, not a guess. Once it's overdue, the order stays flagged and sorted to the top of the queue until someone logs a collection, instead of only surfacing when a customer calls to complain.
A charge beyond the original quote genuinely cannot be billed without customer acknowledgment. Staff can itemize it with a reason, but it sits held until the customer checks a box and types their name from their own status page.
"Acknowledged" here is a typed name and a timestamp. A real build can add an actual e-signature provider for a stronger record; this demo shows the workflow, not a specific vendor.
See it built for a real business: M50 Skip Hire & Recycling.