Multi-State Product Compliance: A Practical Framework for US Importers

You've got one product. It needs to comply with federal law, California's rules, Maine's rules, Washington's rules, and a dozen other state-specific requirements that nobody seems to agree on. Welcome to multi-state compliance.

Here's a fun scenario. You import nonstick cookware. At the federal level, your product needs to meet FDA food-contact requirements. Fine. But then California wants Prop 65 disclosures. Maine has banned intentionally added PFAS in cookware since January 1, 2026. Minnesota banned it in cookware a year earlier and runs its own PFAS reporting requirement. Washington requires PFAS reporting for certain product categories. And other states keep writing their own versions — one of them has probably passed something you haven't read yet.

Same product. Same factory. Same SKU. But the compliance requirements change depending on which state your customer lives in. If you're selling e-commerce nationally — which most importers are — you're selling into all of them simultaneously.

This isn't a new problem, but it's getting exponentially worse. Every legislative session brings new state-level product regulations, and they're rarely aligned with each other. If you don't have a framework for managing this, you're going to miss something. Let's build one.

The problem: a patchwork with no coordination

The US regulatory system for product compliance is, by design, decentralized. Federal agencies like the CPSC, FDA, and EPA set baseline requirements. But states have broad authority to go further — and they do, aggressively.

Some examples of the patchwork in action:

PFAS restrictions. A growing number of states have enacted PFAS-in-products laws, and the details vary. Maine's law bans intentionally added PFAS by category (cookware, textiles, cosmetics and others since January 1, 2026) and reaches nearly all products on January 1, 2032, apart from uses the state rules "currently unavoidable." California's AB 1817 targets textiles. Minnesota bans PFAS in 11 product categories and requires reporting. Washington focuses on specific product categories. Each has different effective dates, different exemptions, and different enforcement mechanisms.

Prop 65 (California). This is probably the most well-known state-level product regulation, and it effectively applies to anyone selling into California — which is everyone selling online in the US. The safe harbor levels, warning formats, and listed chemicals are unique to California. No other state has a law quite like it.

Packaging regulations. States like Maine, Oregon, Colorado, and California have Extended Producer Responsibility (EPR) laws for packaging. Requirements for producer registration, fee payments, recycled content minimums, and labeling vary by state. If you import a product with packaging (which is all of them), you may have obligations you don't even know about.

Children's product safety. While CPSIA is federal, some states have additional requirements. Washington's Children's Safe Product Act requires reporting on certain chemicals in children's products. Vermont has its own notice requirement for chemicals of high concern in children's products. These layer on top of CPSIA's CPC requirements.

The result: an importer selling a single product nationally might need to track compliance against 5-20 different regulatory frameworks simultaneously. And that number only goes up with each product in your catalog.

The framework: five steps to multi-state compliance

After working with importers managing products across multiple regulatory jurisdictions, here's the framework that actually works. It's not glamorous, but it's systematic — and systematic beats scrambling every time.

Step 1: Identify all applicable regulations

Start by mapping every regulation that applies to each product you sell. This means:

• Federal requirements: CPSIA, FDA food-contact regulations, EPA chemical requirements, FSVP (for food imports), FCC (for electronics), etc.
• State-level requirements: Prop 65 (CA), PFAS laws (ME, MN, WA, CA, and others), packaging EPR (ME, OR, CO, CA), children's product reporting (WA), and any category-specific state laws
• Retailer requirements: Amazon, Walmart, Target, and others often have their own compliance requirements that layer on top of legal obligations

This is the step most importers skip or do incompletely. You can't comply with regulations you don't know about. And "I didn't know about Maine's PFAS law" won't help when the AG comes calling.

Step 2: Test against the strictest standard

Here's the efficiency hack that can cut testing costs: identify the strictest applicable standard and test against that first. If you meet the strictest requirement, you'll typically meet all the less strict ones automatically.

In practice, this usually means starting with California or Maine:

• California tends to have the lowest thresholds for chemical warnings (Prop 65 safe harbors) and the most aggressive enforcement
• Maine and Minnesota both ban intentionally added PFAS by product category now, and in nearly all products from January 1, 2032
• Washington has detailed children's product chemical reporting requirements

If your nonstick pan meets Maine's PFAS-free requirement, it also clears Minnesota's PFAS reporting requirement (there's nothing to report). One caution: a strictest-first test only helps when the rules measure the same thing. Prop 65 safe harbor levels are daily exposure amounts, while CPSIA's lead limits are content limits in parts per million, so one result does not answer both. Test smart, not exhaustively.

Step 3: Document everything by jurisdiction

Once you've tested, organize your documentation by both product and jurisdiction. For each product, you should be able to answer: "What are the requirements in State X, and do we have documentation proving compliance?"

This is where spreadsheets start to break. When you've got 50 products across 15 regulatory jurisdictions, that's 750 compliance data points to track, each carrying different effective dates, different documentation requirements, and different renewal cycles. A spreadsheet can hold this data, but it can't alert you when something changes or expires.

Step 4: Monitor for regulatory changes

State-level product regulation is the fastest-moving area of US compliance law right now. New PFAS laws are being proposed in multiple states every legislative session. Packaging EPR is expanding rapidly. Prop 65 adds new chemicals to its list regularly. If you mapped your regulatory landscape in January, it may look different by June.

You need a monitoring process. That could be:

• Subscribing to regulatory update services
• Setting quarterly reviews to check for new state-level regulations affecting your product categories
• Working with a compliance consultant who tracks multi-state developments

The key is making this proactive, not reactive. Finding out about a new regulation from a retailer compliance audit or a customer complaint is too late.

Step 5: Re-test and recertify on schedule

Testing isn't a one-time event. CPSIA requires periodic testing for children's products. Prop 65 safe harbor levels can change. PFAS testing methods evolve. And if you change suppliers, materials, or manufacturing processes, previous test results may no longer be valid.

Build a re-testing schedule that accounts for:

• Regulatory requirements for periodic testing (CPSIA)
• Material or supplier changes that invalidate existing test data
• New regulations that require testing you haven't done before
• Test report age (some retailers and marketplaces set their own limits on how old a test report can be)

How to prioritize when everything feels urgent

If you're reading this and thinking "we're behind on all of this," don't panic. Here's how to prioritize:

Start with California. If you sell to any California consumer (and if you sell online, you do), Prop 65 is your highest-risk exposure. Prop 65 applies to businesses with 10 or more employees, and private enforcers can sue after giving 60 days' notice to the alleged violator and to public prosecutors — no agency has to bring the case. Get your Prop 65 assessment done first.

Then federal requirements. If you import children's products without a valid CPC, or food without FSVP documentation, you're at risk of import holds and recalls. Federal enforcement tends to be more consequential than state enforcement.

Then the expanding state requirements. PFAS is the big one. If your products use coatings, treatments, stain-resistance, water-resistance, or non-stick properties, you need to map your PFAS exposure across states. Maine's cookware ban is already in effect, and its all-products ban on January 1, 2032 sounds far away until you realize you need to reformulate products, re-test, and update documentation — that takes years, not months.

Then retailer requirements. Amazon, Walmart, Target, and other major retailers increasingly require compliance documentation beyond what the law mandates. If you sell through these channels, their requirements are effectively mandatory.

Where Aleph fits

This framework works on paper, but executing it manually across a product catalog of any meaningful size is a full-time job. Aleph takes on the record-keeping part of it:

• Cited checklists per product: Switch on the regulations you're subject to — FSVP, CPSIA, Prop 65, MoCRA — and each product gets a checklist of that regulation's requirements, every row cited, showing where you have documentation gaps.
• Documents and deadlines: Upload test reports, certificates, and supplier statements, including for PFAS, against the products they cover, and get an alert before one expires. Working out which state PFAS laws apply to a product stays your call; Aleph does not map them.

Multi-state compliance isn't going to get simpler. The trend is clearly toward more state-level regulation, more chemical restrictions, more disclosure requirements, and more enforcement. The importers who build systematic compliance programs now will spend less time and money on compliance over the long run than the ones who keep treating each new regulation as a fire to put out.