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

Is Odoo manufacturing a fit for your shop

Odoo fits a discrete manufacturer of about 20 to 100 people that wants orders, stock, purchasing, and cost in one system.

FlecticUpdated 29 min read

Odoo fits a discrete manufacturer of about 20 to 100 people that wants orders, stock, purchasing, and cost in one system. It is a poor stand-in for a dedicated manufacturing execution system when the shop needs machine signals, tight PLC control, or regulated electronic records. Odoo 19 Manufacturing covers multi-level bills of materials, work centers, routings, subcontracting, and order cost. Shop Floor, Quality, and PLM are separate apps, and those folders are absent from the public Community 19.0 tree. As of October 2026, Odoo pricing lists Custom at USD 49.00, USD 61.00, and USD 76.20 per user per month, with a 12-month discount on initial users.

A shop-floor light user is listed at USD 8.90 on that same page and is sold only after an advisor review. The rest of this page is the test we use with operations leads: which apps your routings, holds, lots, and revisions require, what Community already contains, what the software line costs under stated assumptions, and when Business Central Premium is the cleaner buy.

What each Odoo app does on a production order

Odoo describes Manufacturing as the app that schedules, plans, and processes manufacturing orders, with a work-center control panel so a shop-floor tablet can process work orders and trigger maintenance, feedback, and quality issues. The version 19 documentation index behind that sentence is wide. It covers one-step, two-step, and three-step manufacturing, bills of materials including multi-level bills and kits, work centers, work-order dependencies, a master production schedule, scrap, backorders, split and merge, unbuild, by-products, dismantle, lots and serials, Shop Floor, subcontracting, and reports for delays, allocation, overall equipment effectiveness, and production analysis.

That index is a suite, and the apps are installed separately. For a discrete shop, this is the map that matters.

  • Manufacturing (Job on a discrete order: Orders, multi-level bills, kits, work centers, routings, subcontracting, master production schedule, order cost, OEE · What we can confirm as of October 2026: Public Community 19.0 module, summary Manufacturing Orders & BOMs, views for work orders, work centers, bills, routing, and unbuild)
  • Inventory (Job on a discrete order: Components, lots, serials, replenishment · What we can confirm as of October 2026: Manufacturing depends on product, stock, and resource)
  • Purchase (Job on a discrete order: Component buys, including buys that follow a shortage · What we can confirm as of October 2026: Named as its own row on the editions page)
  • Maintenance (Job on a discrete order: Equipment tracking and maintenance requests · What we can confirm as of October 2026: Public Community 19.0 module, depends on mail, not on Manufacturing)
  • Shop Floor (Job on a discrete order: Tablet cards for the order and the operation, operator sign-in, time on the step · What we can confirm as of October 2026: Documented as a companion to Manufacturing. The mrp_workorder folder is not in the public Community 19.0 tree)
  • Quality (Job on a discrete order: Control points, alerts, checks, failure locations · What we can confirm as of October 2026: Separate app. The quality folder is not in that Community tree)
  • PLM (Job on a discrete order: Engineering change orders, stages, version control, approvals · What we can confirm as of October 2026: Separate install. The mrp_plm folder is not in that Community tree)
  • Barcode (Job on a discrete order: Named as a child of Inventory on the editions page · What we can confirm as of October 2026: Confirm the scan on your devices in the edition you buy)

The Community Manufacturing manifest is the anchor for the first row. It is licensed LGPL-3. The Maintenance manifest is also LGPL-3 in that tree. On 5 October 2026 the paths for quality, mrp_plm, and mrp_workorder returned 404 at ref 19.0 in the public repository, which is the mrp_workorder contents call. The editions comparison lists Manufacturing (MRP), then a child line for Shopfloor, Control Panel, Scheduling, plus separate rows for PLM, Purchase, Maintenance, and Quality, and a Barcode child under Inventory. It states that Community is open source and Enterprise is licensed. Treat the manifest and the 404s as the ceiling you can check yourself, and have the quote name the edition that contains Shop Floor, Quality, and PLM.

The manufacturing features page adds the commercial inventory around that core: manufacturing orders, work orders, barcode, repairs, unbuild, Kanban and Gantt planning, multi-level bills, kits, PLM and engineering change orders, quality checks and alerts, maintenance, work-center tablets, worksheets, traceability, cost analysis, and OEE. The manufacturing product page also lists finite-capacity scheduling, a Gantt, barcode, Shop Floor tablets, the master production schedule, by-products, lot and serial traceability, and IoT, with links out to Sales, Inventory, Project, PLM, and Maintenance. Use those pages as the demo script. Use the documentation below as the behavior you accept.

Bills, subcontracting, by-products, and lots

Bills do the quiet work. A kit is a bill with no production step, useful when you ship a bundle of stocked parts. A subcontracting bill is a different type. Subcontracting is a Manufacturing setting, and the docs describe three component flows: the subcontractor sources the parts, you resupply the subcontractor, or you dropship components to the subcontractor. Finished goods can come back to you or go to the customer. A contract manufacturer that already buys, ships, and receives this way can stay inside Manufacturing for that loop, provided the paperwork matches one of those three flows.

By-products are optional. After the setting is on, a bill can name the by-product, the quantity, and the operation that produces it. Completing the manufacturing order posts that by-product into stock. That is a discrete side-output, such as offcuts you put back on a shelf. Potency, catch weight, and a yield that moves with a recipe are a separate test: ask for that calculation on your own item before you treat the by-product tab as the process record.

Lots and serials are in the Manufacturing docs. For serial-tracked products, assigning serials to a multi-unit manufacturing order splits it into one manufacturing order per unit. A shop that serializes every finished unit will see order count rise with quantity. Plan the scanner path and the paperwork around that split, or you will think the scheduler duplicated demand.

Shop Floor, quality, maintenance, and engineering change

Shop Floor is documented as a companion module. It gives a visual interface for manufacturing orders and work orders, lets employees track time, can be installed as a Chrome app on a workstation so operators stay out of the other apps, and uses an operator panel for sign-in. From a work-order card the operator can register production or serials, scrap, modify the routing, add a component, open the manufacturing order, update instructions, create a quality alert, request maintenance, or block the operation so later work orders cannot start. Blocking the next step is the hold most small shops mean when they say the tablet has to stop the line.

Quality is a separate app. Documented check types are instructions, pass-fail, measure, and take a picture, plus control points, alerts, checks, and failure locations. A discrete assembler that needs a torque check or a photo at one operation can configure that without a second quality product. A plant that needs a validated electronic batch record should make the vendor show the signature path on a sample lot. The quality documentation describes instructions, pass-fail, measure, and picture checks.

PLM is not installed when Manufacturing is installed. It is the app for engineering change orders, stages, version control, and approvals. If the shop still builds last month's revision because someone emailed a PDF, PLM is the app that closes that gap, and it is a separate project from going live on bills and work orders. Our routing and work-center setup guide walks the master data those work orders depend on. Read it when you are ready to configure. The decision of whether the module is deep enough comes first.

How to judge whether Odoo MRP is deep enough

Score your own shop on seven tests. A dedicated manufacturing execution system still owns machine signals, tight PLC control, and regulated electronic records. Odoo earns the order when the seven tests below are satisfied by bills, work orders, tablet steps, and the sibling apps, on data from one of your products.

  1. Routings and work centers. You need a place to put each machine or bench, a rate, and a sequence of operations. Community Manufacturing already includes work-center, routing, and work-order views. Walk one product across the real benches and see whether every queue, cure, and inspect step has a home. If the routing omits a step, later capacity pictures invent time the floor does not have.
  2. Finite scheduling. The product page lists finite-capacity scheduling and a Gantt. The behavior to make them demonstrate is a shared machine with a queue: work-order dependencies in the Manufacturing docs, plus OEE once Work Orders are enabled. OEE is the share of a work center's active time that is fully productive, meaning it is processing work orders that have not exceeded expected duration. Documented loss buckets are reduced speed, material availability, and equipment failure. The master production schedule is a different tool. It suggests replenishment from a manual forecast and a safety-stock target. Adding a product does not create a purchase or a manufacturing order until someone orders it, unless replenishment is set to Automatic. Odoo says not to combine the master production schedule with reordering rules on the same product. If your planner needs both a forecast and a min-max rule on one part number, pick one method in the pilot or the suggestions will fight.
  3. Shop-floor capture. List what the operator must record without walking back to a desk: quantity, serial, scrap, a swapped component, a blocked step. The Shop Floor card covers that list. If the requirement is a cycle count from the machine PLC every few seconds, say so in the demo and watch whether it is a typed quantity instead.
  4. Quality holds. Name the operation where a failed check must stop downstream work. Shop Floor can raise a quality alert and block the operation. Quality supplies the check types. If your hold is a paper traveler that a supervisor initials, a pass-fail control point is enough. If the hold is a regulated disposition with named approvers and an immutable signature, ask to see that screen on your part.
  5. Traceability. Upstream lot and serial history is in the Manufacturing scope, and barcode is on the feature list. Run one recall question in the pilot: given a finished serial, which component lots were consumed. Remember the split rule. Serializing a quantity of ten creates ten manufacturing orders, so the trace report is only as good as the scans on each of those orders.
  6. Costing. Manufacturing-order cost starts as a bill estimate: component cost and quantity, plus operation time at the work-center rate and the employee hourly rate. Real cost uses actual quantities, actual durations, and each employee's own hourly cost. After the order is done, Odoo sets the manufacturing-order cost equal to the real cost and rolls completed orders into the product's average cost. A wrong work-center rate lands in every finished good that touched that center. Load rates from payroll and from the machine log before you trust margin.
  7. Engineering change. If two revisions of the same item can be open on the floor, you want PLM's change order, stages, and approvals, not a copied bill with a new description. PLM stays a separate install. Put one real ECO through it during evaluation, including the approval your engineer already requires.

If tests 1, 5, and 6 are the whole list, Manufacturing plus Inventory and Purchase is a fair first system, including on the public Community module for the MRP core. If tests 3 and 4 are in the list, budget the Shop Floor companion and Quality, and confirm the edition in writing. If test 7 is in the list, add PLM to that same confirmation. If the unanswered demand is machine signals, PLC control, or a regulated electronic record, keep Odoo in the running for orders, stock, and cost, and keep a dedicated execution system in the running for the machine layer. For how that scope is delivered on the shop floor, see our manufacturing work for discrete producers.

Where Community stops for a manufacturing shop

Community is a real MRP starting point, and it is a bad place to discover a missing quality or revision app after go-live. The public 19.0 tree contains Manufacturing, with work orders, work centers, bills, routing, and unbuild, and it contains Maintenance as equipment and requests that do not depend on Manufacturing. It does not contain the quality, mrp_plm, or mrp_workorder directories. Shop Floor's documented behavior, including the operator card and the block on later work orders, lives in documentation for a companion module whose folder is outside that tree. Quality's four check types and PLM's change orders are documented as separate apps with the same gap in the public Community source.

The practical reading for a 20 to 100 person discrete shop:

  • You can study bills, routings, work orders, and unbuild on Community, because those views ship in the Manufacturing module.
  • You can track equipment and maintenance requests on Community, because that module is in the same tree. A request fired from a Shop Floor card is a different install.
  • You should budget an edition that includes Shop Floor, Quality, and PLM if any of those tests above are mandatory, and you should see the module list on the quotation. The editions page names the rows. The quotation should list the modules you will receive.
  • Barcode appears as a child of Inventory on the editions page. Confirm scanning on your devices in the edition you will buy.

Two commercial facts sit beside that source gap. Subscription plans exclude implementation services, Odoo.sh hosting for custom developments, in-app credits, and maintenance of custom code. Odoo also says companies under 50 employees usually buy Success Packs from Odoo, companies above 50 employees usually use a partner, and companies above 250 employees should contact Odoo. A manufacturer in the 20 to 100 person band often lands on both sides of that 50-employee line, so ask which path your headcount takes before you compare a pack price with a services proposal.

Custom code is the other cliff. The flexibility that lets a developer change a routing screen is the same path that creates a module whose maintenance is excluded from the subscription and billed extra. Ask who will own that code, who may modify it, and what the monthly maintenance charge is, before the first sprint. Installing Odoo Studio, a second company, or an external API moves you to the Custom plan, which is also the plan that allows Odoo.sh or on-premise. A single-entity shop that can live on Odoo Online can stay on Standard and avoid that step.

What Odoo manufacturing costs as of October 2026

There is no separate manufacturing price. You pay for users, then you pay for services and, if you leave Odoo Online, for hosting. Figures below are the ones displayed on 5 October 2026. Standard shows USD 24.90, USD 31.10, and USD 38.90 per user per month on the pricing page. Custom shows USD 49.00, USD 61.00, and USD 76.20. The page has yearly and monthly toggles, and a footnote that the discount is valid for 12 months for the initial users ordered. Confirm on the quote which of the three figures is the rate you will be invoiced, and for how many months. The detail sits in our Odoo manufacturing pricing guide as well.

  • One App Free (Amount as of October 2026: USD 0 · What it buys: One app, unlimited users, Odoo Online. Dependencies of that first app stay free)
  • Standard (Amount as of October 2026: USD 24.90, USD 31.10, and USD 38.90 per user per month · What it buys: All apps, Odoo Online. Hosting described as free, storage up to 100 GB under the acceptable-use policy)
  • Custom (Amount as of October 2026: USD 49.00, USD 61.00, and USD 76.20 per user per month · What it buys: All apps, plus Studio, multi-company, external API, and the right to host on Odoo.sh or on-premise. The Odoo.sh fee is extra)
  • Light user (Amount as of October 2026: USD 8.90 · What it buys: Sold only after an advisor review. Listed capabilities include Manufacturing Shop Floor for an employee and Inventory Barcode Operator for a user)

One App Free is a real on-ramp for a shop that only wants to try Manufacturing. Because Manufacturing depends on product, stock, and resource, those dependencies stay inside the free-app rule. Quality, PLM, and Shop Floor are not dependencies on that manifest, so the free plan does not pull them in. The moment you need the wider suite, Standard includes all apps for one fee on Odoo Online. Custom is the plan when you need a second company, Studio, the external API, or hosting you run yourself.

A priced stack under stated assumptions

Assume 15 full users on Custom, 8 shop-floor people whom an advisor agrees to sell as light users, a company under 50 employees, one shared Odoo.sh worker, and no dedicated server. Annual software for the 15 full users is 15 times 12 times the displayed Custom rate: USD 8,820 at USD 49.00, USD 10,980 at USD 61.00, and USD 13,716 at USD 76.20. The pricing page lists a light user at USD 8.90 and does not state a billing period for that figure. An approved light-user charge is extra once the quote names the period. If the advisor refuses the light-user license, price those eight people as full users on the same Custom rate as the other fifteen.

Hosting, only because this assumption includes custom modules: Odoo.sh lists a worker at USD 57.60 per month on shared hosting, up to 8 workers, storage at USD 0.20 per GB per month up to 512 GB, a staging environment at USD 14.40 per month, and dedicated hosting at USD 480 per month. Hosting does not include the Enterprise license. One worker for a year is USD 691.20. Dedicated hosting would add USD 5,760 per year on top of workers and storage. This example uses the single worker only.

Services, because the company in the assumption is under 50 employees: Odoo points that band to Success Packs. New-customer prices on the Success Packs page, with 15 percent off the first pack, are USD 493 for 4 hours, USD 3,060 for 25 hours, USD 5,950 for 50 hours, USD 10,625 for 100 hours, and USD 21,250 for 200 hours. Returning prices are USD 580, USD 3,600, USD 7,000, USD 12,500, and USD 25,000. Onsite travel and expenses are extra. Extra monthly charges apply for maintenance of extra modules. The manufacturing row of Odoo's estimator is MRP, PLM, Quality, and Maintenance. Odoo says 80 percent of projects within that estimator scope are put in production in 200 hours or less, and that companies above 50 users should contact Odoo. Odoo also states a 98 percent implementation success rate with a Success Pack versus 65 percent without one, and labels that comparison as its own. Use the hour menu. Do not treat the percentages as an outside audit.

The middle Custom rate below is only a way to add the published lines. Your contract uses whichever of the three figures the quote names. USD 10,980 of full-user software, plus USD 691.20 of one Odoo.sh worker, plus the new-customer 100-hour pack at USD 10,625, adds to USD 22,296.20. Swap in the 200-hour pack at USD 21,250 and the same stack adds to USD 32,921.20. Use USD 8,820 or USD 13,716 in place of USD 10,980 if your quote lands on another displayed Custom figure, and the total moves by the same difference. None of these sums is a quote. They leave out the light-user charge, travel, storage, staging, dedicated hosting, custom-code maintenance, and any services above the pack. A company above 50 employees is in the band Odoo sends to a partner, so the pack menu is the wrong comparison for them. If your team is larger than the pack path, our ERP implementation services are scoped as a phase plan with hours you can see.

The same 15 full users on Standard, still on Odoo Online and still with no Odoo.sh line, would be 15 times 12 times the displayed Standard rate: USD 4,482 at USD 24.90, USD 5,598 at USD 31.10, or USD 7,002 at USD 38.90. An approved light-user charge is extra on this plan too, once the quote names the billing period. Standard is the plan to price first when you have one company, no Studio, and no custom modules. Custom is the plan this example used because the assumption included Odoo.sh.

When Business Central is the better manufacturing system

Choose Business Central when the company already runs on Microsoft 365 and wants US or Canadian localization in that same ledger, and when manufacturing is a known Premium capability with machine centers and a strict production-order status path. Choose Odoo when you want every app inside the user fee once you leave the free plan, and when a real by-product line on the bill matters more than machine centers.

As of October 2026, US Business Central pricing is Essentials at USD 80.00 per user per month paid yearly, Premium at USD 110.00, and Team Members at USD 8.00. Premium is Essentials plus service management and manufacturing. Canadian pricing is Essentials at CAD 108.50, Premium at CAD 149.20, and Team Members at CAD 10.90 per user per month paid yearly, plus applicable tax. Price Odoo from the US dollar figures above. Price a Canadian Business Central estate from the Canadian list on its own. The wider Canadian picture is in our note on ERP for Canadian manufacturers.

Microsoft Learn says the manufacturing features it describes are available only with the Premium experience. They use production bills of materials, routings, work centers, and machine centers. Production order statuses are Simulated, Planned, Firm Planned, Released, and Finished. Essentials at USD 80.00, or CAD 108.50, does not include that experience. A buyer who prices Essentials for a plant will understate the license.

Business Central does not have a dedicated by-product feature. Microsoft documents recording by-products as a negative consumption entry, which credits WIP. A finished production order can be reopened only once, and not if it has no output and cost was written off to an adjustment account. Odoo's by-product is a line on the bill that posts to stock when the order completes. If offcut or co-product inventory is a weekly argument in your plant, that difference is worth a side-by-side on one item. The fuller fork, including finance and inventory outside the plant, is in our Odoo vs Business Central comparison and in Business Central for manufacturing.

The same 15 users, Premium versus Custom

Assume the same 15 people each need a full user who can run manufacturing, and ignore Team Members for a moment. Business Central Premium is 15 times USD 110.00 times 12, which is USD 19,800 per year in the United States. In Canada it is 15 times CAD 149.20 times 12, which is CAD 26,856 per year before tax. Essentials for those same 15 people would be USD 14,400 or CAD 19,530 per year, and it would still leave manufacturing off the subscription.

Set that next to the Odoo Custom software line for 15 full users: USD 8,820, USD 10,980, or USD 13,716 per year depending on which displayed Custom rate the quote uses, before light users, hosting, and services. The Odoo Standard line for the same 15 users is USD 4,482, USD 5,598, or USD 7,002. Odoo's user fee, once you are off One App Free, includes the rest of the apps. Business Central manufacturing means the Premium experience. Essentials leaves that experience off the subscription. Team Members, at USD 8.00 or CAD 10.90, are limited to read, approve, and selected updates. Do not assume a machine operator fits that license. On the Odoo side, the shop-floor employee is the light-user case at USD 8.90, and only after the advisor review.

For one company, with no Studio and no custom modules, Odoo Standard on Odoo Online is the lower software line than Premium at any of the displayed Standard rates. Community is only enough to prove bills and work orders. Shop Floor, Quality, and PLM still belong on the edition check. Move to Business Central Premium when machine centers, the five production-order statuses, and the Microsoft ledger are the requirements you will not give up. Move to Odoo Custom when Studio, multi-company, or Odoo.sh is already decided.

Where Flectic fits

Flectic implements both systems this section sets side by side. We implement Odoo and Dynamics 365 Business Central, earn no vendor quota on either and hold no certification from either vendor. The Odoo and Premium fork is decided on your routings, holds and user mix, and the recommendation arrives in writing before any configuration starts.

Choose Flectic if

  • You build or assemble discrete products with 20 to 100 people in the US or Canada.
  • You want schedule, costing and order book to agree across production, inventory and finance.
  • You want to pilot one cell first while the rest of the plant keeps producing.

Look elsewhere if

  • The plant's record is the machine: high-frequency signals, tight PLC control or regulated electronic signatures.
  • You run formula manufacturing where yield, potency or catch weight drives cost.
  • You need a vendor-certified partner, or you are above about 100 users with multi-site Finance and Operations.

See ERP for manufacturers for how we connect production, inventory and finance.

How a first manufacturing rollout should be phased

License choice does not set the sequence. Inventory accuracy and a short list of bills do. Flectic sets the timeline for a manufacturing first phase in the written scope, with a fixed price, before work starts. The phase content below is the sequence that keeps a discrete shop inside the apps the docs support.

  1. Phase 1 is items, bills of materials, and one-step manufacturing orders. The docs also describe two-step and three-step manufacturing. Stay on one step until a completed order posts the finished good and consumes the components you expect. Include kits here if you sell bundles. Leave subcontracting and by-products for a product that needs them, and only after the plain bill is right.
  2. Phase 2 is work centers, routings, and inventory accuracy. Load a rate and a calendar taken from the machine's posted hours and the wage you pay for that station. Tie purchasing to component shortages only after on-hand quantities survive a count. This is the phase where supply chain implementation either supports the plant or starves it. The master production schedule can wait until a planner has a forecast worth typing, and it must not share a product with a reordering rule.
  3. Phase 3 is Shop Floor, quality control points, and subcontracting. Put one operation's pass-fail or measure check on the tablet. Turn on blocking only for the step that should stop the next operation. Configure one of the three subcontracting flows, not a custom fourth path, unless you have already accepted a module you will maintain.
  4. Phase 4 is PLM and a costing true-up. Run a change order through approval onto one bill. Compare the manufacturing-order estimate with the real cost on a closed order, then look at the product's average cost. Fix the work-center rate or the employee hourly cost before you open the report to the bank.

What pushes a shop past the 200-hour pack

Odoo's 200-hour comment applies to projects inside the estimator scope, and the manufacturing row of that estimator is MRP, PLM, Quality, and Maintenance. The pack does not become a shop-floor design program because the tablet is in the documentation. These are the moves that blow the hours, taken from the exclusions and the settings pages:

  • Custom modules. Maintenance of that code is outside the subscription, and Success Packs add a monthly charge for extra modules. A screen change on the operator card feels small until someone has to carry it through the next version.
  • Studio, a second company, or the external API. Each one forces Custom. If you discover the second entity during phase 2, the license conversation restarts while the floor is mid-pilot.
  • The master production schedule and a reordering rule on the same part. The docs tell you not to combine them. Planners then spend the hours you saved on arguments about which suggestion to trust.
  • A dirty item master and a stock figure nobody will count. Phase 2 cannot finish while quantities move in a spreadsheet the system cannot see.
  • Onsite time. Travel and expenses sit outside the pack prices. A plant that wants the consultant on the floor all week should price that separately from the 100-hour or 200-hour menu.
  • Headcount past the pack path. Above 50 employees Odoo says you usually use a partner. Above 50 users it says contact Odoo. A 200-hour comparison is the wrong yardstick for that company.

Odoo also says its performance team will not work a case until at least the Standard pack, 50 hours, is in place. A 4-hour or 25-hour pack can cover a short question list. Performance help starts at the 50-hour pack. Price routings, quality points, and PLM from the hour menu. The estimator row behind the 200-hour comment is MRP, PLM, Quality, and Maintenance.

Which discrete shops should run Odoo

Odoo manufacturing is a good fit when you build or assemble discrete products, including make-to-order and contract work, and the business around the shop is part of the same decision. Sales, purchasing, inventory, and the average cost of the finished good stay on one database. You need multi-level bills, a routing you can walk, lot or serial history, and a tablet step with a pass-fail or a photo. You are willing to confirm Shop Floor, Quality, and PLM on the edition you buy, because those source folders are not in the public Community 19.0 tree. You can name an owner for item data and for any custom module.

Odoo is the wrong primary system when the plant's record is the machine. High-frequency signals, tight PLC control, and regulated electronic signatures sit outside the behavior the Manufacturing, by-product, and quality docs describe. Have those shown on your batch, or plan a dedicated execution system beside the ERP. The same answer holds for formula manufacturing where yield, potency, or catch weight is the cost driver. The by-product tab posts a quantity you typed. It does not replace a process recipe.

For the shops in the middle, run the seven tests on one product, price the user mix with the three displayed rates still visible on the quote, and phase the go-live so the first orders are one-step bills you already trust.

For the wider comparison of Odoo against Business Central, Acumatica, Kinetic, Katana and MRPeasy by plant size, read best ERP for manufacturing.

How Flectic can help

Bring one product to the call: its bill of materials, routing, hold rules and the user mix that will touch it. We run the seven tests against that product on Odoo and on Business Central Premium, and say which one fits your plant or why neither does yet.

Pilot one cell, then expand: one line goes live with its operators first while the rest of the plant keeps producing. Flectic sends a written proposal with a fixed price for each phase before work starts. Read ERP for manufacturers, then Book a free discovery call.

Sources

Frequently asked questions

Can a shop start on Odoo One App Free with only Manufacturing?

Yes, if Manufacturing is the one app you choose. As of October 2026 the plan is USD 0 for one app and unlimited users on Odoo Online, and the dependencies of that first app stay free. Manufacturing depends on product, stock, and resource. Quality, PLM, and Shop Floor are separate apps, so they are not included through that dependency rule. Move to Standard when you need the wider suite on Odoo Online.

What does an Odoo light user cost on the shop floor?

As of October 2026 the pricing page lists a light user at USD 8.90, and light users are sold only after an advisor reviews requirements. The listed employee capability includes the Manufacturing Shop Floor. The listed user capability includes the Inventory Barcode Operator. If the advisor will not sell that license, price those people as full users on Standard or Custom instead.

Where do implementation services come from for a 20 to 100 person plant?

Odoo says companies under 50 employees usually buy Success Packs from Odoo, companies above 50 employees usually use a partner, and companies above 250 employees should contact Odoo. New-customer packs, as of October 2026, run from USD 493 for 4 hours to USD 21,250 for 200 hours. The subscription itself excludes implementation. Above 50 users, Odoo says to contact them before relying on the 200-hour estimator.

What usually pushes a manufacturing go-live past 200 hours?

Odoo says 80 percent of projects inside its estimator scope go into production in 200 hours or less, and the manufacturing row of that estimator is MRP, PLM, Quality, and Maintenance. Hours grow when you add custom modules, whose maintenance is billed extra, or when Studio, a second company, or the external API forces the Custom plan. Putting a master production schedule and a reordering rule on the same part, or skipping a stock count, also consumes the pack. Travel is outside the pack price.

Does manufacturing require Business Central Premium?

Yes. Microsoft says the manufacturing features it documents are available only with the Premium experience, including production bills, routings, work centers, and machine centers. As of October 2026 Premium is USD 110.00 per user per month paid yearly in the United States and CAD 149.20 in Canada, plus applicable tax. Essentials is USD 80.00 or CAD 108.50 and does not include that experience. Team Members stay limited to read, approve, and selected updates.

Can Odoo handle by-products, subcontracting, and serials without a separate MES?

For discrete work, the version 19 Manufacturing docs cover all three. A by-product is optional on the bill and posts to stock when the order is completed. Subcontracting has three documented component flows, and finished goods can return to you or ship to the customer. Assigning serials to a multi-unit order splits it into one manufacturing order per unit. Machine signals, tight PLC control, and regulated electronic signatures are a different scope and should be shown on your own batch before you drop a dedicated execution system.

What does Odoo.sh add if we need custom modules?

Custom plan users may host on Odoo.sh, and the user fee does not include that hosting. As of October 2026 a shared worker is USD 57.60 per month, up to 8 workers, storage is USD 0.20 per GB per month up to 512 GB, staging is USD 14.40 per environment per month, and dedicated hosting is USD 480 per month. The Enterprise license is extra. Maintenance of the custom code is also outside the user subscription.

More on the blog: Choosing an ERP or CRM