Customer Journey Flow Chart for Logistics Service Blueprint

Tech architecture infographic titled "Customer Journey Flow Chart" — HOW-IT-WORKS adapted as a SERVICE BLUEPRINT for a logistics / supply chain company, with two horizontal swimlanes: Front Stage (customer-visible journey) and Back Stage (internal operations), plus a lower Support Systems lane. Show a left-to-right lifecycle with labeled BOXES connected by directional ARROWS. Front Stage boxes: Customer, Web Portal / Mobile App, Order Confirmation, Shipment Tracking, Delivery Experience, Support Request. Back Stage boxes: CRM, Order Management System (OMS), Inventory / Warehouse Management System (WMS), Carrier Allocation Engine, Transportation Management System (TMS), Dispatch Team, Last-Mile Driver, Returns Processing. Support Systems boxes: Payment Gateway, Notification Service, Analytics Dashboard, Data Warehouse, ERP / Billing, Customer Support Desk. Each box must include a simple generic icon, the component name in canonical English-tech form, and a one-line English role description. Example role descriptions: Customer — "Places order and tracks shipment status"; OMS — "Validates order and orchestrates fulfillment workflow"; WMS — "Reserves stock and coordinates warehouse picking"; TMS — "Plans route, handoff, and delivery milestones"; Notification Service — "Sends email, SMS, and push updates". Use arrows with short English labels describing the flow content, such as: "Order request", "HTTPS checkout", "Payment auth", "Order created", "Stock reservation", "Pick list", "Carrier assignment", "Tracking event", "Out for delivery", "Proof of delivery", "Status update", "Refund request", "Return authorization". Include realistic logistics signals and metrics in small callouts: "ETA 2 days", "Payment authorized 200 OK", "Inventory reserved", "Tracking webhook", "Delivery confirmed", "Refund issued". Add clear stage separators and front-stage / back-stage interaction lines typical of a service blueprint. Include a numbered legend 1-7 in English explaining the lifecycle: 1 Customer submits order via portal, 2 Payment Gateway authorizes transaction and OMS creates order, 3 WMS reserves inventory and generates pick-pack tasks, 4 Carrier Allocation Engine selects carrier and TMS creates shipment, 5 Notification Service sends tracking link and milestones, 6 Last-Mile Driver completes delivery and proof of delivery is captured, 7 Support Desk and Returns Processing handle issues, returns, or refunds. Make the flow technically accurate for commerce and logistics operations, using canonical protocol terms where relevant: HTTPS API call, webhook event, REST status update, 200 OK authorization, JSON payload, barcode scan. Visual style: blueprint schematic, executive-deck grade clarity, dark dashboard palette with deep navy background, cyan grid lines, electric blue and teal boxes, white typography, subtle amber accents for alerts, thin vector strokes, precision arrows, clean layered swimlanes, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Use generic department, warehouse, truck, package, credit card, chatbot, dashboard, and database icons only; no real-company logos, no person-specific names, no watermarks. All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, 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.