Return fraud: checks that protect genuine customers

Assess suspected return fraud using order evidence and consistent checks. Protect genuine customers while documenting exceptions and staff decisions.

Return fraud is deliberate deception to obtain a refund, replacement or other return benefit. Investigate it by checking the claim against order records, giving the customer a chance to explain inconsistencies and sending disputed cases to a person. A suspicious pattern alone doesn’t establish what happened.

Recognise suspicious return patterns

Look for specific contradictions between the customer’s account and the records for that return. A different product identifier or an earlier completed refund warrants a check. Record the contradiction before drawing a conclusion about intent.

Separate four possible explanations when opening the case:

  • The customer made a mistake, such as selecting the wrong order or packing the wrong item.
  • A fulfilment or delivery problem caused the discrepancy.
  • The product has a genuine fault, including one discovered after use.
  • Someone deliberately misrepresented the purchase, parcel contents or refund history.

Frequent returns can reflect sizing problems or inaccurate product descriptions. Damaged packaging can reflect handling in transit. Neither observation alone proves deception, and a delivery scan doesn’t establish the contents of a parcel.

Keep a change-of-mind request separate from a claim about a faulty product. Under the Australian Competition and Consumer Commission’s (ACCC) refund guidance, businesses can assess a product before providing a remedy. Store policies cannot remove consumer-guarantee rights.

Collect evidence without accusing the customer

Start with records you already hold, then request only the missing information needed to resolve the discrepancy. Create one case reference so warehouse staff and customer support work from the same account.

Collect the relevant records for each part of the claim:

RecordWhat to compare
Order and dispatchItem, quantity, variant, recorded serial number and any substitutions or split shipments
Payment and refundOriginal transaction, completed or pending refunds, payment disputes and which item each amount covers
Delivery and return journeyTracking events, recorded parcel weights, carrier exceptions and handover records
Item conditionCustomer’s description, relevant photos and warehouse inspection notes, with who recorded each observation
Customer contactRequested remedy, earlier messages and explanations already given

Treat each record according to what it establishes. A warehouse note written after unpacking has different limits from a photograph of the unopened return. Keep estimates and missing records visible to the reviewer.

Ask a neutral question tied to the gap: “The item label differs from the order record. Could you send a photo of that label so we can check the dispatch?” For a missing item, ask which items arrived and whether the parcel appeared damaged. Explain the next step and when the customer will hear back.

The ACCC says businesses can request proof of purchase. Original packaging isn’t required for a faulty-product return. Use existing order details where they resolve the purchase, and accept another suitable form of proof when needed.

Avoid routine requests for identity documents or full bank statements. If a payment record is needed, ask the customer to hide unrelated transactions and unnecessary account details. Request photos of the item or label without people or private surroundings in view.

For retailers covered by the Australian Privacy Principles, the Office of the Australian Information Commissioner (OAIC) requires collection to be reasonably necessary. Its collection guidance explains why convenient extra information can still be excessive.

Apply checks to the claimed problem

For each claim, choose a check that can resolve the specific discrepancy before changing the outcome. The following checks are a practical review workflow, with alternative explanations to investigate in each case.

SignalProportionate checkNext review step
Wrong item returned or receivedCompare the order, dispatch record and product identifiers with the customer’s descriptionCheck for a picking error, substitution or customer packing mistake before attributing the mismatch
Empty box reportedCompare available weights across dispatch, carrier handover and return receipt, including packagingAsk about damage or missing contents and investigate gaps in the parcel journey
Item appears usedInspect the claimed fault, condition evidence and any applicable change-of-mind termsAssess whether ordinary use exposed a fault or the evidence supports another explanation
Possible duplicate refundReconcile refund status, transaction reference, amount and item across support and payment recordsConfirm whether the earlier refund completed and covers the same claim before authorising another payment

A missing weight record isn’t evidence that a parcel was empty. A pending refund isn’t proof the customer has received money. Visible wear doesn’t settle whether the product was faulty.

Consider this hypothetical case. A returned appliance has a serial number different from the dispatch record, so staff flag a possible substitution. The reviewer checks whether the warehouse recorded the number correctly and asks the customer for the appliance label. A warehouse recording error resolves the mismatch without a fraud finding. If it remains unexplained, the case moves to a senior reviewer with both accounts attached.

Route uncertain cases to a person

Assign a named reviewer whenever the customer disputes the evidence or a fault claim remains unresolved. Give that person authority to correct an automatic flag and obtain further assessment where needed.

Use this sequence for a contested case:

  1. Send the reviewer the claim, relevant records and the exact unresolved inconsistency.
  2. Ask the customer for an explanation of that inconsistency, with a suitable alternative if the requested evidence is unavailable.
  3. Assess the explanation alongside warehouse or carrier findings. Keep any consumer-guarantee assessment separate from a discretionary policy exception.
  4. Give the customer the reasoned outcome, any remedy and a way to request another review. If the dispute continues, explain the available state or territory consumer-protection complaint route.

Set a next-contact time and update the customer if assessment takes longer. Escalation must lead to an assessment, rather than repeatedly sending the same evidence request. Obtain legal advice before a contested refusal where the retailer’s obligations remain unclear.

A shopping agent can collect the return reason and pass the conversation to staff for this review.

shoppa helps customers find and compare products, buy in the chat and get support from the retailer’s own catalogue and documents. Customers can start and track returns in that conversation, then hand over to the retailer’s staff or helpdesk when they need a person. Staff use the return details and conversation context to decide the disputed outcome.

Record the decision and improve the process

Keep a decision record that explains what the reviewer concluded and why. Include the evidence relied on, its limits, the customer’s explanation and any unresolved disagreement. Record the decision-maker, remedy or policy exception, customer notification and review route.

Use factual observations in case notes. “Returned serial number differs from dispatch record” can be checked against the records. A label such as “fraudulent customer” hides the reasoning and can affect later decisions without support.

Restrict case access to staff who need it and apply a retention schedule that accounts for legal obligations and unresolved disputes. Under the OAIC’s security guidance, covered organisations must take reasonable steps to protect personal information. They must destroy or de-identify it when no permitted purpose remains, subject to the stated legal-retention and Commonwealth-record exceptions.

Review flags that staff overturn, complaints upheld after refusal and repeat requests caused by missing internal records. A false positive is a legitimate return that a prevention rule incorrectly flags. Compare false positives with the original trigger to see whether the rule needs narrowing or the fulfilment process needs repair.

When a rule repeatedly flags genuine faults or dispatch mistakes, change the rule and give staff the corrected review instructions. Before closing the next disputed case, confirm that the saved decision explains the evidence, addresses the customer’s account and records the next action.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup