Process Flow Swimlane Diagram for Restaurant Operations

Tech architecture infographic titled "Process Flow Swimlane Diagram" using HOW-IT-WORKS archetype adapted as an executive swimlane process architecture for a restaurant / hospitality company, with subtle org-chart / reporting-tree structure across departments. Show horizontal swimlanes with labeled boxes and directional arrows for operational flow: Guest, Front Desk / Host, Floor Staff, Kitchen, Bar, POS System, Payment Gateway, Inventory / Procurement, Management. Each box must include a simple generic icon, a canonical English name, and a one-line English role description. Example boxes: "Guest — initiates reservation, order, and payment", "Host Desk — manages seating and waitlist", "Server — captures order and serves table", "Kitchen Station — prepares food items", "Bar Station — prepares beverage orders", "POS System — records orders and sends tickets", "Payment Gateway — authorizes card transactions", "Inventory System — tracks stock usage and replenishment", "Manager — monitors service quality and exceptions". Connect boxes with clear arrows and short English arrow labels showing what moves between steps, such as "reservation request", "table assignment", "menu order", "POS ticket", "prep status", "served meal", "payment token", "approval code", "stock deduction", "daily report". Include realistic operational steps and technically accurate transactional labels such as "HTTPS payment authorization", "approved / declined", "receipt data", "inventory update", "shift summary". Add small illustrative metrics in English as examples only, such as "avg wait 12 min", "prep time 18 min", "table turn 75 min", "ticket value $42", "daily covers 180". Include numbered legend 1-7 in English walking through the lifecycle: 1. Guest submits reservation or walk-in request. 2. Host assigns table and opens service session. 3. Server enters food and drink order into POS. 4. POS routes tickets to Kitchen and Bar for preparation. 5. Prepared items are delivered and service status is updated. 6. Payment is processed through Payment Gateway and receipt is issued. 7. Inventory and management reports are updated after service completion. Composition should have executive-deck grade clarity, balanced spacing, strong hierarchy, clean swimlane separators, and a light reporting-tree visual cue for department ownership above lanes. Visual style: corporate executive, warm earth professional palette with terracotta, sand, espresso brown, muted olive, cream, and charcoal accents; polished, trustworthy, hospitality-focused mood. Use editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. No real company logos, no real person names, only generic department and tool icons. 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.