Grocery Order Event Storming

This event storming diagram maps a grocery delivery order from checkout to delivery. Blue nodes are commands that request work, orange nodes are facts that happened, and the green node is a policy that reacts to the order being placed. The simple chain is a useful opening model because the group can ask where exceptions, ownership, and external systems belong. In a workshop, add cancellation, substitutions, out-of-stock handling, and refund events only after the happy path is agreed. Keep the event names concrete and in the past tense so participants can distinguish a recorded business fact from an instruction. Review the underlying definitions and totals before using this view to make an operational decision.

Type OrganigrammeNorme Sugiyama layered DAG + orthogonal routingMoteur schematex-flowchartMis à jour 24/09/2026

La demande

“Create an event storming diagram for an online grocery order: Place order causes Order placed; authorize payment causes Payment authorized; reserve items causes Items reserved; pick order causes Order picked; dispatch delivery causes Order delivered. Color commands blue, events orange, and the payment policy green.”

Essayez ensuiteAdd a Payment declined event and an order cancellation command.Add an Order aggregate beside the first event.

Ce que contient ce dessin

Comprenez les décisions qui le sous-tendent.

01Name facts

Keep events in past tense.

02Separate triggers

Show commands separately from events.

03Expose policy

Make payment authorization explicit.

Use for a chronological workshop map of a bounded business process.

Voir tous les modèles de organigramme →

FAQ

Questions fréquentes

Why are events orange?

Orange is a common event-storming convention for facts that occurred.

What is the payment policy?

It reacts to Order placed by initiating payment authorization.

Where do exceptions go?

Add them as separate commands and past-tense events branching from the relevant point.