Structured ingredient statements, from recipe to package

Sub-recipes become parenthetical sub-ingredients

Compound ingredients need their components declared. When a recipe contains a sub-recipe (your own sauce, dough, or seasoning blend), the generated statement names the component and unpacks its ingredients in parentheses, each internally sorted by weight: "teriyaki glaze (soy sauce, brown sugar, ginger)". That is the parenthetical style FDA describes for declaring an ingredient's own ingredients.

Because the sub-recipe is a first-class object in your library, updating its formula once updates every parent product's statement everywhere it appears. No hunting through SKUs to fix a sauce reformulation, and no risk that one package ships with last quarter's ingredient breakdown while another ships with this quarter's.

A live preview of the printed line

Below the ingredient rows sits the exact statement your package will carry, rendered in the same typography as the label preview and updated on every keystroke. There is no "generate" button to remember to press and no stale text to reconcile: what you see is what prints.

A one-click Copy button puts the finished string on your clipboard for use in external design tools, spec sheets, or a co-packer's artwork brief.

Manual override when the rules need bending

Real-world statements are not always a pure weight sort. "Contains 2% or less of…" groupings, collective names permitted by regulation, a legacy statement your reviewer already approved: there are legitimate reasons to hand-craft the text. Toggle the override and the statement becomes an editable field; the label prints your version verbatim.

Crucially, the override is non-destructive. The auto-generated statement keeps computing in the background, so toggling the override off restores it instantly, and your hand-written version is preserved if you toggle back. You get an escape hatch without losing the machine-checked baseline, the same philosophy behind manual overrides on the nutrition panel.

Allergens declared alongside, not separately

The ingredient statement and the allergen declaration are two halves of one compliance story. NFL tracks each ingredient's allergen profile (down to the named species required for tree nuts and fish) and generates the "Contains:" line that prints immediately after the statement, exactly where FDA expects it.

Because detection runs off the same ingredient rows, adding "soy lecithin" to the recipe updates both the statement and the allergen declaration in one motion; nothing depends on you remembering to edit two places. Species-level tracking, jurisdiction-specific allergen lists, and precautionary "may contain" advisories are covered in depth on the allergens feature page.

One source of truth, through to print

Edits in the Ingredients tab flow straight through to the printed label; there is no separate statement field to keep synchronized, and no copy-paste step where an old version can sneak onto new packaging. The recipe is the single source of truth for the nutrition panel, the ingredient statement, and the allergen declaration alike.

Everything is versioned to your account by cloud autosave, so the statement you approved is the statement that exports, as part of the label PDF, PNG, SVG, or vector file. Questions about statement formatting, type size, or placement? Start with the labels FAQ, or open the generator and watch the line build itself.