Preferences stay with each dish
The dish, ingredients, quantity and kitchen note belong to one order. Your team does not have to piece the details together.
Your guests choose a dish from your menu, customise it if they wish and pay within the ordering flow. The kitchen receives all the details together.
At the table · Takeaway · Delivery · At the kiosk
Your dish. With the ingredients you choose.
Choose a dish, customise your order and follow it through the kitchen to collection or delivery. This example does not place a real order or take a payment.
Model unavailable. Use the location controls to explore the scene.
Try both the guest and team views. Orders, waiter calls and payments in this preview are local examples.
The dish, ingredients, quantity and kitchen note belong to one order. Your team does not have to piece the details together.
A service request arrives with its table number. The team can acknowledge and complete it.
Received, preparing or ready. Guests and kitchen staff see the status of the same order.
Payment status stays linked to the order. We review suitable payment processing and possible POS integration with you.
You receive a specific proposal before work begins.
A menu with images, an ordering flow and a kitchen view. Table service and payments are added according to the agreed scope.
Your menu, prices, ingredients, images and an overview of your service and existing POS system.
You review the menu and a sample order. We then test the workflow on site with your team.
The proposal separates setup from ongoing operation. Payment processing and integrations are reviewed for your restaurant.
We will discuss which workflows help your team and what your guests actually need.