This is an illustrative project pattern, not an attributed client engagement Start a similar project →
Illustrative pattern · Manufacturing

The SOP lived in a Google Doc. Nobody checked it.

A common shape we see on manufacturing floors: quality procedures exist, but they live somewhere the shop floor doesn’t — a shared doc, a printed sheet taped to a machine, or just in the head of whoever’s been there the longest. Here’s the pattern for fixing that inside Odoo itself, without a separate app to maintain.

Start a similar project → See the real published app
Read this first Everything under “Situation” below is an illustrative, composite scenario — a common project pattern we describe to show how this kind of engagement typically goes, not a real named client or a specific attributed engagement. The module pattern itself, however, is real: it’s directly inspired by SOP Builder, Entrophy’s own app published and installable on apps.odoo.com today. That distinction matters to us, so we’re stating it plainly rather than burying it in a footnote.
Situation

Quality procedures that live outside the system of record.

Picture a mid-sized manufacturer running Odoo Manufacturing for BOMs, work orders and stock moves — the production side is solid. But the actual quality procedure for each product family sits in a shared Google Doc, updated inconsistently, and half the shop floor works from memory or from whichever operator trained them. A new hire skips a torque-check step because nobody told them it mattered for that specific product variant. A QA rejection traces back three weeks later to a step that was quietly dropped on a rush order. Nobody can say, with certainty, which version of the procedure was actually followed on a manufacturing order that shipped two months ago — because the doc has been edited five times since.

This is a familiar shape, not a rare one. It’s the gap between “we have a documented process” and “the process is actually enforced, and provably followed, on every single run.”

Approach

Bind the SOP to the record. Not beside it.

The fix isn’t a better document. It’s making the procedure part of the manufacturing order itself, so the system — not a spreadsheet, not memory — is what enforces it.

Required-step blocking

A manufacturing order can’t be marked done until every step flagged as required on its linked procedure has been explicitly confirmed — not just ticked off on a printed sheet.

Frozen procedure version

When a procedure is attached to an order, the version in force at that moment is snapshotted. Edit the master SOP next month, and last month’s runs still point to the exact steps that were actually followed.

Full audit trail

Every step confirmation is logged with who, and when. When a QA question comes up on an order from eight weeks ago, the answer is a click away, not a memory exercise.

Lives on the record itself

The procedure sits directly on the manufacturing order — in the same screen an operator already has open — instead of a PDF viewer or an external checklist app nobody remembers to check.

Additive to existing MRP

No rip-and-replace of your bill of materials or routing setup. The SOP layer sits on top of the manufacturing order workflow you already run.

Step-level notes

Operators can attach a note at the step they confirmed — useful the one time in twenty a step gets flagged and someone needs context on why.

Outcome

Directionally, what changes.

Fewer rejects traced to skipped steps When the required step can’t be skipped in the system, it stops getting skipped on the floor. QA rejections that used to trace back to “someone missed the check” become rarer, because the order literally can’t close without it.
Audits go faster An auditor asking “which procedure was followed on this batch” gets an answer already attached to the order — the frozen version, the confirmations, the timestamps — instead of someone digging through doc revision history to reconstruct what was probably in force at the time.
Institutional knowledge stops living in one person’s head New operators follow the same required steps as the person who’s been there ten years, because the procedure is enforced by the system rather than passed down informally.
FewerQA rejects tied to skipped steps
Fasteraudits, since the procedure version is already on the record
Zeroambiguity about which procedure version ran on a given order
Onesystem of record — no separate SOP app to keep in sync

Running something similar on your shop floor?

If quality procedures at your business live in a shared doc, a binder, or one supervisor’s memory, we can bind them to your manufacturing orders the same way — required steps, frozen versions, full audit trail. Fixed scope, quoted after a short call.