Guests browse products the merchant makes available to the self-service path.
Publish only the items meant for self-service
The kiosk catalog is built from the merchant's configured sellable products instead of a disconnected menu copy. That gives the business one governed product identity while keeping the public selection focused on what guests should be able to order.
Keep price authority with the server
The browser creates the guest's selection, but the server resolves products and pricing before accepting the order. A server-priced cart keeps the public screen from becoming the authority for merchandise value.
Turn the cart into a numbered handoff
After submission, the guest receives an order number that staff can use to recognize the order. The workflow is designed around a clear physical handoff instead of asking the guest to explain an anonymous cart at the counter.
Take payment with the staffed checkout path
The current self-service flow sends the guest to pay at the counter. Staff retain the configured tender, age-check, receipt, and exception controls in the POS checkout that completes the transaction.
Fit the kiosk to the actual service model
During rollout, test the public catalog, difficult products, unavailable stock, cart totals, order-number handoff, counter payment, and staff recovery path on the device and network the merchant plans to use.
Run one guest order from catalog to counter
Publish representative test items, build a cart on the planned guest device, verify the server-priced total and resulting order number, then complete payment through the staffed checkout. Include unavailable stock, a refreshed price, an abandoned cart, and the staff recovery path.
Inspect in the live demo
Use the actual workflow, inspect the resulting record, and confirm how the behavior is configured for your locations. Availability can depend on enabled modules, hardware, payment setup, role, location, and rollout configuration.
Move from the feature to the operation
This capability shares customer, employee, product, location, transaction, and reporting context with the rest of LiftedPOS. The value is not a checked box. It is the handoff the operation no longer has to rebuild.