Product Return Event Storming
This event storming diagram maps an e-commerce return from the customer's request through a completed refund. It separates the return-eligibility policy from the warehouse receipt and refund policy, which helps the group discuss ownership and exception handling. The sequence is intentionally small enough for a workshop wall or card. Expand it with rejected returns, inspection results, partial refunds, exchanges, and carrier failures when those rules become relevant. Use event names that state completed facts, such as Item received, so downstream teams can identify the exact moment their process is allowed to begin. Review the underlying definitions and totals before using this view to make an operational decision.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
Return and refund domain discovery
Key decisions
- Define eligibility: Agree on the policy for approving returns.
- Track custody: Record label issuance and item receipt separately.
- Control refund: Set the event that authorizes a refund.
When to reuse this
Use for a return process with clear policy and warehouse handoff points.
Frequently asked questions
Why is return eligibility a policy?
Should a refund happen before receipt?
What is an aggregate here?
More e-commerce examples
Try the diagram makers.
Tweak it with chat, export PNG/SVG, or fork it for your own use case.