Audit-ready evidence for every food safety clause
- Reads the CoAs, specification sheets, certificates and supplier questionnaires you are sent
- Maps each one to the clause it satisfies in FSSC 22000, IFS Food, 21 CFR 117
- Opens the CAPA when a certificate expires or a clause has nothing behind it
The schemes and records it maps against
What it maps, and what it hands the auditor
What it reads, and what it reads against
Eight schemes, six kinds of document and four public records. FSSC 22000, IFS Food, 21 CFR 117 publish their requirements openly and are mapped clause by clause. BRCGS, ISO 22000, SQF are sold, so Krolda carries their clause identifiers and its own summaries and none of their text. HACCP and Codex Alimentarius are open but are frameworks rather than clause trees, so they sit behind the rest as reference. These are our renderings of the names. No certification body endorses this product.
Opening foundCertificate covering 4.4.1 lapsed 11 days ago
The certificate held against this clause expired and no replacement has arrived. Request the current one, or record the approved alternative and the reason for it. The expired document stays attached either way, because an auditor asks what changed and when.
Example · IFS Food · Certificate expired
4.4.1 Supplier monitoring
Document in, clause out, task routed
Every figure on this page is derived from the source it describes rather than typed, so a count here cannot quietly disagree with the standard or the record it came from. The regulation figures were read on 2026-09-13.
Six document types, one reader
Certificates of analysis, specification sheets, certificates, supplier questionnaires, audit reports and safety data sheets. They arrive as PDF and Word attachments, which is why there is no feed to subscribe to and no format to agree on first.
- Certificates of analysisPDF
- Specification sheetsPDF
- CertificatesPDF
- Supplier questionnairesPDF, DOCX
- Audit reportsPDF, DOCX
- Safety data sheetsPDF
Eight schemes, three mapped in full
Each document is matched to the clause it satisfies. FSSC 22000, IFS Food, 21 CFR 117 are mapped in full because their requirements are published openly. BRCGS, ISO 22000, SQF are mapped by clause identifier, because their text is sold.
- 21 CFR 117.135 · Preventive controlsMet
- FSSC 22000 2.5.3 · Supplier approvalMet
- IFS Food 4.4.1 · Supplier monitoringExpired
- 21 CFR 117.410 · Sanitary facilitiesMet
What the desk works from
Earned, with anyone you compete with left out of it.
The gap opens a CAPA
A clause with no current evidence behind it, or a certificate whose expiry has passed, becomes a corrective action with an owner and a due date. Nothing waits to be noticed during the audit.
- Owner
- Technical Manager
- Due
- 14 days
IFS Food 4.4.1 has no current evidence
The supplier certificate covering this clause expired and no replacement has arrived. Request the current certificate, or record the approved alternative and the reason for it. The clause, the expired document and this action stay attached to each other.
Five screens, and none of them is a score
Every one of these is a real route in the product, photographed rather than drawn. Open a row to see what it holds.
Questions
What does Krolda do?
Krolda is food safety compliance software for quality teams in food and beverage manufacturing. It reads the documents suppliers send, certificates of analysis, specification sheets, certificates, supplier questionnaires and audit reports, and maps each one to the clause it satisfies in FSSC 22000, IFS Food and 21 CFR 117. When a clause has no document behind it, or the document behind it has expired, it opens a corrective action with a due date and an owner instead of leaving the gap for an auditor to find.
Which food safety standards does it map to?
FSSC 22000 v6, IFS Food v8 and 21 CFR Part 117 are mapped in full, because all three publish their requirements openly: FSSC and IFS both release their complete schemes as free PDFs, and 21 CFR is United States public domain, reachable through the eCFR API as 8,425 sections across 276 parts. BRCGS Issue 9, ISO 22000:2018 and SQF are mapped by clause identifier and by Krolda's own summary of each requirement, never by their text.
Why is BRCGS or ISO 22000 content not shown in full?
Because the text of those standards is copyrighted and sold. BRCGS Issue 9 is a paid document and BRCGS actively polices redistribution; ISO 22000:2018 costs about CHF 160 from ISO. Clause identifiers and independent summaries are lawful to publish and the standard's own wording is not. This does not limit what the software can do for a site that already holds its copy, because the work is mapping that site's own documents to clause IDs, not reproducing the scheme. Any vendor showing full BRCGS clause text has either licensed it or should be asked to show the licence.
What does an auditor actually see?
The clause, the document that satisfies it, who verified that document and on what date, and every change since. An audit finding is usually not about whether a control happened, it is about whether the evidence for it can be produced in the room. Krolda is built around that trail rather than around a dashboard, which is the part most document management tools leave until last.
Does it replace a QMS or an audit management system?
No. Krolda is the evidence layer between the documents a site receives and the clauses it is held to. Sites running a quality management system, a document control system or an audit management system keep them; what Krolda adds is the mapping from an arriving document to the requirement it answers, and the corrective action when nothing answers it.
Where does public recall and regulation data come from?
From the primary sources, unmodified. United States food enforcement reports come from openFDA, which published 29,386 records as of 2 September 2026 and requires no API key. Regulation text comes from the eCFR API. European alerts come from the RASFF portal. FSIS meat and poultry recalls are published by USDA but the endpoint is not openly reachable, so those are not yet included. Every figure Krolda publishes from these carries the date it was read.
Is Krolda available today?
Not yet. Krolda is being built with a small number of design partners, sites willing to run part of their next audit on it and say where it fails. Early access is a working conversation rather than a waiting list, and the honest reason for it is that a tool that will be in the room during a BRCGS or FSSC audit has to be wrong in front of somebody before it is trusted in front of an auditor.
Who is it for?
Quality managers, food safety managers and technical directors at food and beverage manufacturers who are certified to a GFSI-recognised scheme and carry the supplier document load that comes with it. It is built for the person who has to stand behind the answer when an auditor asks where the evidence is, which is a different job from the one a procurement or ERP tool is built for.
The evidence stays with the clauseA document is filed against the requirement it satisfies, not against the supplier who sent it, so an auditor asking about a clause gets the document rather than a folder.
Only the clauses you are actually held toEach one mapped on its own, and the reason a document was accepted against it travels with the row.
Every status opensThe whole document is kept, so a clause marked met is a page you can go and read rather than a tick you have to trust.
Checked before the expiry, not afterEach certificate carries its own end date, and the row says who verified it and when that last happened.
Find out which clauses have nothing behind them
The first honest question is not how compliant a site is. It is which requirements have no current evidence held against them today, and which documents were accepted for the rest. The four lines beside this are what that answer comes with.