A certificate is issued to a production line, not to your brand. So what you need is not to sit an exam yourself: it is for your product to be made on a line that already holds it, or for a line to be taken up to that standard. We do both. You only need to tell us where the product is going to sell.
Where you sell decides which certificate you need
If you are building a plant-based product, there is only one practical question about certification: will the absence of a certificate keep you out of the market you want.
Usually yes. Halal opens Malaysia and the Middle East, OU kosher opens the United States, FSSC 22000 opens European retail. Without the one your target market asks for, however good the product is, it does not get listed.
And the certificate is not issued to your brand. It is issued to a production line. So what you need is not to sit an exam yourself. It is for your product to be made on a line that already holds it, or for a line to be taken up to that standard. We do both.
- You bring: target market and categoryWhere it sells and what it is. Those two decide which certificate applies.
- We confirm: the certified scope of available linesWhether your item sits inside an existing certificate. If it does, we use it and no consulting is needed.
- We handle: getting the line certifiedDocumentation, plant conditions, audit support through to issue. That work sits between us and the plant and does not need you in it.
- We handle: your product documentationSpecification, ingredient list, test reports and label review. These are what buyers and channels ask you for.
- You get: a product that can enter the marketThe product, the documentation and the eligibility to clear customs, handed over together.
Documentation, flow remediation, cleaning validation, handling the audit on the day: that is work on the plant side and it is our job. What you need to know is three things: which certificate, how long, and whether an existing one already covers your product.
The audit examines the system, not the batch
Many people assume certification means sending product for testing and receiving a pass report. Food safety system certification does not work that way. The auditor examines the system across the line: how hazard analysis was done, how control points are monitored, what happens on deviation, where records live, who verifies them.
A flawless test report on one batch is therefore not evidence of conformity. Conversely, a well-run line that had a deviation usually does not pick up a major finding, provided it was recorded, corrected and followed up, because what the audit wants to see is whether the system worked when something went wrong.
That difference defines the nature of the engagement. It is not preparing a plant for an exam. It is building a system the plant can run every day and evidence afterwards. A system built for the exam shows itself at the surveillance audit.
Five steps, and the first decides the rest
The first step is a gap assessment on site: an inventory of what the plant has against what the standard requires, ranked by risk and cost. Only after that is it possible to say how much time, how much modification and how much documentation is involved.
It is also why we do not quote beforehand. For the same certificate, a plant with an existing HACCP system and a plant starting from nothing can differ several-fold in effort. A number certain to be overturned helps nobody.
The output is a ranked gap list, not a generic checklist. Generic checklists can be bought, but they describe what the standard wants, not what this plant is missing.
On-site inventory of the gap, ranked. Timeline and cost follow this step.
Food safety plan, hazard analysis, traceability, corrective action and internal audit.
Personnel and material flow, hygienic zoning, ingredient segregation, sanitation validation.
On site on the day, helping answer findings and tracking corrective actions to closure.
Connect the certificate to production, channels and export files, and keep surveillance on track.
Which certificate to do first
The answer is not the best-known certificate. It is the one that is closest to where the plant already is and also opens the target market. Both conditions have to hold.
Closest means the smallest gap against the systems the plant already runs. A plant with HACCP and basic prerequisite programmes in place finds a GFSI-recognised system easier than building halal ingredient traceability from nothing. Conversely, a plant with simple inputs and a short supply chain may reach halal faster.
Opening the target market means the certificate actually solves an access problem. Earning one the target channel does not ask for is progress in systems terms and nothing in commercial terms, and it is the most common misallocation.
So the sequence is decided with the plant’s current state and the market conditions on the same page. Once the first certificate is in hand the second costs noticeably less, because the food safety plan, traceability and internal audit mechanisms largely carry over. Which is exactly why the first one has to be the right one.
Documents have to be runnable, not just readable
The easiest mistake in documentation is writing it too well. A procedure specifying a record every two hours that the floor cannot actually staff is worse at audit than having no procedure at all, because the missing records become a clear non-conformity.
So procedures are designed around the real working rhythm, then checked back against what the standard demands. If the rhythm cannot satisfy it, what changes is the working method or the staffing, not the wording.
That principle defines the engagement: it is plant improvement work, not document production. It also means the plant has to commit people during the project. Without participation from the floor, the system that gets built does not get run.
In practice we settle four questions first: who fills the record in, who verifies it, where it is kept, and how often it is reviewed. A system that cannot answer those four will have trouble at surveillance however complete the paperwork looks.
| Procedure does not match practice | What is written and what is done diverge; the most direct line of enquiry |
|---|---|
| Records incomplete or back-filled | Usually classified as integrity, which is more serious than technical |
| Corrective actions not closed | A problem found with no evidence it was resolved |
| Flows cross | Personnel or material flows cross between hygienic and general zones |
| Weak allergen or ingredient segregation | Shared lines without validated cleaning or changeover records |
| Calibration overdue | Calibration records lapsed on monitoring devices |
| Supplier specifications expired | Ingredient specifications not updated when the supplier changed |
| Incomplete training records | Retraining after staff changes missing or unrecorded |
Certification is the start of a cycle
Certification carries annual surveillance and periodic recertification, and a system that is not run decays. The most common first-year problem is record quality: once the audit pressure is gone, gaps and back-filling appear.
Back-filled records are among the easiest things for an auditor to spot. Handwriting, ink and the regularity of timestamps all give it away, and it is usually classified as an integrity finding, which is considerably harder to resolve than a technical one.
So after issue we connect the certificate to production, channels and export documentation, making it something daily work depends on. A system that gets used does not decay. That is not a management philosophy; it is an observation.
We do not supply a generic document pack. Templates can be bought, but an auditor compares the document against your actual operation, and a template describes someone else’s. The value is in fitting the system to this plant’s flow, staffing and equipment, and there is no shortcut for that.