A packaging label is the end of a longer process. Before artwork is created, the company must know which packaging level it describes, what materials it is made from, which market it will be used in and which markings have a confirmed source. The PPWR requires monitoring of the development of detailed rules, so it is worth building a flexible data model instead of entering content permanently into a graphic file.

Separate data from graphic design

The label file should retrieve approved information from a controlled source. If the material, mass or classification method exist only in the graphic design software, it is difficult to compare them with documentation and update them across all variants.

A data record can store the meaning of the marking, its basis, language, symbol, colour, packaging scope and period of application. The graphic design is a linked implementation that undergoes separate technical and visual approval.

Packaging levels and components

A product may have sales, grouped and transport packaging, as well as components such as a bottle, cap, label, insert and film. A marking must refer to the correct element or to the whole. A single icon on the outer carton does not always describe all the materials inside.

Therefore, the model should maintain a packaging hierarchy. For each component, the material, function, mass, separability, supplier and source are recorded. On this basis, the correct set of information can later be prepared without manually recreating the construction.

Marking register

For a marking, it is worth storing:

The list should distinguish required, voluntary, working and obsolete markings. Without statuses, it is easy to reuse a file that should not be included in a new design.

Digital carriers

A QR code or another carrier may lead to additional information, but it requires management of the target content. The link should be permanent, secure and available for the intended period. It must be known which version of the content was available for a given batch.

A carrier should not automatically replace information that must appear directly on the packaging. The decision on how to split the content must be based on the relevant requirements. The system can store the relationship between the code, address, content and packaging.

Language and market

The explanatory text for a marking may require language versions. The product markets, required languages and translation source must be determined. A version approved for one country should not automatically be given the status of ready for the whole Union.

A change to the symbol or meaning should mark the related translations and designs as requiring review. The history must retain earlier versions used on packaging still on the market.

Design approval process

Approval can be divided into steps:

1. Verification of material data and packaging scope. 2. Verification of the basis for markings. 3. Checking languages and content. 4. Checking the symbol file and its version. 5. Checking legibility, placement and contrast on the design. 6. Comparison of the production sample with the approved file. 7. Recording the implementation date and batch.

Each step should have an author and an outcome. A status of 'accepted' without scope does not show whether the data, graphic or sample was checked.

Change of supplier or material

A new supplier may maintain the appearance of the packaging but change the material or composition of a component. Such a change should trigger a review of the data and markings. It should not be assumed that the previous design remains correct simply because the dimensions have not changed.

The supplier should provide values and documents for the specific specification. After assessing them, the responsible person decides whether the design requires updating. The decision and implementation date remain in the history.

Production file control

The file library needs statuses: working, for verification, approved, in production, withdrawn. Access to the production version should be restricted so that an operator does not send outdated artwork to the printer.

It is worth recording a checksum or immutable file identifier, the supplier name and the production order. This later makes it possible to demonstrate which version was used, even if the file names are similar.

Sample check

A digital design does not show all problems. After printing, the symbol may be too small, have poor contrast, be obscured by a fold or be illegible on the material. The sample check result should include photographs, the date, the design version and the decision.

If a deviation is detected, the correction creates a new revision. The old file should not be deleted, especially if part of the batch has already been produced.

Most common errors

GPSR / PPWR can link packaging data, markings, designs, languages and batches. It does not independently select the required symbols or replace design control. However, it makes it easier to maintain sources and versions when detailed requirements and files evolve over time.