Lawyer's answers
Q&A on Chestny Znak and import labelling
Questions on mandatory import labelling, its connection with the EAEU tariff code, liability under Article 15.12 of the Russian Code of Administrative Offences and the importer’s role.
Does importing a product from abroad automatically mean Chestny ZNAK labelling is required?
Mandatory labelling is determined by the rules for the particular product group, including the relevant HS code and product characteristics. Import status alone is not enough. Check applicability before shipment or customs clearance.
Identification-labelling rules are established through product-specific Russian regulations with their own covered goods, dates and transitional provisions. By 2026 the system covers numerous categories, but the list changes. Verify the current product-group regulation rather than relying on a general catalogue in an older article.
Check the current Chestny Znak product-group information and, more importantly, the applicable Government regulation and any legally relevant decisions for that group. Coverage can depend on HS codes, product characteristics, implementation dates and transitional rules.
Checking labelling only when goods are already at the border can create avoidable storage, relabelling and delay costs. Applicability is better reviewed while the purchase and import model can still be changed.
How are EAEU tariff codes connected with mandatory labelling?
HS classification and the product description are often central to whether a product falls within a labelling regime. A classification error can therefore lead to the wrong labelling conclusion.
A product may fall within or outside a labelling regime depending on the correct HS code and the characteristics specified in the applicable regulation. Adjacent codes can also be phased in on different dates. The legal test should therefore use both classification and the product-specific rule.
Clothing illustrates the point: labelling rules can cover only specified goods within HS Chapters 61 and 62, with distinctions based on the particular product and applicable regulation. A broad commercial description is not a substitute for checking the legal classification and coverage.
Classification and labelling should be reviewed together. Record the chosen HS code, the product characteristics and the regulatory basis for the labelling conclusion. A written file makes later verification easier but does not guarantee the outcome of an inspection.
Who is responsible for import labelling—the supplier, importer or another party?
Responsibility depends on the legal role of each participant and on who performs the regulated act of placing the goods into circulation. Contract terms can allocate tasks and recourse between parties, but they cannot simply transfer away statutory liability imposed on a particular participant.
The participant responsible for placing labelled goods into circulation must comply with the product-specific Chestny Znak rules, including registration, code ordering, application and reporting where required. Article 15.12 of the Administrative Offences Code contains sanctions for specified labelling offences, including confiscation in some cases. The exact offence and sanction must be checked in the version applicable to the goods and conduct.
Possible models include applying codes abroad before shipment, applying them at a customs-controlled location where the procedure permits, or applying them after release but before the regulated act of placing goods into circulation where the product-specific rules allow that sequence. The correct model depends on the customs procedure and the current labelling regulation.
Do not rely on an oral promise that the supplier will “handle the labelling.” The contract should identify who obtains and applies codes, the technical requirements, evidence of completion and recourse for failure. Statutory liability remains governed by law, regardless of how the supplier's obligations are allocated.
Put the labelling model in writing—in the contract, an amendment or the specification. Define how codes are transferred, who applies them, evidence of completion and contractual responsibility for defects. This does not transfer statutory liability, but it creates a clearer contractual basis for recourse against the supplier.
Can goods be released if the labelling issue has not yet been resolved?
It depends on the product-specific rules and customs procedure. In some cases codes may be applied after a particular customs stage but before the regulated act of placing goods into circulation; in others the required labelling must be in place earlier. Check the current rule for the product before release.
If the goods are clearly subject to labelling but codes have not been applied, identify a customs procedure and location in which the required operations are legally permitted before the goods enter circulation. If coverage is disputed, obtain a product-specific legal classification before release. If the goods are outside the regime, keep a written record of the basis for that conclusion.
Depending on the facts, a customs warehouse, another customs-controlled procedure or re-export may be relevant while a labelling issue is resolved. The cited EAEU Customs Code procedures have different conditions and permitted operations, so do not assume that code application is allowed under each of them without checking the current rules.
Improvising after the goods reach temporary storage is expensive and risky. Storage costs rise while commercial deadlines continue. Do not respond by declaring without required labelling, applying codes without checking the technical rules or choosing a customs procedure solely to solve the immediate delay.
Review the labelling requirement before the goods reach customs—early enough to change the supply model if necessary. By clearance, the company should know which labelling model applies and have the supporting documents ready.
What if goods have already been imported and the labelling requirement is disputed?
If the goods have already arrived, resolve applicability promptly. The longer the status remains uncertain, the more storage and operational consequences may accumulate.
Start with the exact HS code and product characteristics, not the commercial name. Then check the current product-group regulation, its implementation dates and transitional provisions, and determine the legal status of the goods at the relevant stage. Coverage may turn on characteristics such as material, use or intended user as well as classification.
The review usually leads to two main outcomes:
If labelling is required, organise code ordering, application and reporting in the sequence required for that product group before the goods are lawfully placed into circulation. Recalculate the transaction costs. If goods may already have entered circulation without required labelling, stop further distribution and obtain case-specific advice on lawful corrective steps rather than assuming a fine can simply be paid while sales continue.
If labelling is not required, keep the legal analysis, regulatory references and evidence of the product characteristics with the customs file. That record can support the position if the classification is questioned later.
If uncertainty remains, seek clarification from the competent authority where an available procedure exists and obtain a legal assessment. A conservative operational approach may be appropriate, but treating goods as labelled “just in case” is not a substitute for determining the actual legal requirements.
Delay is itself an operational risk. The longer the goods remain in an unresolved status, the greater the potential storage, sales and compliance consequences.
Which documents should be checked before importing goods subject to labelling?
Prepare the relevant product, labelling, contractual and downstream-circulation documents before the declaration is filed. The exact set depends on the product group and chosen import model.
For the goods, keep an exact description tied to the HS code and the regulatory labelling criteria, technical characteristics relevant to coverage, manufacturer identifiers and any conformity documents that matter to the product group. The file should make it possible to match the physical goods to the legal rule.
For the labelling analysis, keep the current regulation and the provisions establishing whether the goods are covered, the product-group rules for code application and reporting, evidence of system registration where required, and a practical plan showing who applies the codes, when and how.
Contract documents should state who applies codes, who bears the cost, the timing and quality requirements, and what evidence the supplier must provide. If a third party applies codes in Russia, keep that agreement as well. Preserve system records showing the lawful source and use of the codes.
Downstream contracts should allocate operational responsibilities for labelled goods and record acceptance and transfer where the product-group rules require it. Larger importers may also need an internal control procedure for code handling and reporting.
Labelling is part of the supply model, not an afterthought to customs clearance. It should be designed with classification, logistics, contract terms and product circulation from the start. Late improvisation can create avoidable compliance and operating costs.
What penalties can apply to labelling violations, and when is confiscation possible?
Labelling offences can carry substantial fines and, for some offences, confiscation. The applicable sanction depends on the precise conduct, product and version of the law.
Article 15.12 of the Administrative Offences Code contains separate offences and sanction ranges for specified production, import and circulation of goods without required identification or information. Some provisions include confiscation. Because the article and product-specific regimes can change, calculate exposure from the version in force on the date of the alleged conduct rather than relying on an older fixed range.
Other administrative provisions may become relevant only if their own elements are independently met. A failure in Chestny Znak registration or labelling does not automatically establish offences concerning licensing, pricing or consumer deception; each possible qualification must be checked separately.
Confiscation is available only where the applicable sanction and procedure permit it. The authority competent to impose it and the treatment of confiscated goods depend on the specific offence and procedural rules. Do not describe every labelling case as an automatic loss of the goods.
Certain conduct involving goods without required labelling can also fall within Article 171.1 of the Criminal Code if the statutory elements and monetary thresholds are met. The thresholds and sanctions must be checked in the version applicable to the conduct; they should not be inferred from an administrative case.
Repeated or multiple labelling episodes can increase aggregate exposure, but whether they constitute separate offences depends on the facts and legal classification. The economics of compliance should therefore be assessed before serial shipments begin.
A practical way to reduce risk is to define the labelling model in advance and follow it consistently. Once an inspection begins, the available corrective options may be narrower.
How should remote labelling by a foreign supplier be organised before shipment to Russia?
Remote labelling—codes applied by the foreign supplier before shipment to Russia—can be workable where the product rules and system procedures allow it. The process should be documented from code transfer through application and verification.
In a typical remote-labelling model, the Russian participant obtains the required codes and transmits them securely to the supplier, the supplier applies them in the agreed format, evidence of application is returned, and the importer verifies the goods and completes the required system reporting. The exact sequence must match the current product-group rules.
The contract should cover secure code transfer, application requirements, responsibility for errors, a technical labelling specification, sample approval where useful, evidence of receipt and application, and controls against disclosure or duplicate use. Do not state a universal code-expiry period unless the current system rule for that code type establishes one.
Use quality checks, sample scans or photographs, reconciliation of codes issued against goods actually labelled, and acceptance checks when the shipment arrives. Any time limits should be taken from the current code and product-group rules rather than assumed.
Typical risks include unreadable or misplaced codes, a code linked to the wrong item, duplicate use, disclosure of codes to third parties and reporting that does not match the physical goods. Build controls around the actual system requirements.
For repeat imports, use a written labelling procedure, supplier training and periodic quality checks. For a one-off shipment, document the process before signing and retain evidence of each critical step.