PPWR and Packaging Data in Dynamics 365: Planning vs. Shipping

A product may have an exact packaging specification, yet the shipment leaving the warehouse looks completely different. How can Dynamics 365 connect the plan, actual packaging, and data foundation for packaging reporting?

Inspiration

Let us illustrate the difference between planned and actual packaging in a standard shipping scenario. A customer orders several types of products, each with its own consumer packaging. The warehouse consolidates them into a single shipping box, adds void fill, and—for larger shipments—also uses a pallet, stretch wrap, and strapping. However, the standard box happens to be out of stock, part of the order will ship later, and one of the shipments is bound for an international destination.

As a result, several distinct views of packaging coexist side by side within the enterprise system: product specifications, materials consumed in manufacturing, transport packaging plans, the actual closed container, and the costs of purchased packaging materials. Each of these data points may be correct, yet each describes a different facet of reality.

For packaging compliance reporting, simply selecting a single record or report is therefore insufficient. A company needs to know which data points represent the plan, which confirm the actual packaging, and how specific packaging materials are mapped to the shipment, legal entity, and target market. Using this exact scenario, we will demonstrate what can be captured in Dynamics 365 Supply Chain Management, the role played by Dynamics 365 Finance, and where it may be necessary to augment the process or the data model.

Why Manage Packaging Data in Your ERP

EU Regulation 2025/40 on packaging and packaging waste (PPWR) generally applies from August 12, 2026. However, individual obligations have their own deadlines, and some depend on implementing or delegated acts. For example, according to the European Commission's current interpretation, more detailed design-for-recycling requirements will apply later. It is therefore necessary to verify the company's specific role, packaging type, target market, and applicable date, rather than relying on a single "PPWR deadline."

For manufacturers, importers, and distributors, it is useful to translate the regulation into operational questions: Do we know what the packaging consists of and how much it weighs? Can we substantiate the source of these values? Can we identify which packaging accompanied a specific delivery and who placed it on the given market? Can we correct an exception without losing the audit trail? The Czech EKO-KOM report and methodologies may serve as one of the outputs, but they do not automatically cover all PPWR obligations.

Planned Packaging and Actual Packaging Are Two Distinct Layers

Product packaging, packaging materials in the BOM, or item-level packaging assignments can all be defined in advance. These data points represent the intended configuration and work well as long as operational reality does not deviate. In the warehouse, however, an additional layer emerges: multiple items are consolidated into a single box, an operator selects an alternative box size, adds void fill, and places the shipment on a pallet. A partial shipment then splits the original order across multiple physical packages.

In this model scenario, sales packaging can be assigned to individual units in advance. The shipping carton, its actual type, and its association with the contents are established during packing. Void fill, tape, or stretch film, however, are not necessarily accounted for simply because an operator closes a container. The variance between plan and reality must therefore be captured through a controlled process.

It is equally critical not to conflate three distinct figures. Purchasing 1,000 boxes indicates what the company procured. Warehouse issues reflect consumption—provided the material is actually tracked as inventory. Packaging placed on the target market is derived from specific fulfillment flows and the company’s legal roles. Neither warehouse on-hand balances nor purchase invoices constitute packaging compliance reporting on their own.

What Dynamics 365 Supply Chain Management Offers Out of the Box

Microsoft Dynamics 365 Supply Chain Management includes two relevant yet distinct areas.

Packaging Materials and Fees

The Packing materials and fees functionality enables the definition of material codes and their units of measure, packaging groups, packing units, material weights, and time-valid fee rates. Assignments can be configured for a specific item, an item group, or all items. The sales order line utilizes the packing unit and its quantity, which can be modified during partial delivery or invoicing. Following the invoicing of a sales order, packaging material transactions are generated with weights corresponding to the sales line. For invoiced purchase lines, the documentation indicates that transactions must be created manually.

This area provides an appropriate foundation for tracking standard packaging linked to a product or commercial transaction. A company can thus work with a defined material type, its weight, and quantity, using these values as a data source for subsequent packaging compliance reporting. However, it does not automatically verify that the warehouse actually used that specific shipping box, quantity of void fill, or stretch film.

Containers and Packing Work

The packing station allows operators to validate items and quantities, pack them into a specific container, and record its type, contents, dimensions, and gross weight. Among other attributes, the container type carries its tare or estimated packaging weight and capacity constraints. The Warehouse Management mobile app can support container creation, packing, and closing; starting in version 10.0.45, packing work also supports recording the worker identity and partial shipment scenarios.

In contrast, automated wave containerization proposes containers and picking work based on predefined rules. However, this remains a plan until operational execution confirms its utilization or modification.

Even a closed container, on its own, may not represent a complete material balance for the shipment. Void fill, tape, or stretch film are not automatically recorded as exact consumption. For packaging compliance reporting, it is therefore necessary to verify the links between containers, packaging material transactions, and any actual warehouse consumption.

Dynamics 365 Finance provides a cost and liability framework for the data

Microsoft Dynamics 365 Finance helps track packaging procurement, accounts payable, cost centers, financial dimensions, and controlling. These accounting records answer how much the packaging cost and where the expense was allocated. They do not necessarily indicate which materials were dispatched in a specific shipment.

The standard calculation of packing material fees must also be interpreted correctly: Microsoft explicitly states that while fees can be calculated and reported, the calculation does not generate general ledger transactions. Any resulting liability, ledger posting, or downstream process therefore requires a separate design aligned with Czech regulations and the company's compliance responsibilities.

If a company uses Dynamics 365 Finance without Supply Chain Management, it does not automatically have access to SCM warehouse packing stations and containers. Operational data must originate from SCM, an external WMS, a manufacturing execution system, or another source, and must share common identifiers for the shipment, item, material, and legal entity.

Multiple Warehouses and Countries Require a Common Data Language

Weight and material composition must have a traceable source: supplier specifications, technical data sheets, internal measurements, or approved product documentation. For each value, it is necessary to record the unit of measure, scope of use, and effective date. When a box or film changes, the new entry must not overwrite historical data in a way that prevents the reproduction of earlier periods.

Dynamics 365 can hold structured data and references, but the requirements for versioning, approvals, and document retention must be evaluated for the specific solution. If the ERP is not a suitable document repository, integration with a document management system (DMS or ECM) can be considered. The link must preserve the identity of the version applied to a given transaction; an attachment alone without controlled validity is insufficient.

Get Support with Packaging Compliance Reporting and Dynamics 365 Configuration

You do not need to start with an enterprise-wide project. As a first step, you can select a single warehouse, a representative product group, and several actual shipments: a mixed order, a substituted box, a pallet delivery, a partial shipment, or an export consignment. For each shipment, we will jointly trace the journey from product specification and sales order through the packing station to the accounting and packaging reporting output. We will compare the defined packaging, the shipping container actually used, auxiliary packaging materials, and the target market.

We will help you map the process and data sources, assess the configuration of Dynamics 365 Finance and Supply Chain Management, and verify which out-of-the-box capabilities can be utilized in your specific version and configuration. We will identify missing records or data links and propose the necessary integrations, system customizations, or reporting solutions.

The outcome of this initial assessment will be a concrete overview of what you already track, where system data diverges from actual packaging, who is responsible for individual data points, and which subsequent steps take priority. ERP configuration alone does not replace legal assessment nor does it automatically ensure PPWR compliance; however, it can establish a reliable data and process foundation for meeting regulatory obligations.

FAQ / Frequently Asked Questions

Is Configuring Packaging on the Item Sufficient for Packaging Records??

Not always. Assigning packaging to an item accurately defines standard packaging, but mixed shipments, substituted boxes, void fill, or pallets only originate during shipping. A company must determine when standard specifications are sufficient and when actual usage must be recorded.

Does standard SCM automatically link a closed container to every packaging material?

The documentation describes containers and packaging material transactions as separate functional areas. Therefore, it cannot be assumed that closing a container will automatically generate an exact material balance for void fill, tape, and stretch film. The integration must be verified within the specific version and configuration in use.

Is the system container weight an actual weighed value?

Not necessarily. The container type can use actual or estimated tare weight, and the system calculates the weight from available data; depending on the configuration, it can be confirmed or adjusted during the process. For audit purposes, it is essential to distinguish between measurement, calculation, and manual adjustment.

Can the Quantity Placed on the Market Be Derived from Packaging Purchases?

Only after incorporating defined business rules and additional data flows. The purchased quantity may remain in inventory, be consumed in production, be utilized for a different market, or be scrapped. The output must be derived from relevant operational transactions and the company's designated supply chain role.

How to Handle Box Substitution During Packing?

The worker must be able to select the actual container type, and the process must maintain the link to the shipment. If the change impacts other materials, the method for recording them and reviewing the variance against the plan must also be defined.

Does deploying Dynamics 365 ensure PPWR compliance?

No. Finance and SCM can provide essential data and govern part of the process, but the legal obligation depends on the company's role, the packaging, the market, and the compliance deadline. System configuration should follow the legal and process definition of the required output.