Flow Diagram · e-commerce
Customer Purchase
How a customer turns a shopping cart into a confirmed order, with the entities, metrics and components involved.
Each actor has a lane and time runs left to right. Drag to move, Ctrl + wheel or pinch to zoom, and take the guided tour for the four layers of the notation.
- Key objectiveHere the customer achieves the goal: fast checkout.Every flow needs at least one action where an actor achieves a goal. If there is none, the flow adds no value.
- Why two coloursOrder is born in this flow (yellow). Shopping Cart comes from Browse & Select (grey).Entities are conceptual, not database tables. They bridge what the business asks for and what the technical team models.
- Technical MVPOne deployable covers order, shipping and payment. Split it when the business justifies it.Solid line: synchronous API. Dashed: event. A component's width covers the actions and entities it implements.
- Actors: Proceeds to checkout, Initiate order and reserve items, Collect shipping details, Enter shipping details, Initiate payment, Collect payment details, Enter payment details, Process payment, Process payment result, Order confirmation
- System Entities: Shopping Cart, Shopping Cart Line, Order, Order Line, Shipping address, Payment Intent, Credit card details, PayPal details, Payment transaction result, Order confirmation details
- Metrics: Cart abandonment rate (Shopping carts that do not become an order within 7 days.), Payment success rate (Initiated payments that ended with a success result.), Checkout completion time (From order creation to order confirmation.)
- Technical Components: Shopping Cart Service, Order Management Service, Payment Gateway (external), Order Management Service
- Key objective. Here the customer achieves the goal: fast checkout.. Every flow needs at least one action where an actor achieves a goal. If there is none, the flow adds no value.
- Why two colours. Order is born in this flow (yellow). Shopping Cart comes from Browse & Select (grey).. Entities are conceptual, not database tables. They bridge what the business asks for and what the technical team models.
- Technical MVP. One deployable covers order, shipping and payment. Split it when the business justifies it.. Solid line: synchronous API. Dashed: event. A component's width covers the actions and entities it implements.
