Nutrition facts labels for bakeries

$39 one time, 90 days of edits. $69/mo for unlimited labels and unlimited revisions.

Build My Label

The bakery problem is arithmetic

Nobody sells one baked good. A working bakery has a dozen breads, two dozen pastries, cookies in four flavors, seasonal pie, and three cake sizes. Each is a separate product with its own ingredient statement and its own Nutrition Facts panel. A different pan size is often a different panel.

Then the recipes move. Pumpkin in October, peppermint in December, stone fruit in July. You swap butter suppliers and the fat profile shifts. You cut sugar in the sourdough because a buyer asked. Under per-panel pricing, each of those is a new invoice.

Recipe Cost Calculator's published figure for external lab analysis is $50–$300 per recipe, per revision. That per-revision line is what quietly does the damage, because a bakery reformulates more than almost any other food business.

Unlimited revisions is the reason to subscribe. Not unlimited labels — revisions. Changing the seasonal muffin should cost four minutes, not $40 and a two-week wait.

When labeling actually becomes mandatory

Wholesale. The cafe, the co-op, the grocery buyer. This is the growth path for nearly every bakery that grows, and the moment the retail-bakery exemption stops applying, because the customer is no longer buying from where you baked it. State cottage food exemptions don't help either — almost all are direct-to-consumer only, and even where third-party retail is legal the purchase order asks for a panel. One narrow carve-out sits at 21 CFR 101.9(j)(9): bulk product shipped to another manufacturer for further processing is exempt, since it never reaches a consumer in that form. Par-baked dough sold to a restaurant can qualify. A boxed dozen with your sticker does not.

Claims. "High fiber," "low sugar," "protein cookie." Any nutrient content claim requires the panel that substantiates it, and under 21 CFR 101.9(j)(18) the exemption is void if the claim appears in advertising — your menu board, your Instagram, your sell sheet.

Packaged for someone else's shelf. A sealed bag in another store is a packaged retail food, not a case sale.

The Ohio exception worth knowing about

Ohio runs two separate home food tracks, and confusing them is the most expensive mistake a baker there makes. Cottage food is uninspected, unregistered, free, and limited to twenty categories. A home bakery under ORC 911.02 is a registered bakery that happens to be in a house: $10 a year, renewed by September 30, against $200 for a standard bakery registration, plus an ODA inspection. That buys you cheesecake, cream pie, filled donuts, raw dough, egg noodles, and cream cheese frosting — the refrigerated items cottage food shuts you out of. Neither track requires a Nutrition Facts panel. Full detail: Ohio cottage food and home bakery rules.

Serving sizes will surprise you

You don't choose your serving size. It comes from the Reference Amount Customarily Consumed table in 21 CFR 101.12, which FDA set from consumption survey data, not from how you portion. Two consequences hit bakeries specifically.

A "serving" is often a fraction of what you sell. Cakes, loaves, and large pastries routinely declare a serving that is a slice, with servings per container above one. Customers read the calorie number as the whole item. It isn't, and the panel is still correct.

An oversized single unit can force a dual-column panel. When a discrete unit a person could reasonably eat in one sitting contains 200% to 300% of the RACC, FDA requires both per-serving and per-unit columns. Here are the reference amounts that decide it:

Cookies are where this bites hardest. At a 30 g reference amount, one large bakery cookie weighing 60 to 90 g is already a dual-column product, and plenty of them weigh exactly that.

Muffins are the opposite of what most bakers assume. At 110 g, a standard bakery muffin is about one serving, and even a jumbo at 180–200 g stays under the 200% threshold. It takes a genuinely large muffin — 220 g and up — to trigger the second column. Weigh yours before you assume it either way.

Cakes and loaves usually run past 300% of the RACC, which puts them outside the dual-column band entirely. They are ordinary multi-serving products: a slice is the serving, and servings per container is above one.

Scones, cinnamon rolls, and sweet rolls sit in their own Table 2 categories rather than under muffins, so look yours up instead of borrowing the 110 g figure.

Reference amounts from 21 CFR 101.12, Table 2, Bakery Products category. Verified August 2026 against the GPO annual edition of Title 21 (CFR-2025-title21-vol2). Category wording abbreviated where noted; check the full text for your exact product.

This isn't cosmetic. Missing dual-column labeling on multi-serving products is a documented trigger for Amazon detail-page suppression, and a grocery buyer's compliance review catches it.

How it works

1. Get the recipe in. Photograph the card, paste your production sheet, or type it. The AI reads bakers' shorthand and converts cups, tablespoons, and "one scoop" into FDA units.
2. Confirm ingredients against the database matches.
3. Set batch yield and unit count. Serving size comes from the RACC table; dual-column is detected, not left to you.
4. Download PNG, PDF, and print-ready SVG. Then save the product and re-run it when the recipe changes — that's what the subscription is for.

What you get

• 21 CFR 101.9-compliant panel in standard, tabular, or linear format
• RACC-derived serving size, automatic dual-column detection, correct rounding on every line
• Ingredient statement in descending order by weight, with sub-ingredients
• Allergen declaration across all nine major allergens, including sesame
• Saved products you can revise: 25 on Starter, 100 on Pro, 500 on Business

The four questions bakers ask

"Is a database label actually legal?" Yes. FDA's guidance is that the source of the data used to calculate label values is the manufacturer's prerogative. You're responsible for accuracy, not for having paid a lab. See lab vs. database software.

"Do I even need a label?" If you sell out of your own case, probably not. Walk it through in do I need a nutrition facts label? before spending anything.

"What if I get it wrong?" Rounding, RACC serving sizes, and dual-column detection are handled by the tool, not by you at a spreadsheet at midnight. See nutrition label rounding rules.

"What if my recipe changes?" It will, four times a year. Unlimited revisions on any subscription tier; 90 days of edits on the $39 one-time.

Proof

<!-- SOCIAL PROOF BLOCK — placeholder slots. Do not publish until filled with real, permissioned customers. -->

• [BAKERY NAME], [CITY] — SKU count, wholesale trigger, quote, permission on file
• [BAKERY NAME], [CITY] — seasonal reformulation story, quote, permission on file
• [METRIC] — only if internally sourced and the basis is stated

Pricing

Annual billing saves two months. Most bakeries land on Starter or Pro, because 25 saved products runs out faster than expected. Need one panel for one final recipe? Take the $39.

Ready when you are

Photograph the recipe card. Get the panel in about a minute. $39 one time, or $69/mo with unlimited revisions across the whole menu.

Build My Label