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.
1 · Classify and target
Product resolves to a category and sector. Target markets resolve upward — Saudi Arabia inherits GCC, which inherits the global baseline.
2 · Resolve packs
Applicable rule packs are derived, not chosen. Packs that would apply but are unavailable are named, so coverage is never quietly overstated.
3 · Collect evidence
Counterparties are asked for exactly what their type and risk level require. Expiry is monitored, not discovered.
4 · Check deterministically
Artwork is extracted and canonicalised first. Rules then run over stored facts — same inputs, same findings, every time.
5 · Approve with scope
An approval names the artwork hash, evidence snapshot, pack versions and the markets it covers — and the ones it does not.
6 · Release and hold
The printer gets a certificate they can verify against their own file. Any material change stales the approval automatically.
The lifecycle
Twenty-four states, thirty-nine legal transitions
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 what
it means and what moves out of it.
blocks release release permitted in progressdashed — terminal
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.
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.
packs: core · food · allergen · claims · uk · gcc · halal · material
blocking
Arabic label block not detected for a Gulf target market.
Add the Arabic product name, ingredients, allergens, net quantity, origin, importer details and date marking.
gcc_arabic_label_001 · SA · back_panel
blocking
A food-contact component has no valid migration evidence.
Request the declaration of compliance and migration test report from the component supplier.
material_food_contact_evidence_001 · cmp_film
blocking
Country of origin is mandatory for Gulf markets and was not detected.
Declare the country of origin in both English and Arabic.
gcc_origin_mandatory_003 · SA
major
Certifying body is not evidenced as recognised in Saudi Arabia.
Confirm the certifier's recognition status for each destination, or certify with a recognised body.
halal_body_recognised_003 · SA · human review
minor
Recycling mark present but metallised film is not kerbside recyclable.
Correct the mark to match the construction, or substantiate the recyclability claim.
material_recycling_mark_consistent_004
Partial release, immediately
UK and EU print today. Saudi Arabia and the UAE 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.
US says "not claimed"
Not a pass, not a fail — no rules exist, so 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 below 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.
USUnited StatesNot covered
CACanadaNot covered
AUAustraliaNot covered
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. US,
Canada and Australia are classifiable as target markets today and produce a
clear not covered result, never a pass.
What is actually checked
Mandatory particulars
Legal name · ingredient list · net quantity · date marking · storage · responsible business address · country of origin · nutrition declaration
Allergens
Formula-to-artwork cross-check across 14 canonical allergens and their aliases, with market-specific emphasis duties
Language
Mandatory language per destination, including full Arabic label blocks for Gulf markets
Claims
18 canonical claim families, each requiring approved substantiation permitted in every target market
Certification
Halal certificate validity, certifying-body recognition in the destination, ingredient risk screening
Materials
Food-contact suitability, migration evidence, ink and adhesive declarations, recycling marks that match the construction
Stakeholders
Nobody here is simply "an approver"
Twenty-three stakeholder types, eleven authority scopes. 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.
A scoped portalcounterparties see their request and nothing else
A verifiable certificateprinters check their own file against the released hash
An audit answerregulators get evidence, versions and approver scope
Integration
It sits between the systems you already run
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
Thirty-one documented endpoints. Every dashboard action maps to one; 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.
Jurisdiction
UK · EU · GCC — Arabic label block, importer identification, origin, production and expiry marking.
Sector
Food labelling and the allergen cross-check between the formula of record and the artwork ingredient list.
Certification
Halal — certificate validity, body recognition in the destination market, ingredient risk screening.
Every claim must resolve to approved substantiation permitted in every target market.
Material
Food-contact suitability, migration evidence, and recycling marks that match the actual construction.
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. Five rules execute, four of them blocking.
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.
Fourteen 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.
Eighteen canonical claim families are recognised, from certification (halal, kosher, organic) through nutrition and environmental claims.
United Kingdom — enforced
Layered on top of the food labelling pack, the UK pack asserts how the mandatory particulars must appear.
English language for all mandatory particulars
A UK or Northern Ireland responsible business address
Allergen emphasis within the ingredient list for each of the 14 major allergens
Date marking in a recognised format with the correct durability wording
Minimum 1.2 mm x-height on mandatory particulars
European Union — enforced
Member-state language duties are resolved from the destination country row rather than hardcoded, so one country row carries one language duty.
Mandatory particulars in the official language of each destination member state
An EU-established responsible operator or importer address
Allergen emphasis distinguished by typeset, style or background colour
Nutrition declaration per 100 g / 100 ml in the prescribed order
Minimum 1.2 mm x-height
Gulf Co-operation Council — enforced
A regional baseline that every Gulf country inherits. Arabic is mandatory across member states.
Full Arabic label block covering the mandatory particulars
In-market importer identification
Country of origin, mandatory
Production and expiry date marking
In-date importer registration per destination
Saudi Arabia and the UAE resolve upward to this pack automatically.
Saudi Arabia — enforced
Resolves upward through GCC to the global baseline, so all Gulf duties apply without being restated.
Arabic label block — blocking
Registered in-market importer — blocking
Country of origin in English and Arabic — blocking
Production and expiry dates — blocking
Certification recognition — a certificate must be evidenced as recognised for this destination specifically
Certification-body recognition is checked per market: a body accepted elsewhere in the Gulf is not assumed acceptable here.
United Arab Emirates — enforced
Resolves upward through GCC to the global baseline.
Arabic label block — blocking
In-market importer identification — blocking
Country of origin — blocking
Production and expiry date marking — blocking
Importer registration on file
Suppliers — material and ingredient
Evidence providers. They never see your manifest, your findings, or each other.
What they owe — derived from their type and risk level, never hand-maintained. A packaging supplier owes a food-contact declaration, material specification, migration report and quality certificate.
What they see — a scoped portal: the request made of them, what they have uploaded against it, and its status.
Risk drives the clock — low risk revalidates every 24 months, medium 12, high 6, critical 3.
Suspension propagates — suspending a counterparty invalidates every approval that relied on its evidence, immediately.
Testing laboratories
Producers of the reports that make a material claim defensible.
Migration test reports — 36-month validity, and flagged as requiring human validation because sufficiency is a judgement, not a field.
Certificates of analysis — 12-month validity, extracted for batch, analyte and result.
Nutrition analysis — required whenever a nutrition declaration appears on pack.
Accreditation — the lab's own accreditation and scope are themselves evidence types with expiry.
Certification bodies
Halal, kosher, organic. The certificate is not the end of the question — recognition is.
Validity — an expired certificate blocks, and one expiring before the intended print date is surfaced before you commit plates.
Recognition per market — a body accepted in the UAE is not assumed acceptable in Saudi Arabia. The gap is raised per destination.
Mark usage — using a certification mark on artwork requires confirming the mark belongs to the body named on the certificate and is licensed for that SKU.
They hold authority — certification bodies can be granted certification_mark_approval and sign for it.
Printer
The party with the most to lose from an approval that is not what it appears to be.
Gets a certificate carrying the artwork hash — not an email saying "approved".
Can verify without an account — a public endpoint takes the hash of the file they are about to plate and confirms whether it matches the released artefact.
Sees the scope — which markets the release covers and which are explicitly excluded.
Holds print technical authority — colour, dieline, resolution and bleed are theirs to sign; regulatory content is not.
Distributor / importer
Often the legally responsible party in the destination market, which makes their evidence load-bearing.
Importer registration — an in-date registration is required per Gulf destination before market release passes.
Named on pack — the Gulf pack blocks release if no in-market importer is detected on the artwork.
Market release scope — a release names the exact markets, channels and SKUs it covers, with a quantity limit where one applies.
Retailer
Both a gate on your product and, for private label, a source of requirements of its own.
Validates supplier approval — a retailer can check that a supplier's packaging carries a live release before a listing goes live.
Private label — retailer requirement packs sit alongside jurisdiction packs, and retailer_private_label_approval is its own authority scope.
Channel duties — marketplace and private-label channels add duties on top of the resolved country.
Approvers
Regulatory consultant, QA manager, legal reviewer, export manager. The people whose signature the whole system exists to make meaningful.
Scoped authority — each holds specific authority scopes and may only sign approvals those scopes satisfy.
Context, not a PDF — findings arrive with the rule that produced them, the market, the artwork zone and a recommendation.
Separation of duties — legal claim, regulatory label, certification mark and market release approvals may never be self-approved.
Their decision is pinned — approver, role and the authority scope exercised are recorded on the approval permanently.
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 with whatever is on file today.
Honest scope — for a market with no rules, the record shows "not covered" rather than a manufactured pass.
The eleven authority scopes
An authority scope is the unit of delegated approval power. A stakeholder may only sign an approval their scopes satisfy.