Packaging labelled "reusable" does not yet create a reuse system. Rules are needed for circulation, return, preparation for the next cycle, identification and measurement of actual use. Data should describe both the packaging design and the process in which it operates.
A reusable product versus a functioning system
A durable bottle can be used many times by a consumer, but a reuse system also requires an organisation of flow. It must be established who issues the packaging, how it returns, where it is checked, cleaned or repaired, and when it is withdrawn.
The data model should separate packaging parameters from system parameters. This prevents a company from automatically treating a declared number of cycles as an actual operational result.
Packaging record
For packaging, it is worth maintaining:
- identifier, type and level of packaging,
- materials, weight and components,
- design enabling reuse,
- expected number of cycles and the basis for that value,
- washing, preparation and inspection conditions,
- replaceable parts and repair criteria,
- product and transport restrictions,
- supplier, specification and documents,
- method of permanent identification,
- criteria for withdrawal from circulation.
If packaging has several sizes or versions, it should be established which data are common. A difference in material or closure may affect durability and the cleaning process.
Reuse system record
The operational process should describe:
- participants and their roles,
- issue and return points,
- transport of empty packaging,
- records of cycles or the measurement method used,
- quality checks after return,
- washing, preparation and refilling,
- handling damage, losses and rejections,
- incentives or deposits, if used,
- data needed to measure effectiveness,
- contingency measures if circulation is interrupted.
The process should correspond to actual sales channels. A solution that works locally does not automatically have to cover cross-border shipment.
Identification and number of cycles
Measurement may be based on an individual identifier or a statistical model, depending on the system and requirements. The method, assumptions and limitations should be clearly recorded. The number of issues is not always equal to the number of complete cycles ending in return and preparation.
If codes or tags are used, the system should protect data, ensure the durability of the identifier and handle situations where the marking is damaged. The history cannot depend solely on one external tool without the possibility of export.
Checks after return
Packaging should undergo a defined assessment. Criteria may include damage, contamination, leak-tightness, legibility of markings and conformity of components. The result leads to reuse, repair, component replacement or withdrawal.
The inspection instruction needs a version and training evidence. Deviations should be recorded so that recurring causes of damage or shortening of packaging life can be assessed.
Washing and preparation
The process parameters depend on the application and material. The responsible entity, location, method, control values, frequency and results should be recorded. A document from the equipment supplier does not in itself confirm that each batch has been carried out correctly.
A change of agent, temperature, time or site should be assessed. If it may affect durability or safety, the related instructions and inspection criteria must be updated.
Returns and losses
The system should measure how much packaging was issued, returned, rejected, lost and remains in circulation. The data require a common period and definitions. A return rate calculated for a short period may not take account of packaging still with users.
An analysis of the causes of losses helps improve return points, communication, deposits or design. A single company-wide average may conceal a poor result for a specific market or channel.
Cooperation with partners
If part of the system is operated by an external operator, the scope of data, reporting frequency, definitions and verification method should be established. A contract does not replace operational information. The company should know which packaging and periods the report covers.
A change of partner requires the history to be retained and identifiers to be mapped. Without a migration plan, some cycles may disappear or be counted twice.
Link to product and market
The same packaging may serve different products, but the conditions are not always common. It should be indicated which applications have been approved and on what basis. The market affects logistics, return points, the language of instructions and the actual availability of the system.
A product offer should not promise reuse in a place where the customer has no real route to return or refill. Communication must correspond to the process actually in operation.
Most common errors
- treating durable packaging as a complete system,
- failing to separate design and process data,
- a declared number of cycles without a method and evidence,
- no criteria for checks after return,
- reporting issues as completed cycles,
- one average for all markets,
- no history after a change of operator,
- communicating reusability without an available reuse route.
GPSR / PPWR helps link packaging, process, participants, cycles and data sources. It does not automatically confirm that targets are met or that the system works. It does, however, make it possible to distinguish a designed possibility from actual results and to document decisions on the further use of packaging.