“Why does one store honor a return without a receipt and the store four miles away won’t even look at it?”
An ops director asked that in early November, three weeks before the return volume of an entire fourth quarter lands on service desks built to handle a normal Tuesday. The honest answer is that the question has at least four different explanations, and only one of them gets fixed by reminding associates to follow the policy.
One Complaint, Read Four Ways
A return complaint arrives at corporate looking like a single symptom: a customer denied a return that another store would have honored, or granted one that policy says should have been refused. Read the complaint alone and it looks like a training issue, every time, because the associate is the person standing in front of the customer when it happens.
Read four or five of them together, from different stores, and the pattern stops looking like training. Some associates are following a policy that is genuinely ambiguous about receipt-less returns past a certain dollar amount. Some are applying a clear policy inconsistently, tighter on a slow Tuesday and looser during a holiday rush when the line is long and a manager just wants the customer gone. A few have quietly built a local workaround that has nothing to do with either. The symptom at the service desk is identical. The cause is not.
Put concretely: store 12 processes a receipt-less return over its stated threshold without a second thought. Store 47, four miles away and under the same regional manager, declines an identical return the same week. Both associates can point to the same page of the same handbook.
Is the Policy Itself the Problem?
Start with the least comfortable possibility first: the written policy may simply be unclear. A rule that says a manager may use discretion on returns over a certain dollar amount without a receipt is not a policy so much as a delegation of the actual decision to whoever happens to be running the store that day.
Three Ways the Same Policy Can Fail on the Floor
Assume for a moment the written policy is fine. The complaint can still originate from three distinct places on the floor, sometimes at the same service desk that is also handling online pickup orders during the same rush, and each one calls for a different response:
- Inconsistent application, where the policy is clear but enforcement drifts store to store or shift to shift depending on who is working and how busy the line is
- An undertrained associate who was never actually walked through the receipt-less return threshold and is guessing, confidently, in front of a customer
- A deliberate local workaround, where a store has decided the corporate policy does not fit its customer base and quietly built its own rule, sometimes a better one, sometimes not
A store manager coaching an associate on the second cause is wasting an afternoon if the real problem is the first, or worse, if it is the third and the associate is following store leadership’s own instructions rather than ignoring them. Treating all three the same way, with the same generic retraining email, is how a chain manages to run the identical correction three times a year without ever learning which store actually needed it.
The Test That Tells Them Apart
None of the three causes above announce themselves on a complaint log. The log shows that returns are being handled inconsistently. It does not show why, and coaching the wrong cause fixes nothing while looking, on paper, like the problem has been addressed. That gap between what corporate assumes a store is doing and what actually happens at the counter is the same gap franchise compliance audits exist to close, and it is why a badly written policy and a badly enforced one can look identical from a desk in another state.
Signal Retail runs a Return Policy Test as an add-on to a standard visit for exactly this reason: an auditor presents a specific, pre-scripted return scenario at the service desk and records how it was handled, by whom, and against what stated reasoning. Each attempt gets logged the same way a standard audit finding does, with a timestamp and, where the store allows it, a photo of the transaction screen or the signed override slip. Run the same test across several locations and the pattern usually sorts itself. If every store handles it differently, that points toward inconsistent application or training. If every store handles it the same wrong way, that points back at the policy itself. If one store consistently does something no written policy would produce, that is the workaround. At $125 per test, it is a cheap way to stop guessing which of the four this actually is.
What the Result Changes
Each of the four causes gets a different fix, and the fixes do not overlap much. A badly written policy gets rewritten, not enforced harder. Inconsistent application gets a manager conversation about a specific shift and a specific number, not a store-wide memo. An undertrained associate gets an afternoon of actual training, not a write-up. A deliberate workaround gets a harder conversation about why store leadership decided corporate’s rule did not apply to them, and whether they were right. Applying the wrong fix is not neutral: it burns goodwill with an associate who was never the problem, while the actual cause keeps producing the next complaint.
None of that starts with more coaching memos. It starts with knowing which of the four is actually in front of you, a question a report can answer more reliably than a hallway conversation ever will. See how a report actually gets built before returns season becomes the thing testing it.
