
π Retail & E-commerce Β· Flowchart
How an online store handles a return: eligibility, pickup, quality check at the warehouse and the refund or replacement.
Drawing diagramβ¦
Returns flowchart: the customer requests a return in the app, the system checks the return window (7 days) and whether the category is returnable. Eligible returns get a reverse pickup scheduled, the item reaches the warehouse and goes through quality check: good condition gives a full refund or replacement, minor damage a partial refund, wrong or used items are rejected and shipped back. Refunds go to the original payment method or store credit.
flowchart TD
A[Customer requests return] --> B{Within 7 days and returnable?}
B -->|No| C[Explain why not eligible]
B -->|Yes| D[Refund or replacement?]
D --> E[Schedule reverse pickup]
E --> F[Item reaches warehouse]
F --> G{Quality check}
G -->|Good condition| H[Full refund or ship replacement]
G -->|Minor damage| I[Partial refund]
G -->|Wrong or used item| J[Reject and ship back]
H --> K[Refund to original payment or store credit]
I --> KAn online store split into microservices: catalog, cart, orders, payments and search, with Kafka events connecting them to shipping and notifications.
What happens when a shopper clicks Pay: stock is reserved, the payment is authorised, the order is created and stock is released again if payment fails.
Every status an online order moves through, from placed to delivered, including cancellations, returns and refunds.
A flexible product catalog: categories, products with variants (size, colour), prices, stock per warehouse and images.
How stock stays in sync across stores, warehouses and marketplaces so the same item isn't sold twice.
How an online store builds 'recommended for you' and 'frequently bought together': click and order data, model training and a fast serving layer.