Chestny Znak and 1C integration for product marking

Marking isn't a one-time setup but a daily routine: codes must be received, transferred, written off — and not a single Data Matrix lost. Manufacturers, wholesale and retail all work with the Chestny Znak system today; errors in any link hit everyone.

So the key task is to remove manual entry and the human factor.

An employee can get distracted, mix up a couple of characters or forget to enter part of the data entirely.

Seems minor, but at company scale such "errors" turn into real downtime and losses: documents don't match, goods sit in stock, and lawyers later spend weeks sorting out the fallout.

Automation works here like insurance — the system never tires, never gets distracted and never errs through carelessness.

This is exactly the role that the 1C - Chestny Znak integration fills.

1C already manages the item master, batches, warehouse and sales.

Adding marking codes and EDI on top, you turn 1C into a single environment for accounting and traceability:

Codes are stored in product/batch records, statuses are pulled from Chestny Znak, and stock appears in 1C reports.

No Excel, no duplicates. EDI without copy-paste. Incoming/outgoing UPDs with codes are loaded, signed and sent automatically.

No manual transfer. Online control.

Marking code statuses ("in circulation", "retired", "awaiting confirmation") are visible right in 1C; a problem code is caught before shipping.

Printing and tracking unit, case and pallet codes in one process — order picking is faster, errors fewer.

On-site scanning. The POS and data terminals are all connected to 1C and handle labeled goods without workarounds.

Every failure is logged: it's easier to investigate and resend the document correctly (without creating duplicates).

Ordering marking codes from 1C via SUZ, printing labels, aggregation on packaging, putting into circulation — all in one workflow.

Fewer line stoppages from lost codes, easier handling of defects (withdrawal from circulation/re-marking reflected in accounting).

Receiving by UPD with automatic matching of marking codes and item master.

Picking shipments with a scanner: scan it — the code lands in the document, the EDI is sent, ownership changes. Retail.

Sales in permissive mode: the register won't ring up a bad code.

Returns and write-offs are recorded correctly: the marking code is returned or withdrawn from circulation and does not hang in stock.

Fewer risks of fines and claims during inspections.

The UPD is signed, but the codes are not registered in 1C — the sale is blocked and the warehouse stalls.

The document was sent with an error and cannot be duplicated — you have to sort it out manually, losing time.

Extra or foreign marking codes in stock mean risks of fines and batch freezes.

When accounting is done manually or across disconnected systems, every operation becomes a quest: somewhere a code is lost, somewhere it's entered twice, and somewhere it just wasn't submitted on time.

At first, these seem like isolated minor mistakes, but down the chain they lead to shipment blocks, failed deliveries, and tense negotiations with counterparties.

Standard configurations already can: enable accounting of labeled groups; work with a local module/SUZ to exchange with CRPT; pull in/send codes via EDI; print marking codes and aggregated labels; check the marking code status before an operation.

In practice, integration rollout rarely follows the textbook scenario. Every company has its own habits, rules and even a "human factor" that always makes adjustments. Some keep stock in Excel, some run parallel accounting in notebooks, and some are used to "keeping everything in their head".

With Chestny Znak it is important to align internal processes: define who is responsible for what, where primary accounting is kept, which documents move automatically and which must be checked manually.

It seems like a trifle, but it is exactly these organizational details that ultimately decide whether the system runs like clockwork or turns into yet another "pain point".

The rest is a matter of discipline: release updates, receipt and shipment procedures, staff training.

1C and Chestny Znak integration is basic hygiene for manufacturing, wholesale and retail.

You unite accounting, EDI and marking-code handling in one system, gaining traceability and predictable operations instead of endless makeshift manual fixes.

Chestny Znak is a national digital tracking platform that controls the path of every product unit from the factory or border to the store checkout.

The system is maintained and operated by CRPT (Center for Advanced Technology Development), the operator ensuring its stable performance and growth.

A unique DataMatrix code is applied to the product.

Every movement is recorded in the system: release, shipment, receipt, sale, return, write-off.

On any discrepancy, the code is blocked.

For the business this means the goods exist physically, but in Chestny Znak they no longer exist.

Thus, labeling makes the market transparent and blocks the path for counterfeits.

But for companies it's also a daily obligation — working with marking codes is built into every process: from the warehouse to accounting.

In effect, the system step by step covers all mass market segments.

For the business this means the question "will mandatory marking apply to us" stopped being relevant long ago.

The real question is different: how to embed marking into your processes without halting sales or facing fines.

Where goods used to be tracked by batches or boxes, now every single unit has its own individual code.

This code must be properly introduced into circulation, passed along the chain and correctly written off.

Any error during transfer makes the goods problematic.

That is why integration with 1C becomes not just a convenience but a necessity: it automates the recording of all code operations and reduces the chance of staff errors.

Get an account on the Chestny Znak website.

Issue and configure a UKEP (enhanced qualified electronic signature) to start working.

Set up work with an electronic document exchange operator in 1C (1C-EDI, Diadoc, SBIS, etc.).

Without EDI, exchanging UPD documents with codes is impossible.

Install the current release of 1C (ERP, Accounting, Trade Management, Small Firm Management, Retail).

Mark which groups are subject to mandatory marking (clothing, footwear, dairy, water, etc.). In the "Exchange with IS MP" workstation interface, use the built-in HS code classifier.

For each item, specify the HS code and the marking group.

Manufacturers and importers must set the GTIN in the item master records.

If the product is new, register a GTIN and sync it with the Chestny Znak system. In 1C, set up label print templates with Data Matrix.

Create the "SUZ Marking Code Issuance Order" document. Basis: "Production Order" (for release) or "Purchase Order" (for import).

Once received, codes are printed and applied to the products.

To proceed, create a "Goods Marking IS MP" document based on previously entered documents: purchase, production, or production without an order.

A write-off document is generated for unused or defective codes.

A document is created based on the incoming UPD.

Codes are pulled from EDI automatically.

Sales, return and adjustment documents are used.

When shipping is processed, codes are scanned and sent to Chestny Znak via EDI. In retail — a POS receipt (if the register supports FFD 1.2).

If the POS lacks this function — the "Withdrawal from circulation" document in 1C.

1C has a "Marking Code Check" tool.

It's recommended to enable automatic status control across operations.

Create test documents for introduction, sale and write-off. Make sure the statuses in 1C and in

All operations are logged in the 1C registration journal.

Here you can also see exchange errors (duplicates, mismatches, invalid codes).

After completing all stages, the company gets a fully automated marking process: codes are issued and printed directly from 1C, purchase and sale operations sync automatically with Chestny Znak, and errors and delays are kept to a minimum.

This shortens document processing time, lowers the risk of fines and ensures transparency of product movement at every stage — from production to the end customer.

An incorrectly applied or damaged DataMatrix.

The code prints poorly, smudges or tears when applied — so the scanner can't read it.

What to do: check print quality, use certified printers and scanners. In 1C, enable code status checks via exchange with

Duplicate codes. Identical marking codes land in the same document.

When trying to send — an error from CRPT.

What to do: use scanning at all stages (receiving, shipping, returns).

Disable manual entry of marking codes in documents.

The supplier issued the document but didn't attach the list of marking codes.

What to do: record the discrepancy report in the EDI and do not sign the document until it is corrected.

Data mismatch. The UPD lists 100 units, but only 95 codes were transferred.

What to do: reconcile documents and system data before signing. In 1C, the "Marking Code Verification" report helps detect shortages.

If an incoming UPD is not signed on time, the codes stay hanging in limbo.

What to do: set up reminders or monitoring in 1C to close incoming documents on time.

Resending a UPD with the same number and date equals an error.

What to do: create a corrective UKD instead of resending a duplicate.

The error "code not found" or "not your code". 1C lists the product, but per the system it's still with the supplier or already withdrawn.

What to do: check statuses before shipping; if a code is not on your balance, demand a correct document from the supplier.

Network failures or invalid tokens happen.

What to do: recheck the OMSID and token, refresh the connection to SUZ.

If the network goes down, set up automatic resending.

A written-off item still shows as "in circulation".

If a defect or disposal is not recorded with a document in 1C, the code stays active.

When defective products are found, paperwork can't be delayed. The same day you must record the fact and create the "Write-off of IS MP marking codes" document in the system.

This approach helps avoid accounting errors, prevents reuse of codes and ensures data accuracy in the Chestny Znak system.

A customer return was not processed through the system. The marking code came back physically but was not returned in Chestny Znak.

What to do: process the return via a UKD or a return receipt so the code gets the correct status.

Every typical failure comes down to one thing: a gap between the fact and its reflection in accounting.

To avoid problems: run all operations through 1C documents, scan every marking code, reconcile system data and reports in 1C before sending, and monitor the exchange log with

Marking is now part of everyday business operations. Every year the list of categories expands and more companies fall under the Chestny Znak system. Here the cost of an error is too high: from a batch block to heavy fines.

Integration with 1C removes the chaos and turns marking into a familiar business process. One program unites accounting, EDI, code handling and product movement operations: putting into and withdrawing from circulation.

This reduces the number of errors, speeds up document exchange and makes data transparent for every link in the chain.

The key to success is correct integration setup.

If you update 1C on time, fill in reference data correctly, scan every code and work through documents, the risk of failures is minimal. With support and oversight from the IT and accounting teams, exchange with Chestny Znak becomes routine rather than stressful.