CloudSketch AI Logo
FeaturesTemplatesPricingEnterpriseAboutContactLog in
πŸŒ™β˜€οΈ
Log inStart free
Home/Templates/Retail & E-commerce

πŸ›’ Retail & E-commerce Β· Data Flow

Omnichannel Inventory Sync

How stock stays in sync across stores, warehouses and marketplaces so the same item isn't sold twice.

More Retail & E-commerce templates

Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.

Drawing diagram…

What this diagram shows

  • Every sale, return and receipt updates one inventory service
  • Available-to-promise is pushed to the website and marketplaces
  • A safety buffer protects against overselling

Prompt used

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.

Mermaid code
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"| sup

Inside this diagram

A data flow diagram with 10 processes and outside parties, 2 data stores and 13 data flows.

Processes and outside parties

  • Store POS
  • Warehouse System
  • Online Store and App
  • Marketplaces (Amazon, Flipkart)
  • Suppliers
  • 1.0 Receive stock events
  • 2.0 Update stock per SKU and location
  • 3.0 Calculate available-to-promise
  • 4.0 Publish stock levels
  • 5.0 Trigger replenishment

Data stores

  • D1 Inventory Ledger
  • D2 Safety Buffers and Reorder Points

Data flows

  • Store POS β†’ 1.0 Receive stock events: Sales and store returns
  • Warehouse System β†’ 1.0 Receive stock events: Receipts and dispatches
  • Online Store and App β†’ 1.0 Receive stock events: Orders, reservations, returns
  • 1.0 Receive stock events β†’ 2.0 Update stock per SKU and location: Stock events
  • 2.0 Update stock per SKU and location β†’ D1 Inventory Ledger: Stock per SKU per location
  • D1 Inventory Ledger β†’ 3.0 Calculate available-to-promise: On-hand and reserved stock
  • D2 Safety Buffers and Reorder Points β†’ 3.0 Calculate available-to-promise: Safety buffer
  • 3.0 Calculate available-to-promise β†’ 4.0 Publish stock levels: Available-to-promise
  • 4.0 Publish stock levels β†’ Online Store and App: Stock levels
  • 4.0 Publish stock levels β†’ Marketplaces (Amazon, Flipkart): Stock feed
  • D1 Inventory Ledger β†’ 5.0 Trigger replenishment: Stock below reorder point
  • D2 Safety Buffers and Reorder Points β†’ 5.0 Trigger replenishment: Reorder points
  • 5.0 Trigger replenishment β†’ Suppliers: Purchase orders

Boundaries

  • External entities: Store POS, Warehouse System, Online Store and App, Marketplaces (Amazon, Flipkart) and Suppliers
  • Processes: 1.0 Receive stock events, 2.0 Update stock per SKU and location, 3.0 Calculate available-to-promise, 4.0 Publish stock levels and 5.0 Trigger replenishment
  • Data stores: D1 Inventory Ledger and D2 Safety Buffers and Reorder Points

Make your own diagram like this

Describe your own system in plain English and CloudSketch AI draws it in seconds. See all AI diagram generators.

Related templates

C4 ArchitectureProRetail & E-commerce

E-commerce Microservices Architecture

An online store split into microservices: catalog, cart, orders, payments and search, with Kafka events connecting them to shipping and notifications.

SequenceRetail & E-commerce

Checkout and Payment Sequence

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.

State MachineRetail & E-commerce

Order Lifecycle State Machine

Every status an online order moves through, from placed to delivered, including cancellations, returns and refunds.

Database ERDRetail & E-commerce

Product Catalog Database Schema

A flexible product catalog: categories, products with variants (size, colour), prices, stock per warehouse and images.

FlowchartRetail & E-commerce

Returns and Refunds Workflow

How an online store handles a return: eligibility, pickup, quality check at the warehouse and the refund or replacement.

Data FlowRetail & E-commerce

Product Recommendation Engine

How an online store builds 'recommended for you' and 'frequently bought together': click and order data, model training and a fast serving layer.