Restaurant POS in Bangladesh: What the Till Must Do Before You Add Kitchen Screens

Start with the counter, not the floor plan

A table map looks impressive in a demo. But a restaurant with a perfect table map and a broken shift close still cannot tell you whether yesterday made money. The till has to be right before the floor plan matters.

Three questions should be answerable at any moment:

1. How much cash should be in the drawer right now?
2. What did we sell today, by item and by payment method?
3. What did we give away in discounts and comps, and who approved it?

Shift close is the control

In a busy restaurant, cash moves between people all day. A shift is not an admin feature — it is the point where responsibility changes hands. Opening cash, sales by tender, refunds, paid-outs and the counted cash should reconcile on one screen, with the difference recorded rather than hidden.

If the system only has one daily total, every shortage is absorbed by the owner and every overage is a mystery.

Menu, stock and the ingredient gap

Menu items and stock items are not the same list. A chicken biryani is sold as one plate but consumes rice, chicken, oil and gas. Without recipe-level deduction the POS can still sell perfectly and the kitchen stock will still be wrong, because nothing tied the plate to the ingredients.

That does not make stock useless. Track the high-value ingredients you actually count — meat, oil, cheese, drinks — and reconcile them weekly. A full recipe build can come later; a weekly count of five ingredients catches more theft and waste than a perfect system nobody maintains.

Scope note: if you need table maps, kitchen display screens or automatic recipe deduction, confirm those modules explicitly before buying any system. A counter-first POS and a full kitchen workflow are different builds.

Discounts are where margin disappears

Staff discounts, manager comps, “guest of the owner” and delivery-partner promotions all reduce the same number. If they are typed as a generic discount, the month-end report cannot tell you which one is eating the profit. Give each a reason code and require a user for anything above a limit.

Bangladesh specifics

Cash, bKash, Nagad, card and delivery wallets arrive in the same day. Each needs its own tender so the closing report matches the actual wallets and the bank. VAT treatment varies by menu and by whether the sale is dine-in or takeaway; the invoice should carry the treatment rather than a single blanket rate. And a printed bill with a proper invoice number is not optional once you sell to offices.

What Zuviq Book covers

Counter sales through the POS, shifts with cash reconciliation, per-item discounts, returns and void with the invoice rule, multiple outlets, customer loyalty and a public bill link. Stock is item-based, which suits drinks, packaged goods and counted ingredients; recipe-level deduction is not part of the current build.

The counter-to-kitchen flow is sketched in the restaurant brochure. For a shop with no kitchen, the grocery guide is closer.

Run one real shift

Do not evaluate on a demo menu. Enter your ten best-selling items, open a shift with a counted drawer, take twenty real orders across three payment methods, then close it and see whether the numbers match. That single exercise exposes more than a feature list.

Start the trial and keep every module open for seven days. Pricing is here.