An implementation project, not a subscription
Marking for importers: from ordering codes to the first delivery in Russia
We build the whole import marking process: we design the scheme, write the application and aggregation procedure for the factory abroad, check that codes and documents are correct, pass the ATK to the broker and support the batch up to its first shipment in Russia. We have worked with marking since 2019, since it launched.
we’ll answer questions about your product group
For manufacturers abroad
Work in your customer’s account in your language
In Truemark, employees work by role: your customer decides which sections you view and which you change. Only the importer needs a qualified e-signature; you prepare documents without a certificate
Account and handheld terminal app
- English
- Tiếng Việt
- 中文
- 1
Access to the account
The importer invites you by email in the “Employees” section and assigns a role. The codes they ordered are already in the account, so no files need to be sent
Sign-in with email and password, no certificate - 2
Aggregation at the factory
You create manual aggregation documents in the account or on a handheld terminal, in your language
You prepare it, the importer signs - 3
Put into circulation
You scan the codes of the imported goods on a handheld terminal, and a draft for putting them into circulation appears in the account. The importer only has to enter the goods declaration number and sign
You prepare it, the importer signs
Roles with selected sections are on the Maxi plan; on Opti, all employees have full accessMore on employees and MChD
why it’s not “just ordering codes”
In imports, a marking error surfaces where it is most expensive to fix
The goods are already made, packed and on their way. The codes were applied thousands of kilometers away, and redoing them in Russia means unpacking the batch, manual work and missed deadlines.
01downtime
The batch is stuck at customs
The declaration has no correct aggregated customs code, so release is delayed and the container sits idle.
Truemark
Truemark creates the aggregated customs code automatically: pass it to your broker or declarant
02defects
Codes can’t be read
Wrong label size, contrast or material: the DataMatrix doesn’t scan at the warehouse or at the checkout.
Truemark
Labels in the editor sized to your packaging, printing as a PDF file on any printer or via Connect on a label printer
03reassembly
Aggregation “on paper”
Boxes and pallets are packed differently from what was declared: receipt falls apart and the goods have to be repacked by hand.
Truemark
Box and pallet codes are generated from the order’s packing layout, and with manual packing each code is checked against Chestny ZNAK
04extra operations
Wrong aggregation level
The nesting depth was chosen “however it goes”, and from then on every shipment needs extra operations and people.
Truemark
Any nesting: unit, set, box, pallet, from the order’s packing layout
05rework
The factory did it its own way
The factory got the task without a clear spec or sample checks, and the result shows only on arrival.
Truemark
Samples from the factory are checked with the free code check: status, product and code structure straight from the package
06goods stuck
The goods can’t be sold
An error in the introduction into circulation or in the documents: the batch is physically in the warehouse but legally “doesn’t exist”.
Truemark
Before introduction into circulation, boxes and packages are checked against Chestny ZNAK, and permit documents against the card
how a project works
Stages: from ordering marking codes to the first delivery
Below is the path of an imported batch in Chestny ZNAK. Each stage has a checkpoint: we don’t just set things up, we check the result before it moves on. You can check yourself against all stages in themarking checklist.
-
1
Audit and process design
We look at the product group, volume, number of sites and supply scheme. We define which requirements apply to your product specifically and design the marking scheme before the first code is printed.
Checkpoint: an agreed scheme, not “let’s try and see” -
2
A deliberate choice of aggregation levels
Unit → group package → box → pallet. The nesting depth isn’t chosen at random but to fit your logistics, receipt and further shipments: an extra level means extra operations, a missing one means manual repacking in Russia.
Checkpoint: the aggregation scheme is fixed and clear to the factory How aggregation works in Chestny ZNAK → -
3
Ordering and receiving marking codes
Describing products, getting GTINs, ordering and issuing codes. We set this up so the codes arrive for the right volume at the right time, without a rush before shipment.
Checkpoint: codes received for the actual batch -
4
Passing codes to the factory and the label format
We prepare a clear brief for the factory: in what form to take the codes, what to print, in what size, on what material and where to stick it. The label format is agreed before the print run, together with DataMatrix readability requirements.
Checkpoint: test samples are checked before the batch starts -
5
Application and aggregation at the factory abroad
We write the process for the factory: how codes are applied, how boxes and pallets are packed, how aggregation data is passed on. We work with factories all over the world, mostly in China, and with European factories.
How it works at the factory: a handheld terminal scan instead of Excel sheets Checkpoint: means of identification and aggregation are checked for correctness -
6
Customs: the ATK for the broker or declarant
We create the aggregated customs code, one code instead of tens of thousands of identification codes in the declaration, and pass it to your customs broker or declarant in the form they need
Checkpoint: the ATK covers the whole batch and is accepted by the declarant What an ATK is and how it works → -
7
Import and introduction into circulation
We support the import of the batch and the introduction of the goods into circulation, so the goods in the warehouse are ready for sale not only physically but legally
Checkpoint: the data is filed correctly, the goods are in circulation If an import introduction is rejected: HS code and country → -
8
First shipment: to a trading partner or a marketplace
We see it through to the result: shipment to a trading partner with a UTD carrying the correct code hierarchy, or your own sales on a marketplace such as Wildberries. We check the documents and support you up to the first delivery.
Checkpoint: the UTD and the code transfer are checked Marking for Wildberries →
two different scenarios
Imports from the EAEU and from third countries are different processes
They are often confused, and that is costly. Imports from EAEU countries go without customs clearance and without a goods declaration, so the checkpoints in the process are different too.
| Stage | Imports from third countriesChina, Europe | Imports from the EAEUno customs |
|---|---|---|
| Customs clearance | Yes | No |
| Goods declaration | Required | Not filed |
| ATK for the declaration | We create it and pass it to the declarant | Not required |
| Applying codes | Before import, at the factory abroad | |
| Aggregation at the factory | Designed and checked | |
| Put into circulation | We support it | |
| Key risk | The batch gets stuck at customs | The error is noticed only at the warehouse in Russia |
control
We check what usually comes out after the fact
The point of a project isn’t to “set it up and leave”. We check correctness at every stage and support you up to the first delivery, that is, until the process has proven itself on a real batch.
Discuss a project- Correct creation of means of identification
- DataMatrix readability and a suitable label format
- Actual aggregation matches the declared scheme
- Readiness of the ATK and its acceptance by the declarant
- Correct UTD and code hierarchy at shipment
- Complete and correct data at introduction into circulation
why us
We have worked with marking since 2019, since it launched in Russia
Baldinini: marking applied right at the factory in Italy
One of our first implementations and one of the first projects of its kind in the country: a full turnkey implementation for a large Italian footwear factory, with marking applied at the site in Italy. A client since2019; we still support them today, more than six years in a row.
Since then we have built processes at sites all over the world, mostly in China, for any Chestny ZNAK product group.
request
Tell us about the product and volume, and we’ll come back with an understanding of the process
The more precise the input, the more concrete the conversation. We need to know the product group, the volume and where the goods are shipped from: both the scheme and the cost depend on it.
Just need the service to work on your own, without an implementation project? See Truemark pricing.
Need help with marking?
An expert replies in English in the account chat in 15 minutes on average, 7 days a week. 7 days of full access for free, no card required.
frequently asked questions
Import marking: the essentials
Didn’t find an answer? An expert replies in the account chat in 15 minutes on average. More answers in the knowledge base and blog.
Where is marking applied to imported goods?
Before import into Russia, at the production site abroad. We build this process at the factory itself: we prepare the brief, agree the label format, write the application and aggregation procedure, and check the result on test samples before the batch starts.
What is an ATK and why does an importer need it?
An aggregated customs code is virtual aggregation: one code replaces tens of thousands of identification codes in the customs declaration and is entered as a single line. We create the ATK for the batch and pass it to your customs broker or declarant. Read more in the article on the aggregated customs code.
How are imports from the EAEU different?
Imports from EAEU countries have no customs clearance and no goods declaration, so no ATK is needed either. But application and aggregation are still done before import, at the supplier’s site. The process isn’t simpler, the checkpoint just moves: you will see an error only at receipt in Russia.
How do I choose aggregation levels?
Deliberately, not “however it goes”. The nesting depth (unit → group package → box → pallet) depends on your logistics, receipt and how the goods will be shipped on. An extra level adds operations; a missing one leads to manual repacking of the batch in Russia.
Which product groups do you work with?
Any Chestny ZNAK product group. Requirements and details differ between groups; since 2019 we have been through them on dozens of large projects for importers and manufacturers.
Do you work with factories abroad directly?
Yes. We have built application and aggregation processes at sites all over the world, mostly in China, and our first implementation was at a factory in Italy. The aim of a project is for the factory to get it right from the first batch, not after arrival.
How much does a project cost?
From ₽50,000. The final cost depends on the product group, volume, number of production sites and import scenario (third countries or the EAEU). Describe your inputs in the form, and we’ll come back with a concrete conversation.
What happens after the first delivery?
By then the process has proven itself on a real batch, and you work in Truemark on your own. We have supported our first client, an Italian factory, since 2019 to this day, so support can be long-term too.
Imports forgive a lot, but not a marking error
It’s cheaper to design the process before the first print than to unpack a batch in Russia. Tell us about your product, and we’ll work it out together.
See also: marking for manufacturers · aggregation · complete marking guide