
How the European Qualified Person certifies batches for the medicinal market, what Thai exporters should pre-build in batch folders, analytical packages, and impurity narratives before QP review.
Every batch placed on the European Union medicinal market under the human medicines framework must be supported by Qualified Person (QP) certification appropriate to the product class and import pathway. The QP is not a cosmetic signature—they personally attest that manufacturing and testing occurred in accordance with EU GMP and the marketing authorization (or equivalent framework for unlicensed specials where applicable). Thai exporters succeed when they stop imagining the QP as a distant bureaucrat and instead design batch folders that make QP review boringly straightforward.
Disclaimer: QP obligations are EU-side. Your job as origin is to supply complete, consistent, verifiable evidence. Never substitute this article for importer legal advice.
A complete batch manufacturing narrative spans from starting materials (your herbal substance) through processing, packaging, labelling (as applicable), and QC release at the EU site if further processing occurs. Gaps in Thailand-origin sections force the QP to assume risk or block release.
The analytical package should align with monograph-style thinking where invoked: identity, assay, impurities, microbial, and foreign matter—each tied to validated methods or justified alternates.
Impurity and microbiological narratives should explain not just pass/fail but trend, upstream controls, and specification rationale linked to patient safety.
Many EU importers and contract manufacturers provide QP services as part of their technical package. That does not reduce your origin obligation—it concentrates scrutiny on your Thailand batch records. Operators who arrive with inspector-grade folders shorten technical transfer from months to weeks.
Publish an RACI (responsible, accountable, consulted, informed) for batch folder assembly:
Full-spectrum flower has hundreds of analytes in trace amounts. QP teams still expect rational subset testing justified by risk and regulatory precedent in the target member state. Document why each panel item exists and what happens if a non-spec result appears—retest rules, sampling error checks, investigation triggers.
Send pre-read index 48 hours ahead. Highlight novelties (first SKU, new supplier, process limit change). Never surprise a QP with undisclosed reprocessing on export day.
Quarterly quality reviews should include trending COA parameters, customer complaints (even if zero), change control log, and CAPA aging. Transparency on Thailand-side challenges builds trust faster than polished silence until failure.
Usually no in the practical sense—QP functions are tied to EU manufacturing authorization structures. Your path is to support the EU QP with complete data.
Missing or conflicting batch ID linkage between Thailand and EU relabeling steps. Fix ID mapping in your technical agreement.
Depends on product, packaging, and claims. At minimum, show you have a stability program with protocols, chambers, and early trending—even if long-term data is still maturing.
Yes for EU review, with certified translations where your importer requires them. Bilingual master data reduces interpretation errors.
They are different roles in the EU regulatory landscape; your importer will map which person covers batch certification vs. pharmacovigilance vs. regulatory correspondence. Do not conflate them in export paperwork.
Run mock QP reviews internally: a QA lead pretends to reject any record missing signatures, dates, or test references. Gamify first-time-right documentation.
Expect it for flagship batches or disputes. Archive data in tamper-evident repositories with audit trails where possible.
Define transfer testing and ownership of intermediate hold times. QP will ask whether Thailand release was final or conditional.
Yes where equipment is critical. Expired calibration is an automatic finding in many audits.
Importer may require audit rights or accreditation evidence. Document subcontract scope and data ownership clearly.
Usually not helpful unless discussing label claims only. Keep commercial pressure away from release decisions.
Define SLA in agreement (e.g., 48h for routine, 24h for safety-adjacent). Missed SLAs compound distrust.
Specs, audit cadence, change notification, OOS rules, recall roles, data retention, confidentiality, subcontractor approval process.