Supply Chain Management Architecture Infographic Blueprint

Tech architecture infographic titled "Supply Chain Management Architecture" using SYSTEM ARCHITECTURE archetype. Create an executive-deck grade supply chain map for a logistics / supply chain company, laid out left-to-right as a clear end-to-end operating model with labeled boxes and directional arrows. Include these main modules as boxes: Supplier Network, Inbound Transportation, Receiving & Putaway, Warehouse Operations, Inventory Control System, Order Management System, Distribution Centers, Last-Mile Delivery, Returns Processing, Analytics & Control Tower, and Customer / Retail Channels. Each box must contain an icon, the component name, and a one-line role description in English. Example role lines: Supplier Network — "Provides goods and ASN shipment data"; Inbound Transportation — "Moves inbound freight to warehouse or DC"; Receiving & Putaway — "Checks, scans, and stores arriving inventory"; Warehouse Operations — "Picks, packs, stages, and replenishes stock"; Inventory Control System — "Tracks stock levels, locations, and adjustments"; Order Management System — "Allocates inventory and orchestrates fulfillment"; Distribution Centers — "Consolidates outbound shipments for regional delivery"; Last-Mile Delivery — "Delivers parcels to end customers or stores"; Returns Processing — "Inspects, restocks, or disposes returned items"; Analytics & Control Tower — "Monitors KPIs, exceptions, forecasts, and network health"; Customer / Retail Channels — "Submits orders and receives delivery status updates".

Show arrows with short English labels describing what moves between modules, such as: "PO", "ASN", "Inbound shipment", "Dock receipt", "Barcode scan", "Stock update", "Pick list", "Packed order", "Transfer shipment", "Delivery manifest", "Proof of delivery", "Return authorization", "Restock decision", "KPI dashboard", "Demand forecast". Make flows technically plausible for supply chain operations: Supplier Network -> Inbound Transportation -> Receiving & Putaway -> Warehouse Operations / Inventory Control System; Customer / Retail Channels -> Order Management System -> Inventory Control System -> Warehouse Operations -> Distribution Centers -> Last-Mile Delivery -> Customer / Retail Channels; Returns Processing loops back into Inventory Control System and Analytics & Control Tower; Analytics & Control Tower receives data feeds from OMS, inventory, warehouse, delivery, and returns.

Add subtle photorealistic miniature scenes embedded inside key modules: trucks at Inbound Transportation, pallets and dock doors at Receiving & Putaway, warehouse shelving and forklifts at Warehouse Operations, barcode scanning at Inventory Control System, parcel sorting at Distribution Centers, delivery vans at Last-Mile Delivery, inspection table at Returns Processing. Keep these miniature scenes tasteful, small, and integrated into a clean vector infographic without overpowering the diagram.

Add a numbered legend 1-7 in English walking through the lifecycle: 1. Suppliers confirm goods and send ASN data. 2. Inbound transport delivers freight to receiving docks. 3. Warehouse teams scan, verify, and store inventory. 4. Order Management allocates stock and releases fulfillment tasks. 5. Warehouse and distribution centers pick, pack, and route shipments. 6. Last-mile carriers deliver orders and capture proof of delivery. 7. Returns and analytics feed continuous inventory, service, and planning improvements.

Visual style: corporate executive, presentation-slide clarity, clean hierarchy, balanced whitespace, crisp typography, subtle depth, polished boardroom-ready composition. Color palette: tech blue and cyan with white and light gray neutrals, dark navy headings, cyan accents for active flows, muted blue secondary connectors. Overall mood: strategic, trustworthy, modern, operationally efficient. Include editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. All text rendered cleanly in English, no spelling errors, no gibberish characters, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real-company logos. Use generic icons for departments / tools / vendors. Org-chart titles stay neutral (no real person names). Process timings / costs / volumes are illustrative example values.