A few things
worth knowing.

Service is for restaurant staff and administrators: taking dine-in or takeaway orders, preparing food, confirming delivery and closing checks. These public pages explain the product; customer ordering is not currently available.

An administrator provisions ordinary restaurant staff and their roles before they sign in with Google. Entity administrators can create ordinary staff for their own entity and locations. Only a global administrator can create entities or appoint entity administrators. You can also try the app with a verified Google account: test-drive access is restricted to sample data and cannot open live entities or Admin.

Yes. Choose Try the app and verify your Google account to enter the shared sample restaurant. In the staff app’s Settings, switch between cashier, captain, server, kitchen and entity administrator roles. The administrator simulation includes staff operations only; business configuration stays unavailable. Existing provisioned staff accounts retain their ordinary access.

Yes. The staff app is a PWA that can be installed from a supported browser on a phone, tablet or desktop. Installation instructions depend on the browser and device; sign in with your provisioned Google account to work with your restaurant’s data.

A connection to the backend is required to place orders, update kitchen or delivery status, issue checks and record payments. Installing the app does not enable offline transactions.

No. With a kitchen device, kitchen staff mark queued items ready before floor staff confirm delivery. A location can also operate without a kitchen device, allowing floor staff to confirm delivery directly when the food is ready.

Yes. Multiple orders can belong to the same open table visit, and its placed, noncancelled orders join one check. Place or cancel any drafts before requesting it. Once the check is issued, its order membership is fixed; new orders wait until that visit closes.

Authorized staff can apply a fixed amount or percentage to an item or the bill, with a reason. Item discounts apply first. The bill discount is then allocated proportionately across the remaining pretax item amounts, and tax is calculated using each item’s original tax rates. Discounts must be applied before any payment is recorded.

Yes. Record received cash, card and UPI payments against the same check, with each amount reducing the outstanding balance. These are payment records: Service does not charge a card or initiate a UPI transfer. Use your existing payment terminal or payment app to receive the money.

An authorized user records a reason and confirms the remaining balance. The check closes as written off, keeping the written-off amount separate from payments actually received. A dine-in table must have every item delivered before final settlement or write-off; takeaway can be paid before handover. A fully discounted, zero-value check also has an explicit close action.

The printing integration is designed for Epson Server Direct Print, with the Epson TM-m30III as the first supported model configuration. The printer needs to be configured to connect to your backend, and its network connection must be working. Compatibility and printing should be verified with your actual device during setup. Kitchen and check printers are selected per location and may be the same device.

Entity administrators manage menu, table, tax, staff and printer configuration in Admin. The staff app shows printer assignments and connection status without editing business configuration. Users entitled to more than one entity can switch their current entity in the staff app’s settings; their work remains scoped to that selection and their location access.