Control every shift and branch
See what sold, what was consumed, what was wasted, and what needs attention. Oyo suggests branch actions while managers retain control of approvals.
- 01
Close every branch with fewer reconciliation gaps
- 02
Connect recipe usage to purchasing and margin
- 03
Catch waste, void, discount, and cash exceptions sooner
Illustrative operating workflow
This page shows a target restaurant workflow. Hardware, delivery platforms, payment methods, and FBR scope are verified during discovery.
Where work starts to break
These are the recurring operating gaps the workflow is designed to surface and route.
Sales and consumption drift
POS sales do not always translate into accurate ingredient usage and store balances.
Branch closing is manual
Cash, card, delivery, discounts, voids, and refunds need separate reconciliation.
Waste is recorded without context
Teams can log waste but struggle to connect it to recipe variance, shifts, or purchasing.
Central kitchen planning reacts late
Production and dispatch plans often depend on calls, spreadsheets, and yesterday's view.
From signal to recorded action
Each stage has an owner, a clear output, and a record the next team can trust.
- 01Front of House
Capture the order
Send dine-in, takeaway, and delivery orders through the correct menu, price, and service flow.
POS and kitchen order
- 02Kitchen and Store
Prepare and consume
Route items to KOT or KDS and post approved recipe consumption against branch stock.
Production and usage record
- 03Branch Manager
Close the shift
Reconcile payment channels, voids, discounts, refunds, cash, and delivery settlements.
Shift close with exceptions
- 04Operations and Purchasing
Replenish and review
Prepare branch and central kitchen needs using sales, stock, waste, and lead times.
Approved replenishment plan
Important activity, clearly explained
Oyo shows what happened, why it matters, and what your team can check next.
Approval is the default
Sensitive commercial, financial, quality, and inventory actions remain with authorized people.
- Manager review
Closing difference
Reconcile the shift
- When Oyo flags it
- A shift reaches its configured closing time.
- Suggested next step
- Matches POS, payment, delivery, refund, and cash records, then isolates variances.
- Manager control
- Only an authorized manager can close with an unresolved variance.
- Manager review
Waste above target
Protect food cost
- When Oyo flags it
- Waste or theoretical consumption crosses the configured tolerance.
- Suggested next step
- Links the variance to item, recipe, shift, branch, and recorded reason.
- Manager control
- Inventory adjustments require evidence and approval.
- Manager review
Kitchen readiness
Prepare the next production run
- When Oyo flags it
- Branch demand or central kitchen stock changes materially.
- Suggested next step
- Drafts production and dispatch quantities with demand and shelf-life context.
- Manager control
- Production release remains with the assigned operations lead.
- Manager review
Unusual discounts
Review unusual concessions
- When Oyo flags it
- A void, refund, or discount breaks branch policy.
- Suggested next step
- Shows the receipt, operator, authorization, reason, and related activity.
- Manager control
- Oyo flags the activity for review. It does not accuse or penalize staff.
One operating record
POS and Order Flow
Tables, takeaway, delivery, menus, pricing, KOT, KDS, and payments.
Recipe and Kitchen Control
Recipes, yield, modifiers, production, consumption, and wastage.
Purchasing and Stock
Branch stock, central kitchen, transfers, suppliers, and replenishment.
Branch Finance
Shift closing, settlements, expenses, taxes, cash, and margin.
FBR POS Integrated
Restaurant POS flows can require real-time invoice validation, submission, reference capture, QR printing, and exception handling.
Review the FBR workflow- Validate invoice and tax fields before submission
- Capture the FBR response against the POS receipt
- Print or display the required QR and reference
- Control retries, refunds, and corrections
FBR POS Integrated is configured for the restaurant's selected route, environment, branches, and supported transaction flows during implementation.
Start with one controlled flow
Configure around real roles, rules, data, and approvals before expanding the operating footprint.
- 01
Map menus, modifiers, recipes, service channels, and branch closing rules.
- 02
Validate POS hardware, printers, payments, and delivery integrations.
- 03
Configure manager approvals for voids, discounts, refunds, and variances.
- 04
Start with one branch and one closing cycle before network rollout.
Show us how the work really moves
Bring one branch closing, recipe cost, waste, or FBR exception. We will map the complete operating flow.