Document control
Versions, approvals and distribution with read receipts.
Software for ISO 22716
Good manufacturing practice for cosmetics: staff, premises, raw materials and finished product, all under control.
ISO 22716 sets out good manufacturing practices (GMP) for the cosmetics sector. Its relevance is not voluntary: article 8 of Regulation (EC) 1223/2009 on cosmetic products requires manufacturing in line with good manufacturing practices and presumes compliance where a harmonised standard is followed, which is the role ISO 22716 plays. It covers personnel, premises, equipment, raw materials, production, quality control, out-of-specification product, waste, subcontracting, complaints, recalls and documentation.
Versions, approvals and distribution with read receipts.
Publish and version documents by connecting to OneDrive, Google Drive or SharePoint, without duplicating folders.
Annual program, checklists per standard, findings linked to actions.
Root cause, action, owner, deadline and effectiveness check.
Process objectives fed with real operating data.
A register of legal and other requirements, with validity and compliance evaluation per standard.
Root cause, action, owner, deadline and effectiveness check, all linked to the nonconformity.
Improvement opportunities with an owner and tracking, beyond just fixing what already failed.
A pre-built report with indicators, audits and nonconformities, ready for the meeting.
Approved suppliers with their control history.
Recall procedure with batch traceability.
From the manufacturing batch to the finished product, across the whole chain.
Control results linked to the batch before release.
Requirements covered
Standards covered
Templates and records
Which clause of ISO 22716 calls for each record, which fields it needs, a completed example and what the auditor usually flags.
How to record receipt, quarantine and release of raw and packaging materials under ISO 22716 (6.3 to 6.5)…
How to record cleaning and sanitisation of cosmetic manufacturing equipment under ISO 22716 (5.5)…
What the manufacturing batch record for a cosmetic bulk must capture under ISO 22716 (7.2): formula, raw…
What to record when packaging cosmetics under ISO 22716 (7.3): line clearance, materials, batch coding…
How to document release of a cosmetic batch under ISO 22716 (8.2 and 9.8): batch review, results, retained…
How to investigate an out-of-specification result in cosmetics under ISO 22716 (9.5 and 10): laboratory…
How to record a cosmetic good manufacturing practice deviation under ISO 22716 (13): supporting data…
How to record cosmetic product complaints and recalls under ISO 22716 (14) and Regulation 1223/2009…
How to record change control under ISO 22716 (15): what changes, impact assessment, supporting data…
Frequently asked questions
The edition in force is ISO 22716:2007. When the issuing body publishes a new one, a transition period opens; once it closes, certificates issued against the previous edition stop being valid.
Yes. Your existing system — processes, documents, records, audit history — is loaded in and kept alive from day one. Nothing needs redesigning and the certification cycle does not restart.
Yes, provided they are traceable, controlled and able to show who did what and when. No standard requires paper; every standard requires reliable evidence, and a properly controlled electronic record provides it better than a folder.
Yes, and that is the sensible route. The common Annex SL structure lets a single integrated system share the process map, document control, internal audits, nonconformities and indicators between ISO 22716 and the rest, leaving only the standard-specific parts separate.
It depends on the starting point. An organisation already working with written procedures is usually ready in two or three months; one starting from scratch needs longer. The bottleneck is rarely the tool — it is the availability of the people who know the processes.
It is migrated. Existing procedures, forms and records are loaded with their version and approver, so the history is not lost and the system starts with the memory the organisation already had.
Yes. They are given read-only access with a defined scope and an expiry date. It is more comfortable for both sides than preparing a folder of screenshots and exports.
A major one compromises the system's ability to meet a requirement — a required process missing altogether, systematic failure, or a failure affecting the product — and usually blocks certification until it is closed. A minor one is a specific lapse resolved with an action plan.
Yes, from the data the processes themselves generate. That is the difference between a dashboard that reflects what is happening and a spreadsheet somebody fills in the week before the management review.
Yes. The model is multi-company and multi-site: what makes sense to share is shared, and what belongs to each location stays separate — including the certificate scope where it differs.
We'll show you the module running with data similar to yours.
Keep exploring
Free learning path on ISO 22716: good manufacturing practice for cosmetics explained chapter by chapter with…
Living documentation, planned audits, non-conformities with an owner, and indicators that calculate…
Record which regulations apply to you, get alerted when they change and assess compliance regularly, with…
Analysis certificates, data sheets and declarations built from the real batch data, published on the…
Kimobox is a software for ISO 22716 that digitizes the requirements of the standard: approval and control of raw materials, manufacturing batch traceability, finished product quality control, deviation and complaint management, with full traceability and evidence ready for the auditor.
The platform lets you run an integrated management system that combines ISO 22716 with other ISO standards and sector protocols, sharing the process map, document control, internal audits, non-conformities and KPIs.