Chestny Znak in 1C: how to work with it, export codes, and configure cash registers in 2026

Chestny Znak integration with 1C is needed not only for exchange architecture, but also for daily operations: accept an UTD with codes, check the KM status, sell goods at checkout, remove a code from circulation, process a return or write-off. If 1C, EDI, GIS MT, the POS, and the warehouse are out of sync on statuses, the goods are physically there, but the operation is blocked or sent for manual review. From July 1, 2026, some product groups will receive new retail and EDI obligations, and the retail environment must be ready to switch to TS PIoT.

So below, we start with the practical workflow in 1C, then move to the architecture of a setup that does not fall apart after the next rule change.

In 2026, not only the product group lists change, but also the way codes are handled in daily work. The official Chestny Znak calendar shows item-level tracking from March 1, 2026 for several groups, and 1C separately highlights new stages for sweets, motor oils, caviar, building materials, cosmetics, household chemicals, and personal care products.

For the question "what to do from July 1, 2026," three practical changes matter: retail code scanning for cosmetics and household chemicals, mandatory EDI/volume-based batch tracking in this group, and the end of the old X-API-KEY scheme for retail checks in favor of TS PIoT.

The question "how to withdraw marking codes from 1C" usually mixes two different scenarios. The first is retail sales: the cashier scans the Data Matrix code, the checkout verifies the code in Chestny Znak, and after a successful check the receipt is issued and the code is withdrawn from circulation through the cash register/operator of fiscal data. The second covers other reasons for disposal: write-off, defects, internal use, export, repackaging, or product loss. In that case, you need a 1C/accounting-system document with the reason, links to the codes, and submission of data to Chestny Znak.

If there are many scenarios, it is better to design it from the start integrating 1C with Chestny Znak as a process with logs, alerts, and an error owner, not as a set of manual documents.

Auto-signing is useful only where control is clear: which documents may be signed automatically, who handles exceptions, and where it is visible that the UTD is stuck. The basic setup is this: the qualified electronic signature and permissions are configured for the organization, outbound UTDs are checked for details and codes, then a scheduled job sends the document to the EDI operator, and the log shows the statuses "created", "signed", "sent", "accepted", "rejected".

For the business process, the important thing is not the "sign automatically" button, but the procedure: who is allowed to auto-sign, which checks are mandatory before sending, and who resolves the error before shipment is blocked.

Approval mode works before the receipt is issued: the cashier scans the marking code, the POS software sends it to GIS MT for verification, the receipt is issued if the check succeeds, and the register shows an error if it is blocked. In the 1C landscape, this must be checked beyond the register itself: you need the current cash register driver, support for the required fiscal data format, product group settings, CDN/module availability, a verification log, and cashier instructions.

Main principle:

• verification refusal is not a "cashier problem"
• and a signal
• that it is the accounting fact
• checkout environment
• the state status of the code no longer matches

In the working loop 1C holds the item master, batches, movement documents, code statuses and the link to source operations. The other systems cover their own areas: EDI transmits the UPD document, GIS MT stores the code state, SUZ issues codes, the cash register retires goods from circulation, scanners and WMS record actual movement.

If gaps remain after the checklist - assess your 1C readiness for product marking: we will review your setup and show what to resolve before going live.