What the till loses when channels drift apart
A standalone ordering kiosk with its own menu is a second till you never close. The guest orders chips and sauce at a price the counter stopped charging a month ago. The kitchen still makes it. The desktop POS never sees the sale, or sees it only after someone retypes it. In that retype sit the modifier you forgot, the option the guest did tap and the payment method that is written down nowhere. At the end of the shift the drawer is off, and nobody can say whether the gap was cash or the kiosk.
An ordering website does the same thing from the guest’s sofa. A pickup order that exists only in an email or on a separate tablet is invisible to whoever closes the day. The driver leaves with a bag. That bag’s turnover belongs to the business, even when the money already arrived online. If you cannot see the order beside counter sales, the day’s takings are a partial story. For a snackbar with a hatch, a kiosk and pickup, that is not a theoretical risk. It is Friday night.
The practical symptom is a menu maintained in three places. Someone changes the price on the kiosk and forgets the till. Someone marks a dish unavailable on the site and the counter still sells it. The guest is right to point at the price on the screen where they ordered. You then have two versions of the truth, and the POS is no longer the record.
Keeping one menu and one price
One CMS means the product, the price, the options and the VAT exist once. The counter, the kiosk and the site read those same data. Mark a dish unavailable and it disappears in all three places, not only on the screen you happened to be standing at. A pickup price and a dine-in price may differ, but as two deliberate prices in that one system, not as a spreadsheet beside the till. The integrations around the POS should follow the same idea: less double entry, not another set of books.
The ordering kiosk in the room and the ordering website for home are the channels in this setup, not the source. They let the guest order. They should not carry an assortment of their own that the till then has to copy. From the POS, check whether a change you make at ten in the morning is visible on the kiosk and the site that same afternoon. If it is not, you are still copying.
Being "out" belongs in the same switch. A dish the kitchen can no longer make should stop being sellable on the till, and on the kiosk and the site as well. You do not need a promise of ingredient-level stock for that. You do need one control. Otherwise you sell the last portion twice, once at the hatch and once to someone who already paid on the site.
Where the kitchen and the money should meet
An order the kitchen cannot see is not a connection. Sales from the till, the kiosk and the website should appear on the same kitchen display, with an origin so the counter knows what is pickup and what is eat-in. The work list is one list. The fryer does not ask which screen is right. For restaurants with a kiosk by the door and a site for pickup, that is what keeps the pass from splitting in two.
Payment has to reach the same day’s takings, even when it never touches the drawer. A guest who pays by card on the kiosk, a guest who pays ahead on the site and a guest who pays cash at the counter are three methods in one service. When you close, put them side by side: what the POS knows as turnover, what landed at the bank or the card provider, and what is in the drawer. If the channel is missing from the till, you will look for the gap in the wrong drawer. Fiscal records start with that completeness, not with a prettier dashboard.
Connecting is not an extra screen in the corner. It is the decision that the POS owns the catalogue, that the kitchen has one list, and that every paid order counts when you close the day. The kiosk and the site make ordering easier for the guest. They do not release the till from having to know the order.
