The workflow is familiar. A client emails asking for your packaging data. You find the last spec sheet or the spreadsheet you sent someone else six months ago, update a few values, save a copy, and email it over. Done. Until the next client asks. And the one after that. And then someone from the first client emails again because the numbers do not match what they expected.
This is the standard approach for most packaging suppliers handling EPR data requests today. It works — in the sense that data eventually reaches clients. But it creates five specific problems that compound as the volume of requests grows.
Problem 1: Inconsistent data across clients
When data is created per request rather than maintained centrally, each client receives a slightly different version of the truth. The weight you quoted Client A last March might differ from what you sent Client B in October — not because the packaging changed, but because you pulled from different source files, rounded differently, or corrected a small error in between.
This is not a hypothetical. Two clients selling the same product of yours in Germany and France will each file a declaration that traces back to your data. If they happen to compare notes — or if a PRO cross-references declarations from multiple brand clients of the same manufacturer — the discrepancy raises questions that are difficult to explain.
A centralised BOM eliminates this: there is one set of numbers, and every client who requests data for the same product gets those same numbers.
Problem 2: No audit trail of what was shared, when
EPR compliance is auditable. National authorities in Germany, France, Spain, and elsewhere can request documentation to support a brand's declaration. When they do, brands trace the data back to their suppliers.
If a client calls you and says "we're being audited for 2024 — can you confirm what packaging data you sent us in Q4 2023?", what is your answer? Can you find the email? Was it the correct version? Are you certain the numbers in that email match what the client declared?
An email inbox is not an audit trail. It is a search problem — and not all searches succeed. A proper record of what was shared, with which client, for which product, on which date, and at which version is something email cannot provide.
Problem 3: Packaging changes break everything silently
Packaging changes regularly. A lighter box design to reduce shipping costs. A switch to a recycled-content corrugated board. A new supplier for the inner tray. Each change makes the previous data you sent to clients incorrect.
The email model has no mechanism to propagate updates. You might remember to email your three biggest clients when packaging changes. But what about the client you sent data to 18 months ago who is still using the same file? They do not know the data is stale. You do not know they have not asked for an update.
This creates a slow accumulation of inaccurate data spread across client systems — data that will eventually be used in declarations that regulators can audit.
Problem 4: Repeated work that scales badly
Each new client request involves the same steps: find the source data, format it for this client's template, verify the numbers, send. This is perhaps 30–60 minutes per product line per client.
With five clients, that is manageable. With fifteen clients — which is where many manufacturers will be by mid-2027 as PPWR enforcement expands across all 27 EU member states — the quarterly data request cycle becomes a significant overhead. It is time that could be spent on actual production, not data transcription.
The core issue is that the same underlying data — the material composition and weight of your packaging — is being manually re-prepared from scratch for each recipient instead of being maintained once and distributed many times.
Problem 5: Format chaos
Different clients use different templates. One client wants a tab per product. Another wants all products on one sheet with a specific column order. A third has their own import format that requires polymer type in a different column from material category. A fourth sends a Word document with a table.
Every format requires manual adaptation. And when data needs to be updated, every format needs to be updated separately.
Under the PPWR, harmonized material categories are being introduced across all EU markets. Over the next two years, client request formats will converge — but until they do, format variation adds friction to every request.
What a better system looks like
The alternative is not complex. It has three components:
1. One canonical BOM per product
Maintain a single, version-controlled BOM for each product in your range. This is the source of truth. Every field is filled in correctly once: component name, material type (to the required specificity), weight per unit in grams, packaging level, recycled content percentage.
When packaging changes, you update this BOM — once — with a new version and effective date. The old version is preserved for historical reference.
2. Share access, not files
When a client requests data, you send them a link to the current version of the BOM. They see a clean view of the data and can import it into their compliance system directly — or download it in whatever format they need.
The key distinction from an email attachment: the link points to living data. When you update the BOM, the client can see the update. When a packaging change creates a new version, the old share continues to point to the correct historical version while the new share points to the updated one.
3. Track who has what
A dashboard showing which clients have received which BOM data, when they accessed it, and whether they imported it. When an audit question arrives, the answer is a lookup, not an inbox search.
The economics of switching
Setting up a structured BOM system for a product range of 50 SKUs takes a few hours upfront. That is the one-time cost. After that:
- Each new client data request takes under a minute — find the product, click share, enter email
- Each packaging change requires one update, not one per client
- Audit responses are immediate — you know exactly what was shared with whom and when
- New quarters require no additional work for existing clients
The Pack Declare supplier portal is built specifically for this workflow and is free for suppliers. The brand clients who need your data pay for their compliance tooling — you just provide the data, once, in a structured way.
For how a supplier portal works in detail, see how a supplier portal for EPR packaging data works. For the specific data fields you need to enter once, see exactly what packaging BOM data your clients need.