Setup, training and go-live

A single-station deployment takes about a week from account setup to first live service. Multi-station and multi-location installs with custom floor plans take longer. The menu is built before the hardware arrives, so install day is about the room, not the data.

The five steps

1. Assessment. Service model, menu complexity, floor plan, transaction volume, staff size and the payment program. Sometimes the honest answer is a different platform.
2. Configuration. Menu structure, modifier trees, floor plan, employee profiles and payment settings, all before hardware ships. Pizza operations get the pizza builder configured with their sizes, toppings and pricing rules.
3. Hardware installation. Stations, kitchen printers or display, receipt printers, and a check that every component talks to every other before anyone is trained on it.
4. Staff training, tailored to the service model: order entry, table management, modifiers, payments, end-of-day reporting and manager functions.
5. Go-live and support. We are on the floor for the first live service, and available after for troubleshooting, menu changes and rate reviews.

Day-one checklist

The list we run on a go-live:

1. Stage and set up every station.
2. Test the network and the cellular backup.
3. Match receipt formatting to the outgoing system's receipts, so the kitchen sees no change in its tickets.
4. Run TableTurn side by side with the old POS for the first service, entering orders in both to compare.
5. Validate the whole menu build against what the kitchen actually makes: every modifier, price and option.