Compliant Importers Will Take the First Hit. Here Is Why
SPOT, Chestny ZNAK and marketplaces are beginning to see the same product. Sergey Maltsev explains why compliant importers will feel it first.

Compliant importers will take the first hit. Not because the state has decided to target those who play by the rules. The reason is simpler: compliant business is visible from end to end.
In 2026, three controls are closing around the same product: SPOT, product labelling and marketplaces. They have different jobs and different data sets. But the importer, the product and the documents are the same. If the story does not add up in one control, the next one will expose it.
This is good for the market. It can still hurt an individual shipment through a correction cycle, a delayed launch, or refusal of entry for a vehicle or product listing. Compliant importers will feel that new precision before grey operators. Here is why.
What changed by July 2026
The first control is SPOT. Since 1 July 2026, the system has operated in full for goods entering Russia by road from another EAEU country. Before entry, the importer files DOPP, receives a QR code and makes a security payment unless an exemption applies. The Federal Tax Service is explicit: if the document is missing, its status is unsuitable, or the data conflicts with the shipping documents, the vehicle may be refused entry. The details are in our SPOT guide for cosmetics importers.
The second control is product labelling. For cosmetics, the obligations depend on the product group, EAEU HS and OKPD2 codes, production date and exclusions. If a product is subject to mandatory labelling, it acquires a GTIN, a National Catalogue card, marking codes and commissioning records. The blanket claim that all cosmetics are subject to labelling is wrong. The current stages are covered in our cosmetics labelling guide.
The third control is marketplaces. From 1 October 2026, intermediary digital platforms must verify the product-card information listed in Article 7 of Federal Law No. 289-FZ. The government approved the verification procedure in Resolution No. 821.
Resolution No. 821 lists twelve government systems and databases. For cosmetics, the relevant sources include the state labelling system, the federal accreditation system, EAEU registers of certificates and declarations of conformity and, for some products, the register of state-registration certificates. Platforms will receive some of this information through APIs or machine-readable files updated daily.
Existing listings will be checked too. Resolution No. 821 sets a transition period for information posted before 1 October 2026.
Three systems see the same data
I am keeping this wording deliberately. This article is about import controls, not government database architecture.
SPOT sees the shipment and route. Chestny ZNAK sees the product and its movement. A marketplace sees the seller, the listing and the supporting information. Each system sees its own slice, but the product is the same.
They do not need a shared table to find a contradiction. If SPOT describes one product, the labelling record describes another, and the marketplace listing tells a third story, the discrepancy will not stay buried in somebody's spreadsheet.
That is what I mean by the controls closing the loop. The next system sees what used to get lost between the customs broker, conformity specialist, labelling team and marketplace manager.
Why compliant importers may feel it first
A compliant importer gives the systems the material they need to compare. The importer clears the goods, confirms conformity, labels the product and supplies the marketplace data. Every correct action leaves a digital trail. So does every inconsistency.
Grey goods may avoid some regulated controls for a time. The system does not yet see the whole chain, so it cannot catch the contradiction. That creates an awkward paradox: the operator working in the open is the first one stopped.
But this is a head start, not immunity for grey operators. Federal Law No. 289-FZ narrows their access to the main sales channel. Without the required information, registration in the state labelling system and proof of conformity, a product will have a harder time reaching a major digital storefront.
So my forecast stands. Compliant importers will take the first operational hit. Grey operators will then begin losing sales channels.
What a data conflict looks like
Not every error will stop a vehicle or product listing. But every error costs time: someone has to find the primary document, locate the conflict and correct the data.
Typical situations include:
- the conformity declaration uses the manufacturer's full legal name, while the listing uses an abbreviation or trade name;
- a GTIN belongs to one SKU but appears next to another in a working sheet or product card;
- a declaration or certificate link does not resolve to a valid record;
- the product is subject to mandatory labelling, but the listing lacks the required information or the seller is not registered in the state labelling system;
- DOPP data conflicts with the documents presented by the driver at entry.
The consequences depend on the control. A platform may refuse a listing in the cases set out in Article 7. Under SPOT, a discrepancy may be grounds for refusing entry to the vehicle. Elsewhere, the data may simply be returned for correction. There is no single automatic outcome for every error.
Build the product passport first
We start with a shared data core for the product and shipment. It is the working passport used to complete the documents and system records.
A single product passport links labelling, product records and documents with one red thread
Before ordering a shipment, record:
- the manufacturer's full legal name and details;
- country of origin;
- EAEU HS and OKPD2 codes;
- GTIN and its link to the exact SKU;
- declaration, certificate or state-registration certificate where required;
- whether labelling applies and the product-card status;
- shipment route and participants in the chain;
- the owner responsible for changes to each field.
The passport is then adapted to SPOT, the National Catalogue, conformity documents and the marketplace. The forms differ. The facts about the product do not.
What importers should do
The earlier the assortment, route and documents are assembled in one place, the cheaper it is to correct a conflict. Once the shipment is paid for, the price of an error rises every day.
When preparing a shipment, we identify which data already exists, what is missing and where the first mandatory check will occur. A disputed classification should be settled with the customs broker or conformity assessment body before payment. At the border, the argument is already late and expensive.
If you are planning a cosmetics shipment to Russia, send us the SKU list, route and available documents. We will map the chain and show which data needs to be confirmed before production, import and sales launch.
Sergey Maltsev, CEO, K-Business
Facts and dates were checked on 15 July 2026 against materials from the Russian Federal Tax Service, Federal Law No. 289-FZ, Government Resolution No. 821 and the current cosmetics labelling rules. The forecast that compliant importers will take the first hit is the author's assessment.
Check the data before ordering the shipment
Send us the assortment, route and available documents. We will map the data and checks that need to be completed before production, import and sales launch.
FAQ
Why may compliant importers feel the new controls first?
Compliant importers pass through every regulated control and record product and shipment data along the way. Their discrepancies will therefore surface earlier. This is the author's assessment, not statutory wording.
What must marketplaces verify from 1 October 2026?
Intermediary digital platforms verify the product-card information specified in Article 7 of Federal Law No. 289-FZ. Resolution No. 821 brings Chestny ZNAK, the Russian accreditation system, and EAEU certificate, declaration and state-registration databases into the verification perimeter.
How can importers reduce the risk of data conflicts?
Build a single data core for every SKU and shipment: manufacturer, country, classification codes, GTIN, conformity documents, route and owners. Then adapt that core to each system instead of copying one line into every form.