An instruction or warning is not an add-on prepared only just before publishing an offer. It is the result of work with the product's intended purpose, user group, foreseeable use and identified hazards. When a company handles multiple SKUs, the biggest problem becomes not writing the text itself, but controlling versions, languages, sources and links to the correct variant.

A warning should result from the product assessment

It is better not to start with a library of ready-made sentences. First, the product's use, users, mode of operation, materials, limitations and possible misuse that can reasonably be foreseen must be described. Only on this basis can it be assessed what risk could not be eliminated by design and what the user must be informed about.

The source of a message may be a risk analysis, a standard, a test report, the manufacturer's instructions, a market report or a decision following an incident. In the documentation, the link between the source and the content must be maintained. The text alone, without justification, makes it difficult to assess later whether it still fits the current product.

Instruction, safety information and warning

An instruction describes correct assembly, use, maintenance, storage or disposal where this is relevant to safety. Safety information may cover restrictions, precautions and what to do in an emergency. A warning draws attention to a specific hazard or prohibited behaviour. These elements should form a coherent whole, not three independent files.

In practice, it is good to store content in modules assigned to a product variant. This makes it clear which messages go on the label, which in the instructions, and which in the online offer. A change to one module can then indicate the places that need updating.

Language versions without losing meaning

Information should be provided in a language that is easily understood by consumers in the market where the product is made available, in accordance with the requirements of the relevant country. The translation must preserve the technical meaning. Automatically translating a sentence without review may change the scope of a prohibition, a unit or the order of actions.

Each language version should have a language code, revision number, date, source text and approval status. If the base content changes, previous translations should be marked as requiring review. It is not enough to replace one PDF file and assume that all sales channels are already using the new version.

Linking to SKUs and the product family

A shared instruction may cover several SKUs if it genuinely describes the same essential characteristics and hazards. The decision to share content should be explicit. Differences in power, material, user age, accessories or assembly method may require separate messages.

For a product family, it is worth keeping a matrix: common element, variant, language, channel and applicable revision. This makes it possible to reuse approved content where there is justification, without thoughtlessly copying warnings between different products.

Online offer and materials supplied with the product

In distance selling, certain safety information must be visible in the offer. It should not be assumed that a link to the instructions or a photo of the packaging will always fulfil this function. The information should be legible before purchase and correspond to the product the customer is choosing.

In the publication process, it is worth separating source content from channel formats. One approved piece of information can be used in a shop description, a marketplace field, a PDF file and on a label, but each use should indicate the current revision. A platform should not promise to send data to a channel if it in fact only prepares and organises the material.

Change control and withdrawal of the old version

A change to instructions should have a reason: a new variant, a test result, a complaint, an error correction or an updated risk assessment. The revision should include a description of the change, the author, the approver, the effective date and the list of products and channels affected.

The old version should not disappear. It is needed to establish what information accompanied a batch sold at a given time. At the same time, it must not be available as a current file for new offers. The statuses draft, to be verified, approved and withdrawn help avoid mistakes.

Checklist before approval

How a system helps without generating accidental warnings

A good system ensures completeness, links, versions and statuses. It can indicate that a variant does not have an approved instruction in the required language. However, it should not create a categorical safety message without product data or replace specialist assessment.

GPSR / PPWR stores controlled sources and revisions, so that work on messages is reproducible. Responsibility for the substantive content and its approval remains with the company.