The operational problem
An unpaid parcel returned to the sender and a paid customer return can look similar in a tracking feed. They need different handling. Closing both as “returned” hides whether the goods reached the warehouse, whether stock is sellable and whether money is still owed. The useful automation prepares an exception queue with evidence for each decision, rather than making every tracking event a financial instruction.
Evidence to collect before acting
- Shipment evidence
- Retain the tracking identifier, carrier event, event time and last successful read. A missing event means unknown status, not confirmed arrival.
- Goods evidence
- Record which items the warehouse received, quantities, inspection outcome and any mismatch with the expected return.
- Order and money evidence
- Read the order, fulfillment state, captured payments, previous refunds and existing return record before proposing another action.
A practical workflow
Step 1
Classify the exception
Distinguish an uncollected shipment, a customer-requested return, a delivery dispute and a partial return. Keep the original reason and source reference visible.
Step 2
Verify physical receipt
Compare carrier and warehouse evidence. Shopify’s return guidance describes processing after receipt and inspection; do not infer item condition from a tracking label.
Step 3
Prepare separate decisions
Propose order cancellation, restocking and refunding individually. Show quantities, amounts and notification choices. Paid orders, contradictory records and uncertain receipt need an explicit review path.
Step 4
Execute and verify each outcome
After an authorized action, check the order, return, refund or inventory record relevant to that action. Record partial completion rather than declaring the entire return finished.
Worked example · Illustrative
Illustrative example, not a customer result: a carrier marks parcel DEMO-RETURN-7 as returned, but the warehouse has not recorded receipt. The workflow keeps “warehouse receipt unknown” open. When inspection confirms one sellable item and one damaged item, it prepares separate inventory decisions and a proposed refund for review. It does not assume that both items should return to available stock.
Exceptions that need a separate decision
| Situation | Handling approach |
|---|---|
| Unpaid, uncollected shipment | Establish whether any payment was captured before proposing financial action. Review cancellation eligibility and delivery costs under the merchant’s policy. |
| Paid or partially refunded order | Check prior refunds and the amount still refundable. A cancellation can include refund options; review the actual selected behavior before submission. |
| Returned event without goods | Keep the parcel-to-warehouse discrepancy open and assign a follow-up owner. Do not publish a completion status based on a carrier event alone. |
How to measure the result
Measure time from carrier return event to verified warehouse receipt, unresolved quantity differences, refund decisions awaiting review and completed actions verified in the destination system. Report cash recovered, goods recovered and refunds as separate measures. Reducing an exception queue is useful only when the underlying discrepancies have actually been resolved.
Common questions
Does canceling an order always issue a refund?
The selected cancellation flow matters. Shopify offers refund choices, including refunding later in eligible cases. Inspect payment state and the exact options instead of assuming a universal outcome.
Can a refund happen without a physical return?
Shopify supports refunds without creating a return. Whether that is appropriate is a separate merchant-policy decision. A refund record does not prove that goods arrived or were inspected.
Primary sources
Platform documentation supports the distinctions described here. Workflow controls and measurement recommendations are design guidance from LINKIO.ONE, not evidence of a completed LINKIO deployment.