Restaurant commerce & operations
Baladi Restaurant
PWA ordering, WhatsApp Commerce, KDS, POS and multi-branch restaurant operations.
A connected restaurant technology ecosystem combining customer ordering, WhatsApp Commerce, kitchen workflows, live order status and multi-branch operational control.
Ordering, WhatsApp messages, kitchen preparation, order status and delivery become inefficient when handled in separate places. Multi-branch operations add another layer around menus, roles and service areas.
We developed a PWA-ready restaurant platform with menu customization, WhatsApp ordering, kitchen display workflows, order-status screens, POS, delivery management, multi-branch controls, offers and analytics. Related internal work also digitized procurement, inventory and waste workflows.
The parts of the project that do the actual work.
PWA ordering
Customers browse menus and order through an installable mobile-first experience.
WhatsApp Commerce
WhatsApp participates in ordering and customer communication.
Kitchen Display System
Kitchen staff receive structured orders and status transitions in real time.
Order Status Screen
Live status connects preparation with front-of-house communication.
Multi-branch controls
Branches manage menus, roles, zones and operating rules.
Supply operations
Procurement, inventory, supplier and waste workflows are also digitized.
Menu builder
Items, categories, variations, extras and add-ons are managed as structured menu data.
POS system
In-store orders can share the same menu and operational logic as the wider digital ordering platform.
Delivery management
Orders can move into delivery assignment, address handling and status tracking without leaving the platform.
Offers, coupons & payments
Promotions, discount rules and multiple payment options support the commercial ordering journey.
Analytics & push notifications
Sales reports, order statistics and push alerts support day-to-day restaurant management.
A real interface from the system we built.
The product and engineering decisions behind the result.
Connected front and back of house
The customer order continues into kitchen, status and delivery workflows instead of ending at checkout.
Structured restaurant roles
Admin, manager, chef, waiter and delivery responsibilities can be separated by permissions.
Made the platform branch-aware
Menus, zones, time slots and operating rules can vary by location under one system.
Added operational visibility
KDS, OSS and reporting make order state visible to the teams that need it.
From the first action to the outcome, the workflow stays connected.
Customer chooses
Customer browses menu, variations and add-ons.
Order enters system
The order is captured through PWA or WhatsApp.
Kitchen prepares
KDS moves the order through preparation states.
Status stays visible
OSS and operational views keep progress visible.
Delivery & reporting
Delivery actions and sales feed the wider operating view.
Digital ordering and restaurant operations move through the same workflow.
Customer ordering and back-of-house execution share the same digital flow, reducing handovers between order capture, kitchen status, delivery and branch management.
