How to create an FDA-compliant Nutrition Facts label from your recipe

If you sell packaged food in the United States, you owe consumers a Nutrition Facts panel under section 403(q) of the FD&C Act, implemented by 21 CFR 101.9. What surprises most founders is what the rule does not say: it never tells you how to produce the numbers. There is no requirement to send your product to a laboratory, and there is no pre-approval office that stamps your label before it ships. What the rule does instead is judge the finished product — and that changes how you should think about the whole exercise.

Calculation is a recognized basis — here is the actual legal footing

21 CFR 101.9(g) defines compliance by outcome: if FDA samples your product from the market and analyzes it, the analyzed values must sit within defined tolerances of what your label declares. The regulation is method-neutral about how you arrived at those declared values — laboratory analysis, database calculation from the recipe, or a mix are all legitimate paths, and 101.9(g)(8) expressly contemplates values computed from a nutrient database. FDA even published a dedicated guidance for this route — the 1998 Guide for Developing and Using Data Bases for Nutrition Labeling — which states that the selection of a data source for label values is the manufacturer's prerogative.

One honesty note, because some tools blur it: 101.9(g)(8) describes a voluntary safe-harbor procedure in which FDA agrees to a database in writing, and the rule says such agreement is granted where a clear need exists — the examples are raw produce and seafood. In practice, no commercial database used for general processed foods carries that written agreement. So be suspicious of any vendor implying its numbers are "FDA approved" — that status effectively does not exist for this product category, ours included. Calculation is lawful and standard practice; the compliance question is always whether the finished product matches the label within the (g) tolerances, and that responsibility stays with the food business operator no matter which method produced the numbers.

The parts of the panel you don't get to choose

A recipe calculation is only step one. Most of the citations we see on warning letters and in private lawsuits concern the format and basis rules, which are deterministic and unforgiving:

• Serving size is not your call. It derives from the RACC — the Reference Amounts Customarily Consumed table in 21 CFR 101.12, roughly 140 food categories. You express it as a household measure (cups, pieces) with the gram weight in parentheses, and even the increments are prescribed.
• Dual columns can be mandatory. If your package holds between 200% and 300% of the RACC, 101.9(b)(12)(i) requires two columns: per serving and per container.
• Rounding is regulated, nutrient by nutrient. Calories under 5 declare as zero; up to 50 they round to the nearest 5; above 50, to the nearest 10. Fat has its own ladder, sodium another, and the vitamin and mineral %DVs round in 2, 5 or 10 percentage-point steps depending on level (101.9(c)). Declaring an unrounded value is itself a form error.
• The format itself is specified down to point sizes, bolding and rule weights in 101.9(d) — the panel is effectively a statutory drawing, not a design suggestion.

Added Sugars: the number a lab cannot hand you

Since the 2016 rewrite of the panel, you must declare "Includes Xg Added Sugars" with its own %DV. Here is the catch: chemically, added sucrose and the sucrose that was already in your fruit are the same molecule. A laboratory can measure total sugars in a sample, but it cannot tell you which grams were added — that is a fact about your formulation, not about the sample. The only defensible way to produce the Added Sugars line is to derive it from the recipe itself: which ingredients contribute sugars, and which of those are added within the meaning of 101.9(c)(6)(iii). For this line item, recipe-based calculation is not the budget alternative to analysis — it is the direct method.

Where the real risk lives, and what defends you

There is no pre-market gate in the US system. Enforcement happens afterward, through two channels. The first is FDA itself: market sampling against the (g) tolerances — added ("Class I") vitamins, minerals, protein and fiber must be present at 100% of the declared value or more, naturally occurring ("Class II") nutrients at 80% or more, and the third group (calories, sugars, fats, sodium) must not exceed 120% of the declaration. The second channel is faster and, for small brands, often scarier: class-action litigation over label accuracy, a genuinely American phenomenon where the plaintiff's bar samples products off the shelf.

Both channels reward the same thing: documentation. If a challenge arrives, "our software said so" is not a position. "Here is the database version, the match for each ingredient, the yield and retention adjustments, the rounding rule applied to each line, and the provision each step relied on" — that is a position. Whatever tool or consultant you use, insist on receiving that trail, not just the artwork.

When a lab analysis is still advisable

Calculation and analysis are complements, not rivals. A confirmatory analysis is worth budgeting when:

• your process introduces high variability — deep-frying (oil uptake), fermentation, grilling and heavy browning shift composition in ways database math approximates less well;
• a declared value sits close to a claim threshold or a tolerance boundary, where a few analytical grams decide the outcome;
• a buyer, retailer or co-packer contractually requires one.

The pattern that works for most small manufacturers: calculate first to design the recipe and get to market, then verify analytically where the risk concentrates — and recalculate, rather than re-test, on every reformulation in between.

One trap worth knowing before you print a claim

Many small businesses are exempt from nutrition labeling under 101.9(j) — until they make any nutrient claim. Print "Sugar Free" on the bag and the exemption is gone: you now owe a full, correctly formatted panel, plus the claim itself must satisfy its own thresholds (101.60(c) for sugar claims; the general architecture lives in 101.13 and 101.54–101.69, including "See nutrition information for…" disclosure statements when certain nutrients run high). Claims are where labeling stops being a formality and becomes a chain of interlocking rules.

---

FoodFact computes US Nutrition Facts panels from your recipe using USDA FoodData Central, applies the RACC, dual-column, rounding and format rules above, and issues a legal-basis report that cites the provision behind every value — the documentation trail this post is about. If a US label is on your to-do list, you can see exactly what one order produces on the United States page.

This article is general information about US labeling rules, not regulatory advice. The final labeling decision, and responsibility for the finished product, rests with the food business operator.