Skip to content
For co-packers & contract manufacturers

You don’t run one regulatory program. You run one for every customer on the floor.

By Mirelis Food Systems · Published May 30, 2026 · Updated June 27, 2026

A contract manufacturer with 50 customer SKUs is carrying 50 sets of specs, and the regulatory rules behind each one move on their own schedule, in their own category, in whatever states that brand ships to. Mirelis monitors federal and state regulatory change across the categories your customers actually sell in, lets you filter the view down to a single customer, and gives you a clean slice to drop into a procurement or quality thread. One system, every customer, the record to prove it.

The short answer

A practical way for a co-packer to review regulatory change for its clients is to give one named regulatory owner a per-customer lens: filter a maintained federal-and-state dataset to each customer’s categories and states, then export the relevant record, plain-language summary, official source, and key date to procurement, quality, or the brand team. That turns a broad feed into a more reviewable set of customer-specific filters.

Request access to the Tracker Or discuss your operating scope
The problem

Every customer’s category has its own moving rules.

When you make product under someone else’s brand, you inherit their regulatory exposure without inheriting their regulatory staff. The bakery line, the beverage line, the supplement line, and the snack line on your floor are governed by different federal requirements and different state laws, and each of your customers expects you to be current on the rules that touch the product you ship for them.

Many categories, no single scope

A general regulatory feed isn’t scoped to you; it’s scoped to everything. Most of what lands doesn’t touch a single SKU you run, and the few items that do are buried in the rest. The work isn’t reading the feed; it’s figuring out which line on your floor each change actually hits.

Every customer ships to different states

Federal rules are only half of it. One customer sells into a handful of states; another is national. State legislatures move on additives, disclosures, and labeling on their own timelines, so the map of what matters is different for each brand you produce for, and it changes underneath you.

The update has to leave your inbox

Knowing a rule changed isn’t the deliverable. Procurement has to re-check a supplier spec; quality has to update a control; the customer’s brand team needs a heads-up. If that hand-off lives in one person’s head or one person’s inbox, it doesn’t survive a vacation, a reorg, or an audit.

None of this is hard because the information is secret. The federal and state sources are public. It’s hard because the volume is high, the relevance is low, the scope is different for every customer, and the answer has to reach more than one desk. That’s a sorting-and-routing problem, run continuously, across a portfolio, and it doesn’t fit neatly on anyone’s existing job.

Why the usual tools miss this

A directory tells you a rule exists. A PLM system tracks your specs. Neither watches for what just changed for a given customer, and hands it to you to send.

Regulatory directories and reference libraries are built to answer “what is the rule today.” They’re reference works. They don’t watch for the moment a rule moves, and they don’t know which of your customers that movement touches.

Product-lifecycle and supplier-network tools are built around your documents: specs, certificates, supplier records. They’re good at that. But they’re not watching state legislatures or the Federal Register, and they don’t turn a regulatory change into a routed, shareable alert scoped to one brand on your floor.

What a co-packer needs sits in the gap between the two: monitoring of regulatory change, scoped to the categories and states each customer actually operates in, that produces a slice you can hand to the people who have to act on it. That intersection is what the Mirelis Regulatory Horizon Tracker is built for.

The workflow

Filter to one customer. Share the slice. Keep the record.

The tracker monitors active federal and state regulatory developments across FDA, USDA, FTC, TTB, with daily change-detection on state legislative activity nationwide: normalized, de-duplicated, written in plain English, each item tied to its primary source and its compliance date. For a co-packer, three things matter most about how that runs.

A filtered view per customer

Build a saved view for each brand you produce for (scoped to the categories that customer sells in and the states they ship to), so “what’s moving for this account’s products” is a view you open, not a sort you redo every week. The portfolio stops being one undifferentiated feed and becomes a shelf of per-customer lenses.

A shareable change alert, scoped tight

When a material change is verified and published, the named owner can filter the relevant record and export the summary, official source, and key date for procurement, quality, or the customer’s brand team.

An audit trail you didn’t have to assemble

Because each item carries its source and its date, “when did we know, and what did we do” stops being an email archaeology project. When a customer’s auditor (or your own) asks how you stay current on the rules behind their product, you have a defensible answer scoped to that account, not a shrug and a promise to dig.

The routing still belongs to your operation. A change is handled only after it reaches the person who acts on it, with enough context and source evidence to support the decision. Personal saved views and exports help one regulatory owner prepare that hand-off; they do not replace the team’s approval process.

Built for more than one desk

A regulatory change rarely stops at one person. Founding Access gives the hand-off one clear owner.

A change still has to move between whoever watches the rules, procurement re-checking a supplier spec, and quality updating a control. Today, the tracker gives one named owner a maintained, cited view that can be filtered and exported into that internal hand-off.

Founding Access is a one-user workspace with filters, bookmarks, exports, and cited change history. Organization workspaces, shared resources, scheduled digests, and custom monitoring are handled as separately scoped pilot capabilities, with production activation only after validation.

See Founding Access Request access

The Tracker is invite-only. “Request access” routes to a scope-and-fit conversation, not a checkout or automatic provisioning.

Start with the labels you already run

Start with a scope-and-fit conversation.

Bring the categories, states, and internal hand-offs that make your operation difficult to monitor. Mirelis will determine whether the current one-user Founding Access workspace fits that need or whether the work belongs in a separately written custom engagement.

No product-level analysis or deliverable begins until the scope, inputs, commercial terms, and handling path are agreed in writing. The first conversation is for fit and routing, not an unpriced consulting product.

Discuss your regulatory operating scope

A short scoping call to choose the correct existing offer or define the boundaries of a written custom engagement.

Start the conversation
Why this is a now-problem, not a someday-problem

The rules your customers depend on are already on the clock.

Consider one rule that lands squarely on contract manufacturers: the FDA Food Traceability rule under FSMA 204. Facilities that manufacture, process, pack, or hold foods on the Food Traceability List will need to keep and share specific traceability records, and the date that matters is July 20, 2028: the point before which FDA has been directed not to enforce the rule. (FDA has separately proposed to move the rule’s own compliance date to that same date; that rulemaking is not yet final, but the enforcement date is set either way.) For a co-packer, that obligation doesn’t arrive once; it arrives per customer, per qualifying product, with recordkeeping that has to line up across your suppliers and your customers’ brands.

That’s a single, well-defined example. The reason monitoring matters is that it’s rarely the rule you already know about that catches you; it’s the state bill in a market one of your customers just expanded into, or the federal change that quietly reset a deadline. Seeing those early, scoped to the right account, is the whole job.

Go deeper on this one

FSMA 204 readiness, in eight pillars

Our FSMA 204 Readiness Checklist walks the runway to the 2028 enforcement date across scope, CTEs, KDEs, traceability-lot codes, data carriers, the plan, partners, and a mock traceback, with primary-source citations throughout.

Get the FSMA 204 guide
Common questions from co-packers

How co-packers use the tracker

How should a co-packer monitor regulatory changes for its clients?

A named regulatory owner can build a personal saved view for each customer, scoped to relevant categories and states. Mirelis checks maintained federal and state sources daily; after a material change is verified and published, that owner can export the filtered record with its summary, source, and key date for the right internal team.

How is this different from a regulatory directory or a PLM/supplier-network system?

A directory answers what the rule is today; it does not watch for the moment a rule moves, and it does not know which of your customers that movement touches. A product-lifecycle or supplier-network tool is built around your own specs and certificates, not state legislatures or the Federal Register. A co-packer’s need sits in the gap between them: monitoring of regulatory change, scoped to the categories and states each customer operates in, delivered as a routed slice you can hand to the people who act on it.

How does a co-packer keep up when every customer ships to different states?

One named user can maintain a personal saved view for each customer, scoped to the states that brand ships to. State legislatures move on different timelines, so separate personal filters help the regulatory owner review a multi-state portfolio without treating every state as equally relevant.

Can I share regulatory updates across procurement, quality, and a customer’s brand team?

Founding Access is licensed to one named user and includes filters, bookmarks, exports, and cited change history. Organization workspaces, shared resources, and scheduled digests are separate pilot capabilities available only through a written scope and controlled production activation.

Does this work for private-label brands and distributors too?

The same personal-filter approach can help a named regulatory owner review a multi-brand or multi-entity operation. The current product does not provide shared team workspaces, so internal routing and approvals remain in your existing systems.

What does the tracker cover for a co-packer?

Active federal and state regulatory developments across FDA, USDA, FTC, and TTB, with daily change-detection on state legislative activity nationwide: normalized, de-duplicated, written in plain English, each item tied to its primary source and its compliance date. The Tracker is invite-only; requests are reviewed for scope and fit before access is provisioned.

Continuous monitoring, scoped to your floor

One customer’s rules are a project. Fifty customers’ rules are an operation.

The Mirelis Regulatory Horizon Tracker provides a maintained federal-and-state view with filters, bookmarks, exports, primary-source citations, and key dates. Founding Access is invite-only and provisioned for one named user.

Request access See what the Tracker covers