Guests wait to get a menu or place an add-on.
They scan the table QR, choose Arabic or English, order, call a waiter, and request the bill.
Restaurant operations, connected
One order. One clear path from table to close.
RestuHub connects bilingual table QR ordering with public pickup or delivery. Cashiers, waiters, kitchen teams, and pickup staff share one protected order and payment history.
Built around the way a real restaurant shift moves—not a generic online menu.
Where time gets lost
Replace hand-offs with one shared order record.
RestuHub keeps each role focused while every update lands on the same live order, table, and payment history.
Cashier and kitchen receive incomplete verbal changes.
The cashier confirms the order, then routed original or add-on tickets enter the kitchen print queue.
The floor cannot see who owns a table or request.
Waiter assignments, service calls, table status, and checkout requests stay visible to operations.
Closing totals depend on memory and loose receipts.
Server-calculated totals, payment rows, status history, and table release are persisted together.
The operating loop
A controlled path through the whole shift.
Every step below is implemented in the current product and backed by the same live database.
01 · Guest
Scan and send
The table QR opens its bilingual menu. The guest chooses items and modifiers, then submits a server-priced order.
02 · Cashier
Review and confirm
The order appears as Needs review. Confirmation creates controlled kitchen work and starts its status history.
03 · Floor + kitchen
Prepare and serve
Waiter ownership, service calls, table state, kitchen routing, retries, and add-on tickets remain traceable.
04 · Close
Collect and reconcile
Cash, card, or split collection persists against the order. Exact final payment closes it and safely releases the table.
Rendered from the live system
Real product screens, not dashboard illustrations.
These screens were captured from the working application with PostgreSQL-backed tables, orders, shifts, and menu data. Credentials, QR tokens, cookies, and full record IDs are excluded.
A phone-first guest menu
A real 393px menu view with bilingual controls, table context, a persisted item, and waiter access.
The floor stays visible at the cashier
Needs-review orders, service calls, unassigned work, and live table states share one operational view.
The waiter sees the next action
Shift state, assigned requests, available orders, and table status are fetched from the operational database.
Clear responsibilities
One system, role-specific controls.
Guest
Browse, order, follow
No staff account. A table QR and protected order session keep the guest inside their own visit.
Storefront customer
Order pickup or delivery
A public bilingual menu supports server-priced checkout, protected tracking, cash, and reviewed wallet evidence without exposing another order.
Waiter
Work the floor
PIN access, shift state, owned orders, service requests, table context, and manual ordering.
Cashier
Control the lifecycle
Review, confirm, assign, advance, collect, reprint, and recover through guided actions.
Pickup Man
Dispatch and hand over
Claim ready work, record status changes, collect the exact cash due, attach evidence, and complete a reconciled handover.
Admin / Owner
Configure and inspect
Menu, tables, staff, attendance, printers, theme settings, and restaurant-scoped analytics.
Kitchen
Receive routed work
Confirmed original, add-on, and reprint jobs are routed to configured stations with retry history.
Current single-restaurant plans
Choose the operating depth you need.
Annual prices match the active July 2026 pricing file. Prices exclude VAT; onboarding and printer hardware are separate where shown.
Starter
Small cafés and kiosks · up to 15 tables
12,000EGP / year
- Effective monthly on annual billing
- 1,000 EGP
- One-time onboarding
- 1,500 EGP
- Bilingual QR menu and guest ordering
- Order tracking and waiter calls
- Cashier table and order controls
- One restaurant with the default theme
Growth
Full-service restaurants · unlimited tables
24,000EGP / year
- Effective monthly on annual billing
- 2,000 EGP
- One-time onboarding
- 3,000 EGP
- Everything in Starter
- Waiter and Cashier PIN workflows
- Attendance, staff, and Admin controls
- Assignments, transfers, discounts, and void approvals
Premium
Restaurants adding controlled kitchen printing
34,000EGP / year
- Effective monthly on annual billing
- 2,833 EGP
- One-time onboarding
- 4,500 EGP + hardware
- Everything in Growth
- Original, add-on, and reprint tickets
- Multi-station category routing
- Queue, lease, retry, and failure diagnostics
Storefront
Restaurants adding public pickup and delivery
48,000EGP / year
- Effective monthly on annual billing
- 4,000 EGP
- One-time onboarding
- 5,000 EGP
- Everything in Premium
- Public bilingual menu, checkout, and protected tracking
- Pickup Man, dispatch, evidence, and cash handover
- Manual wallet review and delivery-fee controls
Premium and Storefront include the printing entitlement, but printer hardware is optional and quoted separately. The active cost model estimates 10,000–15,000 EGP for a typical single-station kit.
Multi-branch is not for sale yet
The current release securely scopes one restaurant per account. Consolidated cross-branch reporting and group management are not implemented, so they are intentionally excluded from these plans.
Straight answers
What the current release does—and does not do.
Does the guest need an app or account?
No. The guest scans the table QR in a browser. A protected device session is created only for that table order.
Does every order print automatically?
No. Guest orders first enter Cashier review. A confirmed order creates routed kitchen work; printer hardware and the local print agent are part of the Premium setup.
Can customers pay online?
Storefront customers can choose cash or submit manual wallet-transfer evidence for staff review. Table orders still close through the Cashier, and an automated card-payment gateway is not advertised.
What happens during an internet interruption?
The product reports connection loss and retries safe live-data reads. New orders, status changes, and payments require server confirmation; the page does not claim an unconfirmed mutation was saved.
Do I need kitchen hardware?
Not for Starter or Growth, and Storefront can operate without a printer. Premium or Storefront printing needs compatible thermal-printer hardware and an installed local print agent, quoted separately.
Can I manage several branches in one account?
Not yet. The current release operates one restaurant per account. Cross-branch reporting will not be sold until it is implemented and verified.
See how the product separates each role.
Open the product entry to review the table Guest, Storefront customer, Waiter, Cashier, Pickup Man, Admin, and authenticated Kitchen surfaces available in this build.