An implementation project, not a subscription
Marking for manufacturers: implementing the process from ordering codes to the first shipment
We build marking at your production: we design the scheme and aggregation levels, write the application and aggregation procedure on the line, check that codes and documents are correct, and support you up to the first shipment. We have worked with marking since 2019, since it launched in Russia.
we’ll answer questions about your product group
why it’s not “just ordering codes”
At production, a marking error multiplies with the print run
A line makes no exceptions: if the scheme is wrong, it produces the whole batch wrong. You’ll have to fix not a setting but goods that are already packed.
01defects
Codes can’t be read
Poorly chosen size, contrast, material or application spot: the DataMatrix doesn’t scan at the warehouse or 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
02downtime
The line stopped
Marking isn’t built into the production pace: instead of a flow, you get manual operations and downtime.
Truemark
Codes are ordered in advance for the whole range, up to 50,000 labels in one PDF
03manual labor
Manual aggregation
Boxes and pallets are packed with a scanner one unit at a time: time, people and errors where package codes could be generated from the order’s packing layout.
Truemark
Box and pallet codes are generated from the order’s packing layout, without a scanner
04extra operations
Wrong aggregation level
The nesting depth was chosen “however it goes”, and every later shipment needs extra operations.
Truemark
Any nesting: unit, set, box, pallet, from the order’s packing layout
05goods stuck
The batch won’t ship
An error in the introduction into circulation or the documents: the goods are physically ready but can’t be shipped.
Truemark
Codes are checked before introduction into circulation, and the UTD is built by pallet code with the full hierarchy
06double work
Redoing the print run
Found too late, and now you’re unpacking, re-marking and repacking finished products.
Truemark
Re-marking in the account: new codes and a document to Chestny ZNAK, where the group allows it
how a project works
Implementation stages: from ordering codes to the first shipment
Below is the path of products from the line to the trading partner. 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, packaging and how the line works. We define which requirements apply to your products 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
The nesting depth is chosen to fit your packaging, logistics and shipments, not at random: an extra level means extra operations on every batch, a missing one means manual repacking before shipment
Checkpoint: the aggregation scheme is fixed before launch How aggregation works in Chestny ZNAK → -
3
Ordering and receiving marking codes
Describing products, getting GTINs, ordering and issuing codes. We set up the process so codes arrive for the production plan at the right moment, without a rush before a shift.
Checkpoint: codes received for the actual print run -
4
Label format and application on the line
We agree what to print, in what size, on what material and where to apply it before the print run, together with DataMatrix readability requirements. Application is built into the line’s pace, not bolted on the side.
Checkpoint: test samples are checked before the batch starts -
5
Aggregation at production
We set up package assembly so the hierarchy is built from the packing layout and doesn’t require scanning every unit. This is where production usually loses the most time and people.
Checkpoint: actual aggregation matches the scheme -
6
Correctness check
We check the means of identification, code readability, that aggregation matches the declared scheme and that documents are correct, before the batch leaves
Checkpoint: we check the result, not a report about it -
7
Put into circulation
We support putting products into circulation, so the goods are ready for sale not only physically but legally. If a contractor makes the goods for you or you produce under someone else’s brand, the introduction is filed as contract manufacturing, with the manufacturer and the owner in the document.
Checkpoint: the data is filed correctly, the goods are in circulation -
8
First shipment: to a trading partner or a marketplace
We see it through to the result: UTD shipment with a 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 →
Variable-weight goods are marked at the Marking station: a label with the weight and code prints at weighing.
the key decision of the project
Aggregation levels are chosen once, and you pay for them with every batch
This decision is made before launch and determines how many operations every shipment will take for years to come. That’s why we start with it, not with settings.
An extra level
Every batch drags along operations nobody needs: extra packages, extra scans, extra people on the line.
A missing level
Before shipment, you have to repack by hand what should have been assembled at production.
The right level
The hierarchy is built from the order’s packing layout, shipment takes minutes, and the UTD goes out with ready nesting.
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 shipment, 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
- Correct UTD and code hierarchy at shipment
- Complete and correct data at introduction into circulation
- The process works on a real batch
why us
We have worked with marking since 2019, since it launched in Russia
Baldinini: marking right at the factory
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 right at the production site. 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, for any Chestny ZNAK product group.
request
Tell us about your products 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 and the volume: 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
Implementing marking at production: 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 does implementing marking at production start?
With an audit and design, not with settings. We look at the product group, volume, packaging and how the line works, and design the marking scheme, including aggregation levels, before the first code is printed. Then setup follows the agreed scheme.
How do I choose aggregation levels?
Deliberately, to fit your packaging, logistics and shipments. The decision is made once, and you pay for its consequences with every batch: an extra level adds operations on the line, a missing one leads to manual repacking before shipment. More about levels in the material on aggregation in Chestny ZNAK.
What do you check before the first shipment?
Correct creation of means of identification, DataMatrix readability and a suitable label format, actual aggregation matching the declared scheme, correct UTDs and code hierarchy, and complete data at introduction into circulation. We check the result, not a report about it.
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 manufacturers and importers.
We have large volumes. Can you handle them?
Yes. Our clients’ volumes range from 200,000 to 100,000,000 units of goods a year. The volume affects the process scheme and the project cost, which is why we ask for it in the request. How Truemark works with large volumes of codes is on the page marking for large businesses.
We manufacture abroad. Is this for us?
Yes, but the scenario is different: customs, the declaration and passing the ATK to the declarant come in. We have a separate page for this case: marking for importers. We have built the process at sites all over the world, mostly in China.
How much does a project cost?
From ₽50,000. The final cost depends on the product group, volume, number of lines and sites. Describe your inputs in the form, and we’ll come back with a concrete conversation.
What happens after the first shipment?
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.
A line doesn’t forgive a wrong scheme: it replicates it
It’s cheaper to design the process before the first print than to re-mark a finished batch. Tell us about your products, and we’ll work it out together.
See also: marking for importers · aggregation · complete marking guide · handling permit documents