Reviewing unusual return patterns without accusing customers prematurely

Treat an unusual-looking return pattern as a signal to check, not a conclusion about a customer. Describe the signal, reconcile the order and return history, then compare like cases before referring a specific return for closer review.

Describe the signal

State what raised the question: repeated returns of one product, inconsistent order details or an apparent second remedy for one order line. Record observable details, not labels about a customer's character.

Count orders and items bought as well as items returned, and separate change-of-mind returns from reported product problems. Repeated reports of the same fault or mismatch across customers may point to a product, listing or fulfilment issue.

Compare cases for the same product and reported issue, keeping change-of-mind returns separate from product-problem returns. Compare orders at a similar point after purchase: newer orders have had less time to generate a return than older ones.

Change-of-mind vs. product-problem returns

Reconcile the case history

Start with the affected order lines, earlier return references, payment adjustments and replacements. Check whether a split order, a parcel containing several items, a duplicate support ticket or a refund status that has not updated explains the apparent repeat.

Confirm whether the apparent repeat concerns the same unit or a later purchase of the same product. Separate each record, observation, possible explanation and next check.

For example: “Two requests appear against one order line; one closed without a refund. Check the item and requested outcome in the second request.” This identifies the next check without alleging deception.

Ask a neutral question if records do not settle it

Ask for information relevant to the discrepancy. For example: “We can see two return requests for this item. Could you confirm which item this parcel contains so we can match it to the right order?” Give the customer a way to correct the record and explain the next step.

Decide what the pattern supports

Clear the flag when the records explain the apparent repeat. Refer the specific case for closer review only if, after checking the records and asking a relevant neutral question where needed, an unresolved mismatch affects which order line or item is involved, or whether a refund or replacement has already occurred. A high pattern count alone is not enough to refer a case.

Under consumer guarantees, a return pattern alone does not establish customer misuse or settle a customer's right to a repair, replacement or refund for a faulty product or service. The ACCC explains rights and responsibilities under consumer guarantees but does not resolve individual disputes or give legal advice about an individual right to a remedy.

Review cleared flags for recurring causes. If a rule repeatedly catches a genuine product issue or a duplicate-record process, correct the cause rather than treating those cases as customer behaviour.

Key facts from ACCC guidelines