A customer buys a shirt on the website, it arrives in the wrong size, and she walks into the nearest store to return it. For her it takes two minutes. For the retailer's systems it's one of the most complicated transactions of the day — and one of the easiest to under-test.
What has to happen
For that return to be correct, at least four things must happen, in different systems:
- The refund goes back to the original payment method, for the right amount — including any promotion that applied to the original order.
- The sale is reversed so revenue, margin and the customer's purchase history are right.
- The stock is added back at the store where the shirt now physically sits, not at the warehouse that shipped it.
- The order is updated so customer service, loyalty points and any open delivery tracking reflect the return.
Miss any one of them and something is wrong: a double refund, phantom stock that can be sold online but doesn't exist, or sales figures that don't reconcile at month end.
Why it goes wrong
The point of sale in the store didn't create the original order — the e-commerce platform and the order management system (OMS) did. So the store system has to look the order up, check it's eligible, and trigger the refund against a payment it never took. Each of those is an integration, and each has an owner who usually tests only their side.
The common failure points are predictable:
- The store can't find the online order, so the associate rings it up as a no-receipt return at a different price.
- A multi-buy promotion ("3 for 2") isn't split correctly, so the refund is too high.
- Stock is credited back to the original warehouse, so the store shows zero while holding the item.
- The refund succeeds but the OMS never hears about it, so the customer later gets a "your return is overdue" email.
Scenarios worth testing
Treat the return as a transaction to trace end to end, not a single screen. A useful starting set:
- A full-price item returned in store, paid by card online — refund, stock and sale checked in every system.
- One item returned from a promotion bundle — the refund amount matches the promotion's own rules.
- An order paid partly with a gift card and partly by UPI or card — which tender is refunded first.
- A return outside the return window, and one with the store offline — what the associate sees and what syncs later.
- The same order returned twice, in two stores, a minute apart — the second must be refused.
For each one, check the refund, the stock at the receiving store, the sale reversal and the order status. Four checks, four systems, one transaction.
The wider lesson
Cross-channel returns are a good example of why domain knowledge matters for testers. The screen can look perfect while the business is quietly losing money. Knowing the process, the systems behind it and the data each one owns is what turns "the return worked" into "the return was right".