01 · For product developers

Find the constraints before you commit to the recipe

A brief is not a label, so we do not pretend to judge one. Tell us the species, the claim you want to make and the markets you have in mind, and you get an envelope back: what is permitted, what the ceilings are, and which wording is allowed in each language you will print.

NO ARTWORK, NO ACCOUNT · NO CARD · NO SALES CALL · FREE NEVER EXPIRES

What runs today

From a brief alone — species, class, markets — /envelope names the rules that will judge the product in each market, which of them are not in force yet, and which of those markets we hold nothing for. No artwork and no account. Upload artwork or photograph a pack and every label rule we hold runs against it, per market and per language.

Two halves of the envelope need encoded content rather than code, and are not in the product yet: inclusion ceilings per ingredient and additive, and the permitted wording for a claim in each language you will print. We would rather say that than hand you an almost-empty sheet that reads as nothing to worry about.

The compliance question arrives too late to be cheap

  • The claim was in the brief

    Marketing wrote it, the recipe was built around it, and nobody asked whether it is permitted in French until the artwork came back from the agency.

  • The ceiling was found by failing it

    An inclusion level is only obviously too high once somebody checks it against the market you are launching in, and by then the trials are done.

  • The answer came as a PDF opinion

    Six weeks, a consultant's day rate, and a document that answers the question you asked in June about the recipe you had in June.

How a brief works

Partial input in, a design envelope out

Every field is optional except the species and one market. The envelope gets tighter as you fill more in, and it says which parts are still open.

  1. 01

    Say what you know

    Species, life stage, the product class you have in mind, target markets, and the claims you want to make.

    Partial input accepted

  2. 02

    See what will judge it

    Every rule we hold that would apply to this species, class and market — by domain, before any artwork exists.

    Never a verdict: nothing has been checked

  3. 03

    See where we hold nothing

    A market with no applicable rule is named, not omitted. Zero rules is us having nothing to say, never a clean sheet.

    The row worth reading

  4. 04

    Get the ceilings and the wording

    Permitted inclusion levels per additive, and the approved phrasing for your claim in each language you will print.

    Needs encoded content — in build

The part nobody else does

A claim is checked in the language it will be printed in

A prescribed legal term is a lookup, not a translation. Checking your English copy and translating the verdict is how a compliant product ships with an illegal French panel, so we hold the permitted wording per market and per language and check against that.

  • ClearApproved wording for a joint-function claim in German, quoted from the glossary version it came from.
  • Action neededNo permitted wording for the same claim in France on this product class. Stated as prohibited, with the article.
  • Not assessedItalian wording extracted but not yet accepted, so it is offered as unverified rather than as approved.

What we will not do here

  • Give a verdict on a product that does not exist yet
  • Translate a prescribed legal term
  • Guarantee a formulation will be authorised
  • Submit anything to an authority
  • Confirm a registration is valid

An envelope tells you where the walls are. It does not tell you the room is approved.

Design against the constraints, not around a rejection

Start with a brief and keep the same record all the way to the printed label. The brief becomes the product, the product keeps its history, and the first label check runs against the same object you started with.