A single instruction in Polish does not solve the work of dealing with multiple markets. A company needs a way to identify the source text, translations, market, product and approved version. Without this, a change to one warning may leave some sales channels with old or unverified content.

Start with a controlled source text

Before translation, the base text must be approved. It should derive from product data, risk analysis, intended use and foreseeable users. If the source text changes during translation, it is difficult to establish which versions are current.

The source record should have a revision number, date, owner, identification of products and markets, and substantive sources. Translations are linked to a specific revision, not just to a file name.

Product, market and language map

In practice, it is worth building a matrix containing:

Such a map shows gaps before sales begin. However, it should not by itself determine which language is required. The decision must be based on current market requirements.

Draft and approved translation

Draft text may be generated automatically or prepared by an external provider. The draft status should be visible and block use in production. Only after checking meaning, terminology, units, symbols and consistency with the product can the text be approved.

Verification is not solely a language check. The person checking should understand the product context. A literal translation of a technical term may be grammatically correct but misleading to the user.

Short warnings and full instructions

A warning on the label, text in the offer and a section of the instructions may describe the same hazard to a different extent. They should come from one controlled source, but they do not have to be identical word for word. Consistency of meaning and of the action expected from the user is important.

The system may maintain a relationship: hazard, source message, label variant, online variant and expanded text in the instructions. A change to the hazard then identifies all texts requiring review.

Symbols do not solve everything

A pictogram may reduce the amount of text, but its meaning must be appropriate and understandable. Not every symbol is widely recognised, and some require explanation. Using a symbol found on another product without confirming the basis is risky.

In the documentation, it is worth recording the source of the symbol, the version of the graphic, its meaning and the products in which it has been used. A change to a graphic file should be subject to the same control as a change to text.

Update after a product change

A new material, accessory, assembly method or user group may change the instructions. In that case, it is not enough to replace the source text. All active translations should receive the status 'to review', and the company must determine whether the change affects the whole or a specific part.

After approval, production files, labels, packaging, the website and the marketplace must be updated. For each change, it is worth retaining the implementation time and the batches from which the new version was used.

Working with a translator

The assignment should include the product, photographs, context of use, glossary, units, target market and information on safety-critical parts. A text file alone without context increases the risk of misinterpretation.

On receipt, the file must be linked to the order, supplier, date and source version. If the translator sends a correction, the previous file remains in the history. The name 'final_v2_poprawiony' does not replace a revision number in the system.

Check before placing on the market

Before activating sales, the approving person checks:

1. Whether the correct product and variant have been identified. 2. Whether the required materials have a version for the market. 3. Whether the translation refers to the current source text. 4. Whether the key warnings are consistent in the instructions, label and offer. 5. Whether the production files correspond to the approved revisions. 6. Whether the sales channels have received current content. 7. Whether the result and the responsible person have been recorded.

Withdrawal of the old version

The old instructions should not disappear from the documentation. It is necessary to know which batches received a given version and for what period it was visible online. In the event of a customer report, the company can then reconstruct the information available at the time of purchase.

A withdrawn file should be marked as inactive and protected against reuse. A materials library without statuses may cause an operator to accidentally download an outdated document.

Most common errors

GPSR / PPWR helps maintain relationships between the product, market, source text, translations and channels. It does not automatically confirm linguistic correctness or the requirements of a specific country. However, controlled versions enable a company to direct material to the right person and document approval.