E-commerce return service blueprint
This service blueprint follows an online return through the actions a customer sees and the operational work that follows. Support receives the request, checks eligibility and communicates the outcome. If the return qualifies, the warehouse inspects the item and finance issues the refund. The ineligible branch is equally important because it determines how the retailer explains a disappointing outcome. The blueprint can help teams locate handoffs, clarify ownership of decisions and make sure the customer receives a message at each meaningful stage rather than needing to chase status. It gives teams a concrete starting point for reviewing assumptions, data quality and next steps together.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
An online retailer standardizes its returns experience.
Key decisions
- Define eligibility: Make the order and return-window check visible.
- Communicate outcomes: Send either a label or a clear decision.
- Close the loop: Connect inspection to refund confirmation.
When to reuse this
Use to coordinate a customer request across support, warehouse and finance.
Frequently asked questions
Why map a return service?
Where does eligibility belong?
Can a blueprint include denial paths?
Tweak it with chat, export PNG/SVG, or fork it for your own use case.