Playbook, online store
Money going backwards, and the days nobody in the shop controls
A returns policy question is asked by somebody deciding whether to buy. A refund question is asked by somebody who has already sent the thing back and is now watching a bank app. The two get filed together and they are not the same job. This one is about money in transit between three parties, only one of which is the shop, and the customer's word for all three stages is the same word.
Why this is not the general answer
The handling pattern for refund requests holds across every trade. What follows is the part that does not.
- Customers use return, refund and chargeback interchangeably, and the three are separate processes with separate timings and separate consequences. Working out which one is actually happening is most of the job in the first reply.
- The refund clock in almost every published policy starts when the goods arrive back and are checked, while the customer is counting from the day they walked to the post office, so the two parties are several days apart before anybody has done anything wrong.
- The money returns to the card, wallet or account it came from and cannot be redirected, which is a technical constraint rather than a policy the shop chose, and it comes as news to anybody whose card has since expired.
- After the shop releases the refund there is a second wait at the card issuer that nobody in the shop can see, shorten or confirm, and that invisible half is where almost all of these messages come from.
How it arrives
- how long does a refund take to show up
- i sent it back two weeks ago and heard nothing
- can you refund me to a different card
- do i get the delivery charge back too
- why is my refund less than i paid
- can i have a refund instead of an exchange
What has to be indexed for this to work
| The refund timetable, written as two halves | The working days from goods received back to refund released, stated separately from the wait at the card issuer afterwards. Policies publish one number and customers experience the sum of both, and that gap is where every one of these messages lives. |
|---|---|
| What comes back and what does not | The outbound delivery charge, the return postage, gift wrapping, and how a discount is reapportioned when one item out of a multibuy goes back. That last one is why a refund lands smaller than expected and reads as a deduction nobody mentioned. |
| Where the money is allowed to go | The original payment method rule, what happens when that card has expired or been cancelled, how wallet and split payments behave, and whether store credit is ever offered instead. Write it as a constraint rather than a preference, because that is what it is. |
| What you accept as evidence something was sent back | Proof of postage, a tracked service, a drop-off receipt, and who carries the risk while the parcel travels back to you. A customer who used an untracked service and a shop with no record of arrival is an argument decided entirely by what this document says. |
The reply
I cannot see payments, so I have no way of telling you whether yours has gone through. What the policy says is that a refund is released within the published number of working days from the parcel arriving back with us and being checked, which is a different starting point from the day you posted it [1]. Once we release it, the card issuer adds its own wait before it shows on a statement, and that part is outside our control. The delivery charge you paid on the original order comes back on a full return but not on a partial one [2]. If it has been longer than the published window since your return was delivered back to us, send your order number and the checkout email to our contact address and somebody will open the payment record.
The refusal comes in the first clause so nothing after it can be read as a lookup. It then moves the date the customer is counting from, which is the actual disagreement, before quoting any number at all. Naming the issuer wait as a separate stage stops people writing again the day the shop's own window closes, and putting a threshold on the escalation means the person who genuinely has waited too long knows they are the one who should send it.
Where it stops
The trigger. The visitor gives a date they posted something, quotes an order number, says the amount is wrong, or mentions their bank, a dispute or a claim.
I cannot see payments, so this needs somebody who can open the order. Leave your name, the email address you checked out with and your order number, along with the amount you were expecting, and the team will check the payment record and come back to you.
It stops answering before it guesses, says who will pick it up, and asks for the one thing that makes a reply possible. Nothing about it reads as a dead end.
Never say this here
Out of bounds
- Never confirm that a particular refund has been issued, approved or is on its way, because the payment record is not something the assistant can read and a customer told the money is coming stops chasing it.
- Never name a day the money will appear, since the second half of the wait belongs to the card issuer and nobody at the shop can influence it.
- Never offer to send a refund to a different card, a bank account or a gift card, whatever the customer says has happened to the original one.
- Never tell somebody to wait a little longer once they have mentioned their bank, because a card dispute starts a response deadline and the shop needs to know that day.
Questions
- Can it tell a customer whether their refund has actually been sent?
- No. There is no page anywhere on a shop containing one customer's payment, so there is nothing to read. It can quote the timetable, correct the date they are counting from, and get the two identifiers to a person, which handles most of the volume without pretending.
- Is it worth publishing the issuer delay separately?
- It is the highest value sentence in the document. Customers hold the shop responsible for the whole wait because the policy only ever describes the first half of it. Splitting the two in writing turns a complaint into a shrug.
- Somebody says they are going to their bank. What should it do?
- Take the details and hand over immediately, with no attempt to talk them out of it. A dispute starts a clock on the shop to assemble evidence, and a reply in a chat window does not count as a response to it.
Keep reading
- Everything for a online storeDelivery cut-offs, the returns window and restock questions get asked before purchase. The one thing an assistant cannot do is find an order.
- Handling refund requests in generalA refund question is really about eligibility and timing. What to index, what the reply may promise, and where it has to reach a person.
- It is already on a pick list, which is the whole answerStopping an order ends when the pick starts. The window to change your mind ends much later. Two rights wearing one word.
- The claim belongs to the shop, not to the person with the empty porchThe carrier contract is with the seller, so the buyer cannot claim at all. The window is short and it started at dispatch.
- Never quote a figure the catalogue can change while you typeA catalogue price changes without notice, so an indexed copy of it goes stale within hours. Quote the rules around it instead.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.