Mandatory Digital Marking of Medical Devices in Russia

1. Key takeaways

Russia applies mandatory digital marking to certain medical devices («Честный ЗНАК», Data Matrix codes). The framework rules are set out in Government Decision No. 894 of the Russian Federation (31 May 2023), and category expansion is advanced by subsequent decisions, such as Government Decision No. 375 (6 April 2026): newly added categories become subject to mandatory marking from 1 September 2026, and the marking must be completed before release of the goods. The timing rule converts marking from a warehouse-level task into a customs and logistics task, because the code and the data submission must exist before the goods are released into circulation.

For portfolio planning, the operative point is that the category lists move in batches, and each batch has its own effective date confirmed by official announcements. A product that is outside the marking scope today may enter it with the next decision, so the quarterly reconciliation of product lists against official announcements is not optional housekeeping but the mechanism that prevents a product from becoming non-compliant at the border overnight.

The obligations also reach beyond the importer that physically handles the goods. Because marking must be completed before release, and because the code data must match the registration records and the label, the manufacturer, the authorised representative and the importer share one data chain: any correction of a model designation, a batch numbering change or a labelling revision has to propagate simultaneously into the marking data and the registration records. Treating these as three separate compliance silos is the surest way to produce the inconsistencies described below, which surface at tenders, hospital acceptance and inspections at the same time.

2. Legal basis

The marking regime is defined by a framework decision and category-specific expansions, and interacts with the separate rules on imports of unregistered devices and with the Union-level requirements for marking content. The instruments are summarised below.

Note: the specific effective dates for individual categories are advanced in batches and official announcements prevail. The complete list for each category has not in this instance been verified item by item against the official catalogue; this guide instead sets out a verification method based on the official announcements.

3. Expert insights

Insight 1: marking is a pre-release obligation, not a Swipe added after warehousing. Marking and data reporting must be completed before the goods are released. This requirement pushes the marking action forward into the customs clearance and logistics stage, and compresses the preparation time available to the importer. The practical implication is that printing, data submission and exception handling must be attached to a defined step of the shipping process, with a named owner, because a consignment that arrives at the border without codes has no lawful way to catch up after release.

Insight 2: marking and per-batch notification are two different things. The former belongs to the marking system; the latter belongs to the import / placing notification under RZN Order No. 11020. The two run in parallel and cannot substitute for each other. A device can be correctly marked and still non-compliant if the batch notification has not been filed, and vice versa. Compliance matrices for imports should therefore carry both obligations as separate lines with separate owners and separate deadlines.

Insight 3: the marking data must be consistent with the registration records. The information inside the code must match the register records and the model and batch on the label; inconsistencies surface simultaneously in tenders, hospital acceptance and inspections. Because the code data is machine-readable and centralised, a mismatch is not a local defect that can be explained away at one counter — it propagates into every downstream checkpoint that scans the code.

4. Practical recommendations

The recommendations below keep marking status, process ownership and data consistency under continuous control.

1. Reconcile the marking category lists against your own products once a quarter, and confirm whether any product enters a newly added batch of categories.
2. Embed the marking action into the order — production — shipping flow, and define explicitly which step of the process is responsible for printing and data reporting.
3. Agree completion milestones with the importer for marking before release, and write the allocation of responsibility into the service agreement.
4. Verify code data against the register records and label model and batch before each shipment, so that inconsistencies are corrected at the source rather than discovered downstream.

5. Verification checklist

The checklist below evidences control over scope, process and data consistency.

• □ It has been confirmed whether the product falls within the effective marking category lists
• □ The marking action is embedded in the production and shipping processes
• □ The milestone of completing marking and data reporting before release is written into the agreements
• □ The information inside the code is consistent with the register records and the label
• □ Official announcements on category updates are reviewed every quarter
• □ The parallel per-batch notification duty under Order No. 11020 is tracked separately

Regulatory information verified as of 29 October 2026.

GRZAN supports manufacturers and importers in Russia with mandatory digital marking under the Chestny ZNAK system, including category scope monitoring, pre-release marking workflows, data consistency checks and the parallel RZN notification duties, alongside vigilance, recall and inspection readiness services for the post-market cycle. For marking and post-market support, contact us at info@grzanglobal.com.