Case study · Food & Beverage
Multi-branch F&B chain operations on Odoo 17
How TechUltra unified a multi-branch F&B chain on Odoo 17 — restaurant POS, customer mobile ordering, kitchen workflows, inter-branch supply chain, governed procurement, tiered loyalty, and GCC-oriented HR and payroll on one ERP. The build was delivered for a specialty coffee operator, and the same vertical patterns fit café, restaurant, QSR, and bakery chains running at the same scale.
- GCC
- Multi-branch
- Restaurant POS
- Café + QSR + bakery
- Odoo 17
- Platform
- Odoo 17
- Industry
- Food & beverage chain — café, restaurant, QSR
- Model
- Multi-branch + mobile + POS
- Region
- GCC
Last updated
Overview
What TechUltra delivered
An Odoo 17 deployment with 50+ client-specific custom modules layered on standard restaurant POS, inventory, purchase, MRP, HR, payroll, loyalty, documents, and planning apps. Custom work is concentrated where F&B chains differ from generic retail: POS depth (modifiers, split bill, sub-shift cash), inter-branch transfers, loyalty across channels, governed branch procurement, central-kitchen production, and a workforce platform tuned for GCC employment patterns.
Operating context
A growing F&B brand running branch stores with restaurant-style service — specifically a specialty coffee operator, with patterns shared by café chains, QSR groups, casual-dining restaurants, and bakery chains at the same scale. Multi-company and multi-branch in Odoo, with in-store POS, customer mobile ordering, and kitchen preparation as the customer-facing surfaces, and a large hourly staff base running the compliance and payroll patterns typical of GCC employment.
Business challenges
Six problem areas shaped the build — from channel alignment to workforce governance.
-
Disconnected channels
Mobile orders, in-store POS, and kitchen prep needed a single operational backbone.
-
Branch replenishment
Stock movement between outlets needed approvals, logistics, and traceability — not informal hand-offs.
-
Procurement control
Branch material requests had to be approved before any purchase commitment was made.
-
Restaurant POS depth
A standard checkout cannot run a café — modifiers, toppings, split bills, sub-shift cash, and branded receipts are baseline.
-
Customer retention
Loyalty needed to run across POS and mobile with tiers, referrals, and consistent redemption.
-
Workforce compliance
Employee documents, attendance, leave, advances, penalties, and final settlement had to live on regulated workflows.
ERP solution approach
One Odoo platform, modular vertical domains. Custom work goes where café operations differ from standard retail; everywhere else, Odoo's standard apps do the job.
- Unified order backbone — mobile cart and in-store POS share the same order and kitchen workflow
- Custom POS layer — restaurant features, branded receipts, sub-shift cash control, and loyalty payment methods on the till
- Mobile API — a REST layer for catalog, cart, orders, loyalty, branches, and feedback
- Branch supply chain — inter-branch transfers with area-manager approval and logistics capture
- Governed procurement — requisition → approval → purchase order, with finance and management sign-off
- Production support — production requests for central kitchen and POS-triggered manufacturing for made-to-order items
- HR platform — employee master, documents, attendance, leave, payroll deductions, gratuity, and structured offboarding
- Self-service — employee portal for leaves, attendance, payroll, documents, and HR requests
- Integrations — biometric attendance push and WhatsApp messaging / verification patterns
Architecture — layered on Odoo 17
- Experience POS theme, employee portal, mobile app
- Integrations Biometric attendance, WhatsApp
- Vertical custom layer Loyalty, inter-branch transfers, HR, mobile API
- Odoo 17 core apps POS, Inventory, Purchase, MRP, HR, Payroll, Loyalty
- Platform Odoo 17 — one system of record
One platform, four operational pillars
Odoo 17 platform
One system of record for every operational domain
-
Mobile + POS + kitchen
Unified order model
-
Branch supply chain
Transfers + procurement
-
Loyalty + retention
Tiers, referrals, redemption
-
Workforce platform
HR, payroll, portal
Functional & technical scope
Ten capability domains run end-to-end on the platform — from the till to the kitchen, from a branch material request to a final settlement.
Capability matrix
| Domain | Capabilities |
|---|---|
| Mobile & POS | Mobile API, unified POS orders, kitchen display, order tracking, pickup notifications |
| Restaurant POS | Modifiers, toppings, variants, split bill, kitchen receipts, sub-shift cash, low-stock alerts |
| Loyalty | Tiered membership, birthday rewards, referrals, peer-to-peer point transfers, POS redemption |
| Inventory | Inter-branch transfers, return transfers, logistics metadata, transfer PDF |
| Procurement | Purchase requisitions, petty / daily paths, multi-level PO approval, budgets, vendor ratings |
| Manufacturing | Production requests, consumption / wastage reporting, POS-triggered manufacturing orders |
| HR & payroll | Documents with expiry alerts, leave chain, advances, penalties, overtime, gratuity, payslip PDF |
| Offboarding | Exit, demobilization, exit-interview, and camp-inspection checklists |
| Attendance | Biometric device push, processing jobs, attendance summary fed into payroll |
| Self-service | Employee portal for HR requests, attendance, payroll, and documents |
Technical foundation
- Odoo 17 as the core platform with standard restaurant POS, inventory, purchase, MRP, HR, payroll, loyalty, documents, and planning apps
- 50+ client-specific custom modules covering POS, mobile, HR, supply chain, and loyalty
- Mobile REST API for catalog, cart, orders, loyalty, branches, and feedback — feeding the POS order model
- Biometric attendance via push-protocol device integration (ZKTeco, ESSL, ADMS-compatible)
- WhatsApp messaging and OTP / verification patterns for customer and employee touchpoints
- Custom PDF outputs for branded receipts, payslips, settlement documents, and transfer notes; XLSX exports for POS sales and payments
- Security model with central HR / Finance / GM roles, area managers, transfer supervisors, and portal ACL extensions
Feature deep-dives
Nine capability areas, each tied to a business problem and the work TechUltra delivered.
Mobile ordering on the POS backbone
One order model for mobile, store, and kitchen.
Business problem
- Mobile-app orders living outside the ERP create duplicate entry and kitchen blind spots
- Kitchen and store staff need the same visibility for app and walk-in orders
- Loyalty earn-and-redeem and branch selection must apply consistently across channels
What TechUltra delivered
- A REST API for authentication, catalog, cart, checkout, orders, loyalty, branches, and feedback
- Mobile carts persisted as POS orders tied to the originating branch session
- Kitchen preparation display integration for both mobile and in-store orders
- Order tracking and pickup notification capability through the same workflow
| Stage | What happens |
|---|---|
| Mobile cart | Persists as a POS order draft |
| Branch routing | Tied to the chosen branch's POS session |
| Kitchen | Same preparation display as walk-in orders |
| Loyalty | Earn and redeem against the same wallet on POS |
Restaurant POS & store control
Full-service F&B POS with operational discipline.
Business problem
- Standard retail POS lacks modifiers, toppings, and variants for café, restaurant, and QSR menus
- Table service needs split-bill and kitchen-receipt workflows
- Cash control and float discipline require sub-shift handovers, not just one session per day
- Refund control and branded customer touchpoints are baseline F&B chain expectations
What TechUltra delivered
- Predefined order modifiers and topping selection with extra pricing
- Product-variant selection from a template popup at the till
- Split bill for table service
- Branded receipts with branch-specific numbering and kitchen receipt printing
- Sub-shift open / close for cash and float control
- Low-stock warnings based on ingredient availability
- Refund password and enhanced session-close behaviour
- Multi-currency payment support at till
| Capability | Why it matters in F&B |
|---|---|
| Modifiers / toppings | Café and restaurant menus are highly configurable per order |
| Split bill | Table service needs per-guest invoicing |
| Sub-shift cash control | Multiple cashiers per day on the same till |
| Branded receipts | Per-branch numbering matches accounting trail |
| Low-stock alerts | Prevents selling out-of-stock items mid-shift |
| Multi-currency at till | Useful in tourist-facing café and restaurant outlets |
Loyalty & membership
Tiered retention across POS and mobile.
Business problem
- F&B chains live on repeat custom — café, QSR, and bakery operators in particular run on lifetime-value economics
- Members expect tiers, redemption at the till, and the ability to gift points
- Birthdays and inactivity are obvious points-engagement triggers if automated
What TechUltra delivered
- Silver / Gold / Platinum membership with full point-earning history
- Birthday-reward automation tied to the customer master
- Referral codes attached to member accounts
- Peer-to-peer point transfers with member confirmation
- Loyalty redemption available as dedicated POS payment methods
- Scheduled point maintenance and expiry-notification jobs
| Mechanism | Member-facing |
|---|---|
| Tiered membership | Status progression with on-receipt tier badges |
| Birthday rewards | Automatic point grant on the configured date |
| Referral codes | Per-member code for friend sign-ups |
| Peer transfers | Send points to another member with confirmation |
| POS redemption | Pay-with-points as a payment method |
Inter-branch stock transfers
Governed replenishment between outlets.
Business problem
- Informal stock movement between branches loses visibility and accountability
- Each branch needs to request, justify, and receive against a tracked record
- Logistics — vehicle, driver, dispatch time — has to live with the transfer, not in side notes
- Bakery and raw-material flows have different handling needs from finished goods
What TechUltra delivered
- Transfer requests with a draft → approval → dispatch → receipt workflow
- Area-manager approval with email and Odoo activity notifications
- Logistics capture: vehicle, driver, dispatch time, quality check
- Separate paths for standard, bakery, and raw-material transfers
- Return-transfer support and a printable transfer document
- Cross-links into purchase requests and production requests
| Stage | Owner |
|---|---|
| Request | Requesting branch |
| Approval | Area manager |
| Dispatch + logistics | Sending branch |
| Receipt | Receiving branch |
| Stock update | Odoo Inventory |
Procurement & spend control
Structured requisition-to-purchase flow.
Business problem
- Branch material requests need a controlled path to a purchase commitment
- Petty-cash and daily-spend requisitions need fast-track handling alongside formal POs
- Approval delays cause stockouts and missed deliveries — daily reminders are essential
- Budgets and vendor performance need to be visible at the point of purchase
What TechUltra delivered
- Purchase requisitions with an extended multi-level approval workflow
- Petty-cash and daily-requisition paths with fast-track options
- Daily reminders for pending approvers
- Purchase-order approval chain: Finance Manager → General Manager
- Purchase budgets with spend tracking and vendor ratings
- Vendor association on product pricelists
| Stage | Approver |
|---|---|
| Requisition | Branch / department |
| Approval | Configurable approver chain |
| Purchase order | Procurement team |
| Finance review | Finance Manager |
| Management sign-off | General Manager |
Production & made-to-order
Central kitchen, bakery, and POS-driven manufacturing.
Business problem
- Central-kitchen and bakery items need production planning, not just inventory consumption
- Made-to-order POS items have to trigger a manufacturing order without manual entry
- Consumption and wastage reporting are required for cost control
- Production must tie back into the branch-transfer flow for distribution
What TechUltra delivered
- A production-request workflow before manufacturing orders are confirmed
- Bulk manufacturing with consumption- and wastage-reporting outputs
- Manufacturing orders triggered automatically from POS sales for configured products
- Integration with the branch-transfer and replenishment flows
| Trigger | Output |
|---|---|
| Production request | Planned manufacturing order |
| POS sale of configured product | POS-triggered MO |
| MO completion | Consumption + wastage reports |
| Finished good | Available for inter-branch transfer |
HR, payroll & offboarding
Workforce lifecycle on one platform.
Business problem
- Large hourly workforces need a structured employee master with compliance-document tracking
- Leave, advances, penalties, overtime, and early-out events must flow into payroll automatically
- Final settlement, gratuity, and offboarding checklists are regulatory in GCC employment
- Inter-branch transfer of an employee needs payroll handling, not just a master-data update
What TechUltra delivered
- Employee master with compliance documents and expiry alerts
- Recruitment documents with printable offer / contract outputs
- Multi-level leave approval with eligibility rules
- Salary advances, loans, penalties, overtime, and early-out events linked to payroll
- Final settlement / gratuity workflow with a printable settlement document
- Custom payslip PDF and a payroll-period attendance summary
- Exit, demobilization, exit-interview, and camp-inspection checklists
- Inter-branch employee transfer with payroll handling
| Stage | Record |
|---|---|
| Hire | Recruitment + onboarding docs |
| Work | Attendance, leave, overtime, early-out |
| Pay | Advances, loans, penalties, payslip PDF |
| Branch move | Inter-branch transfer with payroll continuity |
| Exit | Final settlement, gratuity, checklist completion |
Biometric attendance integration
Device punches flow directly into HR attendance.
Business problem
- Biometric devices typically need a middleware layer to feed an ERP
- Branch deployments demand zero-touch attendance capture
- Payroll inputs must be derived from raw punches with shift, overtime, and early-out rules
- Bulk back-loading of attendance is occasionally required for device outages
What TechUltra delivered
- Push-protocol integration for ZKTeco, ESSL, and ADMS-compatible devices
- Device registration, punch records, and processing into HR attendance
- Scheduled jobs for attendance processing and device maintenance
- Excel import option for bulk attendance loading
| Step | Output |
|---|---|
| Punch at the device | Recorded in Odoo via push |
| Processing job | HR attendance record |
| Shift rules | Overtime, early-out, late entries |
| Payroll inputs | Period summary attached to the payslip |
Employee self-service portal
HR requests without back-office bottlenecks.
Business problem
- Distributed branch staff cannot easily walk to the HR office for routine requests
- Leave, payslip, and document requests overwhelm HR back-office teams when not self-served
- Document downloads and equipment / advance / exit requests are repetitive and rules-driven
What TechUltra delivered
- A web portal covering attendance, leaves, payslips, and documents
- Support for expenses, helpdesk, equipment, salary advance, and exit requests
- Portal access rights configured for calendar, documents, and payslip visibility
| Request type | Outcome |
|---|---|
| Leave | Multi-level approval chain |
| Payslip | Self-download from the portal |
| Documents | Personal HR file access |
| Salary advance / equipment / exit | Routed to the right HR queue |
Before & after
A qualitative contrast. The "before" reflects the typical pre-platform pattern in the sector, not an audited baseline.
-
Before
Mobile orders kept separate from store systems
After
Mobile, POS, and kitchen on one order flow
-
Before
Informal branch stock movements with no audit trail
After
Approved inter-branch transfers with logistics captured
-
Before
Manual HR document tracking and ad-hoc renewals
After
Document expiry alerts and structured HR files
-
Before
Ad-hoc purchase approvals over messages and email
After
Requisition and PO approval chains in the ERP
-
Before
Generic POS without restaurant depth
After
Restaurant POS with loyalty and cash discipline
-
Before
HR team handling every leave and payslip request manually
After
Employees self-serve via portal; HR handles exceptions
Business benefits
-
Channel alignment
Mobile, POS, and kitchen share one operational record.
-
Branch control
Replenishment and purchasing follow approval paths, not informal hand-offs.
-
Store discipline
Restaurant POS, sub-shift cash control, and branded customer touchpoints.
-
Retention infrastructure
Tiered loyalty usable in-store and on mobile, with referrals and birthday automation.
-
Workforce governance
Documents, attendance, leave, and settlement on regulated workflows.
-
Self-service capacity
Staff handle routine HR through the portal without escalating to back-office.
-
Audit readiness
Transfer, procurement, and offboarding activities leave structured records.
-
Platform extensibility
Modular custom library supports ongoing branch and feature growth.
Why TechUltra
- Vertical F&B depth, not light configuration — a full chain operating model spanning POS, kitchen, supply chain, loyalty, and workforce
- Mobile architecture that doesn't fork the platform — customer app sits on the POS order model, no parallel e-commerce stack to maintain
- Multi-branch operations built in — area managers, transfer types, and branch-coded receipts reflect real café / restaurant / QSR outlet networks
- Central-kitchen and bakery production tied into branch replenishment — production requests and POS-triggered MO feed the same transfer flow
- GCC workforce complexity addressed — document compliance, gratuity, camp inspections, structured offboarding for hourly F&B staff
- Governed spending — requisition and PO approvals embed financial control in daily branch operations
- Integration without middleware sprawl — biometric attendance and mobile API live inside Odoo, not in a separate gateway
Similar use cases
| Profile | Parallel from this build |
|---|---|
| Multi-branch coffee, café, and tea chains | Restaurant POS + mobile + kitchen on one order flow |
| QSR and fast-casual chains scaling past a single outlet | Sub-shift cash control, branded receipts, branch-coded numbering |
| Casual dining and full-service restaurant groups | Split bills, table service, kitchen receipts, branded customer touchpoints |
| Bakery chains with a central production kitchen | Production requests + inter-branch transfers as one supply chain |
| Cloud / dark-kitchen operators serving multiple brands | POS-triggered manufacturing + mobile API on the same order model |
| Franchise and multi-company F&B groups | Multi-company Odoo with per-branch numbering and consolidated reporting |
| F&B operators launching mobile ordering alongside dine-in | Unified order backbone for app + in-store sales — no parallel e-commerce stack |
| Loyalty-driven F&B retail (specialty coffee, QSR, bakery, juice bars) | Tiered loyalty across POS and mobile with peer transfers and birthday automation |
| GCC employers with large hourly F&B workforces | Documents, gratuity, camp inspections, structured offboarding |
| Chains replacing spreadsheet-driven branch replenishment and HR | Approved inter-branch transfers + employee self-service portal |