BMS FOR RESTAURANTS & CAFÉS
See every step from central kitchen to table
Connect the central kitchen, branches, orders, kitchen, stock and costs in one system. AI explains the data; people make the decisions.
One restaurant workflow
- Central kitchen
- Prepare stock
- Take orders
- Send to kitchen
- Take payment
- Review results
HOW YOUR RESTAURANT WORKS
Choose the work you want to understand
12 flows in 4 categories — see who does what, where BMS and the AI assistant help, and how exceptions are handled.
Choose how your shop works
Select an example and recommended flows. This does not change your store configuration.
Board game cafes have dedicated play-time and billing-group workflows. Select this format to explore its example.
Main guide: restaurants and cafes. Select a shop format to see relevant flows and setup requirements.
FLOW 03 · Related
Take orders, send them to the kitchen and collect payment
Staff or a table QR captures the request, staff review it before kitchen send, then payment, receipt and stock deduction are completed.
Sequence diagram · steps and exceptions
Read from top to bottom. Dashed arrows are replies. Scroll horizontally to see all participants, or use the text transcript below.
Play the guided steps
Choose a case and press Play. The current step is highlighted and spoken using your device voice.
Take orders, send them to the kitchen and collect payment. Staff or a table QR captures the request, staff review it before kitchen send, then payment, receipt and stock deduction are completed.
This browser does not support narration. Try opening the link in a recent Chrome, Edge or Safari. Visual steps and captions remain available. Resuming after a pause restarts the current step.
Read all steps as text
- Staff / cashier → BMS tables and checksVerify staff, open shift and table
- Case: Staff take the order
- Customer → Staff / cashierOrder dishes and options
- Staff / cashier → BMS tables and checksAdd dishes and options
- Alternative: Customer uses table QR
- Customer → BMS tables and checksSubmit requested items
- BMS tables and checks → Staff / cashierPresent proposal for review
- Staff / cashier → BMS tables and checksAccept items into check
- BMS tables and checks → BMS tables and checksValidate menu, options, price and promotions
- Staff / cashier → BMS tables and checksConfirm kitchen round
- BMS tables and checks → Inventory and costsReserve items and recipe ingredients
- Inventory and costs → BMS tables and checksReservation result
- Case: Round sent successfully
- BMS tables and checks → Kitchen displayCreate work by station
- Kitchen display → Kitchen displayKitchen accepts and prepares food
- Kitchen display → Staff / cashierUpdate food status
- Staff / cashier → CustomerServe food
- When applicable: Customer orders more
- Customer → Staff / cashierRequest more items
- Staff / cashier → BMS tables and checksAdd and send another round
- BMS tables and checks → Kitchen displayCreate next round after validation
- Customer → Staff / cashierRequest the bill
- Staff / cashier → BMS tables and checksReview items, discounts, membership and total
- Customer → Staff / cashierPay using a configured method
- Staff / cashier → Payments and shiftsConfirm payment with the request reference
- Payments and shifts → Inventory and costsSettle, deduct stock and record cost atomically
- Payments and shifts → BMS tables and checksCompleted bill and receipt data
- BMS tables and checks → CustomerReceipt
- Alternative: Unavailable or insufficient stock
- BMS tables and checks → Staff / cashierIdentify items to correct
- Staff / cashier → CustomerAgree replacement items
- A retry returns the original result; it must not repeat the sale or stock deduction
Staff must review table QR requests before sending them to the kitchen.
Start with your type of restaurant
Choose the workflows you need, then configure recipes, permissions and responsibilities before taking real orders.
- Dine-in restaurants
- Cafes and drinks
- Pickup / delivery
- Multiple branches
- Central kitchens
Understand the scope before starting
- The 12 flows cover both POS and the web back office. Not every step has a screen in the desktop or mobile app.
- Use the web back office for recipe setup, cost analysis, requisitions, PO creation and access management. POS apps handle sales, kitchen work, transfers and receiving within staff and branch permissions.
- Stores using tables, QR ordering and kitchen workflows must select the Restaurant preset before their first real order.
- Actual costs require receipt evidence and inventory valuation. Missing values remain unknown, never silently zero.
- A central kitchen is one branch in BMS. It produces prepared goods as lots with expiry dates; batch cost uses actual yield and excludes labour, energy and shared expenses.
- The AI assistant reads and explains the low-stock warnings BMS calculates. They are estimates: it does not forecast sales, and it never orders, produces or moves stock on its own.
- Branch requests do not create production automatically, and transfers do not yet support lot- or expiry-tracked products, so goods the central kitchen produces as lots cannot yet be sent through a requisition.
- Recipes and SOP are reference information; your team still needs training and on-the-floor checks.
- foodpanda is sandbox/shadow only. GrabFood and LINE MAN remain dependent on integration agreements.
- Offline dine-in and a complete station-specific printer selection workflow are not supported.
- Rehearse with your actual hardware, payments and handover process before launch. Availability depends on configuration and installed version.
BEFORE YOU START
Choose restaurant software around the work your shop does
Start with counter service, table service or pickup, then trace how orders reach the kitchen, payment and inventory. BMS provides guides for each workflow, including boundaries to check before going live.
What should a restaurant prepare before using BMS?
Prepare menus, prices, recipes and ingredient units, kitchen stations, a floor plan where needed, and staff permissions. Rehearse opening a check, sending kitchen work, taking payment and checking reports before serving real customers.
Does a counter-service cafe need every table and kitchen feature?
No. A shop that takes payment and hands over products immediately can start with the Retail POS food-counter guide. Shops that send work to a kitchen or keep table checks open should follow the restaurant guide. Choose the workflow that matches the shop.
Does taking payment automatically send an order to the kitchen?
Payment and kitchen dispatch are separate BMS steps. Review the order and submit kitchen work through the restaurant workflow. Taking payment alone does not create kitchen work.
Are GrabFood and LINE MAN integrations ready to use?
Do not assume live availability. GrabFood and LINE MAN connections remain blocked by provider contracts and access requirements. Check readiness with the BMS team before planning a rollout. The foodpanda adapter is limited to sandbox/shadow use.
Which workflow matters to your restaurant?
Tell the BMS team about your store, branch count and the work you want to improve.
These diagrams explain system capabilities. They are not live store data or proof of completed transactions. Content reviewed 31 October 2026.