Continuous evidence, not a yearly scramble

Every delivery, connected to the evidence behind it.

HalalOps links suppliers, products, certificates, deliveries and handling records into one chain per branch — and tells you, in plain terms, the moment a link stops holding up.

8
Versioned evidence rules
5
Links in every chain
0
Silent deletions

Evidence chain

1 link broken

Supplier

Bayt Foods

Linked to a confirmed record

Product

BCF-100

Linked to a confirmed record

Certificate

Expired 14 Aug

R-002 — certificate validity ended before the delivery date

Delivery

DN-40219

Linked to a confirmed record

Branch

Whitechapel

Linked to a confirmed record

What HalalOps holds

Four of five links are backed by a confirmed record. The certificate link is expired, so this delivery is marked Attention required.

Goods-in to record

One capture at the back door becomes a permanent, linked record.

Explainable exceptions

Every failure names the rule, the records and both values.

Status, never verdict

HalalOps reports the evidence it holds. It certifies nothing.

The problem

Halal evidence is real work, kept in scattered places.

Restaurant groups already collect what they need. It just never sits in one connected record that anyone can read back.

Layered certificate documents

Today

Paper everywhere, connections nowhere.

Certificates in four places

Inboxes, a shared drive, a WhatsApp photo and a folder behind the pass. Nobody is sure which copy is current.

Expiry noticed too late

A certificate lapses quietly. Deliveries keep arriving against it for weeks before anyone checks.

Substitutions go unrecorded

A supplier sends a different product code. The delivery note is signed, and the difference is never written down.

Audit week is archaeology

Reconstructing twelve months of evidence from memory and scattered files, under time pressure.

How it works

From the goods-in door to a defensible record.

Four steps your team already takes, recorded once and connected for good.

Kitchen staff checking a delivery note at the goods-in door
01

Receive the delivery

Goods-in records the supplier, products and codes on the note. A halal delivery issue — substitution, unexpected supplier, packaging discrepancy — can be captured with a photo, without leaving the flow.

02

Capture the paperwork

Certificates and delivery notes are uploaded as PDF, JPEG or PNG. Assisted capture suggests the fields; an administrator or compliance manager confirms or corrects them. Originals are never discarded.

03

Run the evidence check

Deterministic rules compare the delivery against confirmed records only. Each item comes back as confirmed, pending review, attention required or missing.

04

Work the exceptions

Every failure becomes an explainable exception with the exact records and values. Assign it, attach evidence, close it with a reason — and it reopens by itself if the same rule fails again.

The rulebook

Eight rules. Versioned, deterministic, explainable.

Every run stores the rule version, the subject, the facts it used, the result and the time. Unconfirmed extracted values are never treated as facts — they come back as pending review, not as a pass or a fail.

HalalOps does not make any religious or halal determination. It reports the state of the evidence it holds.

  • R-001

    No certificate on record for the product

  • R-002

    Certificate has expired

  • R-003

    Product falls outside the certificate schedule

  • R-004

    Product code on the delivery does not match

  • R-005

    Delivery date sits outside certificate validity

  • R-006

    Supplier is not approved for this branch

  • R-007

    Confirmed fields conflict with each other

  • R-008

    Required handling record is missing

Trust profile

Share what you choose, and nothing else.

A branch trust profile moves through draft, approved and published. Only approved fields appear on the public page, alongside the date they were last reviewed.

  • Public page reads only approved, published fields — never your private records.
  • Auditors get a secure, time-limited read-only link with access logging.
  • Unpublish at any time; history of what was shown is kept.
Central BranchPublished
Evidence on record
Supplier approvals, certificates, handling records
Certification body
Halal Assurance Council
Last reviewed
21 September 2026

This profile describes the evidence HalalOps holds for this branch. It is not a certification and not a religious ruling.

Roles

Four roles, scoped to one organisation.

Access is resolved on the server before any record is read. Hiding a button is never the access control.

Organisation administrator

Every private record in the organisation: branches, users, invitations, roles, branch scope and policy.

Compliance manager

Evidence review, field confirmation, exceptions, reports and the trust profile, across all or assigned branches.

Branch manager / staff

Assigned branches only: uploads, deliveries, handling records and assigned actions. Cannot confirm extracted critical fields.

Auditor / reviewer

No portal account. Receives a secure, time-limited read-only report or evidence-pack link.

From the floor

Written by the people doing goods-in.

The delivery check caught a product code that did not match the certificate schedule. Ten minutes at the back door instead of ten hours in audit week.

Amina Yusuf

Operations director, four-site group

Exceptions explain themselves. The record it failed against is right there, with both values, so the supplier conversation is a short one.

Daniel Okafor

Compliance manager

Staff upload a photo of the note and get on with service. Nobody is chasing a folder any more.

Sara Rahman

Branch manager

FAQ

Straight answers.

See the evidence chain with real records in it.

The demo portal is loaded with a four-site restaurant group, live exceptions and a published trust profile.