The full journey of an order, from the customer to the till — screen by screen.
Explore the journeyThe journey of an order
Behind the scenes, the admin sets the stage before the first customer ever arrives: locations, menu, theme, permissions.
CUSTOMER
They scan the QR code on their table, browse the menu organized by category with photos, build their order and send it. They then track every step live — validated, sent to the kitchen, preparing, ready, served — and can request the bill or report an issue directly from their phone, nothing to install.
In practice: paying with Orange Money or Areeba Money takes three screens, no app to install.
CASHIER
They're notified as soon as an order comes in, validate it to send it to the kitchen, and can also create an order manually for a walk-in customer. When it's time to pay, they charge cash or mobile money, print the receipt, and see their day's activity (payments, history) at a glance.
In practice: charging an order automatically generates a proper receipt, ready to hand over.
KITCHEN
Every order sent arrives as a ticket, organized by preparation station. The kitchen accepts, prepares and marks each item ready, with allergens and customer notes clearly visible. It can also flag a delay or ask for clarification — to the customer or the cashier, depending on the need.
In practice: a ticket left past the admin's configured threshold changes color — impossible to miss.
FLOOR
The waiter is notified when an order is ready to serve or a table needs help, without being interrupted by what doesn't concern them. They mark orders served and see the history of what they personally handled.
In practice: the waiter only sees the tables that concern them, never the whole floor's traffic.
ADMIN
The location configures its restaurants and dining rooms, its menu and categories, its visual theme, the accepted payment methods, each role's permissions and advanced settings (QR code URLs, kitchen alert thresholds) — all from one place, no code involved.
In practice: changing the location's logo or colors applies instantly, no redeploy needed.
$ ./install-local.sh
Checking Docker…
✓ Docker found
Your restaurant's name › The Conakry Gourmet
✓ Database initialized
✓ Administrator account created
Restora is ready → http://192.168.1.42:3001
In the cloud, on dedicated infrastructure with automatic backups. With a local install, your data stays entirely on your own server — it never leaves your premises.
In the cloud, yes, automatically, no action needed. Locally, a backup script is included (infrastructure/scripts/backup.sh) — schedule it however fits your setup.
Yes — Restora is multi-location from day one. You can add restaurants and branches from the admin area, within your plan's limits.
The 7-day trial gives access to every core feature, no card required. After that, a subscription is needed to keep going — contact us for the plan that fits your location.
Cloud and local are two ways of running Restora, not two different products. Contact us and we'll help you move your data.
The Restora team is available for any technical question, whether you're on the cloud or a local install.
