A refund request may be worth only a pound or two, but it can still create a messy trail. A customer contacts the site, the site calls the operator, somebody pays cash from a till and the same request reaches the office again a day later. Without a clear record, nobody can tell whether the case is open, settled or duplicated.
A simple refund process protects the customer relationship and keeps the vending figures intelligible. It does not need to turn a small complaint into a lengthy investigation.
Give every request one route into the business
Decide where refund requests should go. That might be a business telephone number, a monitored email address or a short web form shown on the machine. Site staff should know the route too, especially if they sometimes reimburse customers from their own till.
The important part is consistency. A message left with a driver, a note behind a bar and an email to the office should not become three separate refunds. Give each request a reference when it arrives, even if that reference is simply the date plus a sequential number.
Record enough to identify the sale
A useful vending machine refund record normally includes:
- the date and approximate time of the purchase;
- the site and machine involved;
- the product selected and amount paid;
- whether payment was by cash or cashless;
- what went wrong, such as no vend, double charge or damaged product;
- how the customer wants to be contacted, if contact is needed;
- who received the request and its current status.
For a cashless sale, use the transaction reference supplied by the payment provider where one is available. Do not ask the customer to send a full card number, expiry date or security code. The payment provider’s own dashboard and refund procedure should be the source for payment checks.
Check the facts without making the customer do the detective work
Start with the information you already hold. Check the machine or site record, recent fault reports, the cashless payment dashboard and any previous requests under the same reference. A driver visiting the site can test the selection and look for a jam, but the refund should not sit unresolved simply because the next visit is several days away.
The Consumer Rights Act 2015 sets standards for goods sold by traders, including satisfactory quality and being as described, and sets out remedies when goods do not conform. Your internal process should help staff reach a fair decision and record it. It should not be used to create unreasonable hurdles over a low-value complaint.
Keep the refund separate from the collection count
A refund is not the same thing as a counting correction. Silently reducing a machine’s collection total to absorb a refund makes the cash-up harder to explain later.
Record what was collected from the machine, then record the refund through the appropriate route. If cash came from the safe or a site till, note the amount, date and person who authorised it. If the payment provider returned a cashless payment, keep its refund reference. If the customer received a replacement product instead, record that outcome rather than calling it a cash refund.
If the collection itself does not match the expected figure, deal with that as a separate issue. The VendMetrix guide on handling a small cash discrepancy sets out a calm process for checking and recording the difference.
Use clear case statuses
A short status list prevents cases from disappearing into an inbox. For example, use received, checking, approved, declined and settled. Add the date of the latest action and name the person responsible for the next step.
Define what settled means for each payment route. A promise to refund is not the same as a completed provider refund, cash handed to the customer or a replacement collected from the site. Store the settlement reference or a brief note so another member of staff can see what happened.
Keep customer details under control
A refund record may contain a name, telephone number, email address or payment reference. The ICO’s guide to the data protection principles says personal data should be adequate, relevant and limited to what is necessary. It should also be kept no longer than needed and protected appropriately.
Collect only the details needed to resolve and evidence the case. Restrict access to staff who handle refunds, set a retention period and remove customer contact details when there is no longer a reason to keep them. Avoid putting refund information into personal messaging accounts or loose notebooks that cannot be controlled.
Review patterns, not just individual complaints
One refund may be a one-off. Several requests involving the same machine, product column or payment terminal deserve attention. Review refund records alongside fault notes, visit history and takings before changing a route or replacing equipment. The log gives you a lead to investigate, not proof of the cause by itself.
VendMetrix’s live features page confirms cash-up records, corrections kept in an audit trail, a running safe balance, bank deposit records and team permissions. It does not currently list a dedicated refund log. Operators using VendMetrix should therefore keep an approved refund record alongside those financial controls unless their own process already provides one.
A short closing check
Before marking a case as settled, check that the original request, decision, payment route, outcome and settlement reference are all present. Confirm that any cash movement has not been hidden inside the machine count and that unnecessary customer data has not been retained.
A good refund record lets the next person understand the case without calling the customer again. That is the standard to aim for.