A restaurant does not need an app for every idea. It needs an order flow that is never retyped, then separate tools where the jobs truly differ. BelloPOS Pro covers checkout, tables, waiters, kitchen display and the local network; BelloPOS also covers stock, purchases and reports by licence. It does not do accounting, payroll, reservations, customer QR ordering, kiosks, delivery-platform aggregation or ingredient recipe cards. The table below says what belongs in the POS and what must be bought elsewhere.
In short
- One operational core: POS, tables, kitchen, stock and close must share the same sales.
- One entry: the dining-room order becomes kitchen ticket, bill, stock movement and report.
- Specialist tools: accounts, payroll, booking and delivery aggregation are not till jobs.
- BelloPOS has clear limits: no customer QR ordering, kiosk, booking, accounting or ingredient recipes.
- Start with real service, then add a tool only when measured re-entry or errors justify it.
The tool map, job by job
The final column is the honest one. No does not remove the job; it shows where another tool, integration or procedure belongs.
| Job | What BelloPOS covers | What you need elsewhere |
|---|---|---|
| Checkout and close | Sales, receipts, payment modes, users and reports | The bank terminal actually processes cards |
| Dining room | Floor plan, open bills, moves and splits in Pro | Online booking and reservation deposits |
| Kitchen | Kitchen display and tickets on the local network in Pro | Cloud routing between establishments |
| Order taking | Till and local waiter app in Pro | Customer QR ordering, kiosk and web ordering |
| Stock | Items, receipts, counts, alerts and purchases | Ingredient recipe cards and automatic food cost |
| Supplier deliveries | Purchases, suppliers, received quantities and cost in Go/Pro | Supplier accounting and bank payment |
| Delivery platforms | A sale can be recorded as a distinct channel | Aggregator or connector to remove re-entry |
| Loyalty | Customer records and history | Campaigns, automated reviews, coupons and omnichannel loyalty |
| Accounts | Exports, receipts and PDF invoices by licence | Accounting software and the accountant’s work |
| Team | Accounts, roles, activity and sales by user | Scheduling, statutory attendance, payroll and filings |
Payments show the boundary: the till records card, but the bank terminal authorises and collects it. Our POS versus payment-terminal guide explains why neither replaces the other.
The core: order to close
The core belongs in one system because every break creates re-entry. A table order opens a bill, reaches the right kitchen station, returns ready, gains another course, splits, settles and feeds the report. If kitchen and till carry different numbers, no later integration repairs service.
- Dining room: The waiter sees open tables and bills. A move or split keeps history instead of recreating a ticket.
- Kitchen: Lines arrive with table, time and options. Our kitchen display guide helps choose paper or screen.
- Counter: Payment closes the same order and appears in the day close without a parallel sheet.
- Stock: The sold item leaves stock. BelloPOS does not automatically break a dish into ingredients; that needs a recipe engine.
- Reports: The manager reads sales, payments, users and items for one period, then sends the useful documents to accounts.
Test this with a split bill, a dish voided after send, a modifier, two payment types and an internet cut. A vendor unable to demonstrate your cases is showing screens, not a system.
Install in order, not on one day
Each layer should produce one clean week before the next, or nobody knows which tool lost an order.
- Week 1: rebuild the menu. Items, families, modifiers, prices, dine-in and takeaway. Turn repeated free-text notes into options.
- Week 2: run dining room and close. Tables, users, voids, bill splits and drawer count. Repair procedure before adding a screen.
- Week 3: connect the kitchen. Choose tickets or KDS by station and measure simultaneous peak orders.
- Week 4: make purchases and stock reliable. Enter receipts and costs, then run a test count. The food-cost guide shows what a real recipe card calculates.
- Month 2: handle delivery. Count retyped orders and errors before buying an aggregator. Our centralisation method gives the decision threshold.
- Month 3: connect management. Define the export sent to accounts, its frequency, owner and archive. Screenshots are not a permanent accounting source.
A small team may stay with three tools: operating POS, bank terminal and accounting. Booking, aggregator and marketing enter only when volume pays for them. Simplicity is architecture, not lack of ambition.
All-in-one is not always a win
A suite covering POS, booking, delivery, loyalty, accounts and payroll can remove re-entry, but also expands dependency, migration and exit cost. Six unowned apps create six passwords and no common truth. Keep the service core together; separate jobs with their own rules and require a standard export at every boundary.
What BelloPOS does well—and what not to ask of it
BelloPOS Pro fits a restaurant where orders start at till or waiter, reach a local kitchen display and a Windows database must continue without internet. Purchases, suppliers, PDF invoices, roles, backups and reports complete the core by licence. For one establishment wanting a one-off software purchase, this is its ground.
Do not choose it when the project depends on a customer kiosk, QR ordering, online shop, integrated reservations, delivery/customer apps, automatic recipes or shared branch stock. Avantages Feedback versus BelloPOS for restaurants compares those features and recommends the competitor when customer ordering is the central need.
The question is not which restaurant tool is best, but where the order begins and how often it is retyped before accounts. Draw the journey. Every manual arrow is an error; every integration is a cost and failure point to test.
- Buy BelloPOS for: local service, tables, KDS, checkout, item stock, purchases and reports.
- Buy elsewhere for: booking, customer QR, kiosk, delivery aggregation, accounts, payroll and ingredient recipes.
- Require between them: order identifier, CSV/PDF export, matching periods, an owner and a recovery procedure.
The buying test in twelve questions
Send this before the demo. Every yes must be shown with a real order.
- Is an order entered once from waiter to report?
- What does kitchen see and how does it mark ready?
- Can a table move, a bill split and a dish void after send?
- What remains available when internet fails?
- Is the bank terminal connected or is the amount retyped?
- Does a sale deduct an item or recipe ingredients?
- How does a delivery order reach kitchen?
- Which exports reach accounts and in what format?
- Are bookings, deposits and no-shows genuinely handled?
- Who owns backups and has restore been tested?
- Can all data be exported before leaving?
- What is five-year cost including integrations and hardware?
Mistakes to avoid
- Buying logos instead of a flow. Three famous tools are useless when the order is retyped between them.
- Confusing item and recipe. Removing a burger is not removing bun, meat, sauce and packaging.
- Calling the till accounting. It produces documents and exports; it does not keep books and filings.
- Connecting delivery without measuring. Count re-entry, errors and commission first.
- Installing everything before training. One week per layer makes errors attributable and repairable.
Frequently asked questions
What tools are essential for a restaurant?
At minimum, POS linking dining room, kitchen and close; a payment route; purchase and stock tracking; then accounting. Booking, delivery and marketing depend on actual volume.
Does BelloPOS do restaurant accounting?
No. It produces receipts, PDF invoices and reports by licence, but bookkeeping, filings and payroll remain in specialist software or with the accountant.
Does BelloPOS calculate recipe food cost?
No. It tracks stock items but does not automatically break dishes into ingredients. You need recipe-card software for that calculation.
Do I need a kitchen display?
Not always. Paper can serve a small kitchen with few simultaneous orders. KDS helps when paper no longer holds order, waiting time and modifications.
How do I centralise delivery orders?
Identify each channel in the till and measure re-entry. When volume justifies the subscription, choose an aggregator compatible with your platforms and test cancellations and refunds.
Which tool should handle booking and QR menus?
A specialist tool or restaurant suite integrating them. BelloPOS offers neither online booking nor customer QR ordering; do not buy it for those functions.
What to take away
The right set is neither software promising everything nor a pile of apps. Keep order, dining room, kitchen, checkout, stock and close in one coherent core; buy accounting, payroll, booking, QR and aggregation elsewhere when needed. BelloPOS covers the local core well, and its limits belong in the decision.
Sources
The figures and rules quoted above come from these pages, read on the date given in the article.
- BelloPOS restaurant features, read 31 July 2026
- Avantages Feedback plans and features, read 31 July 2026
Build the service core first
Test checkout and stock free with BelloPOS Lite. For tables, kitchen display, waiters and the local network, request a BelloPOS Pro demonstration.
Read next
Other practical guides on the same subject: