E-commerce Order Flowchart Template
Order flow from adding to cart to completion: stock check, stock reservation, 30-minute payment timeout, shipping and delivery, confirmation and returns. For e-commerce requirement documents and project reports, exported as PNG, Word or PowerPoint for free.
Edit the text, pick a theme, export Word / PowerPoint / PDF
When to use it
Requirement documents for shops and marketplaces, order system design, and "online store" capstone projects. Three branches that are often forgotten are included: out of stock, payment timeout releasing the reservation, and a return after delivery.
Making it yours
- Add coupons or loyalty points between "Place order" and the stock check.
- The payment timeout is plain text in
H{Paid within 30 minutes?}. - If returns are complex, make "After-sales handling" a subprocess node
M[[After-sales handling]]and draw it separately. - For a role-based view, see the "Order fulfilment swimlane" template.
Mermaid code
flowchart TD
A([Customer opens product page]) --> B[Add to cart]
B --> C[Place order]
C --> D{In stock?}
D -- No --> E[Show out of stock]
E --> Z([End])
D -- Yes --> F[Reserve stock]
F --> G[Choose payment method and pay]
G --> H{Paid within 30 minutes?}
H -- No --> I[Cancel order and release stock]
I --> Z
H -- Yes --> J[Merchant ships]
J --> K[Delivery]
K --> L{Delivery confirmed?}
L -- Return requested --> M[After-sales handling]
M --> Z
L -- Yes --> N[Order complete]
N --> ZAsk an AI for one with this structure
Send the prompt below to ChatGPT or Claude, then paste the whole reply into the editor; the code inside is detected automatically.
Draw an e-commerce order flowchart in Mermaid flowchart TD syntax: the customer opens a product page, adds to cart and places the order; check stock (show out of stock and end if none), reserve stock, choose a payment method and pay; if not paid within 30 minutes cancel the order and release stock; otherwise the merchant ships, the parcel is delivered, and the customer either confirms delivery (order complete) or requests a return (after-sales handling). Use rounded nodes for start and end. Output only the mermaid code block.
FAQ
- Several branches end the flow; can there be one End node?
Yes. Point every edge at the same node id (
Zhere) and only one End node is drawn.- The chart is too tall for one page
Change the first line to
LRfor a horizontal layout, or split after-sales and payment into subprocess diagrams. PDF export sizes the page to the diagram, so nothing is cut off.- Can the cancellation branch be a different colour?
You can add
style I fill:#fde8e8, but it overrides the theme. A dashed edge is simpler:H -. No .-> I.
More in this category
User Registration Flowchart TemplatePhone number sign-up flowchart: check whether the number is registered, send and verify a code, lock after five failed attempts, set a password and create the account. For PRDs and project reports; free PNG, Word and PowerPoint export.
Customer Complaint Handling Flowchart TemplateComplaint handling from logging to closure: resolve on the spot or hand over, investigate, propose a solution and loop until the customer accepts, then follow up. For support handbooks and quality procedures; free PNG, Word and PowerPoint export.
Incident Response Flowchart TemplateProduction incident handling from alert to closure: severity triage (P1 / P2), escalation, root cause, rollback or mitigation, verification, incident report and retrospective. For runbooks; free PNG, Word and PowerPoint export.
Updated 2026-09-05