Direct answer: For a regulated life sciences company on Odoo, use two roles: your quality unit or a computer system validation firm to own and approve the validation, and an Odoo engineering team to configure audit trails, signature controls and lot traceability and produce the test evidence on staging. The ERP Firm fills the engineering role at $5,000, $8,500 or $14,000 a month; it holds no GxP certification and does not sign validation on your behalf.
How do you validate Odoo for GxP use?
Direct answer: Follow a risk-based validation plan, for example one based on GAMP 5: define the regulated records, close the gaps Odoo leaves open, test on staging and release through change control.
- Write the user requirements and mark which Odoo records your predicate rules require you to keep, such as batch records, lot history, quality checks and recall records. 21 CFR Part 11 applies to those electronic records and to the signatures applied to them.
- Run a risk assessment on each requirement and set the depth of testing. Lot traceability and release decisions usually rank high. Reports used only for planning usually rank low.
- Map each requirement to what Odoo does out of the box, what needs configuration, and what needs a module or custom code. The table on this page is a starting point for Odoo 16, 17 and 18.
- Configure traceability. Enable Lots & Serial Numbers and Expiration Dates in Inventory > Configuration > Settings, set tracking By Lots on each regulated product, require lots on receipt, manufacturing and delivery operation types, and set FEFO as the removal strategy where expiry applies.
- Close the audit trail gap. Odoo writes changes to the chatter only for fields marked as tracked. To log every create, change and delete on regulated models with the user and a timestamp, add the OCA auditlog module (published for 16.0, 17.0 and 18.0) or a custom module, and restrict who can edit its rules.
- Close the electronic signature gap. A Part 11 signature shows the signer's printed name, the date and time and the meaning of the signature, is linked to its record, and uses at least two identification components such as a user ID and a password. A custom module can require password re-entry on approval actions, a check Odoo already uses for security settings, and store those details on the record.
- Write test scripts with expected results, execute them on a staging copy of production, and keep the executed evidence: screenshots, exported records and the version of each module tested.
- Release to production only after your quality unit approves the results. Put every later change, including Odoo upgrades and module updates, through the same change control with a regression test on staging.
- Schedule a periodic review of user access, audit log rules and open deviations, and run a mock recall on staging after each upgrade.
Where do Odoo GxP validation projects go wrong?
Direct answer: Most gaps appear when the chatter is accepted as a full audit trail or the Sign app is accepted as a Part 11 signature.
- Accepting the chatter as a complete audit trail. It records changes only on fields that are marked as tracked.
- Using the Sign app for approvals on batch or quality records. Sign collects signatures on PDF documents and does not bind a signature and its meaning to a stock move or a quality check.
- Assuming the Accounting audit trail covers inventory and manufacturing. It applies to accounting records.
- Validating a demo database, then going live on a production copy with different modules, users and data.
- Upgrading Odoo or a connector module outside change control, so the validated state no longer matches production.
- Giving warehouse or lab staff shared logins, which breaks the link between a record and the person who changed it.
- Expecting a vendor or partner certificate to stand in for your own validation evidence.
What changes across Odoo 16, 17 and 18 for a validated system?
Direct answer: Traceability works the same way on 16, 17 and 18. Odoo 17 added an Audit Trail setting for accounting, and each major upgrade needs a regression test under change control.
Lot and serial tracking (stock.lot), expiration dates (product_expiry) and the lot Traceability report are in Community and Enterprise on Odoo 16, 17 and 18. The Quality app (quality.point, quality.check and quality.alert), the PLM app for engineering change orders (mrp.eco) and the Sign app are Enterprise only, and Community users rely on OCA modules for quality checks. Odoo 17 added an Audit Trail setting in Accounting > Configuration > Settings. In Odoo 18 the setting cannot be turned off once enabled, posted journal entries can be cancelled but not deleted, and the report sits under Accounting > Reporting > Audit Trail. The OCA auditlog module has 16.0, 17.0 and 18.0 branches. Each major upgrade changes screens and code, so plan a regression test on staging and update the standard operating procedures that describe those screens. The ERP Firm includes one version upgrade a year in the monthly fee. Unhappy in the first 30 days? Cancel with a full refund.
What does Odoo do out of the box for GxP, and what needs a module?
Direct answer: Once configured, Odoo covers lot, expiry and recall traceability out of the box. A full audit trail on operational records and Part 11 electronic signatures need a module or custom code.
Applies to Odoo 16, 17 and 18. Checked against the Odoo source code and documentation. Your validation plan decides which rows are in scope.
| Requirement | Odoo out of the box | Needs configuration | Needs a module or custom code |
| Lot and serial traceability | Lots & Serial Numbers, lot records (stock.lot) and the Traceability report on each lot, in Community and Enterprise. | Tracking By Lots on each regulated product. Lot entry required on receipt, manufacturing and delivery operation types. | Usually none. A custom report if the recall export needs a fixed format. |
| Expiry and FEFO | Expiration Dates (the product_expiry module), in Community and Enterprise. | An expiration time on each product, and FEFO as the removal strategy on locations or product categories. | None for standard use. |
| Recall and quarantine | Upstream and downstream trace from the lot, and return transfers on the same lot. | A quarantine location and a written recall procedure. | Optional: a recall export by lot in one step. |
| Audit trail on operational records (21 CFR 11.10(e)) | Chatter history on fields that are marked as tracked. | A decision on which models hold regulated records. | The OCA auditlog module or a custom module to log every create, change and delete on those models, with restricted access to the log rules. |
| Audit trail on accounting records | The Audit Trail setting in Accounting, Odoo 17 and 18. | Enable it in Accounting > Configuration > Settings. | None for journal entries. |
| Electronic signatures (21 CFR 11.50, 11.70 and 11.200) | The Sign app (Enterprise) signs PDF documents. Password re-entry exists for security settings. | Rules on who may approve each record type. | A custom module that asks for password re-entry on approvals and stores the signer, the date and time, and the meaning on the record. |
| Quality checks and deviations | The Quality app: control points, checks and alerts (Enterprise). | Control points on the operations and products in scope. | OCA quality modules on Community, or custom fields for deviation and CAPA records. |
| Access control | User groups and record rules on every model. | One login per person, one role per job and a periodic access review. | Usually none. |
| Change control | Staging branches on Odoo.sh or a staging server, with code versioned in Git. | A release procedure with approval before production. | The PLM app (Enterprise) for engineering change orders on bills of materials. |
Who does what in an Odoo validation project?
Direct answer: Your quality unit approves the plan and the results, and the Odoo engineering team builds, tests and documents. A validation firm is optional and helps when your quality unit has no computer system validation experience in house.
| Activity | Your quality unit | Validation firm (optional) | Odoo engineering team |
| Validation plan and user requirements | Approves | Drafts | Reviews each requirement against what Odoo can do |
| Risk assessment | Approves | Leads | Supplies the Odoo detail for each requirement |
| Configuration and code | Approves each change | None | Builds on staging and keeps the code in your Git repository |
| Test scripts | Approves | Writes or reviews | Drafts scripts for the Odoo functions and runs them on staging |
| Executed evidence | Reviews and signs | Reviews | Captures screenshots, exported records and the version of each module tested |
| Release to production | Approves | None | Deploys after approval |
| Changes after go-live | Approves | As needed | Runs a regression test on staging before each release |
When should you bring in The ERP Firm for Odoo GxP work?
Direct answer: When a validation lead is in place, in your quality unit or at a validation firm, and the open items are Odoo work: lot and expiry configuration, an audit log on regulated models, signature controls on approvals and staging tests for each change. Those are requests on the flat monthly plan. If you need a firm to author and sign the validation package, appoint a validation specialist for that role.
If the work involves custom modules, an upgrade, a storefront or warehouse integration, or a production outage, a focused engagement is usually faster than recruiting. See the related service.
See our industry practice
Related Odoo guides
More answers in the Partners cluster and nearby topics:
Commercial pages