Halal traceability built into your ERP — what F&B factories need from day one

A halal-certified product isn’t a product label. It’s a system. The label says “this product is halal” — the system has to prove that every ingredient in every bottle came from a halal-certified supplier, was processed without cross-contamination, and can be traced end-to-end in case of audit or recall.

For F&B factories in Saudi Arabia (SFDA), the GCC (GSO standards), Indonesia (MUI), Malaysia (JAKIM), and increasingly globally, halal traceability is a compliance requirement that lives in your operational systems — not in a binder.

This article covers what the certification regimes actually expect, how AION supports halal traceability, and what an audit looks like.

What halal certification actually requires (technically)

Certification bodies differ in detail but converge on five technical requirements:

1. Supplier qualification with halal certificates on file. Every raw material supplier (concentrate, sugar, additives, packaging that touches food, even processing aids) must hold a current halal certificate. Your records must show the certificate, the issuing body, and the expiry date.

2. Lot tracking from receipt forward. Every receipt creates a lot. The lot inherits the supplier’s halal status and certificate reference. Lots are identifiable in inventory, in WIP, and in finished goods.

3. Production batch records. Every job order records which specific lots of raw materials were consumed. The recipe is one thing; the actual lots used in this batch is the evidence.

4. Finished-goods lot identification. Every output lot from a production run is labelled and tracked. The label carries the production date, expiry, and the lot number that the customer or auditor can reference.

5. End-to-end traceability. Given a finished-good lot, you can show: which raw material lots went into it, which suppliers those lots came from, which halal certificates covered those suppliers at the time of receipt. In reverse: given a raw material lot, you can show every finished-good lot it ended up in.

Audit duration: hours, not days. If the auditor asks “show me the chain for FG lot ABC-2026-0512” and the answer takes 3 hours of warehouse spelunking, your certification is at risk.

How AION supports this

Lot tracking is at the core of AION’s inventory module — it’s not a bolt-on. Every inventory transaction (receipt, issue, transfer, completion, scrap) is lot-aware:

At receipt: A goods receipt against a PO creates one or more inventory lots. Each lot records: supplier, supplier lot reference, manufacturing date, expiry, halal certificate ID (if applicable), and the receipt date.

At issue to production: When a job order issues raw materials, the system records which specific lots were consumed. FIFO or LIFO can be configured per item; for halal-critical materials, FIFO usually applies to maintain freshness.

At completion: Finished-goods receipt from production creates a new lot. The lot’s parent record includes references to all the raw material lots that were issued to the job. The relationship is bidirectional.

At shipment: Sales delivery from inventory specifies which lots ship to which customer. Customer records the lot on receipt. The chain extends to the customer.

Where-used queries: Given a finished-goods lot, walk backward to see source raw material lots and their suppliers. Given a raw material lot, walk forward to see every finished-good lot it became.

For the demo, this all works in the Oasis Fresh BG: trace any Oasis Mango Juice 1L lot back to the Cairo Citrus concentrate that supplied it.

Supplier halal certificate management

Each supplier in AION can carry:

• Halal certificate document attachment
• Certifying body (SFDA, MUI, JAKIM, GSO-accredited body, etc.)
• Certificate number
• Issue date
• Expiry date
• Renewal contact

A dashboard view shows suppliers with certificates expiring in the next 30/60/90 days. POs to a supplier with an expired certificate trigger a warning or hard-stop, depending on your configuration. Most factories run “warning” for routine suppliers and “hard-stop” for critical halal-sensitive ones.

Production batch records

Every job order in AION produces a batch record showing:

• Job order number, product, quantity
• Date and shift
• Operators involved
• Raw materials issued: item code, lot number, quantity issued
• Routing operations completed
• Output completed: FG item, quantity, output lot number
• QA hold and release events

This record is the audit trail. A halal certification auditor can review any job’s batch record to confirm the lots used were halal-certified at issue time.

A worked recall scenario

Imagine: a consumer in Jeddah reports off-taste in a bottle of Oasis Mango Juice 1L. The bottle’s lot is FG-SA-MNG-1L-2026-0512-A.

In a system without integrated traceability:

• AR team pulls shipment records to find which customer this lot went to
• Warehouse team finds the batch record on paper
• QC reviews raw material lots used
• Procurement contacts suppliers to verify lot integrity
• 4-8 hours elapsed; risk: blanket recall to cover uncertainty

In AION:

• AR clerk searches the FG lot. System shows: produced in job JO-2026-00125, completed 2026-05-12, shipped to Panda Retail Co. and Carrefour Saudi Arabia.
• Click “Where Used (Backward)” — system shows: consumed raw material lots include mango concentrate lot CC-2026-0480 from Cairo Citrus Co.
• Click forward from CC-2026-0480: also used in two other job orders (JO-2026-00127, JO-2026-00134), which became FG lots FG-SA-MNG-1L-2026-0515-B and FG-SA-MNG-1L-2026-0518-A.
• Both other FG lots went to 6 customers total.
• Total elapsed time: under 60 seconds.

Decision: targeted recall of 3 FG lots from 7 customers. The financial damage is contained. The certification audit history shows you handled it correctly.

Halal-specific configuration options

A few AION configurations matter for halal-strict operations:

Halal-required items. Mark items as halal-required. The system will only accept lots from suppliers with a current halal certificate. Issues from non-halal lots are blocked.

Halal segregation by warehouse. If you handle both halal and non-halal products (rare but happens in some factories), warehouses can be configured as halal-only. Cross-warehouse transfers are restricted to prevent cross-contamination at inventory level.

Halal status on customer side. Some customers (large halal-certified retailers, specific export markets) require their inbound to be halal-certified. The sales order workflow can enforce this — orders to halal-only customers can only ship halal-certified lots.

Certificate renewal workflow. Automated reminders to procurement when supplier certificates approach expiry. Configurable lead time (typically 60-90 days before expiry).

What this doesn’t cover

Halal traceability via ERP is a necessary condition but not sufficient. You still need:

• Physical segregation in receiving, storage, and production
• Cleaning and CIP protocols documented
• Staff training on halal handling procedures
• Periodic on-site audit by your certifying body

The ERP supports these by capturing the data; the operational discipline is a factory-floor task.

What changes for the certification auditor

A factory with halal traceability built into AION presents to the auditor differently:

• Audit period (typically annual): the auditor requests records for the period. AION generates the lot-trace reports, supplier certificate listings, and batch records. The auditor reviews them on-screen.
• Random sampling: the auditor picks 5-10 finished-goods lots. The factory traces each end-to-end in minutes.
• Findings: usually zero or minor. The integrated data leaves nowhere for issues to hide.

Contrast with a spreadsheet-driven factory:

• Audit period: 1-2 days of reconstructing chains from binders, spreadsheets, and warehouse memory.
• Random sampling: each requires 30-60 minutes to chase down.
• Findings: typically several — gaps in records, expired certificates that were missed, lots that couldn’t be traced cleanly.

The certification body gives more confidence to the first factory. Insurance rates can reflect this. Customer trust definitely does.

Where to go from here

For Saudi factories, ZATCA Phase 2 e-invoicing covers the tax-side compliance that runs in parallel to halal certification. For multi-country groups, GCC VAT 2026 — multi-country in one ERP covers running across SFDA, JAKIM, MUI, and other halal regimes simultaneously.

For the operational details of running a factory with integrated lot tracking, the costing pillar guide covers how cost flows through the lot-aware inventory layer.