Keep the returns queue aligned with refunds and available stock
Assign the next action for each US return while keeping receipt, inspection, refund and stock adjustment records connected.
Reviewed 2026-10-08 · 3 min readKeep each unresolved return visible
As US returns accumulate, the daily task is to identify what can move next. A delivered parcel may still need an item check. An inspected unit may be waiting for the merchant to approve its next use. A refund may be recorded while the goods remain on hold. Keep those events visible separately, then give every unresolved return an owner and a next action.
Link each return to the goods actually received
Start with the store order and return references, then connect the incoming parcel to its receiving record. Keep expected and observed quantities beside each other. If a customer returns several items, create a row for each SKU and condition group so that one missing accessory does not obscure the status of the other items.
Shopify supports processing a return partially or all at once after receiving and inspecting the goods. Use that distinction when reconciling the store with warehouse activity. A single return reference can contain both completed work and units that still need a decision. Check how the actual warehouse connection represents that split before applying it to live orders.
Give the queue separate physical and financial states
Use the physical state to describe completed activity: awaiting arrival, received awaiting inspection, inspected awaiting instruction, or handling completed. Record the refund separately, including its platform reference and the person responsible for checking it. An inspection outcome should describe the observed goods; a customer refund decision belongs to the merchant's commercial process.
Shopify's processing guidance lets a merchant issue a refund when processing a return or issue it later. Restocking is an optional action with a selected location. Keep the receipt, refund and stock adjustment references in different fields so that staff can confirm each event against its own record.
These queue positions are suggested working labels. Map them to the states used by the store, warehouse and support desk rather than assuming each system uses the same words.
| Queue position | Evidence to review | Next decision |
|---|---|---|
| Expected but not received | Return instruction and latest carrier event | Confirm the enquiry owner |
| Received awaiting inspection | Receiving quantity and parcel reference | Assign the agreed check |
| Inspected awaiting instruction | Condition record and affected quantity | Obtain the merchant's handling decision |
| Approved awaiting stock update | Approval and completed handling record | Reconcile location and quantity |
| Financial decision unresolved | Return record and refund reference | Ask the merchant's finance or support contact |
Review unresolved cases by their next action
Set a review time when assigning an inspection or requesting a merchant decision. At the next review, separate work the warehouse can perform from cases waiting on another party. For each overdue action, record the last completed event, the missing input and the person who can supply it. A total count of open returns alone does not explain why they remain open.
When reporting queue age, name the event that starts the clock. Time since the return request differs from time since physical receipt or time since a decision was requested. Compare cases using the same starting event, and agree review targets with the team responsible for the work. Avoid presenting a target as a guaranteed inspection or refund time.
Test the handover before processing a larger batch
Run a proposed test with one return containing two condition groups. Authorise one group for restocking after its agreed checks, and keep the other awaiting a merchant decision. Verify that only the approved quantity reaches the intended stock location. Then compare the return record, refund record and customer message. The message should describe completed activity and the next confirmed step.
If the team processes returns in batches, retain the individual references and outcomes within the batch. Reconcile received quantities to released, held and otherwise authorised quantities before closing the work. A batch completion message should leave unresolved rows visible for the next review.
Agree the scope with the receiving team
Bring sample return rows when discussing US returns and aftercare with Jeton Express. Confirm the receiving location, inspection depth, handling instructions, approval contact and acknowledgement method for the actual project. The queue should show what the team has completed and what it is authorised to do next.