From your menu to a tested counter setup

A new till starts with familiar details: the dishes your kitchen makes, the prices on your menu and the printer behind the counter. Bring those into the workspace, then test a complete order before relying on it during service.

Bring in the menu

Use a supported menu import or enter items directly. When the AI service and your plan's allowance are available, photo capture can turn a printed menu into a draft of items, prices and categories.

Review that draft. Printed menus can have handwritten corrections, similar dish names and unclear variant prices. Confirm names, amounts, modifiers and availability before saving. AI availability is separate from your ability to set up a menu by hand.

Review the business and tax setup

Confirm your registration status and the applicable tax configuration with your accountant. The recorded registration type affects whether the software prepares a tax invoice or a bill of supply. The GST billing guide explains the product behavior and the source material to review.

Check the business details that will appear on the document. Review the menu prices and effective tax rates, then inspect an example bill.

Test the counter and kitchen

Validate the actual browser, screen, printer and transport you intend to use. Printer compatibility depends on the device and connection; owning a thermal printer alone does not establish that it is configured.

Run a test order through the counter, kitchen ticket, preparation and payment recording. Confirm that receipts and KOTs reach the intended printers. Try the floor and order views on the screen sizes your team will use.

If you need offline counter work, prepare the device while connected and check its saved readiness, local storage and bill-number availability. Only supported work can queue offline. Online payments and external services still require a connection.

Roll out in a useful order

1. Review the menu and a test bill. Correct the details before the first service. 2. Walk through the kitchen handoff. Confirm modifiers, station routing and the pass. 3. Assign team access. Give each person the role and outlets they need. 4. Confirm provider availability. Payment and delivery connections need their own activation; check the integration requirements. 5. Add stock and recipes. Record quantities and costs carefully so later reports have useful evidence behind them.

The time this takes depends on your menu, hardware and migration needs. Use a quiet service or an agreed transition period to find the details that a clean demo cannot reveal. The milestone is a workflow your team has tested, not a promised number of minutes.