Returns Data
Part of Returns management for online retailers
Mapping the return journey from request to resolution
Map each return hand-off, owner and completion event so an online retail case can be followed from request to final outcome.
Map a return journey by recording each event the retailer can verify, its owner and the next required action. Start with the customer’s request and end when the outcome and any outstanding item or payment task are accounted for. The map should show where hand-offs fail; it need not put every case through the same stages.
Choose what the map follows
Use one reference for the customer conversation and one line for each affected order item. Record the order reference, item and variant, quantity, reported issue, requested outcome and contact channel. Two products in one parcel may need different assessments and remedies.
A possible sequence is request received → information gathered → route decided → item in transit, if needed → item received → assessment complete → remedy actioned → outcome confirmed. Add states for cases waiting on a customer, carrier or specialist. A refund without a physical return skips parcel stages. A replacement sent before the original item arrives creates two movements to track.
Return Journey: From Request to Resolution
- Request receivedCustomer initiates return with order reference, item details, issue reported, and contact channel
- Information gatheredRetailer collects full details; verifies eligibility under Australian Consumer Law (ACL)
- Route decidedDecision made on remedy: refund, replacement, repair, or cancellation; transport method confirmed
- Item in transit (if needed)Return parcel dispatched via carrier; tracking initiated; expected delivery date set
- Item receivedWarehouse confirms receipt; contents matched to case and order line
- Assessment completeItem inspected; defect confirmed or not; decision documented per ACL guidelines
- Remedy actionedRefund processed (via original payment method), replacement shipped, or repair arranged
- Outcome confirmedCustomer notified of resolution; outstanding tasks (e.g., tracking, payments) assigned with owners
Describe each hand-off
For every stage, name the starting event, owner, completion evidence and next action. “Warehouse has the parcel” is too broad if nobody has matched its contents to the case. Carrier delivery, warehouse receipt and item identification are distinct events.
| Stage | Completion evidence | Question for the next owner |
|---|---|---|
| Request | Case and affected order lines recorded | What information is needed to choose a route? |
| Return route | Applicable instruction sent to the customer | Is an item expected, and how will it be identified? |
| Receipt | Contents matched to the case | What needs assessment? |
| Decision | Finding and remedy recorded | Who must act on the decision? |
| Resolution | Customer outcome and item destination recorded | What remains open? |
Adapt the stages to the products sold and the events the retailer can actually record.
Key Hand-Offs to Track in a Return Case
- Start: Request recordedOrder reference, item variant, quantity, issue description, and contact channel logged
- Owner: Customer service teamResponsible for initial intake and routing
- Completion evidence: Case createdSystem entry with all required fields populated
- Next action: Information gatheringVerify product eligibility under ACL; check warranty or return policy
- Stage: Return route decidedInstruction sent to customer with return address, label, or self-drop option
- Owner: Logistics coordinatorManages carrier coordination and tracking
- Completion evidence: Transport instruction sentTracking number issued or label generated
- Next action: Item receipt confirmationWarehouse logs arrival and matches contents to the case
- Stage: Assessment completeDefect verified; outcome aligned with ACL (e.g., repair, replace, refund)
- Owner: Returns specialistMakes final decision based on product type and issue severity
- Completion evidence: Decision documentedRemedy recorded in system with justification
- Stage: Outcome confirmedCustomer notified via email/SMS; open tasks (e.g., tracking, ATO GST adjustment) assigned
Place rights-sensitive decisions on the map
Keep the customer’s description even when a request is labelled “change of mind”; record any product problem they report. A business may assess a reported problem before providing a remedy. The appropriate remedy depends on the facts.
Add a decision point for return transport. Check the case before sending a standard posting instruction; the appropriate transport approach can depend on the item and circumstances.
Check the map against cases
Take a small selection of completed, delayed and disputed cases and map their recorded events. Look for a stage without a time, owner or completion record. A case stalled after delivery may have an item-matching problem; one stalled after assessment may need a clearer decision hand-off. Check those possibilities against the case record.
Define closure for each route. A refund may be complete while the unit remains unlocated; a replacement may have shipped while the original return is still expected. Keep each outstanding task visible with an owner until it is resolved.
