Operations

In-House vs Outsourced Packaging Compliance: Choosing the Operating Model

Packaging compliance can be run with internal staff, with consultants, with a PRO-managed model, or with a hybrid. The right choice depends on your jurisdictional footprint, SKU complexity, and data maturity. Here is how to think about the operating model, separate from the tooling decision.

By Kevin Kai Wong, Managing Partner at gCurv Technologies

June 5, 2026

In-House vs Outsourced Packaging Compliance: Choosing the Operating Model

1.The decision is about people, not tools
2.What the operating models actually look like
3.When each model fits
4.Staffing implications
5.Triggers that prompt a model switch
6.What this means operationally
7.What to do in 2026
8.How Packgine helps
9.Related reading

The decision is about people, not tools

Packaging compliance touches several disciplines: packaging engineering, supplier management, sales operations, finance, legal, and regulatory affairs. Whether to run that orchestration in-house, outsource it, or split the work is a different question from what tooling you use. A producer can run an in-house team on spreadsheets or a fully outsourced model on a dedicated platform. Both happen.

Treating the operating-model question separately from the tooling question is what makes both decisions tractable. This post focuses on operating model. The tooling decision (build, buy, or stay manual) is a separate workstream covered elsewhere.

What the operating models actually look like

There are five common patterns:

Model 1, Pure in-house. A dedicated compliance team owns the work end to end. They define methodologies, gather data, file reports, manage supplier evidence, and respond to regulators. Common in large producers with multi-jurisdiction exposure.

Model 2, In-house with consultants. A small in-house team coordinates with external consultants who provide jurisdiction-specific expertise (UK PPT specialists, EU PPWR firms, state-specific consultants). Consultants are project- or retainer-based.

Model 3, PRO-managed. Where a Producer Responsibility Organization (PRO) handles much of the operational execution, registration, reporting submission, fee invoicing, the producer's internal role can be smaller. The PRO is not a substitute for producer obligations, but it absorbs the operational layer.

Model 4, BPO / managed service. A business process outsourcing arrangement where a third party operates the compliance function end-to-end as an outsourced service. The producer maintains oversight; execution lives outside.

Model 5, Hybrid by jurisdiction or function. In-house for major markets, outsourced for tail jurisdictions. Or in-house for data and methodology, outsourced for filing execution. Most large multi-jurisdiction producers end up here.

When each model fits

In-house works when:

Multi-jurisdictional exposure is large enough to justify dedicated headcount (typically 4+ obligated jurisdictions, several thousand SKUs, multi-million-dollar fee exposure).

Internal data maturity is reasonable (PLM and ERP are usable, packaging master data has owners).

The producer wants direct control over methodology and evidence.

Audit risk is high enough that close internal control is worth the headcount cost.

In-house with consultants works when:

Core operations are in-house but specific jurisdictions need depth the team does not have (e.g., a US-based team adding the first EU jurisdiction).

Methodology questions are recurring but specialized (eco-modulation strategy, audit defense, novel scope determinations).

The producer wants to retain methodology while buying execution capacity at peaks (filing season, audit response).

PRO-managed works when:

Producer obligations sit primarily in jurisdictions with strong PRO operations (CAA-managed states in the US, established PROs in EU member states).

The producer's data feeds are clean enough to push to the PRO without significant in-house preprocessing.

The producer accepts that operational changes happen at PRO pace, not internal pace.

BPO / managed service works when:

Compliance is a non-core function for the producer.

The producer wants predictable cost rather than headcount.

The producer's internal data is messy enough that bringing it in-house would require building a function from scratch.

The producer is willing to accept slower internal capability development in exchange for getting filings done.

Hybrid works when:

Some jurisdictions are large and material; others are tail.

The producer wants in-house ownership of strategy but external capacity for execution.

Different functions (data, methodology, filing, audit) have different operating-model fit.

Staffing implications

A rough sizing for in-house compliance, by producer scale and jurisdictional footprint:

Single-jurisdiction, mid-size SKU count. 0.5 to 1 FTE, often a part-time role for a packaging engineer or operations manager.

2 to 3 jurisdictions, mid-size. 1 to 2 dedicated FTEs.

4 to 6 jurisdictions, multi-region. 2 to 4 FTEs spanning data, methodology, and filing.

Major multinational, 8+ jurisdictions. 4 to 10+ FTEs, possibly with regional leads, plus consulting capacity for specialized work.

Outsourced models reduce headcount but introduce vendor management and review work, typically 0.25 to 0.5 FTE just to manage the relationship and validate output.

PRO-managed models do not eliminate internal work; they shift it from execution to data quality and oversight.

Triggers that prompt a model switch

Operating models are not permanent. Common transition triggers:

Trigger 1, New jurisdiction goes live. A producer with two jurisdictions adds a third. The current model breaks if the third is operationally different (different language, different PRO, different reporting cadence).

Trigger 2, M&A. Acquisitions add SKUs, jurisdictions, and data systems. The acquiring company's operating model may not absorb the new complexity without redesign.

Trigger 3, Audit failure. A regulator finding produces a remediation requirement that the existing model cannot meet. The fastest path to remediation may be different from the long-term operating model.

Trigger 4, Headcount loss. A single compliance lead leaves. The operating model implicitly relied on tribal knowledge that left with them.

Trigger 5, Cost or capacity pressure. Outsourced spend grows beyond what an in-house team would cost; in-house teams hit capacity limits and need outsourced overflow.

Trigger 6, Strategic refocus. Compliance becomes more (or less) strategic to the business. A producer entering reuse markets at scale may need deeper in-house expertise; one exiting EU markets may shrink their footprint.

What this means operationally

The operating model decision should be revisited annually, with attention to:

Jurisdictional footprint and growth trajectory.

Data quality and where the data sits.

Risk profile (audit history, fee exposure).

Internal capability and key-person risk.

Vendor relationships and their performance.

The wrong-fit operating model produces predictable failures, late filings, audit findings, surprise consulting bills, key-person dependencies. The right-fit model is invisible: filings go out, audits get answered, and the team is staffed to scale.

What to do in 2026

Document your current operating model explicitly. Most producers have not.

Identify the top three risks of the current model.

Identify the top three triggers that would force a change.

Plan transitions in advance of triggers, not in response to them.

How Packgine helps

Packgine works across operating models, pure in-house teams, hybrid teams with consultants, BPO providers, and PRO-managed setups. The data model and reporting outputs are the same; the operating model determines who interacts with the system. When the operating model changes, the platform stays put.