Accurate & Transparent Product Labeling
This criterion assesses the accuracy, transparency, and safety of product labeling, ensuring consumers receive complete, truthful, and accessible information. It evaluates the organization's commitment to 'Amanah' (trust) by providing clear details on ingredients, origin, halal certification, nutrition, usage, allergens, and hazards. To manage diverse product portfolios, the organization implements a mandatory 'SKU Regulatory Classification & Channel Applicability' process (Decision Tree) to determine the specific regulatory regime (e.g., Food, Cosmetics, Chemicals, Electronics) and channel requirements (Physical, Digital, PPDS) before label generation. Deception is strictly prohibited (Man ghashshana fa laysa minna). The organization appoints a 'Labeling/Claims Responsible Officer' (Amanah Owner) to oversee compliance and report risks to senior leadership/trustees. The system ensures 'Digital Parity' where online information matches physical labels exactly. Mandatory on-pack disclosures are never replaced by QR codes. The organization maintains a category-and-market compliance matrix and a rigorous change control system to update labels based on formulation, regulation, or scientific changes.
- Does the organization use a formal 'SKU Regulatory Classification' process to determine applicable regulations before label creation?
- Is there a 'Claims Substantiation File' for every active consumer-facing claim, approved by a designated officer?
- How is 'Digital Parity' ensured? Are ingredients/allergens on the website identical to the physical pack (field-level match)?
- Describe the PPDS operational model. How do you verify the label matches the menu daily?
- What is the policy for Precautionary Allergen Labelling (PAL)? Is it based on a documented risk assessment?
- How is Halal integrity managed per SKU? Is there a register mapping certificates to specific products and validity dates?
- How are translation accuracy and consistency with master data ensured?
- Does the organization have a 3-tier change control process with specific lead times for safety updates (≤72h)?
- Are labeling risks and KPIs reported to the Board or Trustees?
- How are supplier specifications and COAs validated before data publication?
- SKU Regulatory Classification Decision Tree and resulting matrix.
- Claims Substantiation Files (sampled) containing evidence and sign-off.
- Digital Parity Audit Reports (comparison of physical vs digital).
- PPDS Verification Logs and SOPs.
- Risk Assessments for Precautionary Allergen Labelling (PAL).
- Halal Integrity Register and copies of valid certificates.
- Supplier Specification Validation records and COAs.
- Change Control Logs showing adherence to Tier 1/2/3 timelines.
- Governance Reports to Board/Trustees regarding labeling risk.
- User Testing results for label comprehension.
| Level | Rating | Description |
|---|---|---|
| 5 | 5/5 | Leader in transparency. Automated digital parity checks in place. Halal Integrity Register fully operational. Claims substantiation 100% compliant. Zero Tier 1 incidents. Comprehension testing >90%. Change control median ≤15 days. Full 'Amanah Owner' governance active. |
| 4 | 4/5 | Strong compliance. Manual but effective digital parity checks. Claims files present for all active claims. PPDS and PAL policies fully implemented. Minor non-compliances addressed within Tier 2 timelines. Compliance ≥97%. |
| 3 | 3/5 | Meets minimum legal requirements. Classification process exists. Ingredients and allergens accurate. Digital parity is generally good but lacks systematic verification. Basic claims evidence available. Compliance ≥93%. |
| 2 | 2/5 | Significant gaps. Inconsistent digital parity. Missing claims substantiation. Blanket PAL usage. Ambiguous halal status. Reactive change management. |
| 1 | 1/5 | Severe deficiency. Misleading info, missing allergens, or deceptive claims. No formal review process. Disregard for consumer safety. |
Related Criteria
Discussion (1)
📋 **Version updated: 1.0.0 → 2.9.7** **Changes:** Full import from mizan-297.json
Sign in to post a comment.