Packaging specifications: why they are the weakest record in the product file

What a packaging specification contains

A packaging specification describes the pack as a structure by identifying its components and recording the material and weight of each one.

Component-level packaging data

Packaging data has to be held per component because the obligations and the fees attach to the material in each part.

• Material identity. Polymer or fibre type and grade, with the material code used for sorting and fee reporting. A sleeve and the bottle underneath it are two different materials in the same unit.
• Weight. Component weight with a tolerance, plus the source of the figure. Weights taken from a supplier drawing and weights taken from a scale rarely agree.
• Recycled content. The claimed share and its basis, backed by the certificate reference.
• Food contact status. Declarations of compliance for anything that touches the product, such as inks and adhesives on the inside of a laminate.
• Recyclability inputs. The record captures colour and barrier layers. It also captures label coverage and closure material. These decide the grade, so they belong in the record.
• Supplier and plant. Which supplier issued the data and from which site, since the same part made at two plants can differ.

Component granularity makes the roll-up possible, first to the pack and product, and then to a country report.

Where it sits today

Packaging data in manufacturing is spread across four systems that were never designed to agree with each other.

Procurement holds supplier drawings and technical data sheets in a shared drive.

The Enterprise Resource Planning (ERP) system identifies a purchasing item by price and unit of measure.

Polymer type sits outside the record.

Artwork management holds the printed file and its approval history.

And somewhere there's a spreadsheet that one person maintains for the sustainability team's annual return. Nobody is wrong in that setup. Each function built what it needed.

The problem appears when a question spans them: what is the total polypropylene weight we placed on the Spanish market last year, and can we show where each figure came from? Answering it means reconciling four sources by hand, then defending numbers that have no single owner.

This is why packaging data management gets described as a reporting problem when it's a master data problem. The report is only ever as good as the component record feeding it.

What the PPWR now requires

The PPWR, formally Regulation (EU) 2025/40 on packaging and packaging waste, turned packaging design into a documented product-level duty. It entered into force on 11 February 2025, and most obligations apply from 12 August 2026. Its obligations address substance restrictions and design for recycling. They also address minimisation and the declaration of conformity. As a regulation, the text applies directly in every member state.

Harmonised material composition labelling applies from 12 August 2028 under Article 12(1), with the reusable packaging label following on 12 February 2029. Minimum recycled content in plastic packaging starts in 2030, at 30% for contact-sensitive PET and 35% for non-contact-sensitive packaging, and recyclability grading tightens again in 2038.

Each of those duties is answered from component material and weight data. The answer also draws on the recycled share record and on the combined effect of colour and coverage. What matters for the record itself is that a declaration of conformity now needs a traceable source, and a spreadsheet cell isn't one.

Supplier ownership

Most of the data in a packaging specification isn't yours. It comes from the converter who molds the bottle and produces the printed carton or laminated film, which means your compliance position depends on documents you don't author.

That dependency is manageable if you decide two things early.

First, which fields the supplier owns and which you own. They hold weight and polymer grade records. They also hold food contact declarations and recycled content certificates. Pack structure and artwork content sit with you. So does market allocation.

Second, what an acceptable submission looks like. A template with defined fields and units beats a free-form data sheet, because a free-form sheet has to be read by a person before it becomes usable.

The failure mode is familiar. A supplier changes a resin or a barrier layer for reasons of their own, tells procurement in an email, and the specification never moves. Nine months later the recyclability grade in your report is describing a pack that no longer exists. Supplier data needs a version and an effective date. It also needs a named approver, exactly as a formulation would.

Frequent change

The record decays because packaging changes far more often than the product inside it. A recipe holds for years. The pack around it gets a promotional flash or a new claim. Its closure is lightweighted, or continuity brings a second supplier. A new market adds a language.

Each of those is a change to structure, to print content, or to both. Regulatory changes and routine changes look identical in an inbox. A carton that drops 4 grams changes your fee calculation. A new on-pack claim changes what has to be substantiated. A promotional sleeve changes label coverage, which can change the recyclability grade of the bottle.

So the record needs versioning that distinguishes a change in the pack from a change in the artwork printed on it. Without that separation, you either version everything and drown in approvals, or version nothing and lose the audit trail. Effective dates matter too because at any moment one version of a pack is in stock and another is in transit. A third is in design.

How label content traces back

Label content is downstream data. Upstream records supply printed pack content, which is why specification errors that arrive late become label errors.

Ingredients and allergens come from the formulation record. So does nutrition data. Material composition and sorting marks come from the packaging components. Deposit and return marks come from the market the pack is sold into. Recycled content claims come from supplier certificates. When those sources are linked to the label, a change upstream raises a flag on the artwork. When they're copied into a brief by hand, the copy becomes the truth and the link is broken.

The cost of a broken link is visible in enforcement data. The European Commission's 2025 report on the Alert and Cooperation Network recorded 10,490 notifications, an 11% rise on 2024, with labelling and allergen declarations among the recurring hazard categories. Generating the label from source data turns regulatory compliance in product development into a data rule.

Why artwork takes so long

Artwork cycles stretch because the brief arrives incomplete, and the missing pieces are packaging data. After design starts, a reviewer asks which polymer code belongs in the sorting mark. Someone emails the supplier, and the file waits. Then a second round finds the net weight doesn't match the declared content, and the clock restarts.

Count the rounds on a launch and you'll find that the first two are spent gathering facts that already existed somewhere in the business. The issue is one of sequencing.

Two fixes do most of the work. Freeze the pack structure and its component data before the artwork brief is issued, so designers receive fields rather than questions. And carry the approval evidence forward, so a reviewer signing off a claim is signing off a linked source instead of a sentence in a PDF.

Structuring the packaging record

Managing packaging specifications well means holding the pack as structured component-level data inside the Product Lifecycle Management (PLM) system that already holds the product. Version control belongs in that record.

• Model the pack as a structure. One parent pack with its components beneath it. Each component has a quantity per pack.
• Give every field an owner. Supplier-sourced fields carry a supplier and a version. Each field also carries an effective date. Internal fields carry an internal approver.
• Version the pack and the artwork separately. Linked, but not the same object, so a resin change and a promotional flash follow different approval paths.
• Generate the label from source data. Every printed element points back to its source record in formulation or packaging data. Market-specific elements point to the relevant market data.
• Build the report from the record. Fee returns and conformity documents query the same component data used in design, which is what makes a number defensible.

Fixing the packaging record

Component weights, material grades, recycled content and food contact evidence all originate with someone else, change more often than the recipe, and decide both the numbers you report and the claims you print.

C+P Consulting helps manufacturers restructure that. The pack modelled as a structure, every field with an owner and an effective date, and the pack versioned separately from the artwork printed on it, so labels and fee returns read from the same source.

If your packaging data is currently spread across four systems and one very important spreadsheet, let us take a look.

FAQ

More articles