Odoo Lunch: Vouchers, Orders, and Simple Payroll Add-Ons

Introduction

Odoo Lunch centralizes employee data, time off, recruitment, and HR documents so managers and HR work from one file per person instead of parallel folders and tools.

People processes affect every department, yet leave balances, contracts, and hiring status are often unclear until someone escalates a problem.

The Lunch apps connect HR events to the org chart, approvals, and, where relevant, payroll or expense flows, giving leadership a live view of headcount and availability.

HR business partners, office managers, and executives planning workforce changes will find practical patterns to compare with their current setup.

Lunch is part of Odoo's modular ERP. Teams adopt it when they want clear responsibilities, repeatable workflows, and searchable history instead of isolated messages and offline spreadsheets. Odoo Lunch: Vouchers, Orders, and Simple Payroll Add-Ons states the storyline for stakeholders approving budgets.

This article is a ranked Top 10 from Level 1 (easy) to Level 10 (expert). Every level includes numbered steps: what you would actually click in Odoo Lunch.

Start where you are comfortable, not at level 10 because it sounds impressive.

Read the challenge section next, then open the level that matches your team today.

In this guide, you will see:

• What Odoo Lunch is responsible for in a typical company stack
• Where teams feel the most friction today (and why)
• Ten ranked use cases from beginner discipline to advanced strategy
• When automation or integrations justify bringing in an Odoo partner

The Challenge

HR sends a leave approval by email. Payroll finds out late. The manager on site has no idea who is available Tuesday. Everyone trusts HR, but the data is always one step behind reality.

HR processes touch every employee, yet leave, recruitment, and contracts often sit in separate tools. Managers lack a single place to approve requests and see team availability.

Sound familiar? Teams usually hit these walls:

• Leave balances disputed because requests live in email
• Recruitment status unclear across hiring managers
• Contracts signed without a central employee file

The good news: you do not need a big-bang project to fix everything. Pick one use case below, run it for 30 days in Odoo Lunch, and measure what changes.

Top 6 Lunch Use Cases

6 use cases for Odoo Lunch, ranked from Level 1 (easy, do it this afternoon) to Level 6 (expert). Each one answers: what would we build, and what are the clicks in Odoo?

Level 1 is the easy starter. The last level is the ambitious scenario you might dream about but rarely build alone.

Pick your level, follow the numbered steps in a test database, then move up when the previous level feels boring.

1. Order your first lunch from the Today's Menu Level 1 — Easy

Level 1 is the simplest possible Lunch action: one employee, one product, one click. No automation, no payroll wiring, just a real order placed against today's menu.

Here's how you'd do it in Odoo:

1. Install the Lunch app, then go to Lunch, Configuration, Vendors, New, and add a caterer with the days it delivers and a daily order cutoff time.
2. Go to Lunch, Configuration, Products, New, and add today's item with a name, a category, a price, and the vendor you just created.
3. An employee opens Lunch, My Lunch, Order Your Lunch Today, and clicks the product card to add it to the order.
4. The employee picks the delivery location, confirms the quantity, and clicks Order; the line lands in Today's Orders for the manager.
5. The manager opens Lunch, Manager, Today's Orders, validates the line, and sends the consolidated list to the vendor before the cutoff.

What you get: Lunch ordering moves from a paper sheet on the kitchen door to one traceable record per meal, ready to grow into the rest of the workflow.

2. Build a weekly menu with multiple vendors, categories and locations Level 2 — Easy

Level 2 makes the menu real. Several vendors deliver on different days, products are grouped by category, and employees only see what is available at their office today.

Here's how you'd do it in Odoo:

1. In Lunch, Configuration, Vendors, configure each caterer with their delivery days, order cutoff time, available locations, and contact email.
2. In Lunch, Configuration, Products, create the full catalog and tag each product with a category such as Sandwich, Salad, Pizza, or Vegan.
3. In Lunch, Configuration, Locations, add each office or floor where lunches are delivered, with the responsible lunch manager.
4. Upload a photo and a short description on every product so My Lunch shows a visual menu instead of plain text rows.
5. Open Lunch, My Lunch, Order Your Lunch Today, and confirm that filters by category, vendor, and location all work as expected.

What you get: Employees stop asking who delivers today, the menu is right on every floor, and the manager runs one validated order per vendor instead of chasing emails.

3. Manage employee balances with cash moves and monthly top-ups Level 3 — Medium

Level 3 turns Lunch into a small internal wallet. Each order debits the employee account, HR credits it monthly through cash moves, and balances stay visible on both sides.

Here's how you'd do it in Odoo:

1. Go to Lunch, Manager, Cash Moves, New, pick an employee, set the amount as a credit, and add a note such as Monthly Allowance.
2. Each new order automatically posts a matching debit cash move, so the employee balance updates without any manual entry.
3. An employee opens Lunch, My Lunch, and sees the current Account Balance in the header before placing the next order.
4. For recurring top-ups, schedule a server action that posts a fixed monthly credit to every active employee on payday.
5. Use Lunch, Reporting, Cash Moves, group by Employee, to spot negative balances and send a reminder in Discuss before the next order window.

What you get: No more shared envelope or side spreadsheet to track lunch debts: every euro spent and credited is traceable on the employee record and on the report.

4. Drive adoption with alerts, favorite products, and a clean usage report Level 4 — Medium

Level 4 nudges employees at the right moment. Daily alerts remind them to order before cutoff, favorites speed up reorders, and reporting reveals what should stay on the menu.

Here's how you'd do it in Odoo:

1. Open Lunch, Configuration, Alerts, New, and schedule a daily message at 09:30 such as Order before 10:30 to be served at noon.
2. Restrict the alert to weekdays only and to the office locations where lunches are actually delivered to avoid noise.
3. Ask employees to mark their favorite products in My Lunch so a single click reorders the same meal on the next eligible day.
4. Open Lunch, Reporting, Lunch Orders, group by Product and Vendor, and pin the top sellers and slow movers on the dashboard.
5. Share the monthly report with each vendor to renegotiate prices or remove items that almost nobody orders anymore.

What you get: Daily participation grows because the menu is curated by data and reminders, and vendor contracts finally reflect what employees actually eat each week.

5. Roll out to multiple sites with Payroll or Expenses deductions Level 5 — Hard

Level 5 connects Lunch to HR finance. Each site has its own vendor mix and cutoff, monthly statements are pushed to Payroll as a salary deduction, or to Expenses when the employer pays the meal.

Here's how you'd do it in Odoo:

1. In Lunch, Configuration, Locations, add one record per site, each with its own responsible manager, vendor mix, and order cutoff time.
2. Run Lunch, Reporting, Cash Moves, group by Employee and Month, and export the statement that each employee will validate before deduction.
3. In Payroll, Configuration, Salary Rules, create a Lunch Deduction rule that pulls the previous month total from the employee Lunch balance.
4. For employer-paid lunches, automate the creation of one Expenses report per employee from the same monthly statement, with the right analytic account.
5. Add an approval step in Studio so HR validates each statement in one click before it flows into the payslip or into the expense report.

What you get: Lunches become a real HR benefit with clean monthly statements, no shadow accounting, and per-site control on cost and vendor choice.

Wiring Lunch with Payroll salary rules, Expenses workflows, multi-site cutoffs, and Studio approvals is the kind of cross-app setup Dasolo runs as a partner-led engagement.

6. Run an AI cafeteria with vendor APIs, a Discuss bot, and a live dashboard Level 6 — Expert

Level 6 is the full operating system: an AI assistant proposes the menu mix, orders are pushed straight to vendor APIs, employees order through a Discuss bot, and a live dashboard tracks every euro.

Here's how you'd do it in Odoo:

1. Train an AI assistant on past orders, dietary tags, season, and budget so it proposes the optimal weekly menu per location and language.
2. Connect each vendor through API or webhook: the validated daily order is sent automatically and the confirmation message lands back in the Lunch chatter.
3. Add a Discuss bot that handles requests like Order my usual or Suggest a vegan option, and writes the order directly into Lunch on the right location.
4. Use Studio to add custom fields on products for allergens, carbon footprint, and supplier rating, and surface them on every product card.
5. Build a Spreadsheet Lunch Live dashboard with orders per site, vendor performance, average ticket, payroll cost, and CSAT, refreshed every minute.
6. Trigger Marketing Automation to send the weekly menu by email and chat in each employee preferred language, with a one-click pre-order link.

What you get: The entire lunch operation runs on autopilot, costs stay visible by site, employees order in two taps, and HR has hard data to defend the benefit at budget time.

Designing the AI menu logic, the vendor API plumbing, the Discuss bot, and the live cost dashboard across Lunch, Payroll, Studio, and Spreadsheet is the architecture Dasolo designs as a partner-led engagement. Most teams need an outside team to assemble these pieces correctly the first time.

When Expert Help Makes Sense

If levels 1 to 4 fit your world, you can often succeed with standard Odoo Lunch, a patient internal owner, and a sandbox where people are allowed to break things safely.

From level 5 upward, the stakes rise: automated workflows that email the wrong customer, Studio fields that block upgrades, APIs that silently stop syncing stock at 2 a.m.

That is not a failure of your team. It is a signal that architecture, testing, and governance matter.

Bring in a partner when you need multi-app design, country-specific compliance, complex integrations, or a go-live date the board already put in the calendar.

Work With Dasolo

Dasolo helps companies implement Odoo the way they actually work: custom apps, clean integrations, and training people will remember after the consultants leave.

If your roadmap for Lunch includes the advanced use cases in this guide, we can map a phased plan: quick wins first, then automation and integrations with clear owners and test scripts.

You keep control of scope and budget. We bring the Odoo depth so your team does not learn expensive lessons in production.

Book a free consultation:

Schedule your demo