Odoo Quality: Control Points, Alerts, and Inspection Routines

Introduction

Picture the classic scene: sales confirms delivery Friday, the planner finds out Thursday night, and Odoo Quality was never part of the conversation. That is the gap this guide addresses.

We ranked ten scenarios from creating a BOM for a simple table to running a deliberately exaggerated level-10 production puzzle, each with a click-by-click Odoo checklist.

Odoo Quality is where physical reality (stock, batches, pickings, production) meets what customers and finance expect. When it works, nobody retypes quantities. When it does not, everyone blames the ERP.

Plenty of factories and warehouses run on experience, WhatsApp, and Excel tabs called FINAL_v3. It holds until you scale, add a second site, or audit traceability.

Quality is part of Odoo's modular ERP. Teams adopt it when they want clear responsibilities, repeatable workflows, and searchable history instead of isolated messages and offline spreadsheets. Odoo Quality: Control Points, Alerts, and Inspection Routines states the storyline for stakeholders approving budgets.

With Quality, you model how goods actually move: receive, store, pick, manufacture, ship, scrap, replenish. Each step leaves a record your future self will thank you for.

You will read ten use cases with concrete company examples, from first BOM to barcode on the shop floor.

Operations directors, warehouse leads, and production planners are the primary audience. Developers can join later; this is business language first.

This article is a ranked Top 10 from Level 1 (easy) to Level 10 (expert). Every level includes numbered steps: what you would actually click in Odoo Quality.

Start where you are comfortable, not at level 10 because it sounds impressive.

Read the challenge section next, then open the level that matches your team today.

In this guide, you will see:

• What Odoo Quality is responsible for in a typical company stack
• Where teams feel the most friction today (and why)
• Ten ranked use cases from beginner discipline to advanced strategy
• When automation or integrations justify bringing in an Odoo partner

The Challenge

Sales promises delivery Friday. The planner learns Thursday evening because the order lived in email, not in Odoo Quality. Expedite fees eat the margin, and finance discovers the stock gap at month-end, not on Tuesday.

Warehouses and factories run on experience, yet stock and production data often live outside Odoo. That gap creates stockouts, urgent purchases, and month-end surprises.

Sound familiar? Teams usually hit these walls:

• Stock files that do not match what sales promises
• Production or purchasing plans made without live quantities
• Traceability gaps when customers or auditors ask questions

The good news: you do not need a big-bang project to fix everything. Pick one use case below, run it for 30 days in Odoo Quality, and measure what changes.

Top 8 Quality Use Cases

8 use cases for Odoo Quality, ranked from Level 1 (easy, do it this afternoon) to Level 8 (expert). Each one answers: what would we build, and what are the clicks in Odoo?

Level 1 is the easy daily win. The last level is intentionally over the top so you see how far the same app can scale when architecture and data stay clean.

Pick your level, follow the numbered steps in a test database, then move up when the previous level feels boring.

1. Run your first Pass/Fail check at receipt before stock goes live Level 1 — Easy

Level 1 is the simplest possible Quality action: one inspector, one incoming batch, one go or no-go decision. No measurements, no alerts, just a manual check on the warehouse dock before the parts enter sellable stock.

Here's how you'd do it in Odoo:

1. Install the Quality app, then go to Quality, Quality Control, Quality Points, New.
2. Set Operation Type to Receipt, pick the products to inspect, and choose Check Type Pass or Fail.
3. Validate the next incoming Receipt in Inventory; Odoo prompts the receiver to perform the check before closing the transfer.
4. Mark the check Pass to release the goods into stock, or Fail to route them to a quarantine location.
5. Open Quality, Reporting, Quality Checks and group by Vendor to spot which supplier delivers the most non-conformities.

What you get: Out-of-spec parts get blocked at the dock instead of being discovered after a customer complaint, with one signed Quality record per incoming batch.

2. Inspect every unit during manufacturing at the right work order step Level 2 — Easy

Level 2 introduces in-process Quality Control. Quality Points are now anchored on Work Order operations so the shop-floor operator cannot move on until each defined check has been performed and passed.

Here's how you'd do it in Odoo:

1. Go to Quality, Quality Control, Quality Points, New and set Operation Type to Manufacturing.
2. Pick the product or BOM, then choose the Work Order step where the check must happen (Assembly, Functional Test, Packaging).
3. Select Check Type Pass or Fail or Take a Picture so the operator must attach photo evidence on the shop-floor tablet.
4. On the tablet, the operator validates the Work Order step; the Quality check fires automatically before the next step opens.
5. A failed check freezes the Manufacturing Order on the spot and waits for a supervisor decision (rework, scrap, override).

What you get: Defects are caught at the workbench, where the cost to fix is a fraction of what it costs after pack-out or shipment, and every check leaves a timestamped trace per operator.

3. Block defective goods from leaving the door with a final check on delivery Level 3 — Easy

Level 3 closes the outgoing side. Quality Points on Delivery operations enforce a last visual check before any parcel leaves the warehouse, so customer-facing defects stop at your dock instead of at theirs.

Here's how you'd do it in Odoo:

1. Quality, Quality Control, Quality Points, New, with Operation Type set to Delivery.
2. Apply the point to the relevant Product Categories or Customers (for example all key accounts).
3. Choose Check Type Take a Picture so the picker uploads a photo of the packed parcel before validation.
4. The picker scans the Delivery Order, performs the check, and only then can validate the outgoing transfer.
5. Failed deliveries are blocked; the parcel is routed to a Quality Hold sub-location and the salesperson is pinged in chatter.

What you get: Customer-reported defects drop because every shipment carries a timestamped visual proof and a human sign-off before it leaves the warehouse.

4. Turn every failed check into a documented Quality Alert with root cause Level 4 — Medium

Level 4 layers Quality Alerts on top of the checks. A failure is no longer a sticky note on the line: it becomes a tracked record with owner, due date, 5-Whys analysis and a closed status before it can be archived.

Here's how you'd do it in Odoo:

1. Quality, Quality Alerts, New (or click Create Alert directly from a failed check or a customer complaint).
2. Fill in apparent cause, deeper cause and root cause in the 5-Why fields built into the form.
3. Assign an owner, a due date, and a team tag (Production, Warehouse, Engineering, Supplier).
4. Capture both a Corrective Action (fix this batch) and a Preventive Action (fix the process so it does not happen again).
5. Track the alert through stages New, In Progress, Verified, Closed; chatter records every comment for the audit trail.

What you get: Defects produce documented process improvements with a measurable recurrence rate, instead of disappearing into hallway conversations.

5. Switch to Measure checks with tolerances and statistical analysis Level 5 — Medium

Level 5 moves Quality from go/no-go to numbers. Measure-type Quality Points capture real values against engineering tolerances, and the data feeds a process-capability view per product family.

Here's how you'd do it in Odoo:

1. Open a Quality Point and switch Check Type to Measure, then enter the target spec plus the lower and upper tolerance.
2. Set the unit of measure (mm, kg, seconds) so all readings stay comparable across operators and machines.
3. The operator types the measured value on the shop-floor tablet; Odoo flags any reading outside tolerance and stops the Work Order.
4. Out-of-tolerance values trigger a Quality Alert automatically with the value, the lot and the operator pre-filled.
5. Go to Quality, Reporting, Quality Checks Analysis to chart measured values over time, per shift and per product.
6. Watch the trend cross warning limits and react before the process produces an actual defect.

What you get: Quality stops being subjective: process drift is detected days before it becomes a customer complaint, with a single trustworthy number per critical dimension.

6. Trace a defect back to a lot or serial and quarantine the impacted stock Level 6 — Hard

Level 6 uses lot and serial traceability to contain a problem the moment it is detected. From one failed check, Odoo lists every other unit produced in the same batch and quarantines the impacted stock in a single move.

Here's how you'd do it in Odoo:

1. Enable Lots and Serial Numbers on the impacted products in Inventory, Configuration, Settings.
2. On a failed check, open the Manufacturing Order and read the lot or serial automatically captured during production.
3. Click the lot to see the full traceability tree: components consumed, MOs produced, customers shipped, work centers involved.
4. Use Inventory, Operations, Internal Transfers to move the remaining on-hand stock of that lot to a Quality Hold location.
5. Push a list of impacted customers to Helpdesk so proactive recall tickets are opened with the lot reference attached.

What you get: A bad batch is contained in minutes instead of hours, with a list of impacted customers ready before the first complaint comes in.

7. Wire Quality into Maintenance, Helpdesk and ISO audit packs Level 7 — Hard

Level 7 turns Quality into the connective tissue across operations. Failed checks open Maintenance requests on the right work center, customer complaints become Quality Alerts automatically, and the ISO 9001 or IATF audit pack is one click away.

Here's how you'd do it in Odoo:

1. Configure an automated action so a failed check on a work center auto-creates a Maintenance Request tagged with the failure reason.
2. In Helpdesk, configure a team rule that converts any incoming customer complaint above severity High into a Quality Alert linked to the ticket.
3. Tag every Quality Point with the relevant ISO clause so the audit pack export becomes a real document, not a manual rebuild.
4. Generate the annual audit pack from Quality, Reporting, Audit Pack: list of points, checks, non-conformances, CAPAs, with timestamps and signatures.
5. Add a Studio field on Quality Alert for Effectiveness Verified so the management review closes the loop on every CAPA.

What you get: A single failure now triggers the right reactions across Manufacturing, Maintenance and Customer Service, and ISO audit prep compresses from three weeks to two days.

Wiring Quality with Maintenance, Helpdesk, Manufacturing and the audit pack so one failure flows through the right teams without manual re-entry is the cross-app integration Dasolo runs as a partner-led engagement for regulated industries.

8. Run an AI-assisted Quality operating system with IoT capture and live dashboards Level 8 — Expert

Level 8 is the full operating system: shop-floor cameras and scales capture checks automatically, an AI agent predicts which lots will fail before the inspector arrives, and one Spreadsheet dashboard tracks yield, scrap, CAPA and complaints in real time.

Here's how you'd do it in Odoo:

1. Train an AI Agent on past Quality Alerts, complaints and inspection data so new MOs receive a predicted failure risk and a suggested control plan on creation.
2. Connect IoT devices (calipers, scales, vision cameras, label printers) so Measure and Picture checks are captured automatically with no operator typing.
3. Orchestrate Quality, Manufacturing, Inventory, Maintenance and Helpdesk: a single failed check triggers quarantine, MO rework, maintenance ticket, customer notice and BOM update without manual fan-out.
4. Use Marketing Automation to launch a recall email drip in the customer's language when a lot is impacted; bad survey ratings reopen the related Quality Alert automatically.
5. Plug an external data source (supplier ERP or LIMS) so incoming raw-material certificates of analysis are matched to receipts and out-of-spec lots are quarantined before they hit stock.
6. Build a Spreadsheet dashboard Quality Live that tracks first-pass yield, scrap rate, CAPA closure speed, supplier non-conformance rate and customer-reported defects per product family.
7. Refresh the dashboard on every Quality event so daily management decisions run on live data, not last month's report.

What you get: Quality stops being a back-office function and becomes a real-time signal across operations, with yield, scrap and complaint trends that drive daily decisions instead of monthly post-mortems.

Designing the AI prompt library, the IoT capture chain, the cross-app automations and the live Quality KPI dashboards is the architecture Dasolo assembles as a partner-led engagement; most teams need an outside team to wire these pieces correctly the first time.

When Expert Help Makes Sense

If levels 1 to 5 fit your world, you can often succeed with standard Odoo Quality, a patient internal owner, and a sandbox where people are allowed to break things safely.

From level 6 upward, the stakes rise: automated workflows that email the wrong customer, Studio fields that block upgrades, APIs that silently stop syncing stock at 2 a.m.

That is not a failure of your team. It is a signal that architecture, testing, and governance matter.

Bring in a partner when you need multi-app design, country-specific compliance, complex integrations, or a go-live date the board already put in the calendar.

Work With Dasolo

Dasolo helps companies implement Odoo the way they actually work: custom apps, clean integrations, and training people will remember after the consultants leave.

If your roadmap for Quality includes the advanced use cases in this guide, we can map a phased plan: quick wins first, then automation and integrations with clear owners and test scripts.

You keep control of scope and budget. We bring the Odoo depth so your team does not learn expensive lessons in production.

Book a free consultation:

Schedule your demo