Store Returns: A Policy, a Status, and a Way Back into Stock
31 Oct 2026
A return is not a cancel button. It is an item that came back or did not, an amount refunded or exchanged, and a reason that should inform the next purchase. This guide separates what you tell the customer from what the warehouse and the accountant record.
A few weeks after launch, returns appear even in a tidy store: the wrong size, a colour that differed from the photo, or a late shipment. Without a path, a colleague promises the customer on WhatsApp and the warehouse never hears, or the warehouse receives a carton with no order number and shelves it as damaged to be safe.
Policy before screens
Write one sentence: within how many days, in what condition, exchange or refund, and who pays shipping. That sentence is shown before payment. The system applies what you wrote. It does not invent a longer window to calm an angry customer. If some items cannot be returned, such as an opened health product, say so on the item page, not in a general clause nobody finds.
Statuses that deserve names
- Requested: the customer asked and nobody has reviewed it.
- Accepted or refused: inside the policy or outside it.
- On the way back, or received in the warehouse.
- Inspected: sound and sellable again, or damaged and not.
- Closed financially: refund, store credit, or a replacement dispatched.
Jumping from requested to refunded without inspection refunds an item that will not be sold again. Inspection without a financial close leaves the customer chasing you.
Refused at the door is not a return
Refusal before the parcel is opened belongs to cash on delivery, and often never became revenue. A return after delivery is a different event, and collection may already have happened. Mixing the two numbers inflates “returns” and hides an address-confirmation problem. Keep the reports apart. Door refusal is covered in the cash-on-delivery operations guide.
Stock
A sound item returns as quantity on the same variant code, not only on the parent, or the wrong size becomes sellable. A damaged item does not return to available. A place for returns under inspection stops them being sold while still in the carton. That is shelving and a procedure on your side as much as fields in the system.
Money
A card refund goes through the gateway and takes the gateway’s time, not the time of your button. A transfer refund needs a reference. Store credit is a commercial decision and is recorded so it cannot be used twice. Do not promise the customer a one-hour refund if the gateway takes days. Write “after inspection, back to the same payment method” if that is what actually happens.
Who answers the customer during inspection?
The gap between receiving the carton and closing the money is what the customer complains about, not the status name in the panel. Set a number of working hours or days, and name the person who sends the message. The message quotes the order number and what was inspected, not a vague promise. If the item is refused because the policy does not cover it, cite the sentence the customer saw before paying. Anger drops when the refusal matches a line that was visible, rather than a rule that appeared after the purchase.
What the first version includes
A short reason form, the statuses above for a small team, and a link to the original order number. Advanced reason reports wait until a real month of data exists. A reason dashboard before thirty returns is analysis of an empty box.
The store is e-commerce development. If inspection and stock become a wide operations screen, move to custom systems. How refusal differs from a return is in cash on delivery operations.
Send the current policy, even if it is one sentence on paper, from start your project. WhatsApp complaints, with customer names removed, can come from the button on this article.
