For facility management companies that run their contracts and site teams on spreadsheets. Odoo ties every work order and every hour to the contract and the site it belongs to.
AzkaTech has set up Odoo for service operators like EMMS and Generation R Holding, and stays with your team after go-live.
Official Odoo Gold Partner. Implementing Odoo since 2015.
Who it’s for
Companies that service building systems under yearly contracts.
Teams that work in shifts across many client sites.
Firms that look after buildings on behalf of their owners.
Groups that run their own properties and the services inside them.
The problem
Clients report problems by phone and message, and some are never closed.
Service dates for equipment are kept on paper, and nobody is reminded.
You cannot tell which sites cost more to serve than the contract pays.
Jobs outside the contract are done on site but never reach the invoice.
01 · Work orders
A facility company lives on requests. A tenant calls about a leak, a supervisor forwards it by message, and a technician goes when he can. Nobody records what was done or which parts were used, so the office cannot bill it or prove it was fixed.
In Odoo, each request becomes a work order with its site and its priority. The dispatcher assigns a technician, who sees the job on a phone. On site he records the work and the parts used, and the client signs on the screen.
AzkaTech sets up the request types and priorities to match the response times in your contracts.
Example. A tenant reports a leak on the portal at 8 am. The dispatcher sends the nearest technician, who closes the job at 11 with a photo and the client’s signature on his phone.
Who it’s for
Dispatchers and technicians.
Outcome
Every request is followed until it is closed, with proof of the work.
02 · Contracts and billing
Most facility work is sold as a yearly contract with a fixed monthly fee. The cost of serving it sits in wages and in parts, in different files. So a contract can lose money for months before anyone sees it, and extra jobs done on site are forgotten at invoice time.
Odoo invoices each contract on schedule, and collects its costs on the same record. Technician hours and parts are posted to the contract they were used for. Work the contract does not cover is invoiced separately out of the work order.
EMMS, a property and facility management company in Lebanon, replaced its in-house software with Odoo. Its sales and invoicing now run with accounts for three countries, and its projects carry timesheets.
Example. A contract pays $4,000 a month. Hours and parts on that site add up to $4,600 this month, so the contract shows a loss before the quarter ends.
Who it’s for
Contract managers and finance teams.
Outcome
You see revenue and cost for each contract, and you bill everything you deliver.
03 · Planned maintenance
Buildings are full of equipment that needs regular service. When the schedule sits in a spreadsheet, a visit is skipped, and the breakdown that follows costs more than the visit would have. The client then asks for the service history, and nobody has it.
Odoo keeps a record for each piece of equipment, with its site and its service plan. Planned visits are created ahead of time and land in the technician’s schedule. Every repair is logged on the equipment, so its history is one click away.
During setup, AzkaTech loads your equipment lists for each site, with the service interval for each type.
Example. Each unit on a site has a 90-day service plan. Odoo opens the next visit on its own and shows the earlier visits on the unit’s record.
Who it’s for
Maintenance engineers and supervisors.
Outcome
Planned visits happen on time, and each asset has its full history.
04 · Site teams
Cleaning and security teams work in shifts across many buildings, often in more than one country. Attendance comes in on paper, and payroll is rebuilt each month in a spreadsheet. Labor is the biggest cost of a contract, and it is the one least tracked.
Odoo plans shifts for each site and records attendance against them. Hours feed into payroll under the rules of each country. The cost of those hours lands on the site, so you see what each client really costs to serve.
For EMMS, AzkaTech set up attendance and payroll in line with the labor rules of each country it works in.
Example. A guard works 12-hour shifts on two sites this week. His hours are logged per site, so payroll pays him once and each site carries its own cost.
Who it’s for
Operations managers and HR.
Outcome
Every site is staffed, and every hour is paid and costed.
How it works
Parts are kept in a main store and in each van, and Odoo shows what needs refilling.
Their purchase orders and bills are linked to the site, so their cost is part of the contract’s numbers.
Clients log in to report a problem and follow their requests and invoices.
Generation R Holding runs Colibri Hotel and its restaurants in one Odoo. Read the Colibri Hotel case study.
Escales International, a destination management company, takes its reservations and invoices them in Odoo.
EMMS also uses Odoo for recruitment and staff appraisals.
Implementation
AzkaTech uses AI in every phase of the Odoo project, and it stays in use after go-live.
AI capability · Discovery
We follow a request through your company with your dispatchers and your site supervisors. AI turns those notes into a clear list of what Odoo needs to cover.
AI capability · Mapping
Your processes are mapped onto Odoo in a fit-gap analysis. AI matches your site and equipment lists to Odoo and flags what is missing.
AI capability · Configuration
We build the solution with standard Odoo first. AI drafts the setup notes, with one short guide for technicians and one for the office.
AI capability · Testing
AI prepares test cases built on real requests and contracts. Your team runs them in a pilot and signs off before launch.
AI capability · Governance
AI follows open issues and training progress for each site team, so risks show up before launch day.
AI capability · Post Go-Live
After launch, AzkaTech support stays with your team. You also get a knowledge base written around your own setup.
Client proof
Client example · Property and facility management in the MENA region
Hotel and restaurant group in Lebanon
An earlier Odoo project at Generation R Holding never fully went live. AzkaTech restarted it in phases, covering stock and point of sale for the hotel and its outlets, with accounting in the same system. Read the Colibri Hotel case study
FAQ
For most facility companies, yes. Odoo Maintenance and Field Service cover assets, planned visits and work orders, and the same system bills the client. Live sensor data from a building management system needs a connection.
Yes. Clients log in to the portal or fill a web form, the request becomes a ticket or a work order, and they can follow its status.
Yes. Field Service works on the phone, with the job details, a worksheet, photos, parts used and the client’s signature.
Yes. Each piece of equipment gets a preventive plan, and Odoo creates the next maintenance request on that schedule.
Yes. Parts and hours on a work order that are not covered by the contract go to the client’s invoice, so extra jobs don’t get lost.
Yes. Each van is its own stock location, so parts used on a job come out of that van and the main store knows what to refill.
Yes. Odoo Planning assigns people to shifts and sites, and their hours flow into timesheets and payroll.
Odoo charges per user per month. Field Service, Maintenance and Planning are in the paid plans, and running several companies needs the Custom plan. See our Odoo pricing guide.
