Kazakhstan Adopts DataMatrix Marking Rules For Light-Industry Goods

The order covers numerous Eurasian Economic Union tariff classifications, including leather clothing under 4203 10 000, knitted garments in headings 6101 to 6106, outerwear and clothing in 6201 to 6206, household textiles in 6302 and other listed lines. Businesses should confirm each product against the statutory list rather than assume that all textiles are covered.

General provisions take effect 60 calendar days after first official publication. Paragraphs 29 to 32, 36 to 40, 43, 46 and 47, which include parts of the movement and traceability process, apply from 1 October 2027. Stock already in circulation must carry identification marks no later than 1 January 2028.

DataMatrix Codes Connect Each Operator To The Central System

Identification uses machine-readable GS1 DataMatrix codes linked to a Global Trade Item Number and serial number. Manufacturers must mark Kazakhstan-made goods before their first paid or free transfer to a new owner or another person for sale. Importers or authorised economic operators must mark foreign goods before import or before placement under release-for-home-use or reimport customs procedures.

Manufacturers and importers must register themselves and covered products in the Central Marking and Traceability System, obtain codes and transmit marking, placement, movement and withdrawal information. Wholesalers must report transactions. Retailers need a data-capable cash register, a connected device able to read DataMatrix codes and an agreement with a fiscal-data operator for unit-level withdrawal reporting.

Goods covered by Article 8 of the Eurasian Economic Union marking agreement remain outside the marking requirement. The order also allows information to be submitted through the central system's personal account where an operator lacks an integrated hardware and software complex. These provisions should not be confused with an exemption from registration or reporting.

Manufacturers, importers and distributors should build a product-code inventory, confirm GS1 ownership, test code placement and print quality, and map aggregation and disaggregation events. Retailers should validate scanners, till software and fiscal-data connections. Contracts should allocate responsibility for code generation, data accuracy, re-marking damaged labels and handling returns.

Foresight analysis: the phased dates divide physical marking from parts of digital movement reporting, but an isolated label project will be inadequate. Product master data, customs timing, warehouse events and point-of-sale withdrawal must operate as one traceability chain, so integration testing should begin before the delayed provisions become mandatory.

Practical call to action: Map covered tariff codes and operators, then run an end-to-end DataMatrix pilot from code issuance through customs, warehousing and retail withdrawal.