Short answer
A restaurant automates sales and inventory by putting every order into one system: the waiter opens it on a table, the kitchen gets a ticket, the cashier closes the bill with cash or mobile money, bottled drinks come off stock as they sell, and ingredients are tracked through purchases and weekly counts. A QR menu can then let guests view the menu and order from their phones.
On this page
Most restaurants in Tanzania still run on three separate records: the waiter’s order pad, the kitchen’s memory and the cashier’s book. Each one is a place where money leaks. A plate goes out and is never billed, a sack of rice disappears between the market and the store, a mobile money payment arrives with no bill attached. This guide shows how to join those records into one flow, what to automate first, what it costs in shillings, and where a QR menu fits.
Where restaurant money leaks
Before choosing any software, walk through a single lunch service and watch where information gets lost. In most kitchens the same five gaps appear.
| Gap | What it looks like on the floor | What it costs you |
|---|---|---|
| Order to kitchen | Waiter shouts “two pilau, one chips mayai” through the hatch | Wrong plates, remakes, unhappy tables |
| Kitchen to bill | A plate leaves the pass without being written on any bill | Food cost with no sale |
| Bill to payment | Table of six pays partly cash, partly M-Pesa, partly Airtel Money | Shortages at closing nobody can explain |
| Store to kitchen | Cooking oil, rice and meat taken from the store without a record | Ingredient cost rises while sales stay flat |
| Day to month | Takings written in a notebook, never totalled by dish | No idea which dishes actually make money |
A restaurant POS closes these gaps by making the order itself the record that travels from table to kitchen to cashier to stock.
How an automated order flows
Picture a mid-sized restaurant in Arusha with twelve tables, three waiters and one cashier. Here is the same lunch with a POS in place.
1. The waiter opens the order on the table
The waiter walks to table 4, opens a new order against that table number on a phone or tablet, and adds two plates of nyama choma, one ugali and three sodas. The order carries the waiter’s login, so the owner can later see who served which table.
2. The kitchen receives a ticket
As soon as the order is placed, the kitchen gets a ticket listing the dishes for table 4. Cooks prepare exactly what was entered. If the guests ask for an extra portion of kachumbari ten minutes later, the waiter adds it to the open order and a new ticket goes through.
3. The order stays open while guests eat
Nothing is charged yet. The bill grows as guests order more drinks or dessert. The manager can see which tables still have open orders, which matters at the end of a shift when a waiter wants to leave.
4. The cashier closes and splits the bill
When the table is ready, the cashier opens the same order, splits it if the guests want to pay separately, and takes each share by cash, M-Pesa, Tigo Pesa, Airtel Money or a recorded card payment. Tips can be recorded at the same time. The bill can be printed, or sent to the guest as an invoice on WhatsApp.
5. Sales and stock update in the background
Bottled drinks and other items you sell as they are come off stock with each sale. At closing, the day’s sales, payment totals by method and open tables are on one report instead of three notebooks.
SmartBiashara supports this flow with table and order management, kitchen tickets, split bills and tips as part of its restaurant tools, all running in a browser on the POS.
Inventory: the part restaurants skip
Many owners set up the till and stop there. Food cost is usually where the larger losses hide, so plan stock control from the first week.
Split your items into three groups
- Resale items. Sodas, bottled water, beer and packaged snacks. These sell exactly as bought, so every sale reduces stock one for one. Start here: it is quick to set up and shows leaks immediately.
- Key ingredients. Rice, cooking oil, flour, meat, chicken, potatoes. Record them as stock items, receive deliveries against purchase orders, and count them on a fixed day each week.
- Small daily market buys. Tomatoes, onions, dhania, charcoal. Record these as categorised expenses rather than trying to count them.
Receive and count properly
- Raise a purchase order to your regular suppliers, such as the meat supplier or the rice wholesaler, and receive each delivery against it so quantities and prices are on record.
- Keep a supplier ledger, so you know what you owe the chicken supplier who gives you two weeks’ credit.
- Set reorder levels on fast movers. Low-stock alerts then warn you before the cooking gas or the chips run out mid-service.
- Count key ingredients weekly and post the difference as a recorded stock adjustment. Over a month, the adjustments tell you where the leaks are.
If you prepare items in batches, such as juices, sauces or chapati dough, the manufacturing module is available from the Enterprise plan. Most single restaurants do not need it on day one. Weekly counts of key ingredients already show you most of what goes missing.
Where a QR menu fits
A QR menu puts your menu on the guest’s own phone. You print one code per table; a guest scans it with the phone camera and sees today’s dishes and prices. This helps in three common situations:
- Prices change often. When the price of rice or cooking oil moves, you change the menu once online instead of reprinting laminated cards.
- Peak hours are short-staffed. Guests can browse and choose before a waiter reaches them.
- The venue is outdoors. Beach bars in Zanzibar or garden restaurants lose paper menus to wind and rain.
SmartBiashara offers Smart QR Menu for this. It is a separate service with its own sign-up and login, and it includes ordering and a payment step for guests. Because the restaurant POS in SmartBiashara ERP is a different product, ask our team how QR Menu orders reach your till and stock in your setup. That way you know whether your cashier will need to enter anything twice before you print codes for every table.
A simple rule: get the POS, kitchen tickets and stock working first. Add the QR menu once your staff trust the order flow, so you are not fixing two new systems in the same week.
What it costs in shillings
The software is usually the smaller part of the cost. Plan for devices and a few days of staff time as well.
| SmartBiashara plan | Monthly (TSh, excl. VAT) | Yearly (TSh, excl. VAT) | Locations | Users | Fits |
|---|---|---|---|---|---|
| Starter | 15,000 | 150,000 | 1 | 5 | One restaurant with a small team |
| Basic | 35,000 | 350,000 | 3 | 10 | Adding a second outlet, CRM and WhatsApp gateway |
| Standard | 45,000 | 450,000 | 5 | 20 | Up to five outlets, or a lodge with a restaurant using hotel management |
| Enterprise | 55,000 | 550,000 | 50 | 100 | Chains, and kitchens that need the manufacturing module |
Paying for a year upfront gives you twelve months for the price of ten. Watch the user limit: if each waiter has their own login, a restaurant with three waiters, two cashiers, a manager and the owner already needs seven users, which is the Basic plan rather than Starter. Compare every plan limit on our pricing page.
Other costs to budget for:
- One phone or tablet per waiter, unless staff use their own phones under a clear policy.
- A device for the cashier and, if you print bills, a receipt printer.
- A barcode scanner if you sell many bottled or packaged items at a counter.
- Staff time for two or three slow afternoons of practice before you go live.
On TRA fiscal receipts: SmartBiashara records every sale and produces the reports, so talk to our team about how your EFD or VFD fits in before the first service on the new system.
A two-week rollout plan
Week 1: set up and practise
- Day 1: Sign up for the 14-day free trial. Enter your menu with prices, starting with your twenty best sellers. Use Excel bulk import if your menu is long.
- Day 2: Create a login for each waiter and cashier, with the Cashier role. Keep Admin for yourself and Manager for the supervisor.
- Day 3: Enter opening stock for resale drinks and five to ten key ingredients.
- Days 4–5: Run the system in parallel with the order pad during quiet hours. Compare tickets and bills at closing.
- Day 6: Test an internet drop on one device and check the sales sync afterwards.
- Day 7: Review the first full week’s sales by dish and by payment method.
Week 2: go live and tighten
- Retire the order pad for dine-in.
- Raise your first purchase orders and receive deliveries against them.
- Do the first weekly ingredient count and post adjustments.
- Check that mobile money totals in the system match your M-Pesa, Tigo Pesa and Airtel Money statements.
- Decide whether a QR menu would help, and if so, talk to our team about how it connects.
Checklist before you choose any restaurant POS
Use this list with any vendor you are considering, including us:
- Can a waiter open an order on a table and keep adding to it?
- Does the kitchen get a ticket automatically when the order is placed?
- Can one bill be split into several payments with different methods?
- Are tips recorded separately from sales?
- Are M-Pesa, Tigo Pesa and Airtel Money reconciled, or only typed in as a label?
- Does the till keep recording sales when the network drops?
- Can you track drinks and ingredient stock, with purchase orders and supplier credit?
- Is the price shown in TSh, and how many user logins does it include?
- Who answers when something breaks at 1 pm on a Saturday?
If a system passes all nine on a real lunch service, it will cope with the rest of your week. For help setting up the trial, call or WhatsApp +255 749 900 050 (Monday to Saturday, 8am to 8pm EAT).