| 21 CFR 211.100 | Written production and process control procedures, approved by the quality control unit. Deviations are recorded and justified when the work is done. | The Documents app can store a PDF. A PLM engineering change order (mrp.eco) approves a bill of materials, not every procedure. | No controlled procedure with quality-unit approval, and no deviation record on the batch. Custom module or an external QMS. |
| 21 CFR 211.186 | A master production and control record for each drug product and batch size. One person signs it and a second person checks it. 211.186(b)(7) requires the theoretical yield and the minimum and maximum percent that triggers a 211.192 investigation. 211.186(a) still says full handwritten signature. | The bill of materials (mrp.bom) holds components and quantities. PLM versions that BOM. | A BOM is not the master record. It has no second check, no yield limits, and no signed labeling specimens. |
| 21 CFR 211.188 | A batch production and control record for each batch: an accurate copy of the master, dated and signed, plus dates, major equipment, component lots, weights, in-process results, actual yield, and the percent of theoretical yield (211.188(b)(7)). | The manufacturing order (mrp.production), work orders, and move lines (stock.move.line) record dates, lots, and quantities. Quality checks can store in-process results. | No signed copy of the master on the batch, no equipment identity on each step, and no yield percent against the limits in the master record. |
| 21 CFR 211.192 | The quality control unit reviews and approves production and control records before release or distribution. Unexplained discrepancies and specification failures are investigated in writing, including other batches that may be associated. | Enterprise Quality alerts and checks. The Approvals app can route a request. | An approval that does not lock the lot is not a release. Nothing extends an investigation to other batches. |
| 21 CFR 211.165 | Laboratory determination that the batch meets final specifications, including identity and strength of each active ingredient, before release. Product that fails is rejected. | A quarantine location and quality checks (pass or fail, measure, or picture). | Not a laboratory system. No sampling plan and no identity result for each active ingredient. |
| 21 CFR 211.137 | An expiration date from stability testing under 211.166, tied to the storage conditions on the label. | Expiration date on the lot (stock.lot), from the product expiry settings. | The date is stored. The stability study that set it is not. |
| 21 CFR 211.180 | Batch production, control, and distribution records are kept at least 1 year after the batch expiration date. For certain OTC drugs that have no expiration date under 211.137, 3 years after distribution. | PostgreSQL keeps the rows until someone deletes them. | No retention rule and no block on deletion. |
| 21 CFR 211.68 | Computers may be used. Calibrate or check equipment on a written program. Only authorized people change master records. Check input and output. Keep a backup that operators cannot alter. 211.68(c) lets automated equipment replace a second-person check on specific steps only if someone confirms the equipment did the step. | Access rights on the BOM. The Maintenance app can schedule a check. Backups are a hosting task. | No calibration record on the batch. An administrator can still edit master data. A normal backup is not a tamper-resistant copy. |
| 21 CFR 11.10(e) | A secure, computer-generated, time-stamped audit trail of entries that create, modify, or delete electronic records. Changes must not hide the previous value. Keep the trail at least as long as the record. | Field tracking writes some edits to chatter, and only on fields where tracking is turned on. | Stock Odoo does not provide a full Part 11 audit trail. Most fields are not tracked, deletes are easy to miss, and an administrator can delete chatter. |
| 21 CFR 11.50 | A signed electronic record shows the printed name of the signer, the date and time, and the meaning (review, approval, responsibility, or authorship), on screen and on a printout. | Approvals stores an approver. Sign stores a signer on a separate PDF. | Neither writes the meaning onto the batch record. |
| 21 CFR 11.70 | The signature stays linked to its record so ordinary use cannot copy it onto a different record. | The signature sits on a Sign request or an Approvals request, not on the manufacturing order. | Not linked the way 11.70 describes. The signature has to live on the batch record. |