The goods are produced, the packaging is ready, the truck is booked and the shipping date is set. And still the consignment stops at the border. In practice, most delays come not from the product itself but from details nobody checked before dispatch: labelling, documents, the status of the codes in the system, and requirements specific to the product group.
This guide brings together the checkpoints a Turkish manufacturer exporting to Russia should go through before the truck leaves the factory, along with the mistakes we see repeated most often. The aim is not to hand you a formality list, but to make one thing concrete: catching an error while the goods are still on your own premises is far cheaper than catching the same error at the border.
Why “the product is ready” and “the consignment is ready to ship” are not the same thing
Export preparation runs along three separate tracks: the product (production, packaging, label), the documents (invoice, packing list, conformity papers) and the labelling (code generation, application, reporting to the system). It is not enough for each track to be complete on its own; all three must describe the same consignment with the same data.
The pattern we see most often is this: the codes are ready but a document needs correcting; the documents are complete but the labelling does not meet requirements; the vehicle is booked but the consignment is not yet ready for entry into Russia. A single inconsistent detail delays the whole shipment. That is why exporting to Russia has to be planned as one continuous process, from production readiness through to customs clearance.
Five classic mistakes that stop a shipment
1. Starting production before checking the requirements
The most expensive mistake is to manufacture and pack first, and only then look for answers: Is the product subject to mandatory labelling? Which certificates or declarations are required? What information must appear on the packaging? Are there additional requirements for this product category?
If these questions come up after production is finished, the corrections have to be made on a finished batch — packaging is opened, labels are reprinted, pallets are rebuilt. The right approach is to clarify the requirements before the product enters the export process. Start by checking your product against the scope list through its customs code, as set out in our guide to products and HS codes within Chestny Znak scope.
2. Treating the Data Matrix as “just a code on the packaging”
If the product falls under Chestny Znak, obtaining the code and physically applying it is not enough. The code must be generated correctly, recorded in the system and visible in the required status.
A Data Matrix is not an image you download and print: it is a cryptographically protected digital identity, unique to each unit and bound to the GTIN and a serial number. From the outside a batch may look ready — codes applied, cartons sealed, pallets built — while a system check reveals a mismatch. If that mismatch surfaces after dispatch, the cost of fixing it multiplies. You can check the status of a code quickly with our Chestny Znak status check by customs code.
3. Leaving documents to the last minute
Certificates, declarations, manufacturer and importer details and the data printed on the packaging must all agree. A difference that looks trivial — an old company address left on one document, for example — leads to further questions and delay during import.
Documents should therefore be checked during preparation, not after the vehicle is already heading for the border. For the Russian side of the document flow, EDO (electronic document flow) also has to be in place; the transfer notification cannot be made without that infrastructure.
4. Treating labelling, documents and logistics as separate processes
The three are interdependent and are handled by different parties: manufacturer, importer, customs broker, logistics company. Each may confirm “done” for its own part while the chain still breaks somewhere. The critical question is this: are all four working from the same consignment data?
5. Skipping the pre-loading check
The final check before dispatch is not a formality. It is the opportunity to see a problem while the goods are still at the factory — before the vehicle departs, before the batch is turned back, before packaging is reopened and before the delivery schedule is put at risk.
The value of this check is not abstract. In one of our own cases, a single pre-loading check of code status saved the client an additional cost estimated at USD 10,000–15,000: the codes had been generated and applied to the products, but because batch preparation had dragged on, the codes were no longer visible in the system.
Seven checkpoints before a first shipment
1. Is the product described precisely enough?
“Textiles”, “cosmetics”, “footwear” or “food product” is not enough. The full product name, composition, intended use, packaging format, quantity, country of origin and the HS / TN VED code must all be clear. Check: does the product description read the same way at the manufacturer, the importer, the broker and the logistics company? If you are unsure about codes, our guide on the difference between an HS code and a GTIN will help.
2. Are the delivery terms clear to everyone?
Who arranges transport, who is responsible for customs, who prepares the documents, who passes the information to the broker? Check: are the delivery terms, the responsibilities of each party and the document flow set out in writing?
3. Is the importer genuinely ready for this consignment?
Sometimes the manufacturer is ready while the Russian side is not yet in a position to receive the goods. Make sure the importer knows the contents of the batch, holds the product data, has organised the process with the broker and knows what happens when the goods arrive. Check: is the importer saying “we’re ready” in general, or confirming readiness for this specific consignment?
4. Is there a single, current version of the documents?
One of the most common problems is parties working from different versions: one packing list at the manufacturer, a different invoice at the broker, outdated company details at the importer, incomplete cargo data at the logistics company. Check: do the invoice, packing list, transport data, product descriptions and company details all agree?
5. Have the product-specific requirements been checked?
Not every product group is subject to the same rules. Depending on the product, conformity documents, technical regulations, mandatory labelling, label content, packaging conditions or additional requirements come into play. The check has to be made against the product itself and its HS / TN VED code, not against a broad category. Check: is there a concrete requirements list for this product, or is the process running on assumptions?
6. Have the labelling and the label been checked physically?
Having obtained the codes is not enough. Before loading: is the code readable, is the label undamaged, is the right information on the right product, does the data in the system match the actual batch? Check: was a sample taken from the batch and physically scanned? Poor print quality, or confusing a Data Matrix with a QR code, can push the product into a problematic status automatically.
7. Is this consignment genuinely ready to ship?
The manufacturer, importer, broker, logistics company and consultant should carry out a short final check together. The point is not for each party to say “fine” for its own part, but to obtain one answer for the whole chain: yes, this consignment is ready to ship.
Two traps specific to foreign manufacturers
Assuming an EAC certificate is sufficient. For many product categories a Data Matrix code is required in addition; without it the goods do not clear customs. The consequence can be seizure of the goods or an administrative fine — we covered what an unlabelled product costs in a separate article.
Assuming a foreign manufacturer can generate the codes. That authority sits with the importer or authorised representative in Russia; a foreign participant faces clear restrictions in the system. Proper integration is not possible without a local partner. For the registration and signature side, do not skip the step of obtaining a qualified electronic signature (UKEP).
Why an incorrect customs code breaks the whole chain
An incorrect HS code can change the product’s status entirely — perfume being classified as a dangerous goods class, for example. Products with chemical content additionally require an MSDS (material safety data sheet). In publicly available sources, and in what we observe in the field, missing documents of this kind are among the most common causes of difficulty at import.
The customs code determines not only the duty but which set of requirements applies to the product: labelling scope, conformity documents, label content. Code selection is therefore not an accounting detail but the starting point of the whole process. You may also want to read how labelling is checked at Russian customs.
When should the checks be made?
We recommend three checks at three distinct moments:
- Before production: clarify scope, HS code, required documents and label content.
- After labelling: have the codes been recorded in the system, are their statuses correct, did the physical scan test pass?
- Before loading: do the documents, the batch data and the system record all agree?
The third check is the one most often skipped, because by then everything “looks ready”. In our cases it is precisely that third check that prevents the cost. If you are looking at the budget side of the process, we have set out labelling costs item by item.
Frequently asked questions
If I have obtained the codes, is the consignment ready?
No. Generating a code and the product being legally ready for circulation are two different things. The code has to be applied to the product and the application reported to the system; without that report, the product can carry a label while no code exists in the system.
Do codes have a validity period?
Generated codes are expected to be applied to products and reported to the system within a defined period; if that period is exceeded, the codes may lose validity in the system. In our own case roughly three months passed between code generation and shipment, and the codes had disappeared from the system. Periods can vary by product group and with regulatory updates, so confirm the current position for your specific consignment.
If the codes are no longer in the system, does the whole batch have to be relabelled?
Not always. In the case above, instead of relabelling the entire batch, a formal application was made to Chestny Znak to reactivate the previously generated codes, and the result came through in about 10 days. This route is not available in every situation; noticing the problem early is what makes the difference.
Can I generate the codes myself as a foreign manufacturer?
Code generation is carried out by the importer or authorised representative in Russia. As a foreign participant you will meet clear restrictions in the system, which is why the division of roles with the local party needs to be explicit in the contract.
Who should carry out the final check?
Not a single party. The manufacturer, importer, customs broker and logistics company need to give one joint “ready” answer based on the same consignment data. The consultant’s role is to collect that joint answer and make the missing link visible.
An error found at the border costs more than one found at the factory
The principle is simple: an error spotted before dispatch is a workable business matter; the same error spotted at the border means additional cost, lost time and risk to the entire consignment. The difference is usually between a few hours of checking and a five-figure sum.
Global Znak manages the Russian export process end to end for Turkish manufacturers, with offices in Moscow, Istanbul and Podgorica and membership of RTIB. Get in touch for a free initial assessment — we will review your product group, labelling status and document flow together and identify the risk points before loading. You can see our service packages on the Solutions page, and our other guides in the News and Guides section.
Note: This article has been prepared from publicly available sources and our own field experience. It is for information only and does not replace legal or financial advice. Regulations, deadlines and technical requirements may change. Confirm the current position for any specific shipment.
