Bmaster

Waiters carry the order, but who carries the bill?

That is the real friction point in any busy restaurant. A table of six finishes their meal. The waiter scribbles the order, runs to the counter, shouts the items over the noise, and then runs back with a paper bill that might have math errors. The Bmaster app removes that entire chain. It puts the order entry directly into the waiter's hand, on their phone, and sends it straight to the cash register system. No more lost tickets. No more arguments about who ordered what. The app sits on Android and iOS devices, and it talks to the Bmaster cash register system over the network. When the waiter taps "send," the order appears on the kitchen screen and the billing terminal at the same time. That is the first thing that changes when a restaurant deploys this tool.

The second thing is the fiscal invoice. In Serbia, where this app originates, every hospitality business must issue a fiscal receipt that the tax office can verify. Bmaster prints those receipts with a QR code on them. The waiter can print the bill right at the table using a portable POS printer, or they can send it to the main cash register. The QR code lets the customer scan and see the invoice details directly on the tax office portal. That level of transparency is not just a nice add-on; it is a legal requirement in many markets, and Bmaster handles it without the waiter needing to touch the main terminal. The app does not replace the cash register. It extends it to the floor, where the actual work happens.

What happens when two features meet on the same table

Take a table of eight people. They order drinks, appetizers, mains, and desserts at different times. Some want to pay together. Others want separate checks. This is where the Bmaster app shows its real structure. The waiter enters each item under the table number. The app tracks who ordered what. When the meal ends, the waiter can split the order by item or by person. They can also combine items from different tables into one payment if a large group wants to settle together. The app does not force a single bill. It lets the waiter break the order into pieces and then reassemble them for payment. That workflow is not just about convenience. It reduces the time a table spends waiting for the bill, which directly affects table turnover and revenue per hour.

The split feature works alongside the quick payment option. The waiter selects the items for one person, taps quick payment, and the app calculates the total including tax. The printer spits out a receipt with the QR code. The customer pays. The waiter moves to the next person. That sequence, repeated four or five times, happens in under two minutes. Without the app, that same process would require the waiter to run to the terminal, print a preliminary bill, run back to the table, get clarification, run back to the terminal, adjust, and repeat. The app collapses that loop into a single flow from the table.

The reality of running this on an actual device

The Bmaster app is not a flashy piece of software. It does not have animations or gamification. It is a utility tool. The interface is straightforward: a list of items, a search bar, a table number selector, and a send button. The search bar is the most used feature during a rush. Waiters type the first few letters of a dish, and the app filters the menu instantly. That speed matters when the kitchen is waiting for the next ticket. The app also stores customer profiles. If a regular customer walks in, the waiter can pull up their previous orders and preferences. That is a small detail, but it changes the interaction from transactional to personal.

The app does have a downside. It relies on a stable network connection to the Bmaster system. If the Wi-Fi drops, the order does not go through. The app does not cache orders offline, so a network failure means the waiter has to revert to paper and manually enter the order at the terminal later. That is a real limitation in restaurants with spotty coverage. The developer, 5.COM DOO BEOGRAD, does not mention offline mode in the description. The app also requires the restaurant to already have the Bmaster cash register system installed. It is not a standalone POS. It is an accessory to an existing setup. That limits its usefulness to venues that have already bought into the Bmaster ecosystem.

One specific permission and what it actually does

The app requests permission to access the device's location. That is not for tracking customers. It is for the fiscal printer connection. The smart POS printers that Bmaster supports use Bluetooth or Wi-Fi Direct to pair with the waiter's phone. The location permission is a standard Android requirement for Bluetooth scanning. Without it, the app cannot discover the printer. The permission does not send location data to any server. The app does not collect user data at all, according to the Play Store's data safety section. That section states that the app does not share any data with third parties and does not collect any data from the device. That is a rare claim for a business app, and it matches the developer's focus on fiscal compliance rather than data monetization. The app also does not request storage permissions because it does not save photos or files. It only sends text orders and prints receipts. The permission list is short, which is a sign of focused engineering.