Build a State-by-State PFAS Evidence Register for Fiber-Based Food Packaging SKUs

Restaurants, CPG brands, distributors, and institutional buyers operating across U.S. states should manage PFAS screening as a SKU-, state-, and order-specific evidence process. Start with the complete material structure, define the expected food-contact conditions, map the destination state, and then collect documents whose scope can be matched to that exact purchase. A supplier declaration or test result that cannot be tied to the reviewed SKU, material layers, production version, intended use, and destination should remain an open item—not a compliance conclusion.

This article is a procurement framework, not legal advice or a finding that any packaging is PFAS-restricted, PFAS-free, or suitable for food contact. State requirements, definitions, effective dates, test methods, and exemptions require current, state-specific review.

U.S. rules affecting PFAS in food packaging do not operate as one uniform purchasing rule. The product scope, statutory language, enforcement approach, and relevant dates may differ by state. A multi-state buyer can therefore create avoidable risk by applying one broad supplier letter to every market or every fiber-based item in a catalog.

The practical unit of review is not “molded fiber packaging” as a category. It is the specific SKU or configured item for a defined order and state destination. A bowl, lid, wrap, tray, carton, coating, adhesive, or printed component may need its own assessment where its material stack, production version, or intended use differs.

An evidence register makes this work visible. It gives procurement, quality, regulatory, and operations teams one place to see:

• which items are being considered for which state;
• what the item is made of, layer by layer;
• the expected food-contact scenario;
• which supplier documents and tests have been received;
• whether each document can be traced to the actual purchase; and
• what must be reconfirmed when the product or order changes.

It does not replace legal interpretation. It creates the record needed for a qualified reviewer to assess the appropriate rule against the actual item.

Open one register entry for each item that may differ in construction, supplier, factory, coating system, print treatment, or use. Include the supplier’s SKU and your internal item code where available. Add a current product photo, drawing, specification revision, quotation reference, and purchase-order reference once issued.

A description such as “bagasse clamshell” or “paper food tray” is not enough to anchor evidence. It may describe multiple designs and material structures. The evidence record needs a way to distinguish the exact item being reviewed from similar catalog items.

For each SKU, request a bill of materials or an equivalent layer map. The register should identify, to the extent the supplier can provide it:

• the fiber substrate or paper/paperboard component;
• barrier, grease-resistant, or other functional treatments;
• coatings, laminations, or films;
• inks, varnishes, and overprint treatments when relevant to the food-contact configuration;
• adhesives, labels, and release materials where they are part of the item; and
• component supplier, factory, and production location or batch reference when available.

This is not an exercise in requesting generic chemistry. It is a way to identify which materials and treatments a supplier declaration or laboratory result actually covers. If the supplier will not disclose a layer, log that limitation and ask how the requested evidence accounts for it.

A document can be meaningful only in the context of intended use. Before asking for PFAS-related or food-contact evidence, prepare a brief that describes the anticipated scenario for the individual SKU.

Record the intended food type and the conditions expected in normal use, including:

• dry, moist, fatty, acidic, salty, or alcoholic food characteristics as relevant;
• whether the package will hold hot, chilled, frozen, or ambient food;
• expected filling or contact temperature range;
• maximum expected contact, holding, and delivery duration;
• direct versus indirect contact and which surface contacts food;
• microwave, reheating, or other post-fill handling if contemplated; and
• single use, reuse, or any other operational scenario being evaluated.

Do not infer suitability from the package’s appearance or from another SKU’s intended use. These inputs define the question a supplier, laboratory, or regulatory reviewer must answer for the reviewed item.

A food-contact declaration, a material statement, and a PFAS-related test report do different jobs. One document should not automatically be treated as proof of all three topics. In the register, classify each document by purpose, for example:

A missing or non-matching document is a reason to keep the register entry in a clarification status. It is not a reason to fill the gap with a marketing claim.

A “United States” destination field is too broad for a state-specific screening exercise. For each planned shipment, sale, distribution route, or restaurant deployment, record the state or states where the item is expected to be placed on the market or used. Include the planned start date, because requirements and enforcement dates can change.

Where a distributor supplies several states, create separate state rows linked to the same SKU rather than one row marked “nationwide.” That structure preserves a clear answer to a simple question: *which evidence was reviewed for this SKU in this state, for this order?*

The register should identify the person or team responsible for checking the current state rule and should distinguish their finding from supplier-provided information. Useful fields include:

• jurisdiction and source checked;
• product category or statutory definition considered;
• review date and reviewer;
• applicability status: pending, in review, cleared by reviewer, or not applicable as assessed;
• required follow-up; and
• decision owner and decision date.

Avoid pre-populating a permanent “compliant” flag based on a prior order, a company-wide letter, or an assumption about fiber-based products. A register should show the basis and date of the decision, not conceal uncertainty.

When a supplier provides a PFAS-related declaration, check whether it names the precise product or clearly describes the applicable construction. Review the signatory, issue date, factory or product scope, and any qualifications. Ask whether the declaration applies to the proposed order’s materials and production version.

A declaration that names only a product family, a material category, or an unrelated market may be useful background, but it should be recorded as limited-scope evidence until the supplier clarifies the match.

For a laboratory report, record the sample identifier, sample description, collection or receipt date, test method, reported units, laboratory, and report date. Note whether the sample’s construction matches the purchase candidate. A result from a different coating, supplier, factory, thickness, print treatment, or production period may not answer the question for the current SKU.

The correct test method and interpretation depend on the applicable state requirement and the question being asked. Procurement teams should not select a method or convert a result into a legal conclusion without the appropriate technical and legal review.

Every evidence item should have a document version or issue date. The SKU record should also track the current specification or construction revision. Link them so a reviewer can see whether the evidence predates a material change.

At a minimum, the register should flag a new review when any of these changes occurs:

• fiber source, barrier treatment, coating, adhesive, ink, or other material layer changes;
• factory, subcontractor, or production-line changes;
• product dimensions or design changes that alter the food-contact configuration;
• a new printed artwork, coating, or customization that affects relevant materials;
• different intended food, temperature, or contact-duration conditions;
• a new destination state or changed distribution route; or
• an expired, superseded, or scope-limited declaration or report.

An evidence register works only if it is connected to purchasing. Add a gate before quote approval, purchase-order release, or distribution launch: the buyer confirms that the SKU, state, intended use, and supporting documents still match.

For repeat orders, do not assume that last year’s file remains applicable. Ask the supplier to disclose relevant material, factory, or document changes; compare the response with the stored evidence; and re-route the record for review where the change-control triggers apply.

A simple status system can prevent false certainty:

• Information requested — essential SKU, state, use, or evidence details are absent.
• Evidence received; scope check pending — documents exist but have not been matched to the item and order.
• Technical or legal review pending — the evidence is traceable but needs specialist interpretation.
• Approved for the defined purchasing decision — an authorized reviewer has recorded a dated, limited decision for the specified SKU, state, and use.
• Change review required — the construction, intended use, destination, or document set has changed.

The final status should always retain its scope. It should not migrate automatically to a different SKU, state, or order.

A spreadsheet, PLM record, or supplier-management system can use the following fields as a starting point:

The goal is not to collect the largest document set. It is to build a concise, traceable file that can answer what was bought, where it was intended to be used, under what conditions, and why the evidence was considered relevant.

Use questions that require an item-specific response rather than a broad assurance:

1. Which exact SKU, specification revision, factory, and material layers does your response cover?
2. What food-contact conditions is each submitted document intended to address?
3. Does the PFAS-related declaration apply to every relevant layer and treatment in the proposed configuration? If not, identify the exclusions.
4. If a test report is supplied, what sample was tested, by which method, and how does that sample match the quoted item?
5. What changes to materials, production location, treatment, printing, or documentation would trigger notification before shipment?
6. Can you provide an order-specific confirmation that identifies the SKU, destination state, and document set being discussed?

Record both the question and the supplier’s response. An unanswered question is a visible procurement gap, not an implied approval.

For a fiber-based food-packaging purchase spanning U.S. states, the safest procurement habit is to keep a state-by-state evidence register: one that connects the precise SKU and its material layers to the intended food-contact conditions, destination state, testing or declarations, document versions, and change-control decisions. It supports disciplined follow-up without claiming that a product is PFAS-compliant or food-contact compliant.

If you are preparing an RFQ with TakeawayPack, use the Contact / RFQ page to share the product category, material and size requirements, estimated quantity, customization needs, and destination. Ask for the documentation scope to be discussed for the specific SKU, order, destination market, and claim category; review the resulting files against your register before making a state-specific sourcing decision.