Food & Beverage: ready template

Build an internal Kitchen Display System (KDS) that receives orders in real time from the POS and online ordering channels and routes them to preparation stations (grill, appetizers, drinks), with a timer on each order and a color alert when it's running late. Make updates instant over WebSocket so orders appear on screen without a page refresh, with a task queue that guarantees correct ordering during peak times, and caching of each station's status to reduce database load. Add roles and permissions (RBAC): the branch manager sees all stations and reports, while a cook sees only their own station, with secure, encrypted login. Design a database indexed by branch, time, and order status, ready to be partitioned as branches multiply, with scheduled backups and logs for every status change. Make the interface Arabic RTL-first with English support, with large, touch-friendly text suited to a kitchen touchscreen, and accessibility support. Add an observability dashboard showing average prep time per item and station, and the rate of late orders. Apply rate limiting and protection against common attacks on the API. Deliver the system production-ready with basic tests and short documentation on how to add a new branch or station.

Build a self-ordering platform for inside the restaurant where the customer scans a QR code on their table to open the item menu with photos, prices, and add-ons, then orders and pays directly from their phone without waiting for a waiter. Link the order to the table number so it reaches the kitchen display instantly with the location identified, and support payment via mada, Apple Pay, and Moyasar/HyperPay through an API key in the secrets vault, along with issuing a ZATCA-compliant e-invoice (tax number, QR code, and item details). Make the customer interface fast and lightweight, delivered over a CDN and cached so it opens instantly on any phone, Arabic RTL-first with English support and accessibility. Design an architecture that handles thousands of concurrent tables: an indexed database, queues for processing payments and issuing invoices, and protection against attacks with rate limiting. Add an admin dashboard with roles and permissions to edit the menu, prices, and promotions, and instantly disable an item that's out of stock. Provide the customer with real-time order status tracking (preparing/ready), and sales reports by table and time period. Deliver it production-ready with monitoring, logs, backups, tests, and short documentation.

Build a marketing automation engine that gathers customer data from orders (phone number, favorite items, last order date) and triggers automatic WhatsApp and SMS campaigns: a welcome message for new customers, a win-back message for inactive ones, a birthday offer, and a review request after pickup. Base campaigns on segments and rules (e.g., customers who haven't ordered in 30 days), and send them through a task queue with rate limiting to avoid getting blocked, plus scheduled send times. Connect WhatsApp and SMS through API keys in the secrets vault, and log the status of every message (sent/delivered/read) in an analytics dashboard. Design a database indexed by customer, campaign, and status, scalable to millions of messages, with caching for recurring segments and backups. Add roles and permissions (RBAC): marketers create campaigns and a manager approves them, with secure login. Respect privacy with an opt-out option on every message. Make the dashboard Arabic RTL-first with analytics on open rate, conversion, and return per campaign, plus monitoring and error logs. Deliver it production-ready with tests and short documentation.

Build a customer mobile app (Expo for Android and iOS, plus a PWA) that shows the menu, accepts orders for pickup or delivery, and takes payment via mada and Apple Pay, with a loyalty and points program, a digital wallet, and subscription plans (like a monthly coffee subscription). Link points to the customer's phone number and account, update them in real time after every order, and support redeeming points for items or discounts. Send scheduled push notifications for promotions and subscription reminders, and log ZATCA-compliant e-invoices in the customer's purchase history. Design a backend (API) and an indexed database scalable to millions of users, with caching for account and menu data, queues for processing payments and notifications, and a CDN for images. Apply roles and permissions, secure login (OTP via phone), data encryption, protection against attacks, rate limiting, and backups. Make the app Arabic RTL-first with English support, accessibility, and a smooth, professional user experience. Add analytics on customer behavior, order frequency, and customer lifetime value, with monitoring and logs. Deliver it production-ready and Expo Go-compatible, with tests and short documentation.

Build a unified cloud platform that manages multiple brands and dozens to hundreds of branches from a single place, with a multi-tenant architecture that logically isolates each brand's data while sharing the underlying infrastructure. Design it to handle millions of daily orders: an indexed database with sharding/partitioning by brand and branch, multi-layer caching for menus, prices, and stock status, task queues for heavy operations like invoicing, reports, and campaigns, and a CDN for static assets. Route requests through APIs designed for high load, with rate limiting and protection against common attacks. Apply fine-grained roles and permissions (RBAC) at the brand, branch, and user level, with secure login, full encryption, scheduled backups, and disaster recovery. Unify inventory, sales, invoicing (ZATCA), and loyalty across all branches in a central dashboard with aggregated reports and alerts. Add comprehensive observability: performance dashboards, error tracking, and alerts when a branch exceeds load thresholds or goes down. Make every interface Arabic RTL-first with English support and accessibility. Deliver it production-ready with load tests and short architectural documentation for adding a new brand or branch.