Approve packaging before it is printed, shipped, sold, or changed.
A missing Arabic label block is a container stopped at the port. A missing allergen is a recall. Both are decided at artwork stage — in an email thread, against a spreadsheet nobody version-controls.
PackAuth is the authority layer that catches them before the plates are cut, then holds the approval, the evidence and the release certificate that prove why the pack was cleared.
Cloudflare-first · Stripe-metered · API, agent and widget first
The same error, caught at four stages. PackAuth operates at the leftmost bar — the only one where a fix is a file change.
24lifecycle states, concept to archive
12policy rails gating every consequential action
61deterministic rules — no model guesses a verdict
8approval types, each scoped to real authority
The problem
Packaging approval is the last unowned process in the supply chain
Formulation has a PLM. Production has an ERP. Quality has a QMS. Packaging approval — the decision that legally commits a brand to a claim in a market — runs on email, PDF markup and the memory of whoever has been there longest.
The container that does not clear
Artwork ships to a Gulf market without a complete Arabic label block, or without a registered importer on pack. Goods are produced, palletised, shipped — and stopped. The cost is the freight, the demurrage, the re-label and the retail window you just missed.
The allergen that moved
A supplier reformulates. The spec is updated. The artwork is not — or it is, and the emphasis rule for the destination market is missed. This is the failure mode that ends in a recall notice, and it is a data-reconciliation problem wearing a safety hat.
The claim nobody can substantiate
"Halal", "recyclable", "no added sugar" go on pack because marketing asked and nobody could produce the document that says otherwise. Eighteen months later a regulator asks who approved it, against what evidence — and the certificate expired last spring.
None of these are AI problems. They are authority problems: nobody can say who approved what, against which evidence, for which market, on what date.
The solution
An authority layer, not another label checker
PackAuth does not begin at "upload a PDF". It begins at the manifest: what the product is, where it is going, who is responsible, and what evidence that requires. Artwork is one input to that, checked late — not the thing the process is built around.
Every consequential action passes a rail: an ordered set of checks that must all hold before the action is permitted. No approval without a locked evidence snapshot. No print release without a live, in-scope approval. No release at all while a blocking finding is open.
AI proposes. Rules decide. Humans approve. PackAuth records.
What a model may never do here
Approve packaging
Activate a rule
Override a blocking finding
Issue a print release
Mark evidence legally valid
Grant a stakeholder authority
Models extract, classify, translate and recommend — genuinely useful, and genuinely fallible. The verdict comes from deterministic rules over canonical data; the signature comes from a person who holds the authority to give it.
How it works
Six stages, each one gated
The lifecycle is a state machine with 24 states and 39 legal transitions. An illegal transition is rejected with the attempted edge recorded — never quietly coerced into a legal one.
Every stage names one rail and runs it to completion before acting. Select a stage for detail.
The lifecycle
Every state, and what moves out of it
This is the spine. A manifest sits in exactly one state; an illegal transition is rejected with the attempted edge recorded, never coerced into a legal one. Red states block a release, green states permit one. Select any state for detail.
blocks release release permitted in progressdashed — terminalSelect any state for its transitions.
Staleness is automatic. Eleven change classes demote a live approval back to revalidation required — artwork version, formula or spec, target market, rule pack version, standard version, claim, packaging material, supplier evidence expiry, certification expiry, counterparty suspension, and revocation of the approver's authority. Nobody has to notice.
On the artwork
Every finding points at a place on the pack
A compliance run is not a score. It is a list of locations — this panel, this line, this missing block — each traced to the rule that raised it and the pack that rule was bought with. Select any marker.
One run, one artwork version, one set of target markets. The markers are numbered in reading order; four raised a finding and five cleared.
blockingmajorno finding
The pack drawing is illustrative. Every message, severity, recommendation and pack attribution beside it is read from the rule registry at build time — the generator refuses to build if a marker names a rule the canon does not contain, so this figure cannot drift away from the engine it depicts.
The product
What your team actually looks at
The market matrix answers the only question that matters on a Monday morning: which markets can I print for today, and what exactly is stopping the rest.
The product contains allergens but no allergen emphasis or 'contains' statement was detected.
Emphasise allergenic ingredients within the ingredient list, or add a compliant 'Contains' statement.
allergen_emphasis_present_003 · allergen_pack
blocking
An allergen declared in the formula of record is not declared and emphasised in the artwork ingredient list.
Add the missing allergen to the ingredient list and emphasise it in line with the destination market's emphasis rule.
allergen_formula_to_artwork_001 · allergen_pack · human review
blocking
No minimum cocoa solids percentage declared for a chocolate product.
Declare 'cocoa solids: minimum X%' in the same field of vision as the product name.
choc_cocoa_solids_001 · chocolate_pack
major
The artwork declares an allergen that does not appear in the formula of record.
Confirm whether the formula record is out of date or the artwork over-declares. Reconcile the two before approval.
allergen_artwork_to_formula_002 · allergen_pack · human review
major
One or more ingredient suppliers have no valid allergen declaration on file.
Request an in-date allergen declaration from each ingredient supplier.
allergen_declaration_evidence_005 · allergen_pack
minor
A 'may contain' statement is present without a supporting cross-contact assessment in evidence.
Attach the supplier allergen declaration or cross-contact risk assessment that supports the precautionary statement.
allergen_may_contain_substantiated_004 · allergen_pack · human review
Partial release, immediately
UK and EU print today. Blocked markets stay blocked, and the exclusion is recorded on the approval and carried onto the certificate.
Every finding is actionable
A rule that produces a message without a recommendation fails the build. There is no finding here that leaves a designer guessing.
Uncovered says so
Not a pass, not a fail — where no rules exist, no verdict is offered. That column is the honesty of the whole product in one cell.
Workflow
A food export, end to end, across four parties
The work crosses organisational boundaries constantly — and that is exactly where email loses it. Each lane is a different company; each handoff is a gate that either passes or names what is missing.
The supplier never sees your manifest
A counterparty gets a scoped portal: the request made of them, what they uploaded, its status. Not the findings, not other suppliers, not your other products.
The consultant gets context, not a PDF
Findings arrive with the rule that produced them, the market it concerns, the zone on the artwork, and the recommendation — not an email saying "can you check this".
The printer gets something checkable
A certificate with the artwork hash on it. They verify their own file against it over a public endpoint, with no PackAuth account.
Jurisdictions
Markets resolve through a hierarchy, and coverage is stated honestly
A target market inherits every duty above it. Selecting Saudi Arabia pulls in GCC duties and the global baseline without anyone remembering to. Where PackAuth has no rules for a market, it says so — it never reports a pass for a market it did not check.
6
Nothing matches that filter.
European Union
resolves EU → GLOBAL
1 packs5 rules4 blocking
blocking
Mandatory particulars are not present in the official language of the destination member state.eu_member_state_language_001 · eu_pack
blocking
No EU-established responsible operator address detected.eu_responsible_operator_002 · eu_pack
blocking
EU allergen emphasis duty not satisfied for one or more declared allergens.eu_allergen_emphasis_003 · eu_pack
blocking
No nutrition declaration detected for an EU destination.eu_nutrition_format_004 · eu_pack
Packs applied: eu_pack
Gulf Cooperation Council
resolves GCC → GLOBAL
2 packs12 rules8 blockingar required
blocking
Arabic label block not detected for a Gulf target market.gcc_arabic_label_001 · gcc_pack
blocking
No in-market importer identified on the artwork.gcc_importer_details_002 · gcc_pack
blocking
Country of origin is mandatory for Gulf markets and was not detected.gcc_origin_mandatory_003 · gcc_pack
blocking
Gulf markets expect both production and expiry dates; a single durability date was detected.gcc_production_and_expiry_004 · gcc_pack
blocking
A halal claim or Gulf destination is in play but no valid halal certificate is on file.halal_certificate_present_001 · halal_pack
blocking
The halal certificate has expired or expires before the intended print date.halal_certificate_in_date_002 · halal_pack
Packs applied: gcc_pack · halal_pack
United Kingdom
resolves UK → GLOBAL
1 packs4 rules3 blockingen required
blocking
Mandatory particulars must be in English for the UK market.uk_english_language_001 · uk_pack
blocking
No UK or Northern Ireland responsible business address detected.uk_responsible_address_002 · uk_pack
blocking
UK allergen emphasis duty not satisfied for one or more declared allergens.uk_allergen_emphasis_003 · uk_pack
Packs applied: uk_pack
Saudi Arabia
resolves SA → GCC → GLOBAL
2 packs12 rules8 blockingar required
blocking
Arabic label block not detected for a Gulf target market.gcc_arabic_label_001 · gcc_pack
blocking
No in-market importer identified on the artwork.gcc_importer_details_002 · gcc_pack
blocking
Country of origin is mandatory for Gulf markets and was not detected.gcc_origin_mandatory_003 · gcc_pack
blocking
Gulf markets expect both production and expiry dates; a single durability date was detected.gcc_production_and_expiry_004 · gcc_pack
blocking
A halal claim or Gulf destination is in play but no valid halal certificate is on file.halal_certificate_present_001 · halal_pack
blocking
The halal certificate has expired or expires before the intended print date.halal_certificate_in_date_002 · halal_pack
Packs applied: gcc_pack · halal_pack
United Arab Emirates
resolves AE → GCC → GLOBAL
2 packs12 rules8 blockingar required
blocking
Arabic label block not detected for a Gulf target market.gcc_arabic_label_001 · gcc_pack
blocking
No in-market importer identified on the artwork.gcc_importer_details_002 · gcc_pack
blocking
Country of origin is mandatory for Gulf markets and was not detected.gcc_origin_mandatory_003 · gcc_pack
blocking
Gulf markets expect both production and expiry dates; a single durability date was detected.gcc_production_and_expiry_004 · gcc_pack
blocking
A halal claim or Gulf destination is in play but no valid halal certificate is on file.halal_certificate_present_001 · halal_pack
blocking
The halal certificate has expired or expires before the intended print date.halal_certificate_in_date_002 · halal_pack
Packs applied: gcc_pack · halal_pack
Registered, not rule-packed
classifiable as a target market · produces a clear "not covered" result
no rules
IrelandIE · EU member state.
no rules
GermanyDE · EU member state.
no rules
FranceFR · EU member state.
no rules
United StatesUS · Registered but not yet rule-packed — PackAuth does not claim US coverage.
no rules
CanadaCA · Registered but not yet rule-packed — bilingual duty noted, not enforced.
no rules
AustraliaAU · Registered but not yet rule-packed.
These produce no verdict at all — never a pass. Selecting one as a target market is permitted; claiming compliance for it is not.
Why the honest column matters. A compliance product that reports green for a market it never checked is worse than no product — it converts an unknown risk into a false assurance. Registered markets are classifiable as targets today and produce a clear not covered result, never a pass.
Stakeholders
Nobody here is simply "an approver"
Every stakeholder type holds specific authority scopes, and may only sign an approval those scopes satisfy. A regulatory consultant holding label authority cannot sign a market release. A printer holding print authority cannot approve a halal claim. The system does not rely on people knowing this.
Green dashed — evidence flowing in. Solid blue — releases flowing out. Select any party for what they see and what they can do.
PackAuth does not replace your PLM, your ERP or your artwork tooling. It is the approval and evidence layer between them — the part none of them own.
API first
Every dashboard action maps to a documented endpoint. The screens, widgets, CLI and agent tools are clients of the same contract, never parallel implementations.
Webhooks
Signed with HMAC-SHA256 over timestamp.body. Your systems learn about a blocking finding or an issued release without polling.
Embeddable
Consultants embed the flows into their own client portals. A retailer can validate a supplier's packaging approval before a listing goes live.
The business case
The arithmetic is stage-of-catch, not licence cost
PackAuth does not claim to make compliance cheaper in the abstract. It moves the point of catch earlier — and the cost of a packaging error is dominated by how late it is found, not by how serious it is.
Caught at artwork
A file change
The designer moves a block, the consultant re-approves, the run proceeds on schedule.
Caught at print
Plates + substrate
Origination is re-cut and the material already run is scrapped. Schedule slips into the next slot.
Caught in transit
Freight + demurrage + relabel
Stock is held at the border. Relabelling is manual, in-market, at someone else's rate — and the retail window closes.
Caught on shelf
Withdrawal + remediation
Product comes back. The cost is the stock, the logistics, the customer relationship, and the regulatory record that follows the brand.
Where the time goes back
Evidence chasing — counterparties are asked for exactly what their type and risk require, and expiry is monitored rather than discovered
Re-checking after a change — a material change stales the affected approvals automatically and re-runs only the affected packs
Audit preparation — the answer to "who approved this, on what basis" is stored state, not an archaeology project
Market-by-market re-work — partial approval lets ready markets print while a blocked one is resolved
What it does not do
Replace your regulatory adviser — it routes work to them with the context attached
Guarantee compliance in a market it carries no rules for — it reports that market as not covered
Decide whether a product is halal, or whether a claim is true — it establishes whether the claim is evidenced and by whom
Approve anything on its own — every signature belongs to a person holding the authority
Evidence and replay
An approval is only as good as what it was taken against
Every approval locks an immutable evidence snapshot: the exact documents, their versions, hashed. Asked in eighteen months why a pack was cleared for a market, PackAuth answers with what was true then — not with whatever is on file today.
Artwork content hash, pinned
Formula and specification version
Rule pack and dictionary versions in force
Extraction provider and version
Approver, role, and the authority scope exercised
Audit rows and evidence snapshots are append-only at the database level. Continuous integration attempts an update and a delete on every run and fails the build if either succeeds — a trigger that exists but never fires reads as assurance while providing none.
Why was this package approved for Saudi Arabia on 28 June 2026?
The question the whole architecture exists to answer — with evidence, rules, versions and approver scope, not a recollection.
A pack carries executable rules and a price. That is what makes "Add GCC Pack" a product rather than a button. Buy the market you are entering; the checks appear on the next run.
9
Nothing matches that filter.
Core Packaging Lifecycle PackManifest integrity, artwork versioning, evidence snapshot, approval, print release, change control and audit rules. Every manifest resolves this pack.
enforced12 rules
UK PackUK label duties: English language, UK responsible business address, date marking format, allergen emphasis.
enforced4 rules
EU PackEU label duties: member-state language, EU responsible operator, nutrition declaration format, minimum font size.
enforced5 rules
GCC PackGCC label duties: mandatory Arabic label block, production and expiry date marking, importer identification, country of origin.
enforced5 rules
US PackUS label duties. Catalogued, not yet rule-packed — PackAuth reports US as not covered.
planned
Canada PackCanadian bilingual label duties. Catalogued, not yet rule-packed.
planned
Food Labelling PackMandatory food label elements: legal name, ingredient list, net quantity, date marking, storage, business name and address, country of origin, nutrition declaration.
enforced10 rules
Allergen PackAllergen cross-check between the formula of record and the artwork ingredient list, including emphasis and 'may contain' handling.
enforced5 rules
Cosmetics PackINCI list, responsible person, nominal content, PAO, batch code and warning duties. Catalogued, not yet rule-packed.
planned
Chemical / Hazard PackPictograms, signal word, hazard and precautionary statements, supplier identification. Catalogued, not yet rule-packed.
planned
Medical Device Labelling PackRequired symbols, UDI, authorised representative, intended use, IFU language. Catalogued, not yet rule-packed.
Chocolate and Cocoa PackCocoa solids declaration, reserved product naming, vegetable-fat statement and milk-solids duties for chocolate products.
enforced4 rules
Claims PackDetects claims on artwork and requires each to resolve to approved substantiation evidence permitted in every target market.
enforced4 rules
Sustainability Claims PackRecyclable, compostable, carbon-neutral and recycled-content substantiation. Catalogued, not yet rule-packed.
planned
Halal PackHalal certificate validity, certification-body recognition in the destination market, halal-risk ingredient screen, and mandatory human halal review where risk terms are present.
enforced7 rules
Kosher PackKosher certificate validity and certifying-agency recognition. Catalogued, not yet rule-packed.
planned
Organic PackOrganic certification, control-body code and ingredient-percentage duties. Catalogued, not yet rule-packed.
planned
Packaging Material PackFood-contact suitability, migration evidence, ink and adhesive declarations, and recyclability marking consistency for every declared component.
enforced5 rules
Amazon Marketplace PackMarketplace listing-image and e-label requirements. Catalogued, not yet rule-packed.
planned
Supplier Evidence PackCounterparty document chase, expiry monitoring and scope validation. Catalogued, not yet rule-packed.
planned
Packs with no rules yet are listed as planned and never resolve onto a manifest. A pack that is applicable but unpurchased is reported — the run is never reported clean because a check was unpaid.
Start with the market that is blocking you
PackAuth is opening with food and confectionery exporters shipping into the UK, EU and Gulf — the wedge where the cost of a late catch is a container, not a comment. If your packaging approvals currently live in a spreadsheet and an email thread, we would like to talk.
Selecting a Gulf destination resolves the GCC pack on top of the global baseline.
Arabic label block — the full mandatory particulars in Arabic. This is the single most common export blocker and the reason the pack exists.
Importer identification — the in-market registered importer must appear on pack.
Country of origin — mandatory, in both English and Arabic.
Production and expiry dates — Gulf markets expect both; a single durability date raises a finding.
Importer registration on file — an in-date registration for each Gulf destination.
Saudi Arabia and the UAE inherit all of these automatically by resolving upward to GCC.
The allergen cross-check
The highest-consequence rule PackAuth runs, and deliberately asymmetric.
In the formula, missing from artwork → blocking. Under-declaration is a safety failure. The release stops.
On the artwork, missing from the formula → major, human review. Over-declaration is a commercial problem and may mean the spec is stale. A person reconciles it.
Emphasis duty — where the destination flags a term as a major allergen, an emphasis or "contains" statement must be present.
"May contain" — a precautionary statement with no supporting cross-contact assessment raises a finding.
Canonical allergens are matched through their aliases: whey, casein, lactose all canonicalise to milk; spelt, semolina, malt to gluten cereals. Matching is diacritic-insensitive and word-boundary anchored, so an alias never matches inside a longer word.
Claim substantiation
Every claim detected on artwork or declared on the product must resolve to evidence that is approved, in date, and permitted in every target market.
Unsubstantiated → blocking. PackAuth will not release a claim it cannot evidence.
Market recognition — a halal certificate valid for the UAE does not automatically satisfy Saudi Arabia. The gap is raised per market, not waved through.
High-risk claims route to a reviewer holding legal claim authority.
Detected but not declared — a claim on artwork that is not on the product record is surfaced, because it cannot otherwise be substantiated or approved.
European Union — enforced
EU-wide packaging and labelling baseline. Member-state language duties are resolved at country level.
Resolves EU → GLOBAL
Mandatory particulars are not present in the official language of the destination member state. Provide the mandatory particulars in each destination member state's official language.
No EU-established responsible operator address detected. Add the name and address of the EU-established food business operator or importer.
EU allergen emphasis duty not satisfied for one or more declared allergens. Distinguish each listed allergen from the rest of the ingredient list by typeset, style or background colour.
No nutrition declaration detected for an EU destination. Add the mandatory nutrition declaration per 100 g / 100 ml in the prescribed order.
Gulf Cooperation Council — enforced
GCC standardisation baseline; Arabic is mandatory across member states.
Resolves GCC → GLOBAL · required language(s): ar
Arabic label block not detected for a Gulf target market. Add the Arabic product name, ingredients, allergens, net quantity, origin, manufacturer/importer details and date marking.
No in-market importer identified on the artwork. Add the name and address of the registered importer for the destination market.
Country of origin is mandatory for Gulf markets and was not detected. Declare the country of origin in both English and Arabic.
Gulf markets expect both production and expiry dates; a single durability date was detected. Declare production date and expiry date, in Arabic as well as English.
A halal claim or Gulf destination is in play but no valid halal certificate is on file. Upload the current halal certificate covering this product and site.
The halal certificate has expired or expires before the intended print date. Obtain a renewed halal certificate before releasing artwork to print.
The certifying body on the halal certificate is not evidenced as recognised by every Gulf destination market. Confirm the certifier's recognition status for each destination, or certify with a recognised body.
An alcohol-class ingredient or carrier is present alongside a halal claim. Substitute the alcohol-carried ingredient or obtain explicit certifier sign-off for the carrier level.
United Kingdom — enforced
Great Britain and Northern Ireland packaging and labelling requirements.
Resolves UK → GLOBAL · required language(s): en
Mandatory particulars must be in English for the UK market. Provide the full mandatory particulars in English.
No UK or Northern Ireland responsible business address detected. Add a UK address for the food business operator responsible for the product.
UK allergen emphasis duty not satisfied for one or more declared allergens. Emphasise each of the 14 major allergens within the ingredient list where it occurs.
Saudi Arabia — enforced
Saudi market; Arabic label block mandatory, importer details mandatory.
Resolves SA → GCC → GLOBAL · required language(s): ar
Arabic label block not detected for a Gulf target market. Add the Arabic product name, ingredients, allergens, net quantity, origin, manufacturer/importer details and date marking.
No in-market importer identified on the artwork. Add the name and address of the registered importer for the destination market.
Country of origin is mandatory for Gulf markets and was not detected. Declare the country of origin in both English and Arabic.
Gulf markets expect both production and expiry dates; a single durability date was detected. Declare production date and expiry date, in Arabic as well as English.
A halal claim or Gulf destination is in play but no valid halal certificate is on file. Upload the current halal certificate covering this product and site.
The halal certificate has expired or expires before the intended print date. Obtain a renewed halal certificate before releasing artwork to print.
The certifying body on the halal certificate is not evidenced as recognised by every Gulf destination market. Confirm the certifier's recognition status for each destination, or certify with a recognised body.
An alcohol-class ingredient or carrier is present alongside a halal claim. Substitute the alcohol-carried ingredient or obtain explicit certifier sign-off for the carrier level.
United Arab Emirates — enforced
UAE market; Arabic label block mandatory.
Resolves AE → GCC → GLOBAL · required language(s): ar
Arabic label block not detected for a Gulf target market. Add the Arabic product name, ingredients, allergens, net quantity, origin, manufacturer/importer details and date marking.
No in-market importer identified on the artwork. Add the name and address of the registered importer for the destination market.
Country of origin is mandatory for Gulf markets and was not detected. Declare the country of origin in both English and Arabic.
Gulf markets expect both production and expiry dates; a single durability date was detected. Declare production date and expiry date, in Arabic as well as English.
A halal claim or Gulf destination is in play but no valid halal certificate is on file. Upload the current halal certificate covering this product and site.
The halal certificate has expired or expires before the intended print date. Obtain a renewed halal certificate before releasing artwork to print.
The certifying body on the halal certificate is not evidenced as recognised by every Gulf destination market. Confirm the certifier's recognition status for each destination, or certify with a recognised body.
An alcohol-class ingredient or carrier is present alongside a halal claim. Substitute the alcohol-carried ingredient or obtain explicit certifier sign-off for the carrier level.
The 11 authority scopes
An authority scope is the unit of delegated approval power. A stakeholder may only sign an approval their scopes satisfy.
Marketing claim approval — Sign off on non-regulated promotional claims.
Legal claim approval — Sign off on claims carrying legal exposure or substantiation duty.
Regulatory label approval — Sign off on mandatory label elements for a declared jurisdiction.
Formula / spec approval — Sign off on the product formulation or technical specification of record.
Packaging material approval — Sign off on material suitability, food-contact status and migration evidence.
Translation approval — Sign off on the accuracy of a required-language label block.
Certification mark approval — Sign off on the use of a certification mark or logo under a valid certificate.
Print technical approval — Sign off on print-technical readiness (colour, dieline, resolution, bleed).
Market release approval — Sign off on releasing stock to a declared market and channel.
Supplier evidence approval — Sign off that counterparty evidence is sufficient for the declared scope.
Retailer private-label approval — Sign off on a retailer's private-label packaging requirements.
High-risk scopes may never be self-approved.
Suppliers — material and ingredient
Counterparties see a scoped portal: the request made of them, what they uploaded against it, and its status. Never your manifest, your findings, or each other.
Packaging supplier — default risk medium; owes food contact declaration, material specification, migration test report, quality certificate
Required evidence is derived from type and risk level, never hand-maintained per counterparty. Risk drives the revalidation clock: low 24m · medium 12m · high 6m · critical 3m.
Testing laboratories
Counterparties see a scoped portal: the request made of them, what they uploaded against it, and its status. Never your manifest, your findings, or each other.
Required evidence is derived from type and risk level, never hand-maintained per counterparty. Risk drives the revalidation clock: low 24m · medium 12m · high 6m · critical 3m.
Certification bodies
Counterparties see a scoped portal: the request made of them, what they uploaded against it, and its status. Never your manifest, your findings, or each other.
Certification body — default risk medium; owes accreditation certificate, scope of accreditation
Required evidence is derived from type and risk level, never hand-maintained per counterparty. Risk drives the revalidation clock: low 24m · medium 12m · high 6m · critical 3m.
Printer
Counterparties see a scoped portal: the request made of them, what they uploaded against it, and its status. Never your manifest, your findings, or each other.
Required evidence is derived from type and risk level, never hand-maintained per counterparty. Risk drives the revalidation clock: low 24m · medium 12m · high 6m · critical 3m.
Distributor / importer
Counterparties see a scoped portal: the request made of them, what they uploaded against it, and its status. Never your manifest, your findings, or each other.
Distributor — default risk low; owes distribution agreement
Required evidence is derived from type and risk level, never hand-maintained per counterparty. Risk drives the revalidation clock: low 24m · medium 12m · high 6m · critical 3m.
Retailer
Counterparties see a scoped portal: the request made of them, what they uploaded against it, and its status. Never your manifest, your findings, or each other.
Required evidence is derived from type and risk level, never hand-maintained per counterparty. Risk drives the revalidation clock: low 24m · medium 12m · high 6m · critical 3m.
Approvers
The people whose signature the whole system exists to make meaningful.
No legal product name detected — a brand name alone is not a legal name.
In this run — the element was detected, so the rule ran and produced no finding. A rule that could not run at all would block instead.
What resolves it — Add the name under which the food is legally sold, distinct from the brand.
Severity blocking — Must be resolved before any release. Cannot be waived by the platform. It blocks the print release until it is resolved.
How it is checked — A required element must be present on the artwork.
This check ships with food_label_pack. Without that pack the rule never resolves onto the manifest, and the run reports the check as unpurchased rather than passed.
The artwork carries a claim that is not declared on the product record.
In this run — raised against this artwork version.
What resolves it — Declare the claim on the product so it can be substantiated and approved, or remove it from the artwork.
Severity major — Blocks release but may be dispositioned by an authorised approver with a recorded justification. It blocks the print release until it is resolved.
How it is checked — Two sources must agree — e.g. formula allergens against the artwork ingredient list. A person confirms the outcome; the engine never closes this one on its own.
This check ships with claims_pack. Without that pack the rule never resolves onto the manifest, and the run reports the check as unpurchased rather than passed.
Net quantity
food_net_quantity_003 · Food Labelling Pack · format check
No net quantity in a legal metric unit detected.
In this run — the element was detected, so the rule ran and produced no finding. A rule that could not run at all would block instead.
What resolves it — Declare net quantity in g, kg, ml or l in the principal field of vision.
Severity blocking — Must be resolved before any release. Cannot be waived by the platform. It blocks the print release until it is resolved.
How it is checked — A present element must match a declared pattern (date format, net quantity, batch code).
This check ships with food_label_pack. Without that pack the rule never resolves onto the manifest, and the run reports the check as unpurchased rather than passed.
GTIN barcode
core_barcode_present_010 · Core Packaging Lifecycle Pack · format check
No scannable GTIN detected on the artwork.
In this run — the element was detected, so the rule ran and produced no finding. A rule that could not run at all would block instead.
What resolves it — Add the barcode and confirm it matches the GTIN recorded on the product variant.
Severity major — Blocks release but may be dispositioned by an authorised approver with a recorded justification. It blocks the print release until it is resolved.
How it is checked — A present element must match a declared pattern (date format, net quantity, batch code).
This check ships with core_packaging_lifecycle. Without that pack the rule never resolves onto the manifest, and the run reports the check as unpurchased rather than passed.
An allergen declared in the formula of record is not declared and emphasised in the artwork ingredient list.
In this run — raised against this artwork version.
What resolves it — Add the missing allergen to the ingredient list and emphasise it in line with the destination market's emphasis rule.
Severity blocking — Must be resolved before any release. Cannot be waived by the platform. It blocks the print release until it is resolved.
How it is checked — Two sources must agree — e.g. formula allergens against the artwork ingredient list. A person confirms the outcome; the engine never closes this one on its own.
This check ships with allergen_pack. Without that pack the rule never resolves onto the manifest, and the run reports the check as unpurchased rather than passed.
In this run — the element was detected, so the rule ran and produced no finding. A rule that could not run at all would block instead.
What resolves it — Add a tabular nutrition declaration per 100 g or 100 ml, unless a documented exemption applies.
Severity blocking — Must be resolved before any release. Cannot be waived by the platform. It blocks the print release until it is resolved.
How it is checked — A required element must be present on the artwork.
This check ships with food_label_pack. Without that pack the rule never resolves onto the manifest, and the run reports the check as unpurchased rather than passed.
Arabic label block
gcc_arabic_label_001 · GCC Pack · language check
Arabic label block not detected for a Gulf target market.
In this run — raised against this artwork version.
What resolves it — Add the Arabic product name, ingredients, allergens, net quantity, origin, manufacturer/importer details and date marking.
Severity blocking — Must be resolved before any release. Cannot be waived by the platform. It blocks the print release until it is resolved.
How it is checked — Every mandatory language for the target market must be present in the required label block. A person confirms the outcome; the engine never closes this one on its own.
This check ships with gcc_pack. Without that pack the rule never resolves onto the manifest, and the run reports the check as unpurchased rather than passed.
Date marking
gcc_production_and_expiry_004 · GCC Pack · format check
Gulf markets expect both production and expiry dates; a single durability date was detected.
In this run — raised against this artwork version.
What resolves it — Declare production date and expiry date, in Arabic as well as English.
Severity blocking — Must be resolved before any release. Cannot be waived by the platform. It blocks the print release until it is resolved.
How it is checked — A present element must match a declared pattern (date format, net quantity, batch code). A person confirms the outcome; the engine never closes this one on its own.
This check ships with gcc_pack. Without that pack the rule never resolves onto the manifest, and the run reports the check as unpurchased rather than passed.
No responsible business name and address detected.
In this run — the element was detected, so the rule ran and produced no finding. A rule that could not run at all would block instead.
What resolves it — Add the name and address of the food business operator responsible in the destination market.
Severity blocking — Must be resolved before any release. Cannot be waived by the platform. It blocks the print release until it is resolved.
How it is checked — A required element must be present on the artwork.
This check ships with food_label_pack. Without that pack the rule never resolves onto the manifest, and the run reports the check as unpurchased rather than passed.
Regulator / auditor
The party who arrives eighteen months later and asks the question the architecture was built for.
The replay context — manifest version, artwork hash, spec version, evidence snapshot, pack versions, dictionary versions, extraction provider and version.
Immutable — audit rows and evidence snapshots are append-only at the database level, and CI attempts an update and a delete on every run to prove the triggers fire.
What was true then — the snapshot answers with the evidence as it stood at approval, not whatever is on file today.
Honest scope — for a market with no rules the record shows "not covered", never a manufactured pass.