Returns Data
Returns programme improvement
Use real return cases, one targeted process change and comparable customer outcomes to improve a returns programme.
Improve a returns programme by finding a recurring failure in real cases, changing the step that causes it, then checking the customer outcome. Define the problem and a baseline first. A lower return count alone could reflect fewer sales, blocked requests or cases still awaiting a decision.
Set programme priorities across the portfolio
Rank recurring failures by more than volume. Consider how widely the failure reaches the returns process and whether it could affect consumers' ability to obtain the rights or remedy to which they are entitled. A high count alone does not show the greatest programme risk.
Use complaint patterns as one signal that a problem may extend beyond the cases already visible to the team. The ACCC says it focuses on issues that can result in widespread harm and uses reports and other information to inform its education, compliance and enforcement work. Such patterns are relevant to prioritisation, not proof of an individual case outcome.
Choose a problem the team can act on
Look across request, item, decision and payment records. Find a pattern specific enough to investigate: parcels delivered but not matched to cases, repeated update requests, or reported faults routed through a change-of-mind rule. Read the cases behind the pattern. A reason code or delivery scan cannot explain the whole case.
For each proposed improvement, record affected cases, the suspected failed step and the outcome at stake. Keep a suspicion distinct from a finding. In Australia, a retailer must follow a change-of-mind policy it offers, but voluntary conditions cannot remove consumer-guarantee rights for a product problem.
Change the responsible step
Choose one intervention that addresses the evidence. If receiving staff cannot identify parcels, improve the return reference and exception hand-off. If customers cannot tell whether a refund was submitted, correct the status record and message at that point. If a voluntary deadline closes fault reports, correct the route and review affected cases.
Record the change, owner, start date and cases it can reach. Identify old instructions or system rules still in use so staff know which version applies during the transition.
| Question | Record to examine | Decision it supports |
|---|---|---|
| Where does work stop? | Dated case events, owner and next action | Which hand-off to repair |
| Did the change reach the intended cases? | Process or rule version attached to each case | Whether the comparison concerns exposed cases |
| Did service improve? | Comparable outcomes, resolution times and open cases | Whether to keep or revise the change |
| Did another problem appear? | Repeat contacts, misrouted claims and complaints | Whether the change created avoidable harm |
These are suggested management records, not industry benchmarks.
When a programme change affects a customer-facing condition, check that the relevant terms and conditions remain clear and accessible. The published policy and the instructions staff follow should describe the same route, while preserving the distinction between voluntary change-of-mind returns and consumer-guarantee claims.
Keep consumer rights as a programme guardrail
Keep voluntary change-of-mind conditions distinct from routes for product problems. Consumer guarantees under the Australian Consumer Law apply even when an item was bought on sale; a 'no refund' sign cannot remove those rights. The remedy depends on whether the issue is major or minor.
When reviewing the route for a reported product problem, check that the programme does not treat a voluntary policy limit as a bar to considering consumer guarantees. A product must be fit for purpose, safe, durable, free from defects and match its description.
Voluntary Change-of-Mind vs Consumer Guarantee Claims
- Voluntary Change-of-Mind PolicyApplies only if the retailer offers it; does not override consumer rights under Australian Consumer Law (ACL).
- Consumer Guarantee RightsApply regardless of sale price or 'no refund' signs; include fitness for purpose, safety, durability and accurate description.
Review outcomes before expanding
Define the measure before the change starts. Requests, physical returns, refunds and resolved cases are different units. Compare similar cases over periods that allow comparable time for resolution. Show counts alongside rates, and inspect the oldest open cases; faster closed cases can hide a growing queue.
Read later cases as well as the summary. Check whether the intended step changed and whether product mix, staffing or demand changed at the same time. An observed difference does not prove that the programme edit caused it.
Keep the change when cases show the intended improvement without an unacceptable effect on legitimate claims. Revise it if the failure persists. If evidence is thin, record that limit and set another review point.
Include customer experience in the outcome review, not only the operational result. A 2025 Australian Retailers Association survey found that 68% of consumers are more likely to repurchase from a retailer with a hassle-free returns policy. Use this as context about customer expectations, not as evidence that a particular programme change caused repeat purchases.
Do not treat an external report as a substitute for resolving a customer's case. The ACCC accepts reports and may investigate misleading conduct, but it does not resolve individual disputes or provide legal advice about a consumer's rights to a repair, replacement or refund. Keep case resolution with the business while using recurring issues to inform programme priorities.
Key Returns Metrics and Customer Expectations
- Customer Repurchase Likelihood68% of consumers are more likely to repurchase from retailers with hassle-free returns
- ACCC Enforcement FocusIssues causing widespread harm; uses reports to inform compliance and education work
- Refund Processing TimeNot specified – but resolution time is a key outcome metric to track
In this guide
- Auditing a return process with real customer casesSelect varied customer cases, reconstruct each return timeline and turn failed hand-offs into specific process fixes.
- Comparing returns software after a process reviewTurn process-audit findings into a software brief and compare Shopify, AfterShip and Loop against actual gaps and plan limits.
- Setting a service target for return resolution timeDefine the customer-wait clock, separate return routes and set a service target that exposes delayed and unresolved cases.
- Reviewing whether a policy change solved the intended problemCompare cases exposed to a revised returns policy, check its intended outcome and look for confusion or blocked product-problem claims.
