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.

類型 流程圖標準 Sugiyama layered DAG + orthogonal routing引擎 schematex-flowchart更新時間 2026/9/24

需求

“Create an event storming diagram for a product return: Request return causes Return requested; an eligibility policy causes Return approved; issue return label causes Return label issued; receive returned item causes Item received; and a refund policy causes Refund issued. Color commands blue, events orange, and policies green.”

接著試試Add a Return rejected event from the eligibility policy.Add an inspection command between Item received and Refund issued.

這張圖裡有什麼

看懂背後的決策。

01Define eligibility

Agree on the policy for approving returns.

02Track custody

Record label issuance and item receipt separately.

03Control refund

Set the event that authorizes a refund.

Use for a return process with clear policy and warehouse handoff points.

瀏覽所有流程圖範本 →

常見問題

Why is return eligibility a policy?

It reacts to a return request using business rules to decide what happens next.

Should a refund happen before receipt?

That depends on policy; this example issues it after the returned item is received.

What is an aggregate here?

A return or order aggregate can own the state changes represented by these events.