Skip to content
Book a demo

What Restree runs, stage by stage

⁨32⁩ capabilities across the five stages of a restaurant's day, for one branch or a group.

Buy

Order what the week needs, and pay only for what arrived.

Suggested orders
Drafted from every item that fell below its par level.
Purchase orders
Raised against a supplier and sent from one place.
Receiving
Deliveries checked against the order, shortages recorded.
Three-way match
Invoice, order and delivery compared before you pay.
Supplier returns
Sent back, and credited against the invoice.
Price trends
What each ingredient cost, delivery by delivery.

Stock

Know what is on the shelf in every branch, and what it cost.

Stock by location
Every storeroom in every branch, at average cost.
Production
Sauces and bases made in batches, with their real yields.
Transfers
Stock moved between branches, tracked while in transit.
Stock counts
Counted against the book, with the difference costed.
Wastage
Recorded with a reason, and costed.
Par levels and expiry
Minimums per item, and what is about to expire.

Sell

A full Friday doesn't wait for the internet.

The POS
Dine-in, takeaway, delivery and phone orders, with modifiers and split bills.
Offline selling
Keeps taking orders through an outage, and syncs them in order.
Kitchen screens
Each ticket on the station that cooks it, with bump and recall.
Tables and reservations
The floor, bookings and the waitlist.
Call centre
Phone orders taken for any branch.
Delivery
Zones, fees and dispatch to drivers.
Approvals
Voids and discounts past a limit wait for a manager's PIN.

Close

Close the day on counted cash, not a guess.

Shifts and blind counts
Each drawer counted before the expected figure is shown.
Day close
The day won't close with orders or shifts still open.
Refunds and settlements
Refunds traced to their order, card settlements matched.
Journal posting
The day posted to your chart of accounts.
VAT
Collected and paid, by period.
Bank reconciliation
Statements matched to what the books expect.
Month-end close
Close the month and lock it against changes.

Improve

See what every plate earned, and where the gap is.

Profit and loss
Per branch and for the group, with the statements.
Food cost
Cost of goods reconciled against what the recipes used.
Usage variance
Where stock went that no sale explains.
Menu engineering
Which dishes earn, which sell, and which to change.
Branch comparison
Scorecards side by side, the drifting branch flagged.
Budgets
Set per branch, and tracked against the actuals.

Follow one order from the POS to the books

Order ⁦#1042⁩, table ⁨4⁩, at Nawa in Zamalek. Nobody types it twice.

  1. 12:41Sell

    Rung up at the POS

    The internet is down. The POS keeps the order with ⁨3⁩ others and sends them, in order, when the line is back.

  2. 12:41Sell

    On the kitchen screens

    The koshari goes to the hot line, the hawawshi to the grill, the karkade to the bar. Each station sees only its own.

  3. 23:10Stock

    Out of stock, by the recipe

    When the day closes, each koshari recipe takes its rice, lentils and onions out of the stockroom.

  4. 23:10Close

    In the day's numbers

    One of ⁨212⁩ orders in Zamalek's day close report, beside net sales, food cost and a drawer ⁨EGP 50.00⁩ short.

  5. 23:12Close

    Posted for your accountant

    The day's sales, VAT, cash and cost of goods, as one journal entry that balances to the piastre.

Everyone sees their own job

A cashier sees the POS. A chef sees tickets. Nobody is trained on a screen they will never open.

And eight more roles: org admin, supervisor, waiter, kitchen staff, storekeeper, purchaser, delivery driver and call-centre agent.

Built for how restaurants here run

The POS keeps selling
Once signed in, the POS keeps selling through an outage and sends every order, in order, when the line is back.
Arabic, properly
Every screen, report and receipt works right to left, and each person picks their own language.
Every sensitive action is logged
Voids, refunds, price and permission changes are recorded with who, when and on which device, and cannot be edited.
Tenant isolation at the database
The database itself keeps each restaurant's data apart, not only the app.
Export is always available
Take all your data out whenever you like, and for 90 days after you leave.
Accounting
Each day's sales, payments and costs, exported for your accountant's system.
Processor-neutral
Keep the card terminal and bank you already use; payments are recorded against each order.

Questions owners ask before switching

Straight answers about setup, devices and your data.

  • What happens when the internet drops?

    The POS keeps selling once it is signed in. Orders queue on the device and sync when the connection returns — exactly once, in the order they happened. Shift open and close work offline too; sign-in and manager approvals need a connection.

  • What devices do I need?

    The POS and kitchen screens run in a web browser, with a desktop app available. Each is paired to a branch with a one-time code. The back office works in any modern browser, including on a phone.

  • Can I bring my existing menu and stock list?

    Yes. Menus and stock items import from CSV, and a menu import runs as a preview first, so you see what will change before anything is saved. You can also start with a quick menu and add detail later.

  • How does setup work?

    After the demo we create your workspace and owner account. A setup wizard then takes you through your business details, first branch, menu, devices and team, with a go-live checklist that shows what is left.

  • Can I export my data if I leave?

    Yes, at any point, including after cancelling and after a trial lapses. A lapsed workspace goes read-only and stays that way, with export available throughout. After cancellation, your data is kept for 90 days before it can be deleted. It is never silently deleted.

  • How much does it cost?

    Pricing is per branch, not per terminal — so adding a POS terminal, a kitchen screen or a manager's tablet does not move the bill. What you pay depends on how many branches you run and which areas you use, and we quote it on the demo call once we know both.

See your own menu costed

A walkthrough with our team, in Arabic or English, shaped around your menu and how many branches you run.

Book a demo