Flow map
Primary and failure paths
Legend
How to read the diagram
Step details
Detailed notes by stage
These notes work as the no-JavaScript fallback and also serve as annotations for implementation and operations teams.
1. Customer submits return request
Inputs: order id, SKU, return reason, photos when applicable, pickup or drop-off preference. Failure path: missing evidence routes to follow-up request before approval.
2. Support approves
Support checks policy window, category exclusions, prior refund abuse markers, and warranty status. Output: prepaid label or rejection note.
3. Warehouse inspects item
Warehouse compares condition with the approved reason code, verifies serial number where required, and flags accessory mismatches. Failure path routes to manual exception review.
4. Finance issues refund
Finance issues full or partial refund, updates order ledger, and triggers customer confirmation. For gift-card orders, refund destination can differ from original payment method.