How to Review Fiber Food Packaging Evidence for State PFAS Restrictions

For each fiber-based food packaging SKU intended for a U.S. state, build a record that connects the exact product configuration to its material documentation, intended food-contact conditions, destination state, document version, and verification status. A broad supplier statement is not a SKU review. The practical goal is to identify missing evidence before a purchase order, artwork approval, or rollout decision.

A product-family name is rarely specific enough for a state-restriction or food-contact review. Create one review record per SKU and per configuration.

Record the supplier part number, size, shape, base and lid combination, fiber substrate, coatings, additives, inks, adhesives, and any print or barrier treatment. If the intended order differs from the sample or catalog configuration, treat it as a separate configuration until the documentation is reconciled.

The evidence request should also describe how the item will be used:

• Food type, including oily, acidic, dry, or aqueous foods where relevant
• Contact temperature and expected contact time
• Whether the item is used for cooking, reheating, freezing, hot fill, or ambient service
• Direct versus indirect food contact
• Any use with a lid, liner, sleeve, label, or secondary packaging

These details make it possible to assess whether supplied documents address the actual use case rather than an unspecified packaging application.

State restrictions are destination-specific. List every U.S. state in which the SKU is expected to be sold, distributed, or supplied, then keep the list under change control.

For each state, record the effective date being reviewed, the product category used in the review, the restriction or disclosure question being checked, and the source used for the current requirement. Do not reuse a conclusion from one state for another state without checking whether the product definition, timing, or evidence expectation is the same.

A useful internal status is not reviewed, evidence received, evidence gap identified, under specialist review, or approved for the defined use. The last status should only be assigned through the buyer's documented verification process.

Ask the supplier to identify the exact SKU and configuration on every document. A usable package may include the following items.

Request a dated declaration that identifies the fiber substrate and all relevant functional components, including coatings, treatments, additives, inks, adhesives, and liners. It should state whether the declaration applies to the ordered configuration and identify the manufacturing site or controlled product specification where available.

A declaration should not be treated as interchangeable with a test report. It explains what the supplier is representing; it does not by itself establish how a product was tested or whether a state-specific requirement has been evaluated.

Request any PFAS-related declaration, analytical report, test method, laboratory identity, sample description, date, result units, reporting limit, and conclusion supplied for the exact configuration. Confirm whether the tested sample includes the same coating, print, adhesive, or liner as the SKU under review.

If the document uses a threshold, a method-specific term, or a defined PFAS scope, preserve that wording in the record. Do not turn a limited test result into a general product claim. When the destination state or the buyer's policy requires a particular form of evidence, compare the submitted report directly against that requirement.

Request the regulatory basis or other food-contact documentation relevant to the intended market and use conditions. The record should identify the food categories, contact temperature, contact duration, and any limitations described by the documentation.

If the supplier provides a general statement, ask which material layers and use conditions it covers. A food-contact document for one substrate, coating, or use condition may not address a different SKU configuration.

Ask for the document revision date, specification revision, production-lot traceability approach, and a notification process for material or manufacturing changes. These controls help prevent an old report from being applied after a coating, mill, additive, or converting process changes.

Create a simple evidence matrix before approving a SKU. The matrix can include these columns:

The matrix should make uncertainty visible. If a report names a generic item while the purchase specification includes a coating or printed finish that is not named, mark the item as an evidence gap rather than assuming coverage.

Keep supplier documents, your SKU specification, and the destination-state review together in the procurement file. Have the responsible internal reviewer compare them before using claims in product copy, bid responses, customer communications, or rollout approvals.

Verification should include checking document authenticity and dates, confirming that the sample and ordered configuration match, reviewing test scope and stated limitations, and escalating state-law interpretation or unresolved conflicts to qualified legal or regulatory advisers. Retain the completed review and any follow-up correspondence with the SKU record.

Use clear questions that require a document-backed response:

1. Which exact SKU, component layers, and production configuration does each document cover?
2. What food types, temperatures, and contact durations does the food-contact documentation address?
3. Does the PFAS-related document identify the sample, method, laboratory, date, result units, and reporting limit?
4. Which U.S. destination states has the buyer identified for this order?
5. What is the current specification and document revision, and how are changes communicated?
6. Which points remain unverified and require buyer or specialist review?

A disciplined SKU file is more useful than a broad material claim: it lets procurement, quality, and legal reviewers see exactly what was supplied, what it covers, and what still needs verification. For a custom-packaging RFQ, share the SKU configuration, intended contact conditions, and destination states early so the right documentation can be requested and assessed for that specific order.

To start that product-specific conversation, contact TakeawayPack. Specific documents and any resulting conclusions should be verified for the individual SKU, use conditions, and destination state.