Last updated: 2026-11-15 · By the ZhiShuYun Research Team
Chestny ZNAK codes are Data Matrix symbols carrying a GS1-compliant structure — GTIN, a unique serial number and a verification key. Each code must be registered in the CRPT system against the importer or manufacturer before the product can be sold. The label is printed on the production line or applied as a pre-printed sticker, then verified by scanning before shipment.
| Symbology | Data Matrix (ISO/IEC 16022), GS1-compliant element strings |
| Encoded data | GTIN + serial + verification key (per category rules) |
| Registration | Required in the CRPT system before sale; codes are issued per order |
| Print quality | Must scan reliably at retail; low contrast and small module size are the usual failure points |
| Typical carriers | Direct marking on packaging, labels on the unit or on the consumer pack |
The symbol is a Data Matrix, but the payload follows GS1 element strings: a GTIN identifying the product, a serial number that makes the unit unique, and a verification key used by the system. Retail scanners send the decoded string to the CRPT system, which checks registration state before allowing the sale.
This is why an unregistered but technically valid code still fails at the till: validity is a property of the registry, not of the printed symbol.
Data Matrix is dense at small sizes. The most common field problems are insufficient contrast on dark or glossy substrates, module size below what the scanner can resolve, and ink spread closing the finder pattern on inkjet printing.
The practical control is a scan verification step at the end of the production line — not a sample from the print head. Verify a defined percentage of units, log failures, and reprint rather than ship codes that scan only intermittently.
Pre-printed labels are the fastest route for smaller volumes or when the packaging cannot be modified: order codes, print labels, apply and verify. Inline coding suits high-volume lines and removes label cost, but requires the printing equipment to be integrated with the code issuing workflow.
Whichever route you take, the codes must be issued in the correct quantity per order, because they are registered per unit and cannot simply be reused.
Unit-level codes become hard to handle at the warehouse unless they are aggregated. Aggregation records which units are inside which carton, and which cartons are on which pallet, so a single scan at outbound moves the whole consignment instead of thousands of individual scans.
For exports this is not optional convenience: the importer's receipt and SPOT confirmation operate on packages, not on a loose pile of units. Building aggregation into the packing process is cheaper than reconstructing it at the border, and it is the difference between a shipment that clears and one that waits.
Most rejected codes are not printing failures but data failures. A GTIN that does not match the declared product, a description that differs from the customs declaration, a quantity mismatch between the code order and the invoice — each of these produces codes that exist but cannot be used.
The control is a reconciliation step before the codes are ordered rather than after they are printed: confirm product data with the importer, confirm the quantity, confirm the serial range, and only then issue. Reprinting is cheap; unregistered codes on a container are not.
The code only works if the till can read it. Russian retail uses 2D scanners that decode GS1 Data Matrix element strings, but the software behind the scanner — the POS application — decides whether the decoded string is accepted and what it does with it.
Before a production run, ask your importer to test a sample of your printed labels on the equipment used in the destination stores, not on a generic desktop scanner. A symbol that grades well in a lab can still fail behind a scanner glass at an angle under store lighting, and the failure appears as a blocked sale rather than a printing complaint.
The symbology and element strings are GS1-based. The difference is the Russian registration and reporting layer around it.
Yes, if your equipment can print at sufficient quality and you can issue codes per order. Many exporters start with pre-printed labels and move inline as volume grows.
Verify with an actual scanner used at retail, on the real substrate, at production speed. Aim for consistent first-scan success rather than a minimum grade on paper.
Codes are tied to an order and a product. They are not reusable across products or markets; the registration state matters more than a nominal expiry date.
The unit cannot be sold until it is re-marked and re-registered correctly. This is why end-of-line verification is cheaper than fixing failures downstream.
Print quality is the operational risk
A code that cannot be read at the till is worse than no code: it blocks the sale and creates rework that nobody budgeted for. Validate on the real substrate, at production speed, with the scanner used downstream.