Odoo for Manufacturers: MRP, Shop-Floor and Quality Customizations

Short answer: Odoo’s standard Manufacturing, Shop Floor and Quality apps cover a lot of discrete-manufacturing needs without code: bills of materials, work orders, tablet-based execution and configurable quality checks. Customization is usually needed at the edges, such as multi-level planning rules, industry-specific inspection records, machine data and traceability reporting. The trick is knowing which side of that line your plant sits on before you sign a scope.

This guide is for owners and operations or IT leads at small and mid-size manufacturers in the US, UK and EU who are evaluating Odoo or trying to get more out of an existing install.

What standard Odoo already gives you

Based on Odoo’s own documentation for version 18, the baseline looks like this.

Shop Floor. The Shop Floor module is a companion to the Manufacturing app. It gives operators a visual interface for manufacturing orders (MOs) and work orders, with time tracking built in. Specifically, it offers:

• A dashboard of MOs that are ready to start (confirmed, components available).
• One page per work center, plus a “My WO” view for the signed-in employee.
• An operator panel where several employees can sign in on one workstation.
• Timers, step-by-step instructions, lot and serial registration, and recording of produced quantities.
• Options to scrap components, move a work order to another work center, raise a quality alert or request maintenance.

It can also be installed as a Chrome app on a workstation to limit what operators can reach.

Quality control points. The Quality app creates checks automatically for chosen operations, including manufacturing. You can target a specific product or category, and even a single work order operation. Check types include instructions, take a picture, register production, pass/fail, measure (within a tolerance of a norm value), and worksheet or spreadsheet templates. You can also control frequency: every time, randomly, or periodically.

One detail worth knowing: the documentation notes that an Instructions check is the same thing as a step on a work order, and that work order steps are stored in the Quality app.

Planning. Planning, scheduling and subcontracting options differ by Odoo version, so check the Manufacturing documentation for the version you run before you scope.

Where customization usually starts

Most plants find that standard Odoo handles 70 to 80 percent of the workflow (a rough rule of thumb from our own projects, not a published statistic). The remainder tends to fall into five areas.

Area	Typical gap	Common approach
MRP planning	Multi-level planning with your lead-time, lot-size or calendar rules	Configuration first; OCA modules such as mrp_multi_level or mrp_warehouse_calendar; custom code last
Shop floor	Extra data capture (scrap reason codes, machine counters, rework loops)	Custom fields and Shop Floor extensions; integration with PLC or IoT gateways
Quality	Industry-specific inspection records, sampling plans, certificates of conformance	Quality control points plus worksheets; custom reports
Traceability	Genealogy reports across lots, suppliers and customers	Standard lot and serial tracking plus custom reporting
Integration	Scales, label printers, CAD/PLM, MES, accounting	Connectors and APIs, scoped separately

MRP: configure before you code

Planning is where over-customization hurts most. Before changing code, check that your data is clean: accurate BOMs, realistic lead times, correct routing times and reliable on-hand inventory. Most “Odoo planning is wrong” complaints we see are data problems.

If you need planning logic the core app does not offer, look at the community first. The OCA manufacture repository is maintained by the Odoo Community Association and includes modules such as mrp_multi_level (an MRP scheduler), mrp_warehouse_calendar and mrp_subcontracting_purchase_link. At the time of writing, the listing we reviewed showed 19.0 modules. Community modules vary in maturity, so test them against your own data and check that they exist for your Odoo version.

Shop floor: design for the operator

Shop-floor projects fail when the screen asks for too much. A good rule is one decision per screen, with large touch targets and no typing where a button or barcode scan will do. Standard Shop Floor gets you far on this. Customization makes sense when you need to capture something that auditors or customers require, such as a torque value, a machine ID or a reason code, and the standard steps cannot hold it.

Also decide early how work orders are released. Shop Floor shows MOs that are confirmed with components available by default, so reservation and replenishment discipline in Inventory directly affect what operators see.

Quality: start with the checks you already do on paper

Take your existing inspection sheets and map each line to a check type: pass/fail, measure, picture, or worksheet. Most can be built with standard control points. Plan customization only for things the standard types cannot express, such as statistical sampling tables or customer-specific certificate formats.

If your industry is regulated (medical devices, food, aerospace, automotive), Odoo’s checks are a record-keeping tool, not a compliance certification. Validation, document control and electronic-signature requirements are your responsibility, and may call for additional controls or a specialist.

Edition and licensing: check before you scope

Odoo Community is free to license and self-hosted. Enterprise adds support, hosting options and additional apps. In our experience, Shop Floor and the full Quality workflow are Enterprise features, but this changes between versions, so confirm against the edition comparison and pricing for your version and country. Prices are shown per user per month and differ by plan and currency, so we do not quote numbers here. Also note that Odoo documents the Custom plan as the one that allows Odoo.sh or on-premise hosting, and that Standard is hosted on Odoo Online. That matters if you need custom modules, since custom code generally needs Odoo.sh or on-premise.

A practical scoping sequence

1. Map the current process. Walk the floor with a BOM, a routing and a recent job traveler.
2. Run standard first. Configure work centers, routings, control points and Shop Floor with real data in a test database.
3. List gaps with evidence. For each gap, note who needs the data, how often, and what happens without it.
4. Rank gaps. Compliance and customer-required items first, convenience items last.
5. Prefer configuration, then OCA, then custom code. Every custom module is something you must test and port at each upgrade.
6. Pilot on one line. Run one work center or product family for a few weeks before rolling out.

Honest trade-offs

• Odoo is strong on integration, not on depth. Having inventory, purchasing, accounting and manufacturing in one database is a real advantage for SMBs. For very complex production (heavily regulated, highly configured products, deep scheduling), a specialized MES or a more manufacturing-focused ERP may fit better.
• Customization has a tail cost. Upgrades, testing and documentation are ongoing.
• Operators matter more than features. An elegant configuration that nobody uses on the floor is worth nothing.

Talk it through

If you are weighing Odoo for a plant, or have a rollout that is stuck on planning or shop-floor data, we are happy to have a no-charge conversation about your process and tell you honestly whether standard Odoo, a small customization or a different tool is the better fit. Get in touch with Teknologia Solutions whenever it suits you.

---

Sources: Odoo 18 Shop Floor documentation; Odoo 18 Quality control points documentation; Odoo pricing; OCA manufacture repository. Features, editions and prices change between Odoo versions and regions, and the 70 to 80 percent figure is our own estimate. Please verify details against Odoo’s current documentation and your Odoo partner before making decisions.