New: Odoo and Dynamics 365 cost calculators.Estimate your costs

Odoo Maintenance: preventive and corrective equipment care

Odoo Maintenance computes MTBF and MTTR in whole days from closed corrective work. Pricing, blocking, recurrence, and next-failure math, as of October 2026.

OdooOdoo Apps7 min readUpdated 24 sources

Key takeaways

  • Category, company, used by (department, employee, or both), team, technician, used-in location, optional work center
  • Corrective: an existing failure. These requests feed MTBF, MTTR, latest failure, and estimated next failure once the stage is done.
  • Request Maintenance on a Shop Floor work-order card creates a request for that work center.

What Odoo Maintenance does

Odoo describes Maintenance as the app for preventive and corrective maintenance. It computes mean time between failure (MTBF), mean time to repair (MTTR), and an expected next failure date. Odoo 19 user documentation places the app under Supply Chain and says it tracks maintenance requirements to extend equipment effectiveness.

A request is either corrective, to fix an existing issue, or preventive, to prevent future issues. It can point at a piece of equipment or at a work center. It can also link to a manufacturing order and, once that order is set, to a work order. The same database is where Manufacturing records overall equipment effectiveness, so a blocked work center can show up as equipment-failure downtime.

The maintenance models for Odoo 19.0 live in the public Community repository under addons/maintenance. They are not an Enterprise-only add-on in that repository. Shop Floor requests and work-center leaves sit with Manufacturing, so confirm the Manufacturing edition on your database when you scope the rollout.

The marketing page says the dashboard uses automatically computed statistics including MTBF and MTBR. The 19.0 documentation and the application source use MTTR for the repair average. Read MTTR on the equipment form, and treat the MTBR label on that one marketing section as a wording slip.

Equipment records, categories, and the date MTBF uses

Equipment records store category, company, who uses the asset, the maintenance team, the technician, a free-text used-in location, and an optional work center. Used by can be a department, an employee, or both. Product fields cover vendor, vendor reference, model, serial number, effective date, cost, and warranty expiration date.

Serial number is unique across equipment. The 19.0 model constraint rejects a serial number that another asset already uses. Set the effective date when you create the record: the MTBF formula starts from that date. Computed MTBF, estimated next failure, latest failure, and MTTR stay read-only. Expected MTBF, in days, is the only maintenance metric you can edit.

Categories group assets such as machinery or tools. A category can carry an email alias. Maintenance teams have members, shown as technicians on the calendar, an optional company, and an email alias whose incoming mail creates a maintenance request for that team.

Creating a request for equipment requires Equipment Manager access on the Maintenance app (Settings, user, Access Rights, Supply Chain, Maintenance) or being a follower of that equipment. Followers can open work on the assets they watch. Managers can work across the registry.

  • Category, company, used by (department, employee, or both), team, technician, used-in location, optional work center
  • Vendor, vendor reference, model, unique serial number, effective date, cost, warranty expiration date
  • Expected MTBF in days is editable; MTBF, MTTR, latest failure, and estimated next failure are read-only
  • Team and category email aliases can open a request from incoming mail
Where equipment and teams are configured
ObjectWhat it holdsWhere you maintain it
EquipmentThe machine or tool, its product fields, and its read-only reliability figuresMaintenance app, Equipment, Machines and Tools
Equipment categoryA grouping, and an optional email alias that can create requestsMaintenance app, Configuration, Equipment Categories
Maintenance teamMembers (technicians on the calendar), optional company, and an email aliasMaintenance app, Configuration, Maintenance Teams
Work centerAn Equipment tab listing technician, category, MTBF, MTTR, and estimated next failureWork center form, Equipment tab

Corrective and preventive requests, including repeat rules

Corrective maintenance fixes an issue that already exists. Preventive maintenance is scheduled to prevent future issues. Both types use the same teams, kanban, and calendar. Only the preventive type can be recurrent. A corrective request cannot repeat.

When a recurrent preventive request moves to a done stage, Odoo copies it forward by the repeat interval. The interval is days, weeks, months, or years, and the default is 1 week. The copy is created if the repeat is forever, or if the next date falls on or before the end date.

User documentation for 19.0 describes the request types and the calendar, and it does not spell out those repeat fields. The fields are in the 19.0 application source. Set the interval on the preventive request before the first close, because the next copy is made at the moment the current request hits a done stage.

The 19.0 maintenance model does not include a meter or runtime field that opens a request. Time-based preventive copies are the native schedule. The app page mentions automating metrology; that behavior is not in the 19.0 maintenance docs or in maintenance.py, so do not plan meter-based jobs on the standard request form.

  • Corrective: an existing failure. These requests feed MTBF, MTTR, latest failure, and estimated next failure once the stage is done.
  • Preventive: work aimed at future issues. It can repeat. Closed preventive requests stay out of the MTBF and MTTR averages.
  • Repeat units are days, weeks, months, or years. The default interval is 1 week.
  • A done stage triggers the next copy when the repeat is forever or the next date is still inside the end date.
How the two request types behave in Odoo 19.0
TypePurposeCan it repeat?Does a done request change MTBF and MTTR?
CorrectiveFix an existing issue on equipment or a work centerNoYes, if the stage is done
PreventivePrevent a future issueYes: days, weeks, months, or years (default 1 week)No

Requests, stages, priority, and who can open them

Request Date defaults to the creation date, and the 19.0 docs say the user cannot change it. Scheduled Date is a separate planned start. Duration is entered as hours. Priority is 0 to 3 stars. In the source the labels are Very Low, Low, Normal, and High, and a higher priority sorts above a lower one on the kanban.

Default stages shipped in Odoo 19.0 data are New Request, In Progress, Repaired, and Scrap. Repaired and Scrap are marked done and folded. The data file is noupdate, so a database that already changed its stages keeps those names. Completed work should move to Repaired, and work that cannot be repaired should move to Scrap. Any stage flagged done is what the metric and recurrence logic looks at, so a renamed stage still counts once that flag is set.

Instructions on a request can be a PDF upload, a public Google Slides URL, or text. Put the symptom and the production context in the notes, and put the job method in instructions, so the next technician is not rebuilding the procedure from memory.

For a work-center request, Block Workcenter stops work orders and other maintenance from being scheduled on that work center while the request is processed. Stage setup has a second switch: Request Confirmed. If it is ticked and the request is for a work center, the work center is blocked for the listed duration at the specified date, or as soon as possible if the work center is unavailable. If Request Confirmed is clear, Odoo creates no work-center leave.

  1. Open the request with the right access

    Use Equipment Manager rights, or be a follower of that equipment. Choose Equipment or Work Center, set Corrective or Preventive, and assign the team and technician. Link the manufacturing order when the failure happened on a job, then the work order if you need it.

  2. Set dates, duration, and priority

    Leave Request Date as the creation date. Set Scheduled Date for the planned start, Duration in hours, and priority from Very Low through High. Attach a PDF, a public Google Slides URL, or text instructions.

  3. Decide whether the work center stops

    On a work-center request, tick Block Workcenter when the machine cannot take other work. On the stage, tick Request Confirmed if this stage should create the work-center leave for the duration. Leave it clear when the request is only a record and production should keep running.

  4. Close on a done stage

    Move finished repairs to Repaired and equipment you will not restore to Scrap, or to your own stage if it is marked done. That close date drives MTTR in whole days. A preventive request with a repeat rule copies itself forward at this step.

Worked example: MTBF, MTTR, and the next failure date

The assumptions are a single press with effective date 1 January 2026, and three corrective requests whose stages are done. A monthly preventive lubrication request closed in the same year is ignored by the formulas. Dates below are request date and close date. MTTR uses whole days between those two dates, so a same-day close counts as 0 days.

Failure one: request 1 March 2026, closed 3 March 2026, which is 2 days. Failure two: request 1 June 2026, closed 1 June 2026, which is 0 days. Failure three: request 1 September 2026, closed 4 September 2026, which is 3 days. Latest failure is the latest request date, 1 September 2026, not the close date.

MTBF is the days from the effective date to the latest failure, divided by the count of those requests. From 1 January 2026 to 1 September 2026 is 243 days. Divided by 3, MTBF is 81 days. MTTR is the average of 2, 0, and 3 days, which is 5 divided by 3, or 1.67 days if you round to two decimals. Estimated next failure is 1 September 2026 plus 81 days, which is 21 November 2026.

If a planner types 45 into Expected MTBF, the estimated next failure stays 21 November 2026. Expected MTBF is stored for the team to compare against the computed figure. It is not an input to the date. Same-day repairs pull MTTR down, including toward zero, because the average uses whole days and drops the hours.

Press example under the Odoo 19.0 formulas (effective date 1 January 2026)
FieldResult in this exampleRule that produced it
Latest failure1 September 2026Latest request date among corrective requests in a done stage
MTBF81 days243 days from the effective date to 1 September 2026, divided by 3 requests
MTTR1.67 daysAverage of 2, 0, and 3 whole days between request date and close date
Estimated next failure21 November 2026Latest failure plus computed MTBF (81 days)
Expected MTBFWhatever you type, in daysEditable target. It does not change the 21 November date

Walk through a same-day repair on a discovery call

In the press example, the 1 June 2026 repair closed the same day and added 0 days to MTTR. Typing 45 into Expected MTBF left the estimated next failure on 21 November 2026. If your plant closes repairs on the day they open, the average will look shorter than the hours stored on Duration.

[[embed {"type":"booking","title":"See how whole-day MTTR would read on your equipment","body":"A free 30-minute discovery call on the request-date MTBF and the whole-day MTTR, including same-day repairs that add zero. Expected MTBF stays a target and does not move the next-failure date.","points":["Which request dates and close dates your recent repairs would feed","How a same-day close changes the MTTR average","What to bring: effective dates and a sample of closed corrective requests"],"cta":"Book a free discovery call"}]]

Calendar views and how MTBF and MTTR are calculated

In Odoo 19.0 source, MTBF, MTTR, latest failure, and estimated next failure use only corrective requests whose stage is done. MTTR is the average of whole days between request date and close date. Latest failure is the latest of those request dates. MTBF is the latest failure date minus the effective date, in days, divided by the count of those requests. Estimated next failure is the latest failure date plus that MTBF.

A repair opened and closed on the same calendar day adds a zero to the MTTR average. Hours on the duration field do not enter that average. Preventive closes do not enter it either. The effective date is the start of every MTBF day count, so set it to the day the asset entered service before you compare machines.

The maintenance calendar defaults to week view with To Do and Active filters. It also offers kanban, list, pivot, graph, and activity views. Pivot measures named in the docs include Count, Additional Leaves to Plan Ahead, Duration, and Repeat Every. Use Repeat Every to see which preventive requests are set to copy forward, and Duration when you want the hours people typed, which is a different number from MTTR.

Odoo's app page says the product computes MTBF, MTTR, and an expected next failure date, and one dashboard section says MTBF and MTBR. The figure on the equipment record for repair time is MTTR, which is also the name in the application source. Compare your typed Expected MTBF with the computed MTBF when you decide whether to shorten the preventive interval.

Equipment metrics in Odoo 19.0
MetricWho edits itWhat it uses
Expected MTBFUser, in daysA target only. Excluded from estimated next failure
MTBFRead-only(Latest corrective request date on a done stage, minus effective date) in days, divided by the count of those requests
Latest failureRead-onlyLatest request date among those corrective done requests
Estimated next failureRead-onlyLatest failure date plus computed MTBF
MTTRRead-onlyAverage of whole days between request date and close date on those same requests. Same-day close is 0

Work centers, Shop Floor, and equipment-failure downtime

A work center's Equipment tab lists each machine or tool with technician, category, MTBF, MTTR, and estimated next failure. That is the list production sees beside the machine. New equipment can be added from that tab, and it still needs an effective date if you want a usable MTBF.

On Shop Floor, a work-order card menu includes Request Maintenance, which creates a maintenance request for the work center. The same menu includes Block, which stops the current operation and blocks later work orders until someone unblocks them. Use Request Maintenance when a technician should own the job in the Maintenance app. Use Block when the immediate need is to stop the schedule.

Manufacturing OEE treats equipment failure as time a work center is unusable because equipment broke down or was shut for scheduled maintenance. Docs say the work center can be blocked with a maintenance request, and that time counts as equipment-failure downtime. The other OEE loss buckets are reduced speed and material availability. A blocked interval therefore lands in the failure bucket even when the reason was a planned shutdown, as long as the block came through a maintenance request.

The 19.0 maintenance docs and the maintenance model do not show a request consuming spare parts from Inventory or creating a stock move. Keep spare quantities on product records in Inventory if you stock them. Quality and PLM are separate apps that the Maintenance features page links to; a maintenance request does not, by itself, open a quality alert or a product change.

  • Request Maintenance on a Shop Floor work-order card creates a request for that work center.
  • Block on that card stops the current operation and holds later work orders until the block is lifted.
  • Request Confirmed on a work-center request's stage creates the leave for the listed duration. If it is clear, Odoo creates no leave.
  • Block Workcenter separately stops scheduling of work orders and other maintenance on that work center while the request is processed.
  • Time blocked by a maintenance request counts as equipment-failure downtime on the Manufacturing OEE report.

When the built-in app covers the plant, and when a CMMS still comes up

Odoo does not sell Maintenance as its own priced CMMS module. It is an app in the ERP database: equipment, teams, corrective and preventive requests, a calendar, email aliases, and the MTBF, MTTR, and next-failure figures above. For a plant that already runs Odoo Manufacturing, the work-center block and the OEE equipment-failure bucket are the practical reason to start here.

A separate CMMS is a different system of record. Choose it when the program depends on meter or runtime triggers, or on issuing spare parts as stock moves from the maintenance work order. Neither of those behaviors is in the 19.0 maintenance model. Companies of 20 to 100 people often outgrow the app when the crew works across many customer sites with their own service agreements, which is a field-service problem more than a work-center problem.

A workable sequence is to run Maintenance for two quarters, with effective dates filled in and corrective work closed on done stages, then read computed MTBF against the Expected MTBF you typed. If the gap is mostly late preventive copies or slow closes, fix the interval and the instructions inside Odoo. If the gap is missing meter triggers or parts issues, that is the point to price a specialist CMMS and the integration it will need.

Maintenance can be the single app on One App Free. The moment the database also needs Manufacturing, Inventory, or Quality, the subscription moves to a paid user plan. That jump is often larger than the maintenance screens themselves, so price the apps you will run, not the Maintenance menu on its own.

Decision signals for a 20 to 100 person manufacturer
What you needOdoo Maintenance in 19.0Look at a separate CMMS
Corrective and preventive work orders on plant equipmentRequest types, teams, kanban, calendarYou already standardized on another work-order tool
A repeating preventive jobPreventive only, copied when the request hits a done stageThe trigger must be a meter or runtime reading
Stop a work center and see it on OEEBlock Workcenter, Request Confirmed, Shop Floor Block, equipment-failure downtimeDowntime must post in a system outside this ERP
Spare parts on the work orderNot shown as an Inventory stock move from the requestThe work order has to issue and relieve stock
Reliability datesWhole-day MTBF and MTTR from closed corrective requestsYou need hour-level MTTR or a formula you define yourself

The Dynamics 365 counterparts for plant assets and field service

Flectic configures both Odoo and Dynamics 365 for companies in the US and Canada. Plant work centers and customer-site equipment land in different Microsoft apps.

Dynamics 365 Asset Management is a module in Dynamics 365 Supply Chain Management for assets and maintenance jobs, including machines, production equipment, and vehicles. Maintenance plans handle preventive work on individual assets. Maintenance rounds handle preventive work on a group of assets or a functional location. Both generate preventive work orders through the maintenance schedule. Those work orders are the closest match to an Odoo maintenance request for in-plant equipment.

Dynamics 365 Field Service is the app for installations, repairs, and preventive maintenance at customer sites. Agreements are the contracts that auto-generate recurring work orders and invoices on a schedule, which is the usual way teams run preventive visits. A field-service work order holds what work needs to be done. When the pain is a customer-site schedule, Field Service is the Microsoft app to evaluate. When the pain is a blocked work center and an OEE failure bucket, Odoo Maintenance or Asset Management is the closer fit.

The scoping call compares where the equipment lives, who closes the work order, and which database already holds inventory and production. License counts come after that choice.

Where the same job sits in each product
JobOdoo MaintenanceDynamics 365
In-plant equipment and work centersEquipment, work center, maintenance requestAsset Management in Supply Chain Management
Customer-site serviceOutside this app's plant focusField Service work orders
Repeating preventive workPreventive request copied on a done stageMaintenance plans and rounds, or Field Service agreements
Breakdown repairCorrective requestReactive maintenance and work orders

What Odoo Maintenance costs as of October 2026

There is no Maintenance SKU. You pay for the user plan that includes the app. As of October 2026, One App Free is US$0 for one app and unlimited users on Odoo Online. If the app you pick depends on other apps, those required apps are included. Installing any further app moves the database to Standard. Installing Studio, or adding companies, moves it to Custom.

The Standard figures shown together on the pricing page are US$24.90, US$31.10, and US$38.90 per user per month. The Custom figures shown together are US$49.00, US$61.10, US$61.00, and US$76.20 per user per month. The page has Yearly and Monthly toggles, and a footnote says the discount is valid for 12 months for the initial users ordered. The extracted page text does not label which of those amounts is the discounted yearly rate and which is monthly billing, so match the toggle on the live page before you sign.

Custom includes all apps, Odoo Online, Odoo.sh or on-premise (Odoo.sh hosting is extra), Studio, multi-company, an external API, and the agentic AI item Odoo lists on that plan. A light user is listed at US$8.90. Odoo says the light-user quote is custom and requires an advisor meeting. Published light-user capabilities include Manufacturing Shop floor for employee records and do not list the Maintenance app.

Those amounts are US dollars. As of 5 October 2026, the US, en_CA, and fr_CA pricing pages showed the same US dollar figures, and no separate CAD list price was verified. Subscription prices exclude implementation and maintenance of custom code. Success Packs are the published hour bundles, not a fixed Maintenance implementation price.

Odoo list prices that can cover Maintenance, as of October 2026 (USD)
PlanAmount on the pricing pageWhat you are buying
One App FreeUS$0One app, unlimited users, Odoo Online. Required dependency apps included. Extra apps move you to Standard.
StandardUS$24.90, US$31.10, and US$38.90 per user per month, shown togetherPaid user plan once you install more than the free app. Yearly and Monthly toggles; 12-month discount footnote for initial users.
CustomUS$49.00, US$61.10, US$61.00, and US$76.20 per user per month, shown togetherAll apps, Online, Odoo.sh or on-premise (Odoo.sh hosting extra), Studio, multi-company, external API.
Light userUS$8.90 per light userQuote after an advisor meeting. Published capabilities include Shop floor for employee records and leave out Maintenance.

Success Pack hours versus a first usable phase

Odoo says companies under 50 employees usually buy Success Packs directly, companies over 50 employees usually use a partner, and companies over 250 employees should contact Odoo. The Success Pack page lists Manufacturing scope as MRP, PLM, Quality, and Maintenance. Pack prices are hours with a dedicated consultant. They are not a fixed quote for a Maintenance-only project. Travel time and expenses are extra, and Odoo adds monthly charges for maintenance of extra modules or lines of code.

As of October 2026, the new-customer prices already include 15 percent off the first pack: Starter US$493 for 4 hours, Basic US$3,060 for 25 hours, Standard US$5,950 for 50 hours, Custom US$10,625 for 100 hours, and Pro US$21,250 for 200 hours. Returning-customer prices for the same hour bundles are US$580, US$3,600, US$7,000, US$12,500, and US$25,000.

For a company of 20 to 100 people, Flectic sets the timeline for a first phase in the written scope, with a fixed price. That phase is equipment, categories, teams, preventive repeats, stage flags, and the work-center block path, on the subscription you already chose. Engagements are designed to deliver up to 3x faster than a traditional standalone implementation. The free discovery call is where the hour count gets tied to your asset list, not to a generic pack name.

Odoo does not publish what a 25-hour Basic pack includes for Maintenance. Price data cleanup before you choose a pack.

Odoo Success Pack prices as of October 2026 (USD)
PackHoursNew customerReturning customer
Starter4US$493US$580
Basic25US$3,060US$3,600
Standard50US$5,950US$7,000
Custom100US$10,625US$12,500
Pro200US$21,250US$25,000

Price the user plan and the hour bundle on a call

The Standard figures (US$24.90, US$31.10, and US$38.90 per user per month) and the Custom figures (US$49.00, US$61.10, US$61.00, and US$76.20) sit on the subscription. The Success Pack table above is a separate hour bundle, and the new-customer amounts already include 15 percent off the first pack. Odoo does not publish a Maintenance project price that combines the two.

Book a free discovery call to set those amounts against your equipment count and whether Manufacturing is already installed. The call covers the user plan, the hour bundle, and the data cleanup you should price before you pick a pack.

[[embed {"type":"booking","title":"Price the user plan and the hour pack together","body":"A free 30-minute discovery call to match Standard or Custom user pricing, and a Success Pack hour bundle, to your equipment list. As of October 2026 those list prices are in US dollars.","points":["Whether One App Free still fits once Manufacturing is installed","Which Success Pack hour count to budget after you price data cleanup","How the first-phase timeline and fixed price map to that scope"],"cta":"Book a free discovery call"}]]

How Flectic sequences an Odoo Maintenance rollout

Flectic is an independent ERP and CRM consultancy for companies of 20 to 100 people in the US and Canada. A Maintenance rollout is designed to deliver up to 3x faster than a traditional standalone implementation.

The first weeks are the registry: categories, teams, email aliases, unique serials, effective dates, and Expected MTBF as a target the team agrees on. Then come preventive requests with an explicit repeat interval, stage flags so Repaired and Scrap (or your equivalents) count as done, and a written rule for when Block Workcenter and Request Confirmed are ticked.

Shop Floor comes after the request path is stable. Operators need Request Maintenance and Block to land on the right work center, and finance or production needs to know that blocked time counts as equipment-failure downtime on OEE. We read the first closed corrective requests with the whole-day formulas before changing intervals.

If the same company also services customer equipment, the scoping call separates plant work centers (Odoo Maintenance or Dynamics 365 Asset Management) from field visits (Dynamics 365 Field Service). The next step is that call, with your equipment count and whether Manufacturing is already on the database.

  1. Confirm the subscription

    If Maintenance is the only app, One App Free at US$0 is enough. If Manufacturing, Inventory, or Quality must be installed, budget Standard or Custom per user and check the live yearly or monthly toggle.

  2. Load equipment with the dates the formula needs

    Category, team, technician, unique serial, cost, warranty, work center, and effective date. Expected MTBF is optional and does not drive the next-failure date.

  3. Set preventive copies and done stages

    Repeat on preventive requests only. Default interval is 1 week if you leave it. Mark the closing stages done so metrics and the next copy both run.

  4. Connect the work center

    Agree when to block, train Shop Floor on Request Maintenance and Block, and check one closed request against the OEE equipment-failure bucket.

How Flectic can help

Flectic implements Odoo one app at a time on a single database, starting with the apps that remove the most manual work. Our Odoo implementation fits companies of 20 to 100 people in the US and Canada that want sales, stock and finance in one Odoo database at a lower license cost. Across the Core and Growth Odoo industry packages, proposed timelines run from 8 to 28 weeks. To start, book a free discovery call with Flectic.

Sources

  1. Odoo describes Maintenance as the app for preventive and corrective maintenance, and says it computes MTBF, MTTR, and an expected next failure date.

    odoo.comChecked 2026-10
  2. The same marketing page also says the dashboard uses automatically computed statistics including MTBF and MTBR. The 19.0 docs and application source use MTTR, not MTBR.

    odoo.comChecked 2026-10
  3. Odoo 19 user documentation places Maintenance under Supply Chain and says it tracks maintenance requirements to extend equipment effectiveness.

    odoo.comChecked 2026-10
  4. A maintenance request is either Corrective or Preventive, can be for Equipment or a Work Center, and can be linked to a manufacturing order and, if an MO is set, to a work order.

    odoo.comChecked 2026-10
  5. Request Date defaults to the creation date and the user cannot change it. Scheduled Date is a separate planned start. Duration is entered as hours.

    odoo.comChecked 2026-10
  6. If the request is for a work center, Block Workcenter stops work orders and other maintenance from being scheduled on that work center while the request is processed.

    odoo.comChecked 2026-10
  7. Docs say completed work should move to Repaired, and work that cannot be repaired should move to Scrap. Instructions can be a PDF upload, a public Google Slides URL, or text.

    odoo.comChecked 2026-10
  8. Creating a request for equipment requires Equipment Manager access on the Maintenance app or being a follower of that equipment.

    odoo.comChecked 2026-10
  9. Default stages shipped in Odoo 19.0 data are New Request, In Progress, Repaired, and Scrap. Repaired and Scrap are marked done and folded. The data file is noupdate.

    github.comChecked 2026-10
  10. Priority is 0 to 3 stars. Source labels are Very Low, Low, Normal, and High. Higher priority sorts above lower priority on the kanban. Serial number is unique across equipment.

    github.comChecked 2026-10
  11. MTBF, MTTR, latest failure, and estimated next failure use only corrective requests whose stage is done. MTTR is the average of whole days between request date and close date. Latest failure is the latest of those request dates. MTBF is (latest failure date minus effective date) in days, divided by the count of those requests. Estimated next failure is latest failure date plus that MTBF. Expected MTBF is not used in that calculation.

    github.comChecked 2026-10
  12. Preventive requests can be recurrent. Corrective requests cannot. When a recurrent preventive request moves to a done stage, Odoo copies it forward by the repeat interval (days, weeks, months, or years; default 1 week) if the repeat is forever or the next date is on or before the end date.

    github.comChecked 2026-10
  13. Maintenance teams have members, an optional company, and an email alias whose incoming mail creates a maintenance request. Equipment categories can also have an email alias. The Maintenance application code is in the public Community repository at addons/maintenance.

    github.comChecked 2026-10
  14. Equipment records store category, company, used-by (department, employee, or both), maintenance team, technician, a free-text used-in location, optional work center, vendor, vendor reference, model, serial number, effective date, cost, and warranty expiration date.

    odoo.comChecked 2026-10
  15. Expected MTBF is the only maintenance metric the user can edit, in days. Computed MTBF, Estimated Next Failure, Latest Failure, and MTTR are read-only. A work center Equipment tab lists technician, category, MTBF, MTTR, and estimated next failure.

    odoo.comChecked 2026-10
  16. The maintenance calendar defaults to week view with To Do and Active filters, and also offers kanban, list, pivot, graph, and activity views. Pivot measures include Count, Additional Leaves to Plan Ahead, Duration, and Repeat Every. Request Confirmed on a stage controls whether a work-center leave is created.

    odoo.comChecked 2026-10
  17. On Shop Floor, Request Maintenance creates a maintenance request for the work center, and Block stops the current operation and blocks later work orders until unblocked.

    odoo.comChecked 2026-10
  18. Manufacturing OEE treats equipment failure as time a work center is unusable because equipment broke down or was shut for scheduled maintenance. Blocking with a maintenance request counts as equipment-failure downtime. Other loss buckets are reduced speed and material availability.

    odoo.comChecked 2026-10
  19. One App Free is one app, unlimited users, on Odoo Online, at US$0. Required apps for that app are included. Extra apps move the database to Standard. Studio or extra companies move it to Custom. Standard amounts shown together are US$24.90, US$31.10, and US$38.90 per user per month. Custom amounts shown together are US$49.00, US$61.10, US$61.00, and US$76.20. Light user is US$8.90 and the published capability list does not include Maintenance. Subscriptions exclude implementation and custom-code maintenance.

    odoo.comChecked 2026-10
  20. Companies under 50 employees usually buy Success Packs directly, companies over 50 usually use a partner, and companies over 250 should contact Odoo. Manufacturing scope lists MRP, PLM, Quality, and Maintenance. New-customer pack prices already include 15 percent off the first pack: Starter 493, Basic 3,060, Standard 5,950, Custom 10,625, Pro 21,250 USD for 4, 25, 50, 100, or 200 hours. Returning prices are 580, 3,600, 7,000, 12,500, and 25,000. Travel is extra. Extra monthly charges apply for maintenance of extra modules or lines of code.

    odoo.comChecked 2026-10
  21. Dynamics 365 Asset Management manages assets and maintenance jobs in Supply Chain Management, including machines, production equipment, and vehicles.

    learn.microsoft.comChecked verified
  22. In Dynamics 365 Asset Management, maintenance plans cover preventive maintenance on individual assets, and maintenance rounds cover a group or functional location. Both generate preventive work orders through the maintenance schedule.

    learn.microsoft.comChecked verified
  23. In Dynamics 365 Field Service, agreements auto-generate recurring work orders and invoices on a schedule, commonly used for preventive maintenance.

    learn.microsoft.comChecked verified
  24. In Dynamics 365 Field Service, a work order records the work to be done, including installations, repairs, and preventive maintenance.

    learn.microsoft.comChecked verified

Frequently asked questions

Where can I get implementation services, and how much does it cost?

Odoo sells implementation time as Success Packs. As of October 2026, the new-customer prices already include 15 percent off the first pack: US$493 for 4 hours, US$3,060 for 25, US$5,950 for 50, US$10,625 for 100, and US$21,250 for 200. Returning-customer prices for the same hour bundles are US$580, US$3,600, US$7,000, US$12,500, and US$25,000. The Manufacturing scope on that page includes MRP, PLM, Quality, and Maintenance, and the price is an hour bundle, not a fixed Maintenance project. On a free discovery call Flectic scopes a first phase for US and Canadian companies of 20 to 100 people, and the written proposal sets its timeline and a fixed price.

What is included in the subscription?

Maintenance has no separate module price. One App Free is US$0 for one app and unlimited users on Odoo Online, including apps that the chosen app depends on. Standard and Custom are per-user plans; as of October 2026 the page shows US$24.90, US$31.10, and US$38.90 together for Standard, and US$49.00, US$61.10, US$61.00, and US$76.20 together for Custom. The subscription excludes implementation and maintenance of custom code, which sit on Success Packs and on extra monthly charges for custom modules.

How do you define a paying user?

Standard and Custom are charged per user per month. As of October 2026 the pricing page shows three Standard amounts and four Custom amounts on the page at once, with Yearly and Monthly toggles and a 12-month discount for the initial users ordered. A light user is a separate quoted role at US$8.90 and is not the same as that full user. The page does not add a further written test, beyond the plan you buy, for who counts as a paying user.

What is a Light User?

Odoo lists a light user at US$8.90, and says the quote is custom and requires an advisor meeting. Published light-user capabilities include Manufacturing Shop floor for employee records. That published list does not include the Maintenance app. A person who must create or close maintenance requests should be counted as a full user until an advisor confirms a light-user seat will open the app.

Why do I have multiple apps with the One App Free plan?

One App Free is one chosen app at US$0 with unlimited users on Odoo Online. If that app depends on other apps, Odoo includes those required apps. You still have a single chosen app, plus its dependencies. Installing any app beyond that set moves the database to Standard, and installing Studio or adding companies moves it to Custom.

How do I add equipment and which date is used to compute MTBF?

Add the asset under Maintenance, Equipment, Machines and Tools. Record category, company, used by, team, technician, location, optional work center, vendor, model, a unique serial number, cost, and warranty expiration. The effective date is the start of the MTBF formula. MTBF equals the days from that date to the latest corrective request date on a done stage, divided by how many of those requests exist.

How is estimated next failure calculated, and can I type it in?

You cannot type estimated next failure. It is read-only. Odoo sets it to the latest corrective request date on a done stage, plus the computed MTBF. Expected MTBF is the only metric you can edit, and only in days. The 19.0 calculation does not use Expected MTBF for that date. Computed MTBF, latest failure, and MTTR are read-only as well.

How do I block a work center during maintenance?

On a request for a work center, Block Workcenter stops work orders and other maintenance from being scheduled there while the request is processed. On the kanban stage, Request Confirmed must be ticked or Odoo creates no work-center leave. When it is ticked, the work center is blocked for the listed duration at the specified date, or as soon as possible if the work center is unavailable. Shop Floor also has Block on the work-order card, which stops the current operation and blocks later work orders until someone clears it.

How does a shop-floor operator request maintenance?

On Shop Floor, the work-order card menu includes Request Maintenance. That action creates a maintenance request for the work center. The same menu includes Block, which stops the current operation and holds later work orders. From the Maintenance app, a request can also be linked to a manufacturing order and, when that order is set, to a work order.

What is the difference between corrective and preventive maintenance requests?

A corrective request fixes an existing issue. A preventive request is meant to prevent future issues. Only preventive requests can repeat. When a repeating preventive request moves to a done stage, Odoo copies it forward by the interval (days, weeks, months, or years, default 1 week) if the repeat is forever or the next date is on or before the end date. Closed corrective requests are the only ones that enter MTBF and MTTR.

More on the blog: Choosing an ERP or CRM