EventStorming Example: Online Order and Payment Process

A worked EventStorming example for an online order and payment journey, including domain events, commands, actors, systems, and hotspots.

This example maps a customer buying a product online. Use it as starter content for a workshop, then challenge every assumption with people who know the real process.

Process context

A customer browses the shop, adds a product to a cart, submits an order, pays through an external provider, and receives the delivery. The warehouse and customer support teams handle exceptions.

Domain events

Place these events in order on the timeline:

Product viewed
Product added to cart
Checkout started
Order submitted
Stock validated
Payment authorized
Order confirmed
Warehouse notified
Order packed
Order shipped
Delivery update sent
Order delivered

Commands and actors

Command	Actor or system	Resulting event
Add product to cart	Customer	Product added to cart
Submit order	Customer	Order submitted
Authorize payment	Checkout service	Payment authorized
Confirm order	Order service	Order confirmed
Prepare shipment	Warehouse worker	Order packed
Ship order	Courier integration	Order shipped

External systems and policies

Payment provider authorizes or declines payment.
Inventory service validates stock.
A policy sends an order confirmation after payment succeeds.
A policy requests customer notification when delivery status changes.

Hotspots to discuss

How long is stock reserved after checkout starts?
What happens if payment succeeds but order confirmation fails?
Can a customer change the address after the order is submitted?
Who approves a refund after the package is shipped?
Which system owns the delivery status?

Now open the EventStorming Board, create a session, and map this process with your team.