
π Retail & E-commerce Β· Data Flow
How stock stays in sync across stores, warehouses and marketplaces so the same item isn't sold twice.
Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.
Drawing diagramβ¦
Data flow for omnichannel inventory: store POS sales, warehouse receipts and dispatches, online orders and returns all send stock events to a central inventory service, which updates stock per SKU per location, calculates available-to-promise minus a safety buffer, and pushes it to the website, the mobile app and marketplaces (Amazon, Flipkart). Low stock triggers replenishment orders to suppliers.
flowchart LR
subgraph EXT ["External entities"]
pos["Store POS"]
wms["Warehouse System"]
web["Online Store and App"]
mkt["Marketplaces (Amazon, Flipkart)"]
sup["Suppliers"]
end
subgraph PROC ["Processes"]
p1("1.0 Receive stock events")
p2("2.0 Update stock per SKU and location")
p3("3.0 Calculate available-to-promise")
p4("4.0 Publish stock levels")
p5("5.0 Trigger replenishment")
end
subgraph STORE ["Data stores"]
d1[("D1 Inventory Ledger")]
d2[("D2 Safety Buffers and Reorder Points")]
end
pos -->|"Sales and store returns"| p1
wms -->|"Receipts and dispatches"| p1
web -->|"Orders, reservations, returns"| p1
p1 -->|"Stock events"| p2
p2 -->|"Stock per SKU per location"| d1
d1 -->|"On-hand and reserved stock"| p3
d2 -->|"Safety buffer"| p3
p3 -->|"Available-to-promise"| p4
p4 -->|"Stock levels"| web
p4 -->|"Stock feed"| mkt
d1 -->|"Stock below reorder point"| p5
d2 -->|"Reorder points"| p5
p5 -->|"Purchase orders"| supA data flow diagram with 10 processes and outside parties, 2 data stores and 13 data flows.
Describe your own system in plain English and CloudSketch AI draws it in seconds. See all AI diagram generators.
An 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 an online store handles a return: eligibility, pickup, quality check at the warehouse and the refund or replacement.
How an online store builds 'recommended for you' and 'frequently bought together': click and order data, model training and a fast serving layer.