How PPWR Compliance Is Structured in SyncForce

It clarifies which compliance indicators are managed at material, packaging component, packaging process, and Master Packaging System level, and how this supports scalable, auditable Declaration of Conformity management.

Scope

In SyncForce, PPWR compliance is managed differently depending on whether the packaging is part of a fixed SKU-related packaging setup or whether it is selected, assembled, or filled during operations.

SKU-related packaging covers Sales, Grouped, and Transport Packaging linked to supply chain units such as ISU (Individual Sales Unit), GSU (Groupes Sales Unit), and TSU (Transport Stock Unit). In this scenario, the Master Packaging System is the main PPWR compliance object and the main Declaration of Conformity object. Evidence starts at lower levels such as material and packaging component, and is consolidated into the MPS.

Last-Minute Packaging covers packaging selected, assembled, or filled during a controlled packaging process, such as Service Packaging, take away packaging, and eCommerce packaging. In this scenario, the Declaration of Conformity is managed on packaging component level and is complemented by a documented packaging procedure or work instruction that controls how the component is used in practice.

Two packaging scenarios in SyncForce

1. SKU-related packaging

SKU-related packaging applies where packaging is structurally linked to supply chain units and product flows, for example:

• Sales Packaging for ISU
• Grouped Packaging for GSU
• Transport Packaging for TSU

In this model, the Master Packaging System is the compliance object. It represents the approved packaging setup used for the unit placed on the market. Materials and packaging components provide the underlying compliance evidence, but the final PPWR conclusion and DoC are managed on MPS level.

For SKU-related packaging, Article 24 empty space assessment is also managed at MPS level as part of the DoC-ready compliance assessment.

2. Last-Minute Packaging

Last-Minute Packaging applies where packaging is chosen or assembled at the moment of packing or fulfilment, for example:

• Service Packaging
• Take away Packaging
• eCommerce Packaging

In this model, the packaging component is the primary DoC object. Because the final packaging outcome depends on how the component is used in practice, compliance is supported by a controlled packaging process. That process may be manual, semi-automated, or fully automated, but it must be documented and repeatable.

Core data-level logic

Material level

This is the lowest technical compliance layer. It stores the properties that originate from material composition, supplier statements, or test results.

Typical data on this level:

• polymer or material type
• recycled content
• barrier layers and coatings
• heavy metals
• PFAS relevance
• DfR-related material properties
• compostability evidence where relevant

Packaging component level

A packaging component consists of one or more materials. Material data is consolidated here into a usable compliance object such as bottle, cap, label, tray, pouch, cup, carton, filler, or mailer.

This is:

• the main technical compliance object for Last-Minute Packaging
• the building block for Master Packaging Systems in SKU-related packaging

Master Packaging System level

The Master Packaging System is the main compliance object for SKU-related packaging. It consolidates the approved set of packaging components used for Sales, Grouped, or Transport Packaging and is the level where the final PPWR compliance conclusion and DoC are managed.

This is where you typically manage:

• Article 5 final compliance status
• Article 6 recyclability outcome
• Article 7 recycled content outcome
• Article 10 minimisation outcome
• Article 11 reusable packaging outcome
• Article 12 final labelling logic
• Article 24 empty space ratio for SKU-related packaging

Packaging-process level

This level is mainly relevant for Last-Minute Packaging. It controls how packaging components are applied in practice. The process must ensure that the final packaging outcome remains within the compliance assumptions used for the component-level DoC.

Examples:

• work instruction for human packing
• controlled pack-out rule in fulfilment software
• machine setting for automated carton sizing
• defined selection logic for fillers or service packaging components

Design for Recycling logic

For Design for Recycling, the preferred SyncForce logic is:

Material -> Packaging Component -> Master Packaging System

DfR starts at material level, because recyclability is often driven by material characteristics, material combinations, coatings, adhesives, colours, layers, or separability. These inputs are then consolidated at packaging component level and rolled up into the final packaging system assessment where required.

For SKU-related packaging, the final recyclability outcome sits on Master Packaging System level.

For Last-Minute Packaging, DfR usually remains on component level unless a fixed multi-component packaging setup is assessed as a defined packaging system.

Declaration of Conformity logic

SKU-related packaging

• Main DoC object: Master Packaging System
• Evidence source: Material and packaging component records
• Use case: ISU, GSU, TSU related packaging
• Article 24 empty space: managed at MPS level

Last-Minute Packaging

• Main DoC object: Packaging component
• Evidence source: Material and packaging component records
• Additional requirement: Controlled packaging process guideline or documented procedure
• Article 24 empty space: controlled through the packaging process, not just through the component

PPWR compliance indicators by article and data level