A quality-system certificate is not a product claim: read the scope line first

The sentence that matters is the disclaimer

This week ZEO ScientifiX, a Florida cellular medicine manufacturer, said it is the first facility certified under AABB's new Quality Management Systems programme. The company's own disclosure says the certification assesses quality management only and does not evaluate its cellular products. That is an honest statement, and it is the most useful sentence in the announcement. It tells every reader what the certificate is not.

My argument is that QA, QP and compliance teams should adopt this as a standing rule: a quality-system certificate is evidence about how an organisation controls its processes. It is not evidence that any given product, lot or batch is fit for use. Nobody involved has claimed otherwise, but the gap between the two is where supplier files and diligence summaries tend to get sloppy. A certificate gets cited, the scope line gets dropped, and an assurance about a system quietly becomes an assurance about a product.

Lots fail inside certified systems too

Health Canada's Type II recall of one lot of Helena's Plateletworks Collagen Kit shows what product-level failure looks like. According to the notice, internal testing found that many tubes aggregated poorly, which risks falsely suggesting abnormal platelet function. The records say nothing about the manufacturer's certifications or the cause, and I am not suggesting any link. The point is that the harm here sits at lot level. A clinician reading a falsely low result does not care what the supplier's system audit said. The notice also records that the problem was found by internal testing, which is a product-level control and not a system-level credential.

Italy's medicines agency offers a different reminder. AIFA's GMP office has set out how paper GMP measures reach companies, by registered post, and pointed to earlier notices on digitally signed documents and online submissions. Regulatory GMP status is conferred through formal measures from the authority, delivered through defined channels. A voluntary third-party certificate may be a sound input to a quality file, but it sits in a different category from those measures and should be recorded as such.

The strongest counter-argument

The best objection is that this is a fuss over a clearly labelled, voluntary programme. System certification is a legitimate, even necessary, signal: no buyer can test every attribute of every lot, and a well-run quality system is the best available predictor of consistent output. A new programme aimed at cellular medicine, where manufacturing standards are hard to benchmark, deserves credit. ZEO has also stated the limits plainly, so nothing misleading has happened.

I accept all of that. A certificate is a valuable input, and nothing in the records suggests misuse. But the risk is downstream, in how the certificate is summarised in supplier-approval records, vendor questionnaires and deal documents, where scope language rarely survives. A rule that costs one extra field in a template is a cheap defence against that drift. The programme is new, so we do not yet know how widely it will be adopted or how its scope will be described in practice. Teams should set their handling rule now, before certificates start to circulate.

What to do about it

Treat every third-party certificate as a scoped claim. Record what it covers and what it expressly excludes, and keep that wording next to the certificate in the supplier file. Then ask what product-level evidence still has to come from somewhere else: lot release data, incoming testing, authority-issued GMP status or audit findings. If the answer is none, the file has a gap, however good the certificate looks.