Help for owners
Every refund and cancellation is handled by hand across three systems
Short answer
Refund automation applies the same steps whenever an order is cancelled or returned: stop fulfilment, return the money, update stock and the books, tell the customer. The risks are double refunds, refunds without a matching return, steps done in the wrong order, and books that no longer match the payment provider.
Does this sound like your situation?
- A cancellation needs me in the shop, the payment dashboard and the accounts.
- A customer was refunded twice.
- A cancelled order was still shipped.
- The refunds in my books do not match what the payment provider shows.
- Customers ask where their money is and nobody can say.
Why does this happen?
Several systems each hold a part of the story
The order is in the shop, the money in the payment provider and the invoice in accounts. A refund in one place does not update the others unless something connects them.
The same event arrives twice
Notifications from payment and shop systems are sometimes delivered more than once. If the automation does not recognise a refund it has already processed, it can repeat it.
Order of steps matters
Stock should return only when the goods are back, and the credit note should match the amount actually refunded. Doing steps in the wrong order leaves wrong stock and wrong books.
Partial cases
Part of an order cancelled, a shipping fee kept or one item returned need amounts calculated per line. A flow built for full refunds gets these wrong.
No rule for who approves
Refunding money is irreversible for the business. Without limits and approvals, an error or a misuse goes straight through.
What can I do about it today?
- Write your refund policy in plain stepsWhen a refund is due, how much and in what form. The automation can only follow what is written.
- List each system a refund touchesShop, payment provider, accounts, stock and customer messages, with who owns each.
- Keep a person on the money stepEven if the rest is automated, someone approves the actual payout, at least above an amount you set.
- Check a month of refunds against the booksCompare the provider's list with accounts. Mismatches show where the process leaks.
- Tell customers what happens nextA clear message with what you will do and what the customer has to do, in your own words.
When should I bring someone in?
- Refunds have been duplicated or paid out wrongly.
- Your payment provider sends notifications to your own software that must be handled correctly.
- Subscriptions, partial returns or several currencies are involved.
How do I handle it?
- Map one refund from request to booksEvery step and system, in order, including the partial and failed cases.
- Make each refund happen only onceEach refund carries a unique reference, so a repeated notification is recognised and skipped.
- Put approval where the money movesRefunds above a limit, or outside the policy, wait for a named person.
- Reconcile automaticallyA daily comparison of the payment provider, the shop and the accounts flags any difference.
- Follow each provider's documentationI read your payment provider's current refund and notification documentation first, so I do not rely on assumptions.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Can refunds be fully automatic?
For small, clearly eligible cases it can work. I recommend a person approves larger or unusual ones.
What about refund rules for consumers?
They depend on your country and product, and I do not give legal advice. Your policy is the input, and a lawyer or adviser can confirm it.
Will the books update by themselves?
Yes where your accounting software has a documented way to receive credit notes or adjustments. I check yours first.
How was this page made?
I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.