Did they pay when they dropped it off?
A customer collects a coat and two jackets. The assistant on the counter this afternoon was not on in the morning when they were dropped off. The ticket has a total, a tick, and a scribble. The customer says they paid already. The assistant believes them and hands the order over.
At the end of the week, the till does not match. A few orders were collected with no payment recorded anywhere. Others were charged at drop-off and again at collection, and one of those customers has already rung to complain.
Nobody took anything. The payment status was simply unclear, and the assistant made a reasonable guess.
Busy periods make it worse. On a Saturday with a queue, nobody wants to make a regular wait while they dig through the drop-off records, and the easy answer is to trust the customer and move on. The same thing happens with part payments for alterations and deposits on wedding dresses, where the amount outstanding is written on a ticket in pencil.
Payment status lives in several places
In a typical shop, payment can happen at drop-off, at collection, by account, by the van driver, or partly at each. Each route is recorded differently, and the ticket at the counter shows none of it reliably.
- Tickets show a total but not clearly whether it has been paid.
- Part payments and deposits are noted by hand.
- Delivery payments are taken by the driver and entered later.
- Account customers look the same as unpaid customers at the counter.
- There is no end-of-day check of collected orders against payments.
Small leaks and awkward refunds
Each unpaid collection is a small loss, but they add up over a year. Double charges cost you in refunds and goodwill. Staff feel awkward asking a regular if they have paid, so they do not ask. And without a daily check, problems are only found at a monthly reconciliation when nobody can remember the details.
How we make payment status visible and checked
- Every ticket carries a payment status that updates automatically: unpaid, part paid, paid, on account, or pay on delivery.
- Card and cash payments at the counter update the status straight away. Driver payments update it from the driver's app.
- When the ticket is scanned for collection, the screen shows the status in large colour. An unpaid ticket needs payment or a manager override with a reason before it can be marked collected.
- Printed tickets and tags can show a simple paid mark, so staff at the rail can see it too.
- At closing, a short reconciliation lists every order collected today with its payment, and flags any collected unpaid or charged twice.
- Payments flow into your accounting software, such as Xero or QuickBooks, as a daily summary.
| Customer says | Today | With payment status |
|---|---|---|
| I paid when I dropped it off | Believe them or argue | Screen shows paid or not |
| I paid half | Scribble on the ticket | Part paid with amount |
| It goes on the company account | Check a folder | On account status |
| The driver took my card | Entered later, maybe | Updated from the driver app |
If your point of sale already tracks payment status well, the change may just be making it visible at collection. We will say so if that is all you need.
Collections without the guesswork
The afternoon assistant scans the ticket and sees paid in green. The morning assistant's shift and the afternoon's no longer need to hand over a list of who paid what.
Accounts customers show as on account rather than unpaid, so nobody asks them for money they are not meant to pay at the counter. No awkward question for the customer. When it shows unpaid, the assistant asks politely, and the conversation is backed by the record. At closing, the manager looks at a one-screen reconciliation instead of a weekly puzzle.
Is money slipping out with your orders?
- Staff are unsure whether an order has been paid.
- You have found orders collected with no payment.
- Customers have been charged twice.
- Driver payments are entered at the end of the day or week.
- The till rarely matches collections exactly.