Tree Nut Allergen Requirements in New York: FALCPA Individual Naming Rules
FALCPA requires tree nuts to be named individually in US allergen declarations — not just listed as "tree nuts." New York food businesses must apply this requirement for all products.
Under FALCPA, tree nuts are a major allergen — but unlike other major allergens, tree nuts must be named individually in the allergen declaration. Simply stating "contains tree nuts" does not meet the legal standard.
Why Individual Tree Nut Naming Matters
Different tree nuts cause different allergic reactions in different individuals. Someone allergic to cashews may not be allergic to almonds. Someone allergic to walnuts may tolerate macadamia nuts. The individual naming requirement gives allergic consumers the specific information they need to assess their personal risk.
This is a meaningful distinction from UK Natasha's Law, which accepts "tree nuts" as a category allergen declaration without requiring individual naming.
Which Tree Nuts Must Be Named Individually?
The tree nuts covered by FALCPA include:
- Almonds
- Brazil nuts
- Cashews
- Chestnuts
- Filberts / hazelnuts
- Macadamia nuts
- Pecans
- Pine nuts (pinon)
- Pistachios
- Walnuts
Each type present in your product must be named in the allergen declaration.
How to Declare Tree Nuts Correctly
Correct (FALCPA compliant): "Contains: Milk, Eggs, Walnuts, Cashews" Or in ingredient list: "roasted cashews (cashews)" — where the common name of the specific tree nut appears.
Incorrect (FALCPA non-compliant): "Contains: Milk, Eggs, Tree Nuts"
Implications for New York Businesses
New York businesses manufacturing or labelling food products must apply this FALCPA requirement. Products labelled without individual tree nut naming are not legally compliant for sale in New York or interstate commerce.
Implement correct tree nut allergen declarations with Allergen Matrix — with US mode requiring individual tree nut specification.
How Tree Nut Allergens Enter Products Indirectly
One of the most common compliance failures for New York food businesses is failing to account for tree nuts that enter a product through compound ingredients rather than as a primary component. A product containing a store-bought pesto, for example, may include pine nuts through that sauce without the manufacturer consciously thinking of pine nuts as a standalone ingredient. Similarly, a chocolate ganache filling may introduce almonds via a commercially produced praline paste. These secondary sources must still be declared individually by nut type in your allergen statement.
The same logic applies to flavouring compounds, spice blends, and nut-derived oils that retain allergenic protein. If your recipe includes a mixed nut butter, you cannot simply declare the allergen as "tree nuts" because the individual nut species within that butter each require their own named declaration. The burden is on you as the manufacturer or labeller to trace the exact species composition of every compound ingredient you use and reflect that accurately in your Contains statement.
This is particularly relevant for businesses sourcing ingredients from multiple suppliers or reformulating products seasonally. A supplier may change the nut composition of a compound ingredient without prominently flagging it, which means your previously compliant label can become non-compliant without any deliberate change on your part. Regular ingredient specification reviews and supplier communication are essential components of maintaining FALCPA-compliant tree nut declarations across your entire product range.
Cross-Contact Statements and Tree Nuts
Precautionary allergen labelling — commonly seen as "may contain" or "produced in a facility that also processes" statements — is voluntary under FALCPA but widely used by food manufacturers to communicate cross-contact risk. For tree nuts specifically, the voluntary nature of these statements does not remove the obligation to declare any tree nut that is intentionally present in your formulation. These are two separate declarations serving two separate purposes, and conflating them is a labelling error that can mislead consumers and create regulatory exposure.
When you do choose to include a precautionary statement for tree nuts, best practice is still to name the specific nut or nuts that pose the cross-contact risk, rather than using the generic category term. If your facility handles walnuts and pecans on shared equipment, your precautionary statement should reflect that specificity. While this goes beyond what voluntary labelling guidance strictly requires, it aligns with the consumer-first philosophy that underpins the individual naming rule and helps allergic shoppers make genuinely informed decisions about the risk level they are comfortable accepting.
For New York businesses selling through e-commerce channels, precautionary statements on your digital product listings should match what appears on your physical packaging. Inconsistencies between online descriptions and label text can create confusion for customers and complications during any regulatory review. Maintaining a single source of truth for your allergen information — covering both intentional presence and cross-contact risk — makes this consistency far easier to manage at scale.
Tree Nut Naming in Multi-Format Product Ranges
Food businesses that produce multiple product variants face a particular challenge with tree nut declarations because nut composition can shift significantly across a range. A chocolate bark sold in four flavour variants might contain almonds in one, pistachios in another, mixed pecans and walnuts in a third, and no tree nuts at all in the fourth. Each variant requires its own precise allergen declaration, and the label for each must reflect only the nuts actually present in that specific product rather than any collective description covering the range.
This becomes more complex when products share a base recipe but receive different inclusions at a late stage of production. The base itself may be free from tree nuts, but inclusions added after the base is prepared can introduce one or more specific nut types. In these cases, each finished SKU must carry an allergen declaration that accounts for the final composition of that individual product. A label prepared for the base recipe alone would be non-compliant for any variant that receives nut-containing inclusions, even if those inclusions represent a small fraction of the finished product by weight.
Managing this across a growing product catalogue requires systematic recipe documentation and a labelling workflow that ties allergen declarations directly to finalised formulations rather than to product families or base recipes. Businesses using spreadsheets or manual processes to track this often find that errors accumulate as the range expands. Purpose-built tools that enforce individual tree nut specification at the point of recipe entry help prevent these errors from reaching finished product labels in the first place.
Updating Labels When Recipes or Suppliers Change
Recipe and supplier changes are a routine part of running a food business, but each change carries the potential to alter your tree nut allergen profile and therefore your labelling obligations. Substituting one nut for another — swapping macadamia nuts for cashews in a cookie recipe, for instance — requires an immediate label update to reflect the new species present. Continuing to use existing label stock after a formulation change is one of the most avoidable sources of FALCPA non-compliance and one that regulators and plaintiffs treat with particular seriousness.
Supplier changes that affect compound ingredients also require review even when your own recipe has not changed. If your nut paste supplier begins blending a different combination of species, or if a coating chocolate changes its almond sourcing in a way that affects allergenic content, your downstream declaration obligation changes accordingly. Building a regular cadence of specification checks into your procurement process — not just at onboarding but at each contract renewal and whenever a supplier notifies you of a formulation update — provides a practical safeguard against inadvertent non-compliance.
For New York businesses operating under New York's own food safety inspection framework in addition to FALCPA, the stakes of outdated allergen information are compounded. State inspectors reviewing labelling compliance will assess whether your declared allergens match your current formulation and ingredient specifications. Keeping your recipe records, supplier specifications, and product labels synchronised is not just good practice; it is a foundational requirement for operating responsibly in the New York food market.
Digital Menus, Shopify Listings, and Tree Nut Disclosure
For food businesses selling through Shopify or other e-commerce platforms, allergen information presented in digital product listings carries the same accuracy requirement as information on physical packaging. If your product contains cashews and walnuts, your online listing must name both, not simply indicate that tree nuts are present. Customers purchasing food online rely heavily on digital descriptions to make safe purchasing decisions, and vague category-level allergen statements in product listings create real risk for tree nut allergic consumers who are depending on that information.
Shopify merchants managing large catalogues of food products need a structured approach to allergen data that scales with their product range rather than relying on manual entry for each listing. As new products are added, as recipes evolve, and as supplier specifications are updated, the allergen information displayed on the storefront must update accordingly. An approach that stores allergen data at the recipe or product level and surfaces it consistently across all relevant listings is considerably more reliable than managing this information through free-text product descriptions edited individually.
Tree nut declarations in digital listings also need to account for variant-level differences where a product is sold in multiple configurations. A Shopify product with multiple variants should present allergen information specific to each variant rather than a single consolidated statement that may not accurately represent every option. Tools that integrate with your Shopify product data and enforce individual tree nut naming at the variant level help ensure that your digital storefront reflects the same compliance standards as your physical labels. Explore how Allergen Matrix handles this for US-market Shopify stores.
Try Allergen Matrix free at saltai.app — no credit card required.
SaltAI Team
SaltAI builds focused Shopify apps for food merchants and general merchants. Every app is tested in production at a real food store — including Vanda's Kitchen — before it ships.