Use: any change to certified products must be pre-approved — a new material, an alternate supplier of an existing material, a reformulation, a new process step, or a new product. Approved changes go into the material register; significant changes may trigger BPJPH/LPH review (🔎 per case).
Related: Guide 05 §3 · criterion 2 §5
Report fields
| Field | Content |
|---|---|
| Company | |
| Change ID / date | |
| Change type | new material / alternate supplier / reformulation / process step / new product / packaging |
| Current state (what is used today) | material name, supplier, register reference |
| Proposed state | full details incl. 中文 name, manufacturer, address |
| Reason for change | |
| Halal evidence for the proposal | certificate (issuer + LHLN check date) / flowchart + animal-free statement / CoA·TDS·MSDS·RDS wording / exemption basis |
| Alcohol relevance | ethanol source (khamr vs non-khamr), level, finished-product impact |
| Risk class (per criterion 2 §2) | CRITICAL / LOW |
| Affected products | |
| Proposed first-use date | |
| Submitted by / date | |
| Approval decision | approved / approved with conditions / rejected — reason |
| Approved by / date (halal supervisor; LPH/BPJPH if required 🔎) | |
| Register updated? (reference row) |
These fields describe the proposed change; the rules below govern how it gets approved.
Rules
- Before use, not after. Using an unapproved change — even a halal one — is an NC.
- Rejection reason must name the missing evidence (e.g., “issuer not on LHLN list”).
- Keep a log of all change reports: it is the first thing surveillance asks for (Guide 05 §3).
- For alternate suppliers of already-approved materials, the decision tree runs again from L1 (the new certificate/evidence belongs to the new supplier).