For most exporters shipping to Russia, customs paperwork and EAC conformity documents are the most visible part of market entry. For products within scope, though, that's not the whole story: the goods also need to be digitally marked under the Chestny Znak system. The two obligations are separate, and satisfying one does not satisfy the other.
This guide covers what Chestny Znak is, how the DataMatrix code actually works, what the process looks like step by step, what foreign companies can and can't do inside the system, and the mistakes that come up most often in practice.

Quick answer: Chestny Znak (Честный Знак, roughly "Honest Sign") is Russia's official, mandatory system for digitally marking and tracing products from production to point of sale. It is not a certificate — it's a record-and-verification mechanism attached to the product's journey, not to its physical quality.
The system is operated in Russia by the Center for Advanced Technology Development (CRPT/ЦРПТ) (source: official Chestny Znak website). Every unit of a marked product is assigned a unique DataMatrix code, requested by the manufacturer or importer, applied to the product or its packaging, and tracked every time it changes hands along the supply chain.
The purpose is to fight counterfeit and unregistered goods, create end-to-end traceability, and let a consumer verify a product's authenticity through an official app. Chestny Znak is not a quality certificate, a safety certification, or a conformity declaration — so it does not replace something like the EAC mark.
The system is often referred to informally as "Russian chipping." That name is misleading: no physical chip or electronic component is embedded in the product. What actually happens is a DataMatrix code printed on the packaging.

A product's path through Chestny Znak runs from manufacturing to final sale in a series of connected steps.
1. Scope check. Usually handled by the manufacturer, exporter, or Russian importer. Whether a product falls under mandatory marking is determined by its TN VED/HS code — not its trade name. A common mistake is assuming a product is out of scope just because it doesn't sound like a "marked" category; the classification code is what actually decides this, and getting it wrong can cause costly delays at shipment.
2. GTIN and product card creation. The manufacturer or brand owner is responsible here. Every product variant needs a GS1-compliant GTIN (Global Trade Item Number) and a linked product card (source: GS1). Incomplete or inaccurate product card data causes problems later when codes are matched to physical goods.
3. System registration and authorization. The party registering — typically a Russia-registered importer or another eligible local participant — needs a qualified electronic signature and a signed agreement with CRPT. Starting this too close to the shipping date is one of the most common causes of delay.
4. Requesting DataMatrix codes. A registered participant requests codes based on planned production volume; each code carries a cost. Over- or under-ordering creates both financial and operational friction.
5. Printing and physical application. The manufacturer or a labeling service provider handles this. Print quality, contrast and readability matter here more than anywhere else: low-resolution printing is a common reason a code becomes unscannable — and an unscannable code is treated the same as no code at all.
6. Activating codes in the system. The importer or local representative matches the codes to production or import documentation and activates them.
7. Import and customs clearance. Handled by the importer and customs broker. For imported goods, the marking data must appear in the customs declaration according to the rules for that product group, and the required notifications must be completed before the goods are released into free circulation; otherwise delays at customs are likely.
8. Reporting supply-chain movements. Every party in the chain (importer, distributor, wholesaler, retailer) is responsible for its own share of reporting. Depending on the product group and the transaction type, movements are reported through the electronic-document system, most often using a UPD document; some product groups generate this report automatically. Delayed reporting can leave a product looking "stuck" in the system.
9. Deactivating the code at retail sale. The point-of-sale system does this automatically: once the product is sold, the code is retired and its lifecycle in the system is complete.

Quick answer: DataMatrix is the square, two-dimensional barcode type used in Chestny Znak, generated uniquely for every individual unit of a marked product. It combines a GTIN, a serial number and a cryptographic verification element — which is what sets it apart from a standard barcode or a QR code.
A DataMatrix code identifies a single physical unit, not just a product category. It has three components: a GTIN, which identifies the product variant/SKU globally (not the individual unit); a unique serial number assigned to each physical unit; and a cryptographic signature designed to prevent forgery. What actually makes a unit unique and verifiable isn't the GTIN by itself — it's the combination of the GTIN and the serial number.
The image of a code can technically be photographed or copied. But if the same code is reported against more than one product, or reported more than once, Chestny Znak flags it as a duplicate or suspicious entry — which makes a copied code effectively useless in practice.
Print quality is an operational requirement, not a technical nicety. Insufficient contrast, printing the code too small, not leaving enough quiet zone around it, or printing on a glossy/reflective surface at low resolution can all make a code unreadable by scanners. An unreadable code is treated the same as an unmarked product. This is why codes need to survive production, transport and storage without physical damage.
| Feature | DataMatrix | QR code | Standard barcode |
|---|---|---|---|
| Primary use | Unit-level identification for government traceability systems | Marketing, link redirection, general information sharing | Inventory and checkout scanning |
| Data carried | GTIN, serial number, cryptographic signature | URL, text, short data | Product/category code (usually a 1D number string) |
| Used in Chestny Znak | Yes — the system's official, mandatory format | No | No |
| Uniqueness | Each unit is unique via GTIN + serial number | The same code can often repeat across products/prints | Shared at product-group level, not per unit |
| Read method | System-approved 2D scanner or the official app | Standard camera/QR reader | Laser barcode scanner |
Quick answer: DataMatrix codes are scanned at the production line, warehouse, customs, retail store and by consumers, using 2D scanners or the official mobile app. A code being physically scannable doesn't automatically mean it's correctly matched to the right product in the system — full verification also requires checking the system record.
On the production line, codes are scanned to confirm printing and application accuracy. Warehouses and logistics hubs use bulk-scanning setups. Customs checks whether the codes were reported in advance. At retail, the checkout system scans the code at the point of sale and deactivates it. Consumers can scan a code through the official app to see the product's registered information.
The point worth remembering: a code being scannable by a camera or reader doesn't by itself confirm it's valid, correctly matched, and active in the system. A reliable check combines physical readability, product data accuracy, and the system record — all three together.
Quick answer: Chestny Znak's scope has expanded in stages since 2019 and today covers more than 20 product groups (source: official Chestny Znak website). The legal basis for the product list and phase-in dates is Russian Government Order No. 792-r of 28 April 2018 and its subsequent amendments; the list is updated regularly through new government orders. That means scope should always be confirmed against the current official list and the product's TN VED/HS code — never assumed from a trade name alone.
The categories most relevant to exporters include:
This list is a general orientation — the scope changes frequently. A product's commercial name is never sufficient on its own; scope has to be checked against the product's technical characteristics together with its TN VED/HS code and, where relevant, its OKPD2 code. Even within one category, some sub-items may be excluded, so scope should be re-checked ahead of every shipment.

Quick answer: Whether marking is mandatory depends on the product's TN VED/HS classification — a product within scope cannot legally enter Russia or be sold there without it. But who actually carries out each obligation, and at what stage, is a matter to settle by contract between the exporter, the Russian importer and any local representative.
A foreign manufacturer or exporter's role inside the system is limited. As a general rule, companies without Russian tax residency cannot register directly as a fully authorized participant (source: Chestny Znak community site, on participant eligibility rules); this is handled through a Russia-based importer or an accredited branch (some sectors, such as certain pharmaceutical manufacturers, have different rules — this detail should be confirmed against current regulation for your specific product). That's why it's worth locking down responsibilities with your Russian partner in writing before shipping.
In practice, code requests, system registration and pre-clearance notifications are usually the Russian side's responsibility (importer or authorized representative), while the accuracy of product card data, print quality and timing sit largely with the exporter. Putting these roles in writing before shipment avoids both delays and disputes over who was responsible for what.
| Party | Main responsibility | Pre-shipment check |
|---|---|---|
| Exporter / manufacturer | Accuracy of product card data, print quality, on-time delivery | Confirm early whether the product is in scope |
| Russian importer | System registration, code requests, pre-clearance notification | Electronic signature and system access ready |
| Labeling/coding service provider | Matching codes to the correct SKU, print testing | Verify code-to-product matching before shipment |
| Customs and logistics | Managing clearance after notification | Confirm notification status before customs |
| Distributor/retailer | Handover reporting (usually UPD), deactivation at sale | Every change of hands reported on time |
Quick answer: An HS code is the standard international customs classification; Russia/the Eurasian Economic Union uses its own version, TN VED. GTIN is a product variant's global trade identification number under the GS1 standard. OKPD2 is Russia's domestic economic-activity classification. All four serve different purposes and are not interchangeable.
| Concept | What it's for | Who uses it, and where | Relevance to Chestny Znak |
|---|---|---|---|
| HS code | Classifies a product for customs tariff purposes | Customs authorities and import/export procedures worldwide | Reference point for finding the Russian TN VED equivalent |
| TN VED | Russia/EAEU's version of the customs tariff classification | Russian customs, Chestny Znak scope determination | Directly determines whether a product is in scope |
| GTIN | Identifies a product variant/SKU globally (not the physical unit) | Manufacturer/brand owner, via GS1 | The core identifier embedded in the DataMatrix code; combined with a serial number to make each unit unique |
| OKPD2 | Groups products and services under Russia's domestic classification | Russian official registration and statistics | Sometimes used as a secondary reference for scope |
An HS code and Russia's TN VED code both follow the same Harmonized System logic, but they are not identical line-for-line — so the TN VED equivalent needs separate confirmation. GTIN is an entirely different system: it has nothing to do with customs classification and everything to do with a product variant's global identity; what makes a specific physical unit unique is pairing that GTIN with a serial number.
Labeling can happen at different points in the supply chain, and the right model depends on the product group, the manufacturing location and the logistics chain — so treat the options below as a general framework to be confirmed for each product group.
| Labeling model | Advantage | Risk | Best suited to |
|---|---|---|---|
| On the production line | No extra logistics step; issues are caught early | Requires investment in printing infrastructure and integration | High-volume, regular exporters |
| Pre-shipment via a third-party service | No production-line investment needed; flexible | Extra time and cost, coordination overhead | Variable-volume or new exporters |
| In Russia / bonded warehouse | Leverages local expertise on the Russian side | Requires timing and communication coordination | Companies with a strong local partner in Russia |

No. EAC conformity certification/declaration and Chestny Znak digital marking are separate obligations.
EAC shows that a product meets Eurasian Economic Union technical regulations — it's about safety and quality compliance. Chestny Znak is about digitally marking a product and tracing it through the supply chain. Holding an EAC certificate does not exempt a product from marking obligations; where a product is in scope for both, each requirement has to be met separately.
| Mistake | Why it happens | How to prevent it |
|---|---|---|
| Wrong HS/TN VED classification | Classifying by trade name instead of technical specification | Verify classification with a specialist based on technical characteristics |
| GTIN and physical product data don't match | Production starts before the product card is updated | Cross-check product card against physical goods before shipment |
| Confusing DataMatrix with QR | Teams assume the two formats are interchangeable | Confirm format before printing |
| Poor print quality | Using unsuitable printing equipment | Print testing and scanner verification |
| Code applied at the wrong packaging level | Unit/case/pallet levels not clearly separated | Plan codes by packaging level in advance |
| Ordering unplanned or unused codes | Estimating production volume loosely | Match orders to the actual production plan |
| Codes matched to the wrong SKU | Manual matching errors | Automate or add a double-check step |
| Skipping pre-clearance notification | Timeline not built into the shipping plan | Integrate the notification deadline into shipping planning |
| Delayed UPD/data reporting | Poor coordination between supply-chain parties | Define reporting responsibilities contractually |
| Assuming EAC covers marking | Confusing the two separate obligations | Track both processes independently |
| Responsibilities not defined in the contract | Roles agreed verbally instead of in writing | Put responsibility splits in writing |
| Missing regulatory phase-in dates | Scope not checked regularly | Schedule periodic scope reviews |
| No process for returns, samples or destroyed goods | Assuming these follow the normal sales flow | Build a separate procedure for these cases |
If a product within scope enters Russia or reaches the market without proper marking, several risks can materialize at once:
Under Russian law, producing, releasing or selling unmarked goods can result in an administrative fine and confiscation of the products (source: Russian Code of Administrative Offenses, Article 15.12); the size of the penalty depends on the type of violation (production versus sale), the offender's status (individual, official, or legal entity) and the quantity involved. In especially large-scale or deliberate cases, the law also allows for criminal liability. Because exact figures and thresholds vary by product group and by the specific violation, it's worth confirming current regulation with a legal advisor before shipping.
Quick answer: Chestny Znak governs how a product must be marked — it says nothing about whether exporting that product to Russia is permitted in the first place. Depending on where you're shipping from, that's a separate check that has to happen alongside marking compliance, not instead of it.
Since 2022, a number of jurisdictions — including the EU, the US, the UK and others — have progressively tightened export controls and sanctions affecting trade with Russia, covering categories such as dual-use goods, certain industrial and electronic components, and specific raw materials, with growing scrutiny of trade routed through third countries. These rules are updated frequently and vary significantly by jurisdiction and by product.
This check doesn't replace Chestny Znak marking, and marking doesn't replace it either — they're independent requirements that both need to be satisfied where applicable. Because export-control classifications and sanctions lists change with each new regulatory update, it's worth confirming your product's current status with your national export control authority or a trade compliance specialist before finalizing a shipment.
Chestny Znak planning should begin at the production and packaging stage — not when the shipment reaches customs. The number of products and SKUs, GTIN preparation, the electronic signature process, system registration, printing infrastructure and any software integration all affect the overall timeline. Because these variables differ from company to company, a fixed, guaranteed timeframe isn't realistic; every company's process runs on its own readiness.
Pre-shipment checklist:
Given the technical detail and timing involved, most companies find this process difficult to run entirely on their own. Professional support can make a difference in areas such as:
This support doesn't make the process risk-free — its purpose is to catch problems early, reduce delays, and make responsibilities clear.
If you're not sure whether your product falls under Chestny Znak, or you want clarity on where you stand in the process, getting a pre-assessment before your production and shipping schedule is locked in can save both time and cost. When you reach out to the Chestny Znak Türkiye team, you can expect a scope assessment based on your product's TN VED/HS code, a list of the steps needed for registration and code requests, and concrete feedback on printing and reporting — plus support managing the technical and language gap between Turkey and Russia, so you're not left translating regulatory correspondence yourself. Export control and sanctions screening for your own jurisdiction is a separate matter best handled with your national trade compliance advisor. If you'd like to set the process up correctly from the start, get in touch with the Chestny Znak Türkiye team (English-language assistance is available on request).
Chestny Znak is about your products' legal and operational compliance; your digital identity in the Russian market is a separate matter. Companies exporting to Russia on a regular basis, or planning a lasting presence there, may want to secure their brand name under a .ru domain. A local domain can read as a market-focused, trustworthy digital presence to Russian users, and it helps prevent your brand name from being registered by someone else first. Registering a domain doesn't replace trademark registration, regulatory compliance, or Chestny Znak registration — it's a separate, complementary step. If you're mapping out your digital presence for the Russian market, check .ru domain availability and registration options.
Chestny Znak is Russia's official digital marking and traceability system, tracking products from production through to sale. Every unit gets a unique DataMatrix code, and its movement through the supply chain is reported to a government system. It's operated by the Center for Advanced Technology Development (CRPT/ЦРПТ).
It depends on the product. If your product's TN VED/HS code falls within mandatory marking scope, it cannot legally enter Russia or be sold there without being marked. Products outside that scope have no such obligation — so scope needs to be checked before every shipment.
No. Chestny Znak doesn't certify a product's quality or safety — the system exists to trace products from production to sale and combat counterfeiting. Conformity documents like EAC are a separate obligation and don't replace marking.
Yes, that's a common informal name for Chestny Znak, but it's misleading — no physical chip or electronic component is added to the product. The system relies on a DataMatrix code printed on the packaging.
A registered participant — usually a Russia-registered importer or another eligible local participant — requests the code through the CRPT system. Before requesting, you need ready GTIN and product card data, a qualified electronic signature, and completed system registration.
No. Both are 2D barcodes, but they serve different purposes. A DataMatrix code combines a GTIN with a unique serial number and a cryptographic signature for each unit. A QR code is typically used for links or general information and isn't an accepted format in Chestny Znak.
No. EAC shows a product meets technical regulations; Chestny Znak is about digital marking and traceability. Where a product is in scope for both, each obligation has to be satisfied separately — one doesn't cover the other.
Yes — these are separate, independent checks. Chestny Znak governs how a product must be marked; it says nothing about whether the export itself is permitted. Depending on your jurisdiction (EU, US, UK and others all maintain their own rules), you may need to confirm your product isn't subject to export restrictions or sanctions before shipping, regardless of its Chestny Znak status.
As of today, more than 20 product groups fall under mandatory marking, including textiles, footwear, perfume and cosmetics, pharmaceuticals, dairy, bottled water and beverages, tobacco products, tires, and certain electronics. Because scope keeps expanding, check your product's status against the current official list and its TN VED/HS code.
As a general rule, companies without Russian tax residency can't register directly as a fully authorized participant. This is handled through a Russia-based importer, an accredited branch, or an authorized representative. Some sectors, like certain pharmaceutical manufacturers, may have different rules — confirm this against current regulation for your product.
Labeling can be done on the production line, through a third-party service before shipment, or in Russia/a bonded warehouse. Which model fits depends on the product group, manufacturing location and logistics chain, so check the group-specific rules before choosing.
A DataMatrix code that can't be physically scanned is treated the same as an unmarked product, which can cause customs delays, blocked sales, or re-labeling costs. That's why print quality testing before mass production matters.
There's no fixed timeframe. It depends on the number of products and SKUs, GTIN preparation, the electronic signature process, system registration, printing infrastructure, and how prepared each party is. It's best started at the production planning stage, not close to shipment.
GTIN is a product variant's global trade identification number, embedded in the DataMatrix code; what makes a physical unit unique is pairing the GTIN with a serial number. An HS code is the customs tariff classification, with TN VED as its Russian equivalent. The two serve completely different purposes.
Because the process mixes legal, technical and operational elements, advisory support can help set up scope checks, registration coordination, code and printing steps, and reporting management correctly and early, reducing the risk of delays and rework.