Chestny Znak for Textile and Apparel Exports to Russia: A Sector Guide (2026)

Textiles, ready-to-wear and footwear are among the strongest export lines from Türkiye to the Russian Federation. They are also the product groups that entered Russia’s mandatory labelling system, Chestny Znak, earliest and whose scope is widened most often. This guide sets out how a textile or apparel exporter should structure the labelling process step by step, who is responsible for what, and the mistakes we encounter most often in the field.

Why do textiles and apparel need particular care?

The logic of the system is the same in every sector: a unique DataMatrix code is generated for each product, printed onto it, and the product’s movement from production to final sale is tracked centrally. But ready-to-wear has several sector-specific features that complicate it:

• Variant density: the size, colour and fabric composition of the same model produce different product identities. A single collection can mean hundreds of separate product cards.
• The physics of the label: the code must stay readable through washing and handling. The choice between a fabric label, a card tag and a packaging label matters as much as print quality.
• Subcontracted production chains: manufacture is often spread across several workshops. If it is not defined from the outset at which stage and by whom the codes will be printed, the shipping day brings a blockage.
• A widening scope: the scope in light industry grows regularly. A sub-group outside the scope today can be inside it in the next period.

Scope: which products are subject to mandatory labelling?

Footwear was one of the first groups made mandatory. In light industry the obligation came into force in stages, and the scope has since been widened several times by Russian government regulation. New sub-groups entering scope in the 2026 period include protective workwear, hard hats, life jackets, leather belts and work gloves.

In practice the only correct answer to the scope question comes from a check at customs-code level. A product name or commercial description can mislead; what decides is the product’s position in the Russian customs tariff. In textiles and apparel the most common headings fall under knitted clothing, woven outerwear, home textiles, leather clothing and footwear. The scope check is the first and most critical step of the project — skip it, and all the rest of the planning rests on a wrong foundation.

Three questions for the scope check

1. What is the product’s customs code on the Russian side?
2. Is that code on the mandatory labelling list currently in force?
3. Which date starts which obligation for that group — code generation, pre-customs labelling, the ban on selling unlabelled stock?

Who is responsible: the manufacturer or the importer?

In exports to Russia the labelling obligation falls on the party placing the product on the Russian market — in most scenarios the importer in Russia. The importer registers in the system, opens the product cards and requests the marking codes. But the physical application of the codes usually happens at the manufacturer’s factory, because the product is expected to be labelled before it reaches customs.

This split is the most fragile point in the process: the party requesting the codes and the party printing them are different. Code files have to reach the manufacturer in the right format, mapped to the right variant, and on time. When exporters struggle to build that bridge, shipments slip. That is exactly why we run the process end to end: our Moscow office handles registration and code requests on the importer’s side while we set up the production and printing flow in Istanbul.

The process, step by step

1. Scope and customs code analysis. Working from the collection list, we establish which products are subject to mandatory labelling.
2. System registration and electronic signature. The Russian legal entity registers in the system with a qualified electronic signature (UKEP). The electronic document flow (EDI) infrastructure is set up.
3. Opening the product cards. A product identity (GTIN) is defined for every variant and the product card is completed. The size and colour breakdown is settled at this stage.
4. Requesting the marking codes. Unique codes are generated to match the order quantity and delivered as print-ready files.
5. Printing and labelling. The codes are applied to the product on the production line. Label type, print resolution and a read test are verified at this stage.
6. Entry into circulation and shipping report. The codes are reported to the system; the products become traceable through customs and afterwards.
7. Reporting along the chain. Import, warehouse movements and wholesale transfers are reported in the system.

The five mistakes we see most often

• Incomplete variant descriptions. When the size and colour breakdown is not reflected in the product cards, the codes generated do not match the physical stock.
• Unreadable printing. Low print resolution or the wrong label material leaves the code unreadable to a scanner. A verification test after printing is essential.
• The label in the wrong place. Positions that are damaged in washing, or lost when the packaging is opened, cost a great deal later.
• Starting the process in shipping week. Registration, the electronic signature and the product cards all take time; labelling belongs at the beginning of the shipping plan, not the end.
• Neglecting the reports. Printing the code is not enough on its own; the product’s movements along the chain also have to be reported.

Marketplace sales: where the chain breaks most often

A significant share of companies shipping textiles to Russia now sell through marketplaces such as Wildberries and Ozon. The most common mistake here is treating labelling as “a job that ends at customs”.

In fact the logic of labelling extends all the way to the final sale. The code has to move correctly through the system as the product enters the marketplace warehouse, leaves it, and is sold to the end consumer. The marketplace takes on some of this reporting on its own side; but the match between the product card data and the code on the physical item remains the supplier’s responsibility.

The typical blockages we see in the field:

• Variant mismatch: when the size/colour breakdown on the marketplace differs from the GTIN breakdown on the product card, goods arriving at the warehouse are not recognised by the system.
• Unreadable code: a code that cannot be scanned at warehouse receipt can lead to the whole batch being returned — which is exactly why the test batch at the factory matters.
• Reporting gap: the exporter prints the code and ships, the importer does not file the transfer report, and the product cannot be listed for sale on the marketplace.

The weakest link in the chain is usually not technology but staff who do not know the process. The warehouse and operations team on the Russian side knowing the scanning and reporting flow matters at least as much as print quality. You can check what a code in your hand actually returns in seconds with our free code lookup tool.

1 October 2026: product cards will be verified

There is a concrete date approaching for this part of the chain. According to publicly available sources, the federal law regulating the platform economy in Russia (289-FZ) takes effect on 1 October 2026 and places a new obligation on marketplaces: verifying the seller and the product documentation before a product card is published.

The scope as reported has two parts:

• Seller verification: checks against the EGRUL register for companies, EGRIP for individual entrepreneurs, and identity/registration via Gosuslugi.
• Document and code verification: certificate of conformity, declaration of conformity, a refusal letter (отказное письмо) where applicable, and Chestny Znak labelling codes — checked before goods are cleared for sale.

New cards do not go live until they pass this check. For cards published before 1 October, a 180-day transition period is reported — existing cards are not blocked on the day, but are expected to be brought into compliance within that window.

What changes for an exporter? Until now labelling was, for most companies, a job that ended when the goods shipped. Under this regulation the state of your codes and documents directly decides whether your product can be listed for sale in Russia at all. Your goods can sit in the warehouse and still not be sellable if the card fails verification.

The practical step: before the season, put two questions to your buyer in writing — are your registrations (EGRUL/EGRIP, Gosuslugi) current, and are the documents and codes for our products ready for card verification? Those two answers are the cheapest way to avoid a surprise in October.

What happens if you are not compliant?

With unlabelled or incorrectly labelled goods the nearest risk is commercial: the goods wait at customs, the delivery date is missed, the relationship with the buyer suffers. Beyond that, Russian regulation provides for administrative sanctions and seizure of the goods for breaches of the labelling obligation, with the scope of the sanction depending on the nature of the breach. Date limits are also imposed on selling unlabelled stock in the groups brought into scope — which puts direct time pressure on a buyer holding unlabelled goods in a warehouse.

Frequently asked questions

Are footwear and textiles subject to the same rules?
Both fall under mandatory labelling but are managed as separate product groups; scope dates and product card fields can differ. What decides the matter is the product’s customs code.

Should we print the code in Türkiye?
Goods are expected to be labelled before they reach customs, so printing is usually done on the production line in Türkiye. The party that orders the codes, however, is the importer in Russia.

If we sell on a marketplace, does responsibility pass to the marketplace?
No. The marketplace may take on some reporting on its own side, but the match between product card data and the physical code stays with the supplier.

Does every size and colour need its own code?
Every variant requires its own product identifier (GTIN), and every physical unit carries its own unique code. That is why the number of product cards grows quickly as a collection expands.

We hold unlabelled stock — what happens to it?
Date limits are being introduced on selling unlabelled stock in groups brought into scope. For a buyer holding unlabelled goods in a warehouse this is direct time pressure; we covered the enforcement framework in our penalties guide.

How does the 1 October 2026 marketplace rule affect us?
Under the regulation as reported, the marketplace will verify the seller’s registration and the product documentation — certificates or declarations and Chestny Znak codes — before publishing a product card, with a 180-day transition for existing cards. In practice this means your codes and documents now decide not only customs clearance but whether the product can be listed at all.

Related guides: Customs code or GTIN? · Products in scope and customs codes · EDO electronic document flow

Where should you start?

The right start is not buying software or labels; it is establishing your scope. Draw up your product list and customs codes, determine which lines are mandatory, then put the registration–code–printing–reporting chain onto a calendar.

From our offices in Moscow, Istanbul and Podgorica we build that chain end to end: scope analysis, system registration, the electronic signature, product cards, code generation, print preparation and reporting, all under one responsibility. Look at our solutions, browse our other guides in the guide archive, or send your product list and request a free initial assessment.

This content is for general information and does not replace legal advice. Because dates and scope in force can change, we recommend checking current regulation before making a shipping plan.