A Multi-Device POS Your Waiters Share Across Phones, Even Offline

It is a Friday night at a lounge in Lekki. Every table is taken, the music is loud, and two waiters are moving fast between the bar and the floor. Table 3 orders a bottle and four small chops. Table 9 is still waiting for peppered snail from twenty minutes ago. A third waiter jumps in to help and takes a fresh order on table 3, not knowing what his colleague already wrote down.

At closing the numbers do not add up. Two bottles left the bar but never made it onto a bill, one table walked thinking another had paid, and nobody can say exactly what happened. That is the real problem. Not the number of guests, not the number of waiters. The fact that your waiters cannot see the same table at the same time.

This guide is about running a bar or restaurant with several waiters, each on their own phone, sharing the same tables and the same bill down to the second, without depending on an internet connection that drops on you the very night the place is packed.

When one person rings up every sale, it all lives in their head and their notebook. The day you grow to three or four waiters, each one has their own version of the night. A bottle added to table 5 by one waiter does not exist for another. Two waiters open the same table without knowing. The kitchen gets the same order twice, or not at all.

A POS on a single phone does not fix this, it just moves the queue. The waiter has to walk back to the counter to enter everything, a line builds up, and while they type nobody is serving. What you need is not one more till. You need one till that several phones share, where every action by one waiter shows up for the others straight away.

Here is the idea in plain terms. Each waiter carries an Android phone. All those phones sit on the same network: the same router, or a simple access point behind the bar. One device, usually the tablet at the counter, acts as the central point. The others connect to it.

From there, the tables, the orders and the bills live on that local network, not at the far end of the internet. A waiter opens table 4 on his phone, another sees it appear on hers within a second. He adds a bottle, she sees it. The kitchen gets the ticket. All of it moves from one device to another over the venue's own wifi, never touching a server on another continent.

The technical name for it barely matters. Hold on to the principle: your devices talk to each other, on site. The internet is now good for one job, backing all of it up online when the connection is there. It is no longer standing in the middle of every order.

Plenty of tills sold today push every order through the internet. The waiter takes an order, it travels to a distant server, comes back, and only then can a colleague see it. On paper it looks clean. In a full lounge on a Friday, it is a gamble.

You know the reality. The network crawls at peak hours. NEPA takes the light and the router blinks out until the generator catches. A downpour knocks the mast. A till that needs the internet just so two waiters can see the same table freezes at the exact moment you need it most, and the whole floor goes back to scribbling on paper in front of a packed room.

A POS on the local network does not depend on any of that. The sharing between waiters runs over the wifi on site, which does not go down when the carrier's mast coughs. Your waiters keep seeing the same tables, the kitchen keeps getting tickets, and you keep taking money. The internet can come back later and catch everything up.

This is the move that changes a shift. A waiter opens table 6, takes a starter and two drinks, then heads to the bar. His colleague passes the table, the guest wants to add a plate. She pulls out her phone, opens table 6, it is already there with the starter and the drinks, and she adds the plate. No hunting for the first waiter, no "let me go and check".

With a full team that means no guest waits for one particular waiter to be free. Anyone on the floor can pick up any table, because everyone sees the same live state. On the night you are one waiter short, the others absorb it and the service does not collapse.

When the guest asks for the bill, they want it correct, not a negotiation. With separate notebooks, a table three waiters passed through becomes a memory test, and that is exactly where money leaks. With a shared till, table 6's bill holds everything that was added to it, by whoever added it, nothing forgotten and nothing counted twice.

And when the table wants to split the bill, each guest settles their share how they like, one by transfer, two in cash, without the totals getting tangled. Splitting a bill, which turns into a headache on paper, becomes a ten-second job.

A good part of the chaos happens on the trip between the table and the fire. The little paper goes missing, the handwriting cannot be read, the waiter forgets the guest said no pepper. When the devices are on the local network, an order taken on the floor reaches the kitchen right away, on a screen or a printer near the pass, with all its details.

The same logic covers the bar. Drinks go to the bar printer, food to the kitchen, each station sees only what concerns it. All of it over the venue's network, no internet required. The cook is no longer looking up every two minutes to grab a scrap of paper, he works off a clean queue of tickets in order.

Here is what should happen when the connection returns: nothing you have to do. The night's sales, taken during the outage, upload on their own the moment the network is back. You find everything in your reports, and from home the next morning, as if the outage never happened.

That is the right division of labour. The local network runs the service, on site, without a gap. The internet is there to back up and to let you check your figures from anywhere. Confirm this exact point before you buy: the upload must be automatic. A sync you have to trigger by hand every night is a sync that gets forgotten on precisely the wrong night.

In Nigeria a guest pays several ways: cash, bank transfer, Opay, Moniepoint, PalmPay, sometimes a card at the fancier spots. The problem is not accepting all of it. The problem is not mixing it up. If you add everything into one total at closing, you will never know whether the cash drawer is right, or whether what landed in your account by transfer matches the tables that paid that way.

A till that records each payment method separately, offline sales included, gives you that check every night in two minutes: count the cash, open the transfer alerts, compare. A shortfall shows up the same night instead of hiding inside a month of mixed totals. Whatever system you pick, refuse one that cannot split payment methods cleanly.

With several waiters, the question turns up sooner or later: an order vanished, a bill was cancelled, and nobody knows who did it. Without a trail, you end up suspecting everyone, which is the fastest way to wreck an honest team.

A good till gives each waiter their own PIN. Every order, every discount, every cancelled bill carries the name of the person who did it. Rights are set by level: a waiter sells, but only a manager can void an order, change a price or open the sales reports. The night the drawer is short, you do not accuse anyone at random, you open the history and see. It is your honest waiters that this record protects first.

The good news is that the kit is modest. You need one Android phone per waiter, and the ones already in their pockets often do the job. A device that stays at the counter, plugged into power, acts as the central point: a low-end tablet is fine.

You need a local network. Not a fast internet line, just steady wifi on site: the router you already have, or a small access point behind the bar for somewhere around ₦15,000 to ₦40,000 once. Add a thermal printer for receipts, roughly ₦25,000 to ₦60,000 depending on the model, and a second one near the kitchen or the bar if you want to route tickets. That is the whole list. Be wary of anyone forcing their own proprietary terminal on a monthly hardware fee: the phone in your pocket does it better, for free.

Honest question: if you ring up every sale yourself behind the counter, none of this helps you. A shared POS on the local network starts to pay off with two people taking orders at the same time, and becomes essential at three. That is the point where the notebooks contradict each other, where two waiters open the same table, where the bill turns into a memory test.

A small suya spot with an owner and one waiter runs fine on a single phone at the counter. A fifty-seat lounge on a Friday, with three waiters on the floor and a separate bar, leaks money every shift until its people see the same thing. Look at your room at peak, not at a quiet hour. The rush is what decides.

The first, we said it: picking a till that needs the internet just for waiters to share tables. It will drop on you at the worst moment. The second is not setting a PIN per waiter from day one. A shared till with no trail is worse than a notebook: everyone can do everything, nobody is accountable, and the day the drawer is short you have nothing to go on.

The third mistake is neglecting the wifi. Local sharing rests on your network on site: an access point stuffed in a corner behind a thick wall, and the phones at the back of the room drop out. Mount it high and central, and test from the farthest table before service. The fourth is training one waiter and hoping he shows the rest. Take a quiet hour, train the whole team together, and let your most senior waiter be the first to adopt it, the others will follow.

The last one is the quietest: skipping the close each night. The cash, transfer and Opay check takes five minutes. Skip it for a week and the small gaps have grown into a mystery you cannot untangle.

Do not take anyone's word for "it works on a network". The test costs five minutes. During the demo, grab two phones, open a table on the first, add a plate. Does it show up on the second within a second? Then cut the internet: the router, the mobile data, all of it. Open a new table on one phone, add to it from the other, take payment, print the receipt. Does everything keep working between the two devices with no internet?

Finally, reconnect and watch whether the sales upload by themselves. Ask the vendor these questions and listen for specifics. Do the phones talk to each other on site, or do they go through your server? How many devices can connect at once? If the central device shuts down, do I lose the night? Confident, concrete answers are a good sign. Vague reassurance, or a demo that only runs on the showroom wifi, tells you everything you need to know.

Do not try to move everything over in one night. Week one, load your menu into the till, drinks and food with their prices, and run two phones on the floor with your notebooks still beside you for safety. Week two, add the rest of the waiters and the kitchen printer, and deliberately cut the internet on a quiet night to watch the till carry on. Once the first month is behind you, set PINs per waiter and the closing reports.

On the software side, start free and judge for yourself. digabloPos costs nothing to begin with, runs on the Android phones your waiters already carry, keeps each device working when the network drops, splits cash from transfers and Opay, and gives each waiter a PIN. Load your menu, run it for a week beside your usual routine, and pull the internet at least once to watch it shrug. The till you want is the one that does not even notice the internet is gone.