Front of Package Labeling: FDA Proposed Requirements
Front of package labeling requirements explained for FDA's proposed Nutrition Info box, including scope, exemptions, package sizes and claims.
FDA front of package labeling requirements for the proposed "Nutrition Info" box are not currently mandatory. FDA published the proposed rule in the Federal Register on 16 January 2025 at 90 FR 5426 under Docket No. FDA-2024-N-2910, and it has not been finalized. No packaged food in the United States has to carry the box today, and no compliance clock is running.
This article takes the proposed front of package nutrition label requirements as written and answers the operational questions: which products would be covered, which packages would be exempt, and what would need to change on your artwork.
It is the manufacturer-facing companion to the front-of-package nutrition label guide, which covers what the box shows and where the rulemaking stands, and to the front-of-package sodium article. Read those for the design specification and status history. Stay here for the product-by-product work.
Front of package labeling scope: which products would be covered?
The scope provision in proposed 21 CFR 101.6(a)(1) is short but broad. The box would apply to all food covered by 21 CFR 101.9, the Nutrition Facts regulation, that is marketed for people ages 4 and older.
That is the basic test.
There is no category carve-out, no exemption for foods that happen to score well, and no distinction between branded and private-label products. If a package requires a Nutrition Facts panel and is marketed to the general population, assume it would fall within the proposed rule.
The box would require no new nutrient analysis. It republishes three values already derived from your nutrition information, making it entirely dependent on the existing Nutrition Facts label requirements.
Two populations would sit outside the proposed rule.
Foods marketed for infants and children under 4 would not be covered. FDA asked for comment about extending the policy to ages 1 through 3 in a future action, which is a signal rather than a requirement.
Most dietary supplements would also fall outside the scope for a structural reason. Supplements are labeled under 21 CFR 101.36 with a Supplement Facts panel and are exempt from 101.9 through 101.9(j)(6), so they never reach the proposed scope provision.
| Product | Box required? | Why |
|---|---|---|
| Retail snack, cereal, sauce, frozen entree | Yes | Covered by 101.9, marketed to ages 4 and older |
| Toddler pouch marketed for ages 1 to 3 | No | Outside the ages 4 and older scope line |
| Dietary supplement | No | Labelled under 101.36, exempt from 101.9 at (j)(6) |
| Bulk ingredient for further manufacturing | No | Exempt from 101.9 at (j)(9), so exempt at 101.6(c)(1) |
Front of package label requirements: the exemptions in proposed 101.6(c)
The proposal contains four exemptions, each based on a different rationale. Understanding the reason behind each one helps determine whether a particular SKU actually qualifies.
1. Any food exempt from 101.9 under 101.9(j), unless otherwise stated. This is a derivation rule. The proposed box reproduces %DV information already calculated for the Nutrition Facts label, so a food with no mandatory Nutrition Facts panel has no figures to reproduce.
That provision sweeps in restaurant and ready-to-eat foods prepared and sold on site under (j)(2) and (j)(3), foods with insignificant amounts of all mandatory nutrients under (j)(4), such as coffee beans, tea leaves and spices, medical foods, bulk foods for further manufacturing, raw fruits, vegetables and fish under (j)(10), and the small-business low-volume exemption at (j)(18) for firms averaging fewer than 100 full-time equivalent employees and selling fewer than 100,000 units.
The familiar trap remains. Most 101.9(j) exemptions disappear when you make a nutrient content claim. Lose the 101.9 exemption and you would pick up the front-of-package obligation with it.
2. Small packages with less than 12 square inches of total surface area available to bear labeling. This exemption is based on space. Twelve square inches is the same threshold that can exempt a package from mandatory Nutrition Facts labeling under 101.9(j)(13), provided no claims are made and the label provides an address or phone number for nutrition information.
3. Packages marketed as gifts containing an assortment of foods. A gift basket has no single nutrition profile or meaningful serving, so one box on the outer package could misrepresent the different foods inside. This exemption is tied specifically to gift assortments and is not a general exemption for multi-item packages.
4. Unit containers inside a multiunit retail package when those units are exempt under 101.9(j)(15) and the outer package carries the box. The rationale is to avoid duplication. If inner units state "This Unit Not Labeled For Retail Sale" and the outer carton provides the full nutrition labeling, the outer carton would carry the box and the individual sleeves would not.
Check this SKU by SKU. Many inner units are also sold individually and therefore do not qualify for the (j)(15) exemption.
Small packages: 12 square inches versus the 40 square inch reduced box
The proposed FDA front of package labeling requirements contain two separate package-size rules that are easy to confuse.
A package with less than 12 square inches of available labeling area would be exempt from the box entirely.
A package with 40 square inches or less would not necessarily be exempt, but it could use a reduced version of the box.
The reduced box removes the "Per serving" and "% Daily Value" column subheadings and eliminates the numeric %DV figures.
What remains is the "Nutrition Info" heading, the three nutrient names and their Low, Med or High classifications. The nutrient names would be shortened to "Sat. Fat" and "Add. Sugar." Sodium remains unchanged because its name is already short.
The result is a small-package format that gives the shopper the classification without displaying the underlying percentages.
| Element | Standard box | Reduced box (40 sq in or less) |
|---|---|---|
| "Nutrition Info" heading | Yes | Yes |
| "Per serving" with household measure | Yes | Omitted |
| "% Daily Value" subheading | Yes | Omitted |
| Numeric %DV column | Yes | Omitted |
| Nutrient names | Saturated Fat, Sodium, Added Sugars | Sat. Fat, Sodium, Add. Sugar |
| Low / Med / High | Yes | Yes |
The size test uses available labeling area, not simply the footprint of the front panel.
Regardless of format, the proposed box would appear in the upper third of the principal display panel. Its type would have to be at least 8 point and no smaller than the net quantity of contents declaration required by 21 CFR 101.7(h) and (i).
The PDP calculator handles the geometry for cylinders, boxes and pouches.
Front of pack labeling for package types needing special handling
Variety packs and aggregate displays
When a package contains several different foods and uses an aggregate Nutrition Facts display, the proposal would require one box per product, not a single averaged box.
The individual boxes would appear in a horizontal or vertical line in the upper third of the principal display panel, with the name of each food right-justified above its corresponding box.
A twelve-count package containing three flavors would therefore need three boxes across the upper portion of the carton.
This is one of the provisions most likely to disrupt existing artwork because that same upper band often contains the primary brand block.
Dual column, per serving and per unit
Products using dual "per serving" and "per unit" Nutrition Facts declarations would display a front-of-package box based on the per serving column.
There would not be a second box representing the per-unit values.
As packaged versus as prepared
Products declaring nutrition information both as packaged and as prepared, such as dry cake mix or condensed soup, would use the as packaged values for the box.
The box would also need a statement such as "Represents product as packaged" or "See Nutrition Facts for As Prepared information."
That distinction can materially change the classification. A dry mix may score Low in its packaged state but produce very different values after butter, oil or milk is added. The accompanying statement is the proposal's mechanism for directing consumers to the prepared nutrition information.
Two population groups, bulk foods and game meats
A product labeled for two population groups, such as one carrying nutrition information for children 1 through 3 and for the general population, would use the values for ages 4 and older only in its box. There would be no second box for the younger population.
For bulk foods, the box would appear on the bulk container labeling so that it is visible at the point of purchase.
For game meats, the box would be presented consistently with the way that product's nutrition information is already presented, reflecting the flexible treatment provided under 101.9(j)(11) and (j)(12).
Nutrient content claim changes included in the proposal
The same proposal also contains amendments to the nutrient content claim rules in 21 CFR 101.61 and 101.62. These changes are easy to miss because they sit behind the more visible Nutrition Info box.
"Low sodium" would tighten from 140 mg to 115 mg or less per RACC, with 115 mg or less per 50 g when the RACC is 30 g or less or 2 tablespoons or less, and 115 mg or less per 100 g for meals and main dishes.
The reason is mathematical. A sodium amount of 115 mg equals 5% of the 2,300 mg Daily Value, which is the upper boundary of the proposed "Low" classification. FDA does not want a package to say "low sodium" while the Nutrition Info box beside it classifies sodium as "Med."
A food using the low sodium claim would also have to display "Low" for sodium in its box.
"Low saturated fat" would retain its existing requirement of 1 g or less per RACC and no more than 15% of calories from saturated fat. A food making the claim would also have to display "Low" for saturated fat in the proposed box.
Importantly, the binding definitions today remain 140 mg for low sodium and 1 g plus 15% of calories for low saturated fat.
Nothing about a currently compliant claim becomes non-compliant because of this proposal.
However, a product containing 130 mg sodium per RACC and carrying "low sodium" today would fail the proposed threshold. That makes the SKU worth identifying now rather than discovering it during a future artwork revision.
Check current eligibility with the claim validator.
| Claim | Binding today | Proposed |
|---|---|---|
| Low sodium, individual food | 140 mg or less per RACC (and per 50 g if the RACC is 30 g or 2 tbsp or less) | 115 mg on the same two tests, plus "Low" shown for sodium in the box |
| Low sodium, meals and main dishes | 140 mg or less per 100 g | 115 mg or less per 100 g |
| Low saturated fat | 1 g or less per RACC and 15 percent or less of calories | Unchanged, plus "Low" shown for saturated fat in the box |
| Very low sodium | 35 mg or less per RACC | Not changed by this proposal |
Preemption and the proposed front of package labeling timeline
Proposed 101.6(d) would preempt state and local front-of-package requirements that are not identical to the federal rule.
For a national manufacturer, that could allow one federal box rather than a patchwork of state-specific formats. It has no present effect because the proposed preemption provision would matter only after a final rule exists.
The proposal establishes two compliance periods, both measured from the effective date of a final rule:
- 3 years for businesses with $10 million or more in annual food sales.
- 4 years for businesses with less than $10 million in annual food sales.
That is the entire proposed compliance schedule.
Neither clock has started because no final rule has been published. Comments closed on 15 July 2025, and the earliest compliance date would therefore be at least three years after a future publication date that cannot currently be named.
Any specific front-of-package compliance date presented before a final rule exists is a projection, not a deadline.
The deadlines already established for other labeling changes are tracked in the FDA nutrition label changes timeline.
How to audit front of package labeling across your portfolio now
The useful work now is not redesigning packaging. It is auditing the nutrient data you already have.
The proposal uses the %DV figures already calculated and rounded for the Nutrition Facts panel. FDA said the proposal does not address calculation or rounding, so no new nutrient analysis is necessary.
For each SKU, pull three values:
- Saturated fat %DV.
- Sodium %DV.
- Added sugars %DV.
Then classify each one into the proposed Low, Med or High bands.
| Band | %DV | Saturated fat | Sodium | Added sugars |
|---|---|---|---|---|
| Low | 5 percent or less | 1 g or less | 115 mg or less | 2.5 g or less |
| Med | 6 to 19 percent | above 1 g, under 4 g | above 115 mg, under 460 mg | above 2.5 g, under 10 g |
| High | 20 percent or more | 4 g or more | 460 mg or more | 10 g or more |
The gram and milligram equivalents come from the adult Daily Values of 20 g saturated fat, 2,300 mg sodium and 50 g added sugars.
The proposal itself defines the bands in %DV, so treat absolute gram and milligram amounts as a sense check rather than the legal test.
If your product data contains grams or milligrams but not percentages, use the Daily Value calculator.
Once the three values are available, answer four questions for each SKU.
First, which products would display at least one "High"?
Second, which products sit only a percentage point or two from a band boundary, where a small reformulation or correction to serving size could change the classification?
Third, which products currently use "low sodium" while containing between 115 mg and 140 mg sodium per RACC and would therefore lose the claim under the proposal as written?
Fourth, for every SKU that would need a box, is there enough space in the upper third of the principal display panel to place it at 8 point or larger without covering the brand mark, net quantity statement or a vignette?
For variety packs, repeat that space test with two or three boxes in the same row.
This portfolio audit remains useful whether or not the proposed rule is eventually finalized in its current form.
Front of package labeling frequently asked questions
Do I have to put a Nutrition Info box on my product now?
No. The front of package labeling rule is proposed, not final. It was published on 16 January 2025, comments closed on 15 July 2025, and no final rule has been published. Nothing currently requires packaged foods in the United States to carry the proposed Nutrition Info box.
My product carries "low sodium" at 130 mg per RACC. Is it non-compliant?
No. The binding definition remains 140 mg or less per RACC under 21 CFR 101.61, so 130 mg qualifies. The 115 mg threshold is proposed only. Flag the SKU because, if that provision were finalized as written, you would need either a reformulation or a claim change within the applicable compliance period.
Would a package under 12 square inches ever need the front of package label?
Under the proposal as written, packages with less than 12 square inches of total surface area available to bear labeling would be exempt. However, the parallel 101.9(j)(13) exemption is conditional on making no nutrient content claims and providing an address or phone number for nutrition information. Losing the underlying 101.9 exemption would pull the product into the proposed front-of-package requirement under 101.6(c)(1).
How would a variety pack with three flavors be labeled?
Each product would receive its own box. The three boxes would be arranged in a horizontal or vertical line in the upper third of the principal display panel, with each food's name right-justified above its corresponding box. A package containing three flavors would therefore display three boxes.
Which figures would apply to a dry mix prepared with other ingredients?
The as packaged figures would be used. The box would also carry a statement such as "Represents product as packaged" or "See Nutrition Facts for As Prepared information" directing the shopper to the full Nutrition Facts panel for the prepared values.
Whatever happens to the proposal, the saturated fat, sodium and added sugars figures it would display already need to be correct on the Nutrition Facts panel. Build that panel with the label generator and keep the three %DV values in a sortable format so a future portfolio audit becomes a filter rather than a full packaging project.
