Multi-stage Odoo inspection plans (incoming, in-process, final, shipping) with AQL sampling and pass/fail gating that blocks downstream moves. One-time license from $249.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Multi-stage Odoo inspection plans (incoming, in-process, final, shipping) with AQL sampling and pass/fail gating that blocks downstream moves.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Odoo's stock and MRP apps give you a place to record a Quality Check, but they don't enforce a disciplined quality workflow: a lot arrives, gets received, and moves on whether or not it was ever inspected. This build-to-order module turns Odoo into a real quality gate. ECOSIRE designs and develops a dedicated quality.inspection.plan model tree that ties an inspection plan to the exact stage where quality matters — receiving (incoming), work-order or operation checkpoints (in-process), pre-shipping (final), and outbound (shipping) — so nothing slips past the checkpoint that should stop it.
Four built-in inspection stages — incoming (receiving), in-process (per operation/work order), final (pre-shipping) and shipping (outbound) — each configurable as its own inspection point
AQL sampling plans: the module reads lot or batch size and derives the required sample count from a lot-size-band sampling table agreed during scoping, so inspectors sample the correct number of units
Three check types per point — quantitative measurement with min/max tolerances (computed and validated via @api.depends), attribute pass/fail, and visual/manual confirmation
Pass / fail / hold verdict that gates the workflow: a fail or hold sets the record state and blocks the downstream stock move (receipt validation, work-order progression or delivery confirmation)
Inspector assignment with digital sign-off — the responsible user, timestamp and result are recorded on the inspection record and locked once signed
Reusable inspection plan templates linked to products, product categories or operations, so a plan is auto-selected when a matching receipt, work order or delivery is created
Each plan holds an ordered list of inspection points, and each point declares a check type — a measurement with tolerances (min/max computed and validated via @api.depends), a pass/fail attribute check, or a visual/manual confirmation. For lot-based receipts you get AQL sampling: the module reads the lot or batch size and derives the required sample count from the sampling table you agree on during the build, so inspectors sample the right number of units instead of guessing. Results roll up to a plan verdict of pass, fail, or hold. A fail or hold sets the record state and, through server actions and Odoo's stock move framework, blocks the downstream move — the receipt can't be validated, the work order can't advance, or the delivery can't be confirmed until quality signs off or an authorized user records a documented deviation.
Because it is native Odoo, the module ships the full stack you'd expect from a professional add-on: models and fields in models/, security via ir.model.access.csv plus record rules so inspectors, supervisors and read-only auditors see only what they should, list/form/kanban views and OWL widgets for the inspection cockpit, a QWeb PDF Certificate of Conformance / inspection report, automated actions to notify on failures, and XML-RPC/JSON-RPC endpoints so an external MES, LIMS or scanner app can push measurements in. It is compatible with Odoo 17, 18 and 19, and works on Community or Enterprise (we scope any Enterprise-only touchpoints, such as the native Quality app, before we build).
This is not an instant download. ECOSIRE builds this module to your process — your stages, your check types, your sampling table, your gating rules — installs it on your database, and hands over documented, upgrade-safe code with training and a support window. Typical delivery is 2 to 4 weeks after a short scoping call.
Owns the quality system and wants inspection gates that are actually enforced across receiving, production and shipping — not optional checkboxes. Needs role-based access, defensible audit trails and Certificates of Conformance ready for customer and regulatory audits.
Inspects incoming lots at the dock and needs the system to tell them exactly how many units to sample for a given lot size, capture measurements and pass/fail results fast, and block a receipt from being validated until quality clears it.
Runs the shop floor and needs in-process checkpoints tied to work orders that hold a job when a stage fails, plus an authorized, logged deviation path to release a hold without breaking traceability.
Maintains the Odoo instance and wants a clean, upgrade-safe custom module (proper manifest, ORM models, access rules) that works on their version and edition and integrates with existing MES/LIMS/scanner tools via XML-RPC/JSON-RPC.
Buy the license on ecosire.com and download the Incoming/In-Process/Final Inspection Plans module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Incoming/In-Process/Final Inspection Plans, and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Multi-stage plans (incoming, in-process, final, shipping) | Built as one model tree covering all four stages, tuned to your flow | Possible but you design and build the whole state machine yourself | Varies by app; many cover only one stage or a generic check | |
| AQL / lot-size sampling | Sampling table implemented to your standard; sample count auto-derived | You must design and code the sampling logic from scratch | Sometimes included, rarely matching your exact standard | |
| Pass/fail/hold gating that blocks downstream moves | Hard gate on stock moves with an authorized, logged deviation path | Achievable but you own the server-action and edge-case logic | Often advisory only, or blocks without a controlled override | |
| Fit to your exact process & documents | Scoped to your stages, check types, roles and Certificate of Conformance | Full control, but full cost and full maintenance burden on you | Fixed to the vendor's opinion; configuration only | |
| Delivery model | Built, installed and validated on your database in 2-4 weeks | Depends entirely on your team's capacity and backlog | Instant download, then self-integration and self-support | |
| Support, updates & upgrade path | Support window, source handover and a documented upgrade path | You maintain it and migrate it every Odoo version yourself | Vendor support quality and version coverage varies widely | |
| Odoo 17 / 18 / 19 & Community/Enterprise coverage | Delivered for your specific version and edition, verified on both if needed | You test and port across versions yourself | Listed versions only; may lag new releases |
This is a build-to-order module, not an instant download. After a short scoping call to confirm your inspection stages, check types, sampling table and gating rules, typical delivery is 2 to 4 weeks. We build in a staging environment, review it with you, then install on your production database. Complex integrations (external MES/LIMS, unusual sampling logic) can extend the timeline — we give you a firm estimate before we start.
Every build includes a post-go-live support window covering bug fixes and usage questions under agreed response terms. You receive the full module source and documentation, so you're never locked in. We also provide a written upgrade path, and can quote a support/maintenance retainer to keep the module current across future Odoo releases and to add new inspection stages or rules as your process evolves.
It works on both. The module is compatible with Odoo 17, 18 and 19, Community or Enterprise. On Community it provides the full inspection-plan, sampling and gating workflow on its own. If you run Enterprise and want to interoperate with the native Quality app, we scope those touchpoints during the build so the two work together rather than duplicating checks.
When an inspection point or plan resolves to fail or hold, the module sets the inspection record's state and, through server actions on Odoo's stock move framework, blocks the corresponding downstream action — the receipt can't be validated, the work order can't advance, or the delivery can't be confirmed. The only way past is a documented, audit-logged deviation approved by an authorized supervisor, so nothing slips through silently.
Yes. For lot- or batch-based receipts the module reads the quantity and derives the required sample count from a lot-size-band sampling table (AQL-style) that we implement to your standard during scoping. Inspectors are told how many units to check instead of guessing, and the sampled results roll up to the plan verdict.
Yes. Because it's native Odoo, the inspection models are reachable over XML-RPC and JSON-RPC. An external MES, LIMS, digital gauge or barcode-scanner app can create inspection records and post measurement or pass/fail results directly into Odoo. We include a short integration note and can build the connector as an add-on scope item.
We build clean, upgrade-safe custom code — proper __manifest__.py versioning, standard ORM models and views, no core patching — so it upgrades like any well-built addon. We hand over the source and a documented upgrade path, and can handle the version migration for you as a scoped engagement when you move from 17 to 18 or 19.
Multi-stage Odoo inspection plans (incoming, in-process, final, shipping) with AQL sampling and pass/fail gating that blocks downstream moves.