Document and Labelling Language Requirements in Belarus

1. Key takeaways

Application documents, labelling and instructions for use for devices in Belarus must be submitted in Russian or Belarusian; language compliance is a hard threshold at the acceptance level, not a soft requirement at the translation-quality level. The requirement operates on two fronts simultaneously: it governs whether a registration file is accepted for review, and it governs whether the product may lawfully circulate on the market after registration. Consistency between label content and the registration dossier is a standing inspection focus in post-market checks — a label that drifts from the registered information is treated as a violation even if the drift looks minor. For manufacturers, the practical reading is that language work is a compliance deliverable, not a procurement afterthought: the same set of translations typically serves both the review and the market, so the terminology must be fixed once, applied everywhere, and version-controlled so that every label revision can be traced back to the dossier entry it implements.

2. Legal basis

3. Expert insights

Insight 1: The language requirement has two layers — the filing language and the market language. The filing language decides whether materials are accepted for review; the market language decides whether the product may be lawfully sold. Both must be satisfied, and in practice both are served by the same set of translations. Companies that treat them as separate projects — one translation for the dossier, another for the label once the certificate arrives — create two terminology universes that diverge over time, and the divergence is exactly what post-market inspections look for. The efficient approach is to plan translations for dual use from the start: the wording prepared for the application documents should be reusable, unchanged, on the label and in the instructions for use, so that approval and market language are one continuous system rather than two reconciliations waiting to happen.

Insight 2: Terminology consistency matters more than fluency of the translation. Russian-language medical device terminology is a relatively fixed system, and reviewers search and compare documents by term. A translation that invents renderings or uses inconsistent equivalents across documents will be asked to unify — and the unification round consumes review time, sometimes a full correction cycle inside the 90-calendar-day limit. Fluency without consistency is therefore a liability, not an asset. GRZAN recommends fixing a terminology table at project start: product name, component names, intended-use statements and recurring risk phrases are settled first, and every translator and every document works from that table. The table should also become the reference for label wording, so the same terms appear in the dossier and on the box without a separate negotiation when the label is drafted.

Insight 3: Label content must match the registration dossier. The product name, manufacturer, intended use and registration information shown on the label and in the instructions for use must agree with the registration dossier. After market entry, any deviation between label and registered information is treated as a violation in circulation checks — there is no materiality threshold that excuses small drift. This makes label governance a continuing obligation, not a one-time task at registration: every label revision must be checked against the dossier, and where the revision itself requires a dossier amendment, the amendment should precede or accompany the label change, never trail it. The companies that stay clean in inspections are those that treat the registered dossier as the single source of truth for every word that appears on the product.

Insight 4: The national technical regulation TR 2010/006/BY is the carrier of safety requirements at the national level. The Belarusian national technical regulation system exists in parallel with the Union-level decisions of the EEC. On the national pathway, the requirements of TR 2010/006/BY — including its safety and information requirements covering labelling and instructions-for-use language — must be checked on their own terms; on the Union pathway, Union instruments such as Decision No. 27, whose Section 13 addresses marking requirements, take precedence as the reference set. Mixing the two is a classic dual-track error: a label built to No. 27 alone may miss a national-pathway requirement, and vice versa. Dual-track projects should therefore run two requirement checklists side by side and record, per requirement, which instrument it comes from and which pathway it binds.

4. Practical recommendations

1. Fix the terminology table before translating. Settle the product name, component names and intended-use statements first, and apply them uniformly across all documents, labels and instructions.
2. Prepare labels and instructions in step with the registration file. Do not wait for the certificate; build the label alongside the registration documents so consistency is designed in rather than reconciled afterwards.
3. Map label versions to dossier entries. Establish the traceability rule that every label revision points to the corresponding dossier clause, so post-market checks can be answered from records, not memory.
4. For dual-track projects, check both language-requirement sets. Verify the national pathway against TR 2010/006/BY and the Union pathway against Section 13 of Decision No. 27; never merge the two checklists.

5. Verification checklist

• □ Core terminology table fixed before translation started
• □ Application documents submitted in Russian or Belarusian
• □ Labels and instructions for use prepared in step with the registration documents
• □ Traceability between label versions and registration dossier entries established
• □ For dual-track projects, TR 2010/006/BY and Section 13 of Decision No. 27 checked separately

Regulatory information verified as of 2026-10-30.

On the Eurasian Economic Union market, GRZAN’s core capabilities concentrate on three points. First, distinguishing the applicable conditions and remaining time windows of the two pathways — Union-wide registration versus national registration in each member state: the national registration procedure for medical devices in Belarus has been switched wholesale by Council of Ministers Resolution No. 211 of 2026-04-28 (state register No. 6-1/55925, effective 2026-05-01), which compressed the total time limit for preliminary technical works to 90 calendar days, closed the list of such works and prohibited the organising body from expanding it, while the window for filing applications under the national procedure treats 2027-12-31 as the critical cut-off — pathway selection must therefore be decided in step with the time window. Second, authorised representative services: GRZAN can act as the manufacturer’s statutory representative in Belarus, undertaking registration filings, responses to technical queries, registration dossier amendments and post-market reporting obligations, and has synchronised its coordination mechanisms after Council of Ministers Resolution No. 378 of 2026-07-27 (effective 2026-07-30) transferred adverse-event functions to the state organisation for pharmaceutical supervision. Third, quality system and testing support: assistance in establishing a quality management system conforming to ISO 13485, and in organising technical documentation according to the target pathway — the national pathway follows the annex to Ministry of Health Resolution No. 55, while the Union pathway follows EEC Council Decision No. 46.

For business inquiries: info@grzanglobal.com