Bilingual storefront
English/Arabic menu with dish-of-the-day weekly scheduling, portions from single plates to family trays, dish photos and allergen info.
Restaurant OS + Storefront
Bait Zeina.
A delivery kitchen's complete operating system: a bilingual customer storefront with WhatsApp checkout, and the POS, kitchen, inventory, finance and CRM that staff run the business on every day.
Visit baitzeina.com Lebanese home-cooking delivery kitchen — Tripoli, Lebanon
A coded depiction of the real product — the live system is one click above.
The situation
Bait Zeina cooks Lebanese home food daily, with a menu that rotates by weekday and a cash drawer that lives in two currencies — USD and Lebanese pounds at a moving rate.
Orders arrived as free-text WhatsApp messages: no order codes, no kitchen visibility, no stock or cost tracking, and settling a mixed USD/LBP payment meant mental math at the counter.
What we built
WhatsApp checkout
Cart builds a structured WhatsApp order with a friendly code (ORD-042) and a live tracking page — customers order in the app they already use.
Touch-first POS
Counter sales with USD/LBP split payments and live change math at the house rate, cash-shift open/close, bilingual 80mm receipts and WhatsApp receipts.
Orders & kitchen
One order lifecycle from confirmed to delivered — coordinator buttons for the real team flow, delivery fees, and a kitchen board when it's needed.
Inventory & purchasing
Ingredients, purchase orders, stock counts and supplier invoices with due dates — the kitchen's costs stop being a guess.
Finance & analytics
A single source of truth for orders, expenses and payments. Profit is computed from costs frozen at sale time, with role-based dashboards.
Customer CRM
Customer records build themselves from orders — phone, name and delivery address are remembered for next time, with follow-ups for the team.
Staff & roles
Six staff roles with per-module permissions — the cashier, the kitchen and the accountant each see exactly what they need.
Under the hood
- Every database write goes through server-side functions — prices are computed server-side, so a tampered cart physically cannot create a mispriced order
- Row-level security on every table; deny-by-default access
- Idempotent order submission with rate limiting — a double-tap or replay cannot create a duplicate order
- 40+ versioned database migrations and an automated test suite guard every change
- Two-currency accounting with Beirut-timezone-correct daily books
ReactTypeScriptTailwindSupabaseVercel
Want a system like this?
One scoping call, a fixed quote, and we build.