An equipment register with preventive schedules and breakdown requests any employee can raise, in Arabic and English.
Saudi factories, chains and facility companies lose production and sales to breakdowns that were reported in a WhatsApp group and forgotten, while Civil Defense, insurers and clients keep asking for maintenance logs nobody can find. Odoo Maintenance keeps every machine, its history and its schedule in one register, routes requests to the right team on a Kanban board, and ties equipment to the work centers in Odoo Manufacturing so planned downtime shows on the production calendar.
Equipment and request screens work in Arabic and English, so a technician who reads Arabic and a manager who reads English see the same record. Maintenance contracts and inspection dates for fire equipment, HVAC and lifts are tracked with reminders, which supports the Civil Defense Salamah licence and the Balady renewals that depend on it. Spare parts purchased with VAT in SAR are costed to the asset, and Naqlah, an Odoo Gold Partner in Saudi Arabia, configures the register around your branches, cities and shift patterns.
Licence-ready records
Fire extinguisher, alarm, HVAC and lift maintenance history is available on the equipment record when Civil Defense, Balady or an insurer ask. The accredited contractor's visits are logged as requests, so a lapsed contract is noticed before it blocks a renewal.
Multi-branch register
One register per company, with equipment located per branch and maintenance teams per city. HQ sees downtime across Riyadh, Jeddah and the Eastern Province while each outlet manager raises requests for their own machines.
Production-aware planning
Planned maintenance on a work center appears in the Manufacturing calendar, so production planning respects it. Ramadan night shifts and summer HVAC peaks are handled by adjusting the schedule, not by rebuilding it.
1. The request is raised
An outlet employee or line operator opens the equipment record, or scans the QR label on the machine, and submits a request with a photo and priority from their phone or tablet.
2. The team sees it on the board
The request lands on the maintenance team's Kanban board with a deadline, and the planner assigns a technician based on branch and skill. If the machine is a work center, Manufacturing shows the downtime immediately.
3. The technician does the work
Time spent, spare parts consumed from stock and the description of the fix are logged on the request. Parts not in stock trigger a purchase through Odoo Purchase.
4. History and schedules update
The request closes, the equipment history and MTBF update, and the next preventive date is recalculated. Cost per asset in Accounting reflects the labour and parts just used, as explained on our integrations page.
Timelines depend on the size of the equipment list and the number of branches, and Naqlah gives you a clear roadmap in the first consultation.
| Area | Before | With Odoo via Naqlah |
|---|---|---|
| Equipment list | An Excel sheet per branch, rarely updated | One register with location, vendor and full history |
| Breakdown reporting | A WhatsApp message that scrolls away | Request with photo, priority, owner and deadline |
| Preventive maintenance | Memory and calendar notes | Schedules generated automatically by interval or usage |
| Spare parts | Ad hoc purchases, no link to the machine | Consumed against the request from stock, costed to the asset |
| Downtime visibility | Unknown, argued about in meetings | MTBF, MTTR and downtime per machine and branch |
| Compliance records | Folders and contractor logbooks | History on the equipment record, ready for Civil Defense and insurers |
Everything else, we cover in a free 30-minute consultation.
Free consultation. Meet the team and get a clear roadmap in one call.
.svg)
.svg)