The catalog your quality system revolves around.
Products, parts, SKUs — whatever you call them — kept facility-scoped, revision-aware, and lifecycle-managed. The catalog stays an accurate picture of what’s current without ever losing what came before.
PRD-118 · Hydraulic manifold assembly
A new revision chains — it doesn't overwrite.
When a part changes enough to warrant a new revision, create one. QFormance copies the part's details forward into a fresh catalog entry, retires the previous revision, and links the two so the history reads in a straight line. Records created against the old revision keep pointing at the revision they were made against — revising a part never rewrites the past.
Retire a part without losing its history.
Most parts that leave service shouldn't be deleted — they should be retired. Marking a part inactive hides it from the day-to-day catalog while keeping it fully on the record, so anything that ever referenced it still resolves. Retiring and reactivating both capture a reason on the audit trail. Genuine mistakes can be deleted instead — and a deleted part is recoverable for 90 days before it's permanently purged.
Mark PRD-074 inactive?
Hidden from default catalog lists. Historical record links keep resolving. Captured in the audit trail.
Reason
End-of-life — superseded by PRD-118 on the 2026 platform.
Each site sees the parts that apply to it.
A product belongs to one or more facilities, and the catalog defaults to the parts in scope for wherever you're working — switch to All facilities to widen the view. Parts can nest one level deep, so an assembly and its components read as a small hierarchy without turning into a sprawling bill-of-materials tree.
Tied to the work — and the relationships — around it.
A part never sits on its own. Non-conformances, changes, FMEAs, exemptions, and meetings link to the products they concern, so the context travels with the record. And a product points at the supplier that makes it or the customer it's built for. Links stay attached to the exact revision they were made against — revise a part and the history doesn't move.
Built to fit how your team already works.
Your vocabulary, your numbering, your roles — the catalog adapts to you, not the other way around.
Your label, org-wide
Call them Products, Parts, or Items — set the label once and it reads consistently across the sidebar, page titles, and every button. Categories and the numbering prefix are admin-configurable too.
Revisions that read straight
Every revision links to its predecessor. The current revision is obvious; the ones before it are one click away — and the records made against each one stay attached to it.
Recoverable delete
A part deleted by mistake sits in Trash for 90 days with one-click restore. A part that's genuinely end-of-life gets marked inactive instead — retired, but never lost.
The right people, the right actions
Creating, editing, retiring, and deleting parts are each their own permission. Decide once who maintains the catalog — the role system keeps the lines clean from there.
A part catalog that stays honest.
Every revision chained, every retired part still on the record, every site seeing exactly what applies to it.