Returns Portals
Returns portals and self-service tools
Plan a returns portal that captures useful requests, explains the next step and routes Australian consumer-guarantee claims for assessment.
A returns portal lets customers identify a purchase, explain what happened and submit a request. It should tell them what happens next and give staff the original account needed to review it. A submitted request is not an approved return or a completed refund.
For an Australian retailer, the portal should offer a route for reported product problems and explain the store's change-of-mind policy.
Make the first step clear
Place a recognisable “Start a return” action on the returns page and near order information. Explain what customers need before they begin, including any account sign-in or verification step.
Let customers select the affected item and quantity. Ask what happened separately from what they would like the store to do. Record the requested outcome separately from the reported problem.
Provide a contact route when the portal cannot find an order, the customer lacks the purchaser's details or the item needs special handling. An unexplained error should not end the enquiry.
Use rules to route requests
A portal can show the store's change-of-mind terms and available outcomes. Label those terms clearly. If a customer reports a fault or another product problem after that period, provide a way to submit the account for assessment.
A portal should acknowledge a reported problem and explain any review process rather than promise one automatic outcome for every selected reason.
Send unclear descriptions and conflicting order details to a staff member who can read the customer's words. Make sure an automated rule does not turn a change-of-mind condition into a blanket refusal of a product-problem claim.
Set expectations about external escalation as well as the store’s own review. The ACCC educates consumers about consumer guarantees and accepts reports about business conduct; it uses reports to inform its education, compliance and enforcement work. It does not resolve individual disputes or give legal advice about a consumer’s right to a remedy.
Change-of-mind vs. product fault: key differences in returns policy
- Proof requiredChange-of-mind: none. Product fault: evidence of defect or failure expected.
- Outcome eligibilityChange-of-mind: refund or exchange only. Product fault: repair, replacement, refund or compensation (ACCC guidelines).
- Automated decision riskChange-of-mind claims may be auto-approved. Fault claims require manual review to avoid misclassification.
Keep the request and outcome distinct
After submission, show the affected item, the customer's account, a reference and the next step. Use statuses only for events the business can confirm, such as request received, information needed or instructions sent. A parcel delivery scan does not establish what was inside it.
The staff record should retain the original description alongside any reason code, requested outcome, messages, decision and outstanding action. Items in one parcel may need separate findings.
Do not use a portal status as proof that a refund has reached the customer or that an item is ready for resale. Those actions have separate records.
Choose and introduce the tool
Check candidates against the store's actual cases. Can a customer complete a request on a phone, explain a problem outside the preset menu and reach staff when an automated rule cannot decide it? Can staff see the original account and give return instructions the store can fulfil?
Before launch, rehearse a change-of-mind request, a reported fault after the voluntary period, a multi-item order and an item that cannot readily be posted. Review both the customer screen and staff record. For a faulty product that is large, heavy or hard to remove, ensure the portal captures the circumstances and allows staff to decide how transport will be handled.
After launch, review abandoned requests, reasons staff frequently recode, cases without an owner and messages asking what a status means. Read the cases before changing a rule.
In this guide
- Comparing return portal features: Shopify, AfterShip, LoopCompare documented portal features and limits for Shopify, AfterShip and Loop, including reasons, exchanges and Australian return routes.
- Collecting return reasons without forcing the wrong categoryDesign return-reason questions that preserve the customer's account, support staff review and avoid misleading categories in an Australian returns portal.
- Testing a customer return request on mobileA mobile test procedure for return requests, covering order lookup, reason capture, submission, staff records and selected accessibility checks.
