Applicability comes before the condition
Not every rule applies to every product. A check tied to an ingredient, product category or particular claim first needs evidence that its trigger is present. When the trigger is reliably absent, the check is outside scope.
For example, a sweetener-related statement should not be required merely because a product name happens to match a broad term. If ingredients or the relevant statement cannot be read, applicability may remain uncertain and require review. Draft rules are not the same as active checks.
Ingredients, allergens and statements
The ingredient list, allergen statements, their relationship to the product name and conditional statements are evaluated using readable label text. Finding a word and verifying its required visual emphasis are separate evidence questions.
Even when an allergen word is extracted, its bold or distinctive printing may not be verifiable from every source. A visual review is then needed. Recipes and production records confirming the actual composition cannot be derived from the packaging image alone.
Net quantity, units, ℮ and origin
Quantity checks need the number, unit and context together. “100 g” in a nutrition table, a serving size or an ingredient percentage must not be treated as the product’s net quantity. Conflicting readings should not be combined into an invented value.
Origin, business address and producer information are separate fields. A country in an address does not by itself confirm an origin statement. If a panel is missing or its wording cannot be read, compare the report’s detected and expected evidence.
The ℮ symbol and its relationship to quantity are reviewed according to the active rule’s conditions. Read the rule source and explanation as well; distinguish an internal checking requirement from its legal basis.
Nutrition information and numerical consistency
Checks examine nutrient names, order, units and values that can be extracted reliably. Fields such as energy, fat, saturates, carbohydrate, sugars, protein and salt are evaluated against the relevant configuration.
Decimal separators, column headings and the “per 100 g / 100 ml / serving” context change what a number means. An uncertain digit or decimal separator in a low-resolution image can affect an entire calculation. Unreliable values should not support a definite numerical conclusion.
Product-specific checks
Chocolate, fruit juice, milk and dairy products can require different information and conditions. Product category, naming and ingredients must be established sufficiently before a category-specific conclusion can be made.
Examples include cocoa-related statements for chocolate, the actual category of a fruit drink, or the relationship between a dairy product’s name and composition. A check is reported only when the relevant rule is approved and active and the available evidence brings the label within its scope.
These examples do not imply that every category regulation or exception is configured or automatically verified. Assess the report against the rule version that was actually run.
Language consistency and evidence beyond the label
When Turkish and English text is detected, language checks appear in separate sections. Shared numerical fields and statements may be compared. Changing the interface language does not change the country’s regulations applied by the system.
Recipes, laboratory certificates, actual package dimensions, printed character size and production or traceability records may be absent from the uploaded file. The report should identify additional evidence or review needed. A preliminary report is not a certificate of compliance with every regulation.