Who Owns the Packaging Compliance Last Mile?

Who prepares the regulatory output, who completes the action, and who remains accountable?

You can spend months assembling packaging specifications, material weights, supplier evidence, and sales data. Software may help you organize those records and prepare regulatory outputs. But when a report is ready to file, or a Declaration of Conformity is ready for review, who takes the next step?

The answer depends on how you've divided the work among your team, software providers, reporting specialists, and compliance services. Three responsibilities matter: preparing the required output, completing the regulatory action, and remaining accountable for the result. They may involve different parties.

Understanding that division is what I mean by the packaging compliance last mile.

From packaging information to regulatory action

Before you can prepare reliable regulatory outputs, your packaging data needs to be usable. That can mean collecting missing specifications, resolving conflicting supplier responses, connecting packaging components to products and markets, and distinguishing measured or confirmed information from estimates. It's an essential foundation, but a reliable packaging record is only the starting point.

What happens next depends on the obligation.

U.S. state packaging EPR (CAA-administered programs). Circular Action Alliance (CAA) describes how producers assemble data about covered materials, prepare state-specific reports, and submit them through its Producer Portal. The precise requirements vary by state. A reporting application may prepare the data, while the producer or an authorized party completes the portal process and confirms its status.

UK packaging EPR. Government guidance specifies the reporting file's fields and codes, and explains that a producer can submit data directly or use a compliance scheme to do so. Preparing the prescribed file and submitting it are distinct activities.

EU PPWR conformity. The Packaging and Packaging Waste Regulation has applied since August 12, 2026, with requirements taking effect according to their respective provisions. Under Articles 15, 38, and 39, manufacturers must carry out or arrange the relevant conformity assessment, prepare technical documentation, and draw up an EU Declaration of Conformity when conformity has been demonstrated. By drawing up the declaration, the manufacturer assumes responsibility for packaging compliance. Unlike an EPR report submitted through a reporting portal, the declaration is issued and maintained by the manufacturer, supported by technical documentation that must be retained and provided to competent authorities when required.

These processes illustrate why a software product that generates a report or document may address only part of your obligation. The consequential question is what must happen after that output is prepared, and who is responsible for making it happen.

How the work gets done

There are several practical ways to organize the relationship between packaging records and regulatory execution. The following arrangements are illustrative and can overlap.

1. Your team prepares and submits

You maintain the packaging information, use software or internal methods to prepare the necessary outputs, and have your own staff complete registrations, submissions, reviews, and follow-up. CAA's producer reporting process explicitly calls for an internal person or team to coordinate the report before submission through its portal.

This approach keeps execution close to your organization, but the people and expertise required are part of the operating cost. You need to understand how much classification, review, portal work, and correction handling remains after the software has produced its output.

2. Your packaging system connects to a specialist reporting application

Your packaging specifications remain in one system while a connected application applies jurisdiction-specific reporting rules. This can let you retain an existing packaging-data foundation and use specialist software for regulatory calculations or reports.

Specright describes its connection with Lorax EPI as one such arrangement. The described connection transfers packaging specification information into Lorax's EPR reporting environment. Specright separately offers native PPWR Declaration of Conformity generation. The same provider therefore illustrates partner-supported EPR reporting and native PPWR documentation, with the actual workflow and responsibilities needing confirmation for your implementation.

For your evaluation, the important questions are what data crosses the integration, which regulatory outputs the connected application produces, and who performs the submission or final review.

3. One software environment supports data and regulatory outputs

Some products combine packaging-data management, regulatory calculations, and reporting or documentation workflows. SAP Responsible Design and Production, for example, describes using enterprise packaging information for EPR fee calculations and reporting. SAP's product documentation also describes generating PPWR Declaration of Conformity documents.

Its conformity-workflow guidance describes specific supported requirements, evidence management, and review-and-release activities. The organization retains the conformity decision. An integrated environment can reduce some handoffs, while the supported scope, human approvals, and any separate regulatory submission steps still need to be established.

4. A specialist or compliance service performs the work

You may engage a compliance scheme or provider to collect and check information, prepare regulatory outputs, and complete submissions within a contracted service scope. The specialist might use its own software, work with your existing records, or combine both approaches.

Valpak describes flexible services for packaging-data collection, calculation, and submission. Its June 2026 enrollment guidance makes one boundary explicit: the producer's approved person must complete initial enrollment in the UK's Report Packaging Data service. Valpak can subsequently handle agreed data-submission work. Under the UK's packaging EPR rules, approved compliance schemes can take on specified registration and reporting obligations for members, while producers retain duties to verify the information they supply and make it as accurate as reasonably possible.

Lorax EPI describes a different service choice within the same reporting platform. Software-only customers operate the reporting process themselves, while its outsourced-compliance offering includes data collection, report preparation, and submission to scheme portals where required.

Both examples show why the service agreement must be read alongside the applicable regulations. You need to know which tasks the provider performs, what you must supply or approve, and which legal responsibilities remain with your organization.

What you need to establish

When evaluating a solution, start with one real obligation in a market where you operate. Ask the provider to follow it from packaging information through the required regulatory output and final action.

Four questions will reveal much of what you need to know:

• Who prepares the output? Identify the party performing data collection, regulatory classification, calculations, report generation, or technical-document preparation. Separate native software functions from integrations and services.

• Who completes the action? Establish who registers, submits, signs, releases, or responds to the relevant authority or scheme. Ask to see how that step works in the applicable jurisdiction.

• Who remains accountable? Identify the legally obligated entity in each jurisdiction, the decisions or approvals it must make, and the records demonstrating completion. Depending on the obligation, that might be a portal acknowledgement, an accepted reporting status, or an issued and retained Declaration of Conformity.

• What work remains with you? Include supplier follow-up, exception handling, corrections, changing requirements, integrations, specialist fees, and recurring internal effort.

These answers also clarify cost. A software subscription may leave substantial recurring work with your team; a managed service may assume more of that work for an additional fee. Either can be appropriate when the responsibilities and dependencies are understood.

For a more detailed method of testing those responsibilities, implementation needs, evidence, and total cost, see The Packaging Software Buyer’s Playbook.

The last mile needs clear ownership

The examples illustrate several ways organizations can divide the work. Your software may generate the necessary output, a specialist may complete the next action, and your organization may retain important approval or legal responsibilities.

A dependable operating model makes those boundaries clear before anyone relies on the result.

Research note

Sources reviewed October 2026. Vendor examples are not endorsements; they illustrate publicly described capabilities and service arrangements, not independently verified customer outcomes. Product coverage, contract terms, and regulatory requirements should be confirmed for the jurisdictions and obligations that apply to your organization.