Getting halal certified, and the harder job of keeping it

Companies approach halal certification as an event: book an audit, pass it, receive a certificate, print the logo. That framing is why the process so often takes twice as long as planned, and why certificates are lost by companies that earned them.

Certification is a claim about a system. The audit samples the system on one day, and the certificate asserts that the system continues. Everything difficult about this follows from that second half.

Before the audit: what to settle first

Two decisions belong before any conversation with a certifier, and reversing the order is the most expensive mistake available.

**Which markets are in the plan.** Recognition of a certification body is granted market by market, so the body you appoint determines which markets your certificate reaches. Appointing first and checking recognition afterwards risks a restart, because there is no remedial step that makes an unrecognised certificate recognised. Include markets eighteen months out, not only the one in front of you.

**Which products and lines are in scope.** A certificate covers named products and named lines, not the company. Scoping narrowly to save money on the first audit means returning for an extension when the second product sells, and an extension is not free either.

For meat there is a third: whether the certifier can also authorise the slaughter for your destination. Those are separate approvals, and for Malaysia the list of Islamic societies recognised to authorise slaughter is published by the CFIA as an annex naming two Canadian organisations.

What the auditor is actually assessing

Producers prepare the obvious part and are surprised by the rest. The audit follows the product further than most people expect, and the recurring theme is segregation.

**The line and the schedule.** If the plant runs non-halal product at all, the certificate depends on showing the two never meet: not on shared lines without validated cleaning, not in shared chill storage without physical separation, not on shared handling equipment, and not in a despatch bay where labels are the only thing keeping them apart.

A plant that has always managed this informally has the hardest version of the problem, because the practice may be sound and the evidence may not exist.

**The ingredient chain.** Every input has a status of its own. That means supplier certification and the paperwork behind it, and it extends to items that are not on anyone's ingredient list: processing aids, carriers for flavours and colours, release agents, enzymes, and anything arriving on a rework stream.

**Storage and transport.** The certificate follows the product past your gate. A consignment that left the plant compliant and then travelled alongside non-halal cargo has acquired a problem nobody on your site could have prevented, and your certifier will still raise it with you rather than with the freight forwarder.

**People and records.** Who is responsible, what they are trained on, what is recorded and how it would be found a year later. A system that exists in one person's practice is a system that fails at their holiday.

None of this is exotic and none of it is quick to retrofit, which is why an audit date booked six weeks out is frequently the wrong date. The constraint is not the auditor's diary. It is how long the plant needs before it can evidence what it already does.

The three clocks, and only one is yours

A programme runs on three schedules that do not overlap, and understanding which is which prevents most of the disappointment.

**The certifier's audit calendar**, set by the demand they are already carrying, not by your shipping date.

**Your closure of whatever the audit raises**, paced by the finding, not by the plan. A documentation gap closes in days; a physical segregation issue can mean capital work.

**The destination's recognition of that certifier**, which is a standing fact you either had before you started or did not. It is not something the audit produces.

The third is the one that turns a delay into a restart. A finding you can close in a fortnight costs a fortnight. A certifier the destination does not recognise costs the whole programme.

Keeping it is the part nobody plans for

A certificate is issued against a system on a date. Four things routinely put a company out of line with its own certificate without anybody noticing.

**A new product on a certified line.** Not automatically inside the scope. This is the most common inadvertent breach, and it happens because the plant is certified in everyone's mental model even though the certificate names products.

**A reformulation or a supplier change.** An ingredient's own halal status is part of the assessment, so changing a carrier or a source can put a certified product outside its certificate with nothing visible happening on the floor.

**A change in the certifier's recognition.** Yours to watch and nobody's to tell you. Your own renewal is invoiced; your certifier's standing with a foreign authority is not part of your contract with them.

**Staff turnover.** The person who understood why a procedure existed leaves, the procedure survives as a ritual, and it decays.

The first two are procurement and product development events. Neither department is watching a halal certificate, which is why the useful control is a change-notification step in those processes, not a periodic review that becomes a ritual of its own.

Questions to ask a certifier before appointing them

None of these is confrontational and all have answers the body already holds. They are simply not volunteered.

• Which destination authorities currently recognise you, and until when
• Are you mid-application or mid-renewal anywhere, and on what timetable
• Does your recognised scope in each market cover my product category
• What is your audit lead time, in weeks, for a plant of my size
• Do you authorise slaughter for Malaysia, or only certify product
• If one of your recognitions lapses, what happens to certificates already issued to me, and who tells me

The last one separates a supplier from a vendor. A certifier who has thought about what a withdrawal does to a client's product in transit answers immediately.

The cost question, answered honestly

Certification fees are not published in any form we can cite, and quoting ranges we cannot source would be inventing numbers. What can be said is where the money actually goes, which is more useful.

The audit fee is rarely the largest line. Preparation is: documenting practice that already exists, closing physical or procedural gaps, obtaining supplier documentation, and the internal time of whoever runs it. Then the recurring cost of surveillance and renewal, and the cost of extensions when scope grows.

Two things worth knowing. The cost of appointing an unrecognised body is the whole programme, not a fee, and it is unrecoverable. And in Malaysia the certifier's name is marked on the goods, so changing certifier obsoletes packaging stock as well.

One offsetting point: certification obtained as part of entering a new market may sit inside what federal export funding covers. The AgriMarketing Program's Market Diversification stream funds activities directed at diversifying into non-traditional markets, its cost share is seventy per cent, and costs incurred before an application is deemed complete are not eligible.

That last clause is the reason to check the funding question before booking the audit rather than after.

What a surveillance visit is for

Certification is not a single event followed by a renewal years later. Bodies conduct surveillance between issue and expiry, and the purpose is different from the initial audit in a way worth understanding.

The first audit asks whether the system exists. Surveillance asks whether it is still being operated, which is a harder question to pass by preparation because the answer is written in records made months earlier.

Three things surveillance reliably finds.

**Records kept for the auditor rather than for the process.** A log completed retrospectively looks exactly like a log completed retrospectively, and it undermines confidence in everything around it.

**Changes made and not assessed.** A new supplier, a reformulation, a line modification, a new product run on certified equipment. Each is defensible if it was assessed; none is if it was not.

**Drift in the parts that depend on people.** Cleaning validations not repeated, training not refreshed for new staff, a segregation practice loosened because it was inconvenient and nothing went wrong.

The useful preparation is not preparation. It is having a system whose records are a by-product of doing the work, so that an unannounced visit and an announced one produce the same answer.

The order that works

• Settle the markets, then check which bodies those markets recognise
• Scope the products and lines, including what you expect to add
• Ask the certifier the questions above, in writing, before appointing
• Prepare the evidence before booking the audit, because that is the real constraint
• Check whether the work is fundable before spending on it
• Build change notification into procurement and product development, not into an annual review
• Diary your certifier's recognition dates alongside your own certificate's

The theme is that the certificate is the output and the system is the asset. A company that treats the audit as the goal buys something fragile and owned by somebody else. One that treats the system as the goal can re-evidence it with a different body in weeks if it has to.