A compliant product can still ship in packaging whose evidence is missing or whose approved version no longer matches. Packaging needs its own controlled ERP record.
Category: ERP, E-commerce & Packaging Operations
What changed today
The EU Packaging and Packaging Waste Regulation, Regulation (EU) 2025/40, generally applies from August 12, 2026. Known as PPWR, it covers packaging across materials and sectors. That general date does not mean every later target, label, calculation method, or implementing measure became due today.
Some requirements do matter now. The European Commission's August 3 FAQ says the substance-of-concern minimisation duty in Article 5(1) applies from August 12. Article 5 also limits PFAS (per- and polyfluoroalkyl substances) in food-contact packaging at or above specified thresholds from this date. The regulation says compliance with those food-contact packaging limits must be demonstrated in the technical documentation described in Annex VII.
Article 16 requires packaging and packaging-material suppliers to give manufacturers the information and documentation needed to demonstrate conformity. Manufacturers retain the conformity-assessment, technical-documentation, and declaration responsibilities described in Articles 15 and 39. Importers, distributors, final distributors, and fulfilment service providers have separate duties. One business may hold more than one role, so the mapping must be assessed case by case.
Other PPWR measures are staged. The Commission's FAQ separates later provisions covering recyclability, recycled content, packaging restrictions, and reuse targets. Its implementation page also shows that work on some labelling and recycled-content measures is still in progress. Operational teams need a dated obligation map, not a single “PPWR complete” checkbox.
This article focuses on evidence operations, not an exhaustive inventory of duties starting August 12. The implementation lesson is practical: if a business cannot identify the packaging version used for a product and retrieve its supporting evidence, the trail can fail even when the product record is correct.
Why operational leaders should care
When an ERP or e-commerce design treats packaging only as a description, purchasing line, or warehouse instruction, it may be enough to buy cartons. It is not enough to control which specification was approved, which supplier evidence supports it, when that evidence changed, and which product-market combination used the version.
The control can break at a handoff. Procurement receives a revised declaration. A product manager changes a carton. The warehouse continues using old stock. An e-commerce team launches the item in another market. Finance sees the invoice, but not the evidence status. Support finds the order, but not the pack version that shipped.
This is why PPWR is an ERP, e-commerce, and integration issue as well as a legal and packaging issue. A useful implementation connects product catalogs, packaging specifications, suppliers, purchase receipts, warehouse release, orders, shipments, and retained evidence. AorBorC recommends qualified human review for evidence sufficiency and legal applicability; the system makes that decision visible and enforceable at the right boundary.
The packaging-to-shipment evidence map
Here, a packaging version means a dated, approved specification for the packaging components used with a product in a market—not a legal certification label. The following is AorBorC's suggested operating model, not a field list prescribed by PPWR.
| Control point | Suggested operational record | Release question |
|---|---|---|
| Role and scope | Legal entity, market, packaging role, packaging type, and applicable date | Has the responsible owner confirmed which duty applies? |
| Packaging specification | Controlled ID, version, material or component structure, supplier, and effective dates | Is this the approved version for the product and market? |
| Supplier evidence | Document reference, issue date, coverage, reviewer, status, and expiry or review date where applicable | Is the evidence complete enough for the responsible party's assessment? |
| Product and catalog | SKU, bundle, variant, market, channel, and packaging-version relationship | Can the store promise the item without bypassing a packaging restriction? |
| Procurement and receipt | Purchase order, supplier batch or delivery, received packaging version, and discrepancy | Did the received item match the approved specification? |
| Warehouse release | Available stock by version, pack instruction, hold reason, approver, and release time | Is the version allowed for this packing run? |
| Order and shipment | Order, fulfilment location, shipment, product quantity, and packaging-version reference | Can the business reconstruct what was used? |
| Exception and change | Superseded version, remaining stock decision, deviation, corrective action, and audit history | Was the change controlled rather than overwritten? |
Not every organisation needs every field on one screen. In a defensible operating model, packaging identity and evidence status should remain linked as the record moves from catalog planning to procurement, warehouse execution, and shipment reporting.
A ten-step implementation checklist
- Map roles before fields. For each legal entity and sales market, identify who is acting as manufacturer, importer, distributor, supplier, or another relevant operator. Have qualified legal or compliance counsel validate the interpretation.
- Create a packaging register. Give each packaging specification a stable ID and version. Record components, materials, intended use, supplier, effective dates, status, and the products or bundles it supports.
- Separate evidence from approval. Store supplier documents as evidence records with source, issue date, coverage, and review state. Do not let an uploaded file automatically mean “approved” or “compliant.”
- Link products, markets, and channels. Relate each SKU or variant to the permitted packaging version by market and channel. Include bundles, kits, replacement parts, and promotional packs where they change the packaging combination.
- Control purchasing changes. Put the required packaging version on the purchase order or approved supplier specification. Route a material, component, or supplier substitution through review before receipt and use.
- Verify the receiving handoff. Capture the version actually received, any supplier batch or delivery reference, and discrepancies. Quarantine or flag packaging that cannot be matched to an approved record.
- Add a warehouse release gate. Make the packing instruction show the approved version and any hold. Define who can release an exception, what evidence is required, and whether remaining superseded stock can be used.
- Preserve shipment traceability. Link the packaging version or controlled packing run to the order and shipment at the level proportionate to the risk. Do not overwrite history when a specification changes.
- Reconcile connected systems. Test how Odoo or another ERP sends product, inventory, order, procurement, finance, and reporting data to Shopify or another storefront. Confirm that the sales and fulfilment path cannot silently bypass an applicable packaging hold.
- Run one evidence-retrieval drill. Select a shipped order and retrieve the product, market, packaging version, supplier evidence, approval, receipt, and warehouse release. Record gaps, owners, and remediation dates.
Risks, limits, and where the hype is not useful
- PPWR does not turn every packaging obligation on at once. Treating August 12 as one universal deadline will create false assurance as easily as unnecessary alarm.
- The immediate PFAS limits discussed here concern food-contact packaging. Do not generalise them to every pack or use a generic material label as proof.
- A supplier document is an input to assessment, not an automatic compliance verdict. Manufacturers retain responsibilities described in the regulation and FAQ.
- Role, market, packaging type, transition treatment, and later application dates can change the answer. Use qualified advice for the legal interpretation.
- An ERP record cannot test material composition. It can preserve evidence, approvals, versions, and release decisions so people can act consistently.
- Odoo, Shopify, Zoho, or a custom application should not be presented as a native PPWR certification engine. Configuration and integrations must reflect the operating model and be tested.
- This article is operational guidance, not legal, chemical-safety, product-safety, or regulatory advice.
The AorBorC view
The useful system boundary is not “upload the declaration.” It is the moment an approved packaging version becomes eligible for a product, a market, and a packing run. That is where evidence, inventory, warehouse work, and the commercial promise meet.
AorBorC's Odoo implementation work can structure packaging specifications, supplier records, procurement, inventory, approvals, finance handoffs, and reporting around that boundary. Where the standard model is not sufficient, our ERP module development focuses custom logic on controlled records and observable exceptions rather than hidden automation.
For Shopify and other online channels, our e-commerce systems work connects product catalogs and checkout readiness to order, inventory, warehouse, and support workflows. The goal is not to make a storefront decide the law. It is to prevent a sales promise from outrunning the approved operational state.
That founder-led, human-reviewed approach also guides AorBorC rescue and audit work: reconstruct the flow, locate the evidence or ownership break, and build a durable control teams can operate.
Business takeaway
Packaging is no longer safe as a note attached to a product. Give it a versioned record, link its evidence to the responsible review, and make warehouse release prove which version can ship.
Your next move
Choose one EU-bound SKU and trace its packaging from supplier evidence through product setup, receipt, warehouse use, and a shipped order. If the version or approval disappears at a handoff, plan a packaging-to-ERP workflow review before automating more of the process.