Over 20 tonnes of goods, roughly 2,700 units, codes obtained and applied, pallets built. All that remained was to load the truck and set off. A single check carried out just before dispatch saved our client an additional cost we estimated at USD 10,000–15,000.
This article describes a real case with an olive and olive oil producer preparing their first shipment from Türkiye to Russia. No client details are disclosed; what follows concerns the process itself. Our aim is not to say “checks matter” — it is to show, step by step, exactly what the check caught, how the alternative cost was calculated and how the problem was resolved.
The starting point: everything looked ready
Our client was making their first shipment to Russia. The consignment was substantial: over 20 tonnes, roughly 2,700 units in total. The Chestny Znak codes had been obtained, physically applied to the products, cartons had been sealed and pallets built.
To an outside observer the batch was ready to ship. As we set out in our pre-shipment checklist, “the product is ready” and “the consignment is ready to ship” are frequently not the same thing. The difference does not sit on the product; it sits in the system.
The suggestion: one last check before loading
Immediately before the truck was loaded, we suggested checking the status of the codes in the system one more time. This is the step most often skipped in practice: the codes have already been generated and applied, so it is assumed there is nothing left to check.
When we ran the check, the picture changed.
The problem: labelling on the product, no code in the system
Preparing the batch had taken longer than expected. Roughly three months had passed between the generation of the codes and the planned shipping date.
In Chestny Znak, generated codes are expected to be applied to products and the application reported to the system within a defined period; publicly available sources give this as one month from generation. Because that step had not been completed in time, the previously generated codes were no longer visible in the system.
The situation was precisely this:
- The labelling is on the product.
- The codes are not in the system.
The gap between those two means that at customs, and afterwards, the goods cannot legally enter circulation. The label is physically in place, but the record behind it is not. We covered how labelling is checked at Russian customs in a separate article.
Timeline: where did the three months go?
To understand the case, it helps to look at the order of events. The codes had been obtained early relative to the production plan — in itself a sound reflex: code procurement is a waiting item, and pulling it forward makes sense.
But delays occurred on the production and packing side. The longer batch preparation took, the longer the codes sat “waiting”. Nobody was doing anything wrong; each party was progressing its own part. That is exactly where the problem arose: no one was tracking the fact that the codes had a shelf life.
This is a gap we see often. If the production plan slips, the production team knows; if the logistics plan slips, the carrier knows — but the clock on the labelling side keeps running silently. The practical safeguard is simple: record the code generation date as one of the critical dates in the production plan, and re-check code status whenever batch preparation is delayed.
Loading was stopped. We advised the client to halt loading immediately. The decision was taken within a few hours and the truck did not depart.
In our team’s assessment, had the truck set off, the consignment would have been turned back at the border and returned to Türkiye. Beyond that point it is no longer a correction; it is starting over.
How the alternative scenario would have added up
If the batch had come back, the work required would have been:
- breaking down the pallets,
- opening the packaging,
- relabelling roughly 2,700 products,
- repacking and repalletising the goods,
- arranging a new transport.
The estimated additional cost was in the USD 10,000–15,000 range. Two items dominated that figure: repacking the entire batch, and the truck travelling from factory to border and back to Türkiye. That does not include the slipped delivery schedule or the loss of confidence with a buyer on a first shipment.
A note on the number: it is an estimate specific to this case and varies with batch size, product type and route. We have set out the budget for labelling under normal conditions, item by item, in our cost article.
The route chosen: recovering the codes rather than relabelling
Relabelling the whole batch was the obvious solution, but not the only one. As Global Znak we submitted a formal application to Chestny Znak and started the process of reactivating the previously generated codes in the system.
Roughly 10 days later we succeeded in restoring the codes. As a result, 2,700 products did not need relabelling; the goods waited on their pallets with the packaging unopened.
It should be said that this route is not available in every situation. What made the difference was that the problem was spotted while the goods were still at the factory. Had the same problem surfaced at the border, we would have had neither the time to negotiate nor a physically accessible batch.
A second finding: the old address on the documents
We did not stop at solving the technical problem. Because this was the client’s first shipment to Russia, we reviewed the documents from scratch as well. A second inconsistency emerged there: the company’s registered address had changed, but some documents still carried the old details.
On its own it looks like a small detail. In practice it leads to further questions during import, requests to correct documents, and delay. Consistency across documents is also necessary for the EDO (electronic document flow) chain on the Russian side to work properly.
We updated the details, began working directly with the customs broker and followed the import process through to the end.
The outcome
Once all the preparation was complete, the import formalities were finished in about 1.5 days and the goods reached the client’s warehouse without incident.
- 2,700 products — not relabelled.
- USD 10,000–15,000 — potential additional cost avoided.
- 10 days — to reactivate the codes.
- 1.5 days — to complete the import process.
A single check made before dispatch cost far less than an error discovered at the border.
Four lessons from this case
1. Generating a code and having a valid code are different things. The code has to be applied to the product and the application reported to the system. Without that report the label stays in place; the record does not.
2. Time is a risk item. The longer the gap between code generation and shipment, the higher the risk. If production or packing is delayed, code status must be re-checked. You can see the status of a code quickly with our Chestny Znak status check by customs code.
3. A first shipment is a test of the entire process. In this case, looking for a code problem uncovered a document problem. On a first shipment you should examine not only the labelling but the documents and company details as well.
4. A problem found early has options. Spotted at the factory, you have room to negotiate, apply and wait. Spotted at the border, there is only cost. We have separately written about the administrative price of an unlabelled product.
Frequently asked questions
Do the codes really have a time limit?
Generated codes are expected to be applied to products and the application reported to the system within a defined period; publicly available sources give this as one month. The period and its application details can vary by product group and with regulatory updates, so confirm the position for your specific consignment.
If the codes have dropped out of the system, is relabelling always necessary?
No, not in every case. Here, a formal application to Chestny Znak was made to reactivate the codes and the result came through in about 10 days. The outcome of this route depends on the state of the batch, the product group and the timing of the application; it cannot be guaranteed.
What would have happened if we had noticed at the border?
In our team’s assessment the consignment would have been turned back and returned to Türkiye. Breaking down the pallets, relabelling roughly 2,700 products, repacking and arranging new transport would then have followed — an estimated USD 10,000–15,000 burden.
Can we run this check ourselves?
Seeing the status of codes in the system requires access to it; as a foreign manufacturer there are restrictions on that access, and code generation is carried out by the importer or authorised representative in Russia. In practice the check is done together with the importer or the consultant. Whether your product falls within scope you can check against the scope list by customs code.
Is an import time of 1.5 days normal?
That figure is the result of the preparation being complete: the product description was clear, the documents were consistent, the labelling was visible in the system and we were working directly with the broker. Where preparation is incomplete the duration becomes unpredictable; most delays come not from the customs procedure itself but from what was missing beforehand.
The cost of the check is small next to the cost of the error
What mattered in this case was not a piece of technical expertise but a habit: looking once more at the status of the codes in the system before loading. A few hours of work prevented a five-figure cost and kept the first shipment on schedule.
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 — particularly if you are preparing a first shipment, let us check the status of the codes, the documents and the consignment data together 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 draws on our own field experience and publicly available sources. It is for information only and does not replace legal or financial advice. No client details have been disclosed. The figures quoted are estimates specific to this case; regulations, deadlines and technical requirements may change. Confirm the current position for any specific shipment.
