Start with the question you need answered
What do I need before opening with a POS?
Prepare your menu, staff access, supported devices and opening stock. Agree payment and printer setup before live service.
How do I switch without losing my records?
Confirm supported imports and opening balances, keep historical records accessible and agree a cutover procedure. Migration is not automatically included.
Why does counted stock differ from sales and purchases?
Follow one ingredient through receipts, recipes, recorded use, waste and a physical count. A difference calls for investigation; it is not proof of theft. See the workflow and requirements
How do I check cash and M-PESA against my bills?
Compare recorded bills and tenders with counted cash and provider records. A pending M-PESA prompt is not a confirmed payment. See the workflow and requirements
What will my first year actually cost?
Compare the VAT-inclusive annual subscription by staff logins, then confirm devices, locations, setup scope, connectivity and provider or usage charges. See the workflow and requirements
Can I use my current phone, laptop or printer?
DineHQ runs in a browser. Verify your exact device, printer model and print path; don't assume any printer is compatible or that online services work without internet. See the workflow and requirements
From a table order to the closing report
Evaluate the POS with one of your own restaurant bills. Check the order, kitchen handoff, payment and ingredient records together instead of comparing a list of isolated features.
- Record a table or counter order and send its kitchen ticket using a compatible printer.
- Settle the bill by cash, M-PESA or split payment, checking each payment result separately.
- Review recipe ingredient use alongside recorded purchases, waste and physical counts.
- Check the daily sales and payment totals, then investigate differences using the staff-linked records.
Opening a restaurant or replacing a basic till?
Start with the problem you need to fix: slow order handoffs, unexplained cash differences, rising food costs or reports that arrive too late. Evaluate the whole workflow, not only how quickly a till prints a receipt.
DineHQ connects orders and payments with recipe stock, supplier purchasing, staff/payroll records and daily reports. Reliable records still depend on correct setup, recorded purchases and expenses, physical counts and staff procedures.
- Opening: prepare your menu, recipe units, staff logins and supported devices.
- Replacing a till: agree what data can be brought across, verify opening stock and keep access to historical records.
- Comparing systems: bring one of your own bills and ask to see ordering, kitchen handoff, split payment, ingredient use and closing reports.
A workflow to evaluate, not a feature promise
Capture table or counter orders, send kitchen tickets, settle cash, M-Pesa or split tenders, and review staff-linked orders and recipe stock.
Worked example — illustrative figures only
Illustrative only: ingredients KES 120 and selling price KES 400 give 30% food cost and KES 280 ingredient gross profit. Labour, rent and other overheads are not included.
Use consistent tax treatment for cost and selling price. These invented figures explain arithmetic, not customer results or market benchmarks.
Restaurant operating checklist
Use this checklist with your own operator before buying.
- Prepare menu, recipes and individual staff logins before service.
- Review running bills and kitchen handoffs.
- Compare recorded tenders with cash counted and verified M-Pesa.
- Investigate stock counts, voids and discounts; variance is not proof of theft.
Where the fit stops
Use an internet connection to record orders and payments. Your cart and saved actions are kept; saved actions may need authorized review. M-Pesa STK Push and live fiscal submission need connectivity. Check printer compatibility.
A table order and kitchen ticket are not a fiscal invoice. Complete the bill through settlement before checking the fiscal result.
Moving from paper, spreadsheets or another POS
Start with a clean menu, selling prices, ingredient units and recipe quantities. Agree an opening-stock count and cutover time before recording real service. Keep the old system’s sales, tax and supplier records available for historical checks; do not assume historical transactions or balances migrate automatically.
Ask DineHQ to confirm the supported import template, field mapping and setup assistance for your files before buying. A spreadsheet export from another POS is not a promise of one-click migration. Scope printers, payment configuration, staff roles and training separately; no fixed setup duration is promised.
- Prepare a small menu sample and test units, portions and modifiers before loading the full catalogue.
- Give each staff member their own access and confirm who can void, discount, receive goods and view reports.
- Count opening ingredients at the agreed cutover time; avoid entering the same sale in two systems.
- Rehearse a table order, kitchen ticket, split payment and daily close using an agreed test procedure before live service.
- Retain the old records and agree a paper fallback and rollback decision with the manager.
A restaurant POS demo should follow your own bill
Use a real menu example without customer details. Ask the demonstrator to show the entire workflow rather than only a feature list. Record each requirement as demonstrated, configuration needed or not supported.
- Enter a table or counter order, add an item with kitchen instructions and show the kitchen ticket.
- Show cash, M-Pesa and split tenders; distinguish a pending provider result from confirmed payment.
- Check one recipe’s ingredient use, record a physical count and explain the variance without assuming theft.
- Review permissions, the end-of-day sales/tender report and the owner’s phone view.
- Test your exact device and printer. Confirm the available outage fallback; online payments and fiscal confirmation require connectivity.
- Ask for a written annual software and extras quote, setup scope and unresolved gaps before deciding.
