Halal food verification breaks down when every result is forced into a shallow yes-or-no verdict. A product may have a direct certifier record. It may only have company-level context. It may exist in the product catalog without any reliable halal claim attached yet. Those are different states, and a serious platform has to preserve the difference between them.
Tayyib treats identity first and verdict language second. The barcode or GTIN is resolved into a product record. Only then does the system ask what kind of halal evidence is attached to that record, whether the evidence is current, and whether the evidence belongs to the product itself or only to a wider company context.
What Tayyib keeps distinct
- Direct product certification remains stronger than company-level certification context.
- Expired or suspended records remain visible as expired or suspended rather than being treated as active.
- Unknown remains unknown when the dataset does not yet justify certainty.
“So ask the people of knowledge if you do not know.”
Qur'an 16:43
The point is not to make the scanner feel dramatic. The point is to make it honest. That honesty is what allows the public product scanner to become more useful over time as stronger certifier data is added.
Why the scanner sits inside a wider Tayyib surface
People do not only need a barcode tool. They also need context around ingredients, manufacturing ambiguity, label reading, and what counts as strong evidence. That is why Tayyib is being built as a knowledge surface with a scanner inside it, not as a disconnected utility with no explanatory layer.