Tuesday, 11:40. The old till freezes in the middle of lunch. There is no rehearsal, no mapped modifiers, and the only person who knew both systems is off. The first ticket after the emergency switch prints as a nameless item because “no onions, extra pickle, side salad not soup” never made the export. The pass starts calling the floor. Guests wait. That is not a software vendor problem. That is a cutover with no owner and no fallback.
Venues rarely cling to the old POS out of love. They cling because nobody wants that Tuesday. Pick the go-live date last. Map what can break first.
Migrations fail before anyone logs in
A new screen will not tidy workarounds you already live on.
The menu exists in three versions: till, PDF, a note by the bar. After migration you still have three versions, plus new hardware.
Nobody owns the final card, the floor test, the kitchen test or the right to stop the rollout. Decisions happen in a group chat during service.
Today you already phone the kitchen, scribble extras and skip the till. The new system will copy those shortcuts, only faster.
If those three are messy, a go-live date is theatre.
What to freeze before you unplug the old till
Menu
Items, extras, sizes and prices must be the ones the team actually uses at peak. Migrating a messy card yields a messy card on new glass.
Roles for the first service
Who walks the floor with a checklist? Who watches the kitchen? Who can roll back? Who tells a guest an item is off? Without that, the change runs on guesses.
Sequence, not “everything Tuesday”
Many venues are safer launching floor and kitchen first, then pickup, QR or extra stations after one calm service. A single-day leap only fits a short process the team has already rehearsed.
The product-side version of that sequence is on switching system.
A rollout the team can survive
A workable order:
- Clean the menu and the basic order path.
- Test the real scenarios: table, modifier, payment, correction, pass.
- Go live on a limited slice: one shift or one section.
- Add stations, channels and reports after that slice holds.
This is not caution for its own sake. It stops the venue learning a new tool in the same hour it is still recovering yesterday’s process.
Readiness test: can the team take an order to the pass without a phone call to the office, a scrap of paper, or “I’ll tell them at the window”.
Where the first hours actually break
It is rarely “a button that will not click”. It is usually:
- the floor cannot work the new layout under volume,
- the kitchen cannot read the first tickets,
- the manager stacks a new POS, a new menu, new prices, a new online channel and a new KDS into one service.
Set one checkpoint after go-live. Not to find a culprit. To check whether floor, kitchen and manager already share the same logic. A short review after the first or second shift usually beats another round of improvised workarounds.
Name the day-one minimum. Not everything has to ride the cutover. The first version has to be readable and able to serve food.
When a big-bang switch is the expensive option
A full leap costs more than a few extra weeks of prep when the venue has high turnover, no single current menu, or floor, pickup and delivery without shared statuses. Start with one area or one module. A migration in the wrong week lingers in reviews and in the team longer than a delayed date.
Do not sell yourself a clean Tuesday
OrderNow is worth a look when the old setup no longer holds floor, kitchen and later expansion, and you want a change in an order that does not wreck service. It is not a marketplace. It will not silently replace every fiscal device on the bar. Direct online is not in Start. Scope follows the venue, not a “switch everything” slide.
If you are close to a decision, book a presentation from a real lunch: menu, roles, first ticket. If you want the rollout checklist first, stay on switching system.
Cost and scope still belong with the POS buying guide and price components before anyone sells you a date without a risk list.
Related articles:
- POS system for a restaurant: how to choose it without burning your budget
- POS prices: components of the system cost
- How much does a POS system for a restaurant cost? TCO calculator