Document control
Versions, approvals and distribution with read receipts.
Software for FSSC 22000
ISO 22000 plus sector prerequisites and additional scheme requirements, in a single structure.
FSSC 22000 is a GFSI-recognised certification scheme built on three pieces: the ISO 22000 food safety management system standard, the relevant sector prerequisite programme (the common part ISO 22002-100 plus the sector part, such as ISO 22002-1 for food manufacturing) and a set of additional scheme requirements. Version 7 was published on 1 May 2026 and incorporates the new ISO 22002 series of prerequisites: audits against version 6 are only accepted until 30 April 2027, and upgrade audits to version 7 take place between 1 May 2027 and 30 April 2028.
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.
Additional scheme requirements in a single structure.
Suppliers and external services under the same control.
Test results linked to the batch and the quality certificate.
Staff training plan with competency records by role.
Requirements covered
Standards covered
Templates and records
Which clause of FSSC 22000 calls for each record, which fields it needs, a completed example and what the auditor usually flags.
How to carry out the threat assessment and food defense plan FSSC 22000 requires (2.5.3): threats…
How to document the food fraud vulnerability assessment FSSC 22000 requires (2.5.4): exposed raw materials…
What the allergen management plan FSSC 22000 requires must include: risk assessment, controls, validation…
How to design and record the environmental monitoring of pathogens and indicators FSSC 22000 requires…
How to document the food safety and quality culture objectives FSSC 22000 requires: communication, training…
How to record line clearance at every start-up and product changeover, quality parameters and quantity…
How to document the equipment purchase specification and change management FSSC 22000 requires: hygienic…
How to document the food loss and waste policy, objectives and controls FSSC 22000 v7 requires, including…
Frequently asked questions
The edition in force is FSSC 22000 version 7, with audits against version 6 until 30 April 2027. 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 FSSC 22000 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
The ISO food safety standard: prerequisites, a HACCP plan with CCPs and OPRPs, traceability and emergencies…
Free guide to ISO 22000:2018: prerequisites, hazard analysis, the HACCP/OPRP plan, traceability and…
HACCP is mandatory under Regulation (EC) 852/2004; FSSC 22000 is a voluntary certification built on ISO…
A free learning path on FSSC 22000: ISO 22000's clauses and the scheme's additional requirements explained…
Kimobox is a software for FSSC 22000 that digitizes the requirements of the standard: iso 22000 and iso 22002 series prerequisites, additional scheme requirements, services and purchasing management, quality control and testing, with full traceability and evidence ready for the auditor.
The platform lets you run an integrated management system that combines FSSC 22000 with other ISO standards and sector protocols, sharing the process map, document control, internal audits, non-conformities and KPIs.