Druvus

F&B Ops

Guests order from the table by scanning a code. Orders split themselves between the kitchen and the bar. Cashiers settle, managers watch the numbers as service happens, and nothing leaves the building without a name attached to it.

In service

How one order moves.

A single table, from the moment they sit down to the moment the number lands in your report. Tap any part of it.

The table scans and orders Kitchen food tickets Bar drink tickets Stock comes down Cashier bill and settlement Reports sales, stock, staff
01

The table orders

A guest scans the code on the table and the menu opens on their own phone. Nothing to download, nothing to wait for. If they would rather not use a phone, the waiter places the same order from theirs.

Tap any box to hold it.

What it runs

Service, and everything that moves behind it.

Ordering

Guests scan the code on the table and order from their own phone. No app to install, no waiting to catch someone's eye. Waiters can place orders for a table themselves when a guest would rather not use a phone, and the order follows the same path either way.

  • Menu by category, in your own words
  • Waiter-placed orders for tables that prefer it
  • Guests can see the status of what they ordered

Kitchen and bar

One order arrives as two tickets, in the two places that need it, at the same moment. Nobody carries a docket across a busy floor, and nothing gets lost between the pass and the bar.

  • Separate screens per station, updating live
  • Timers so nothing sits waiting unnoticed
  • The waiter is alerted, with a sound, when an item is ready

Stock

Every dish and every drink is linked to what it is made of. When an order is placed, the ingredients behind it come off stock automatically, with no one keying anything in. A bottle sold is a bottle gone. A plate of brochettes moves the meat, the oil and the garnish together.

  • Recipes linked to items, so stock follows sales on its own
  • A floor set on any item, with an alert before it runs out
  • What was used against what was sold, so gaps show up the same week
  • Counts that start from a live figure

Cashier and settlement

Bills reach the cashier directly, whether the guest requested it or a waiter did. Settlement, closing a table and anything written off all leave a record with a name against it.

  • Bills waiting, open tables and settlements in one place
  • Closing a table with an outstanding balance requires a reason
  • Walkouts, comps and staff meals recorded rather than absorbed

Management

What a manager needs during service, and what an owner needs after it.

  • Sales, top items, waiter performance and settlements
  • Shifts, clock-in and clock-out, with tables handed over automatically
  • Staff, tables and menu managed from one place

Who it is for

Venues where service happens fast and money moves through many hands.

Restaurants and lounges

Full service venues where the floor, the kitchen and the bar have to stay in step through a busy night.

Bars and coffee shops

High volume and fast turnover, where a lost order or an unrecorded drink adds up quietly across a month.

Hotel F&B

Properties that want their restaurant and bar running properly without replacing the system that handles rooms.

Built here, for how service actually runs here.

F&B Ops was not adapted from a system built for somewhere else. It was shaped in a working Kigali venue, on real Friday nights.

It runs in a browser on whatever hardware a venue already owns: phones, tablets, an old laptop at the till. It installs to a home screen, so staff open it the way they open any other app.

F&B Ops is a product of Druvus Ltd.

Questions we get asked

The practical ones, answered plainly.

Do we need to buy tablets or a till system?

No. It runs in a web browser, so it works on the phones your staff already carry, a tablet if you have one, and any laptop for the cashier and manager. Guests use their own phones and install nothing.

The only thing you actually need is a printed QR code on each table, which we generate for you.

What happens if the internet goes down?

The system needs a working connection. It is hosted in the cloud rather than on a machine in your back office, which is what lets you check your numbers from home and keeps your data safe if a laptop is stolen. It does mean a total outage stops ordering until the connection returns.

In practice that means a venue should have a backup, usually mobile data on the manager's phone. We would rather tell you this now than let you find out on a Friday.

How long does setup take?

The work is mostly your menu and your floor plan. You can paste a menu in as a block of text instead of typing it item by item, tables are created once with their codes generated automatically, and staff accounts take a few minutes each.

We set it up with you rather than handing you a login and wishing you luck, and we are there for the first live service.

Where does our data live, and who can see it?

Your venue's data is held in a cloud database hosted in South Africa, the nearest region to Rwanda, and it is isolated from every other venue on the system. Nobody at another venue can see your sales, your menu or your staff.

Every role signs in separately: managers, waiters, kitchen, bar and cashier. Every action carries a name, which is the point of the audit trail.

Can we try it before committing?

Yes. We will set it up against your own menu and walk it through with you, so you are judging your venue rather than a demo one. If it does not fit the way you work, that is a useful answer too.

See it running in your venue.

Tell us the venue, roughly how many tables, and whether you already use anything. We will set it up against your own menu and show you that, not a demo.

Email

hello@druvus.rw

Find us

Norrsken House Kigali
1 KN 78 Street, Nyarugenge
Kigali, Rwanda