SIPOC — Omnichannel Apparel Returns
A deliberately mis-bounded charter: the scope ends at the refund but the process carries on to restocking, so the engine confirms the start boundary and flags the end as running past its own limit alongside an 8-day refund cycle against a 3-day target.
Make it your own.
title "Omnichannel returns — apparel"
scope "Return requested" -> "Refund issued"
owner "Reverse logistics manager"
metric "Refund cycle time" target: 3 actual: 8 unit: days
metric "Returns resold as A-grade" target: 85% actual: 62% better: higher
metric "Fraudulent returns detected" target: 95% actual: 88% better: higher
suppliers: Customers, Store colleagues, Carrier network, Returns processing centre
inputs: Return request, Original order record, Returns label, Returned garment, Reason code
process: Receive return request -> Issue returns label -> Receive at processing centre
-> Inspect and grade -> Issue refund -> Restock or dispose item
outputs: Refund transaction, Graded stock, Disposal record, Reason code analytics
customers: Returning customer, Merchandising team, Finance, Sustainability reporting
requirement input "Returned garment": "Tags attached, unworn, inside the 28-day return window" (CTQ)
requirement input "Reason code": "Chosen from the 12 standard codes, never free text"
requirement output "Refund transaction": "Issued to the original payment method inside 3 days" (CTQ)
requirement output "Graded stock": "Regraded and repriced before it re-enters the sellable pool"