When the kiosk menu drifts away from the till
Two lists feel harmless at the start. A colleague changes the dish of the day on the till, and the kiosk still shows yesterday’s. Or the kiosk has a new price, and the till charges the old one when someone orders at the counter. The guest notices at the hand-over or at the card machine. Then you are explaining why the screen said something other than the receipt. The shorter queue has turned back into a conversation.
Sold out gets lost the same way. The tray of croquettes is empty, the till says “off”, the kiosk still offers the product. The guest pays, the kitchen cannot make it, and someone has to reverse the amount while the next person is already ordering. That is not stock theory. That is a switch that has to flip in one place, so both sides stop offering the product. If either side lags, the shop sells something it does not have.
A POS system is not a legal requirement in the Netherlands. You do not have to buy a particular brand or a particular kind of till before you are allowed to put a kiosk on the floor. Keeping the books on your sales is a different question from choosing a system. If you do use a till, the agreement from the kiosk’s side is simple: the same dishes, the same prices, the same extras, the same things that have run out. Without that agreement the kiosk becomes a second menu, and two menus are two truths.
The kiosk is the guest’s side of this. It cannot “just” correct a price from memory, the way a colleague at the counter sometimes does. What is on it, gets ordered. That is why the source of the menu should not live on the screen itself, and not in a folder beside the till, but in one place that feeds both. How the ticket then reaches the kitchen is in connecting the kiosk to the till and the kitchen screen.
One menu for the kiosk, the till and online ordering
In the CMS you keep the menu once: products, prices, extras, photos and what is no longer available. The kiosk reads that list. The till we supply with it reads the same list. Change the price or the build and you change it there, not on two screens one after the other. A colleague who still has to copy a price onto the till after closing forgets it on the busy day. One source removes that second action.
The same menu also belongs on the other channels where the guest already orders, such as the ordering website or a QR code on the table. Otherwise the shop still has two menus, only digital ones. On the page about self-order in hospitality that is the agreement: kiosk, till and ordering channel show the same card. The kiosk is not the boss of the till. It is the place where a mismatch hurts first, because the guest reads it themselves.
What the till does next with those sales, the shift, the tables, the day, sits on the till’s side. We do not retell that from the kiosk. It is on mijnkassasysteem.nl. From here only this counts: if a till stands beside the kiosk, it should not have the menu a second time. No second entry, no private list of “roughly the same” prices. Roughly is exactly enough for a complaint.
Not every floor needs that till in order to be allowed to trade. Someone who only wants a kiosk for a simple sale does not first buy a POS because it would be compulsory. It is not. Someone who does have staff at a counter and a kiosk wants those two not to sell against each other. The integrations show which systems we connect as standard, and where the API takes over when your software is different.
Stock that matches on the kiosk and the till
In hospitality, “stock” is usually not a warehouse count. It is the question whether the kitchen can still make this dish now. The tray is empty, the daily special has gone, a sauce did not come in. You switch that off on the product. The kiosk stops offering it, and the till does too. You do not hang a note on both. If you want to keep a number down to the portion, do that where it matches the kitchen. The kiosk gains nothing from a figure that only lives in a spreadsheet nobody opens during the shift.
Retail stock is different. There the quantity often comes from the webshop: Shopify, WooCommerce or another system that the shop and the kiosk both read. The guest then sees a price and an availability that were not invented on the kiosk alone. That link is on retail and webshop and on the matching Shopify, WooCommerce and other integrations. Do not confuse that with the snack bar. A fryer does not have a shelf of twelve identical snacks in a stock location. It has a product that is on or off.
The test is small and mean. During a quiet half-hour, switch one product off and try to order it on the kiosk and, if you have one, on the till. Both should refuse, or both should show that it has gone. Switch it back on and check that the price is the same everywhere. Do it with a product that has an extra, not with a bare item. The extra is where lists diverge first, because someone updated the sauce on one channel and not on the other.
One menu and one stock list are not a slogan next to the kiosk. They are the reason the guest trusts the screen. If they do not trust it, they walk back to the counter, and you have the queue back that the kiosk was meant to remove. Keep the source in the CMS, let the till read along if you use one, and treat sold out as a switch rather than as a message someone has to pass on. You choose the hardware around that afterwards, on the product lines, not as a substitute for the agreement.
