1C integration with Chestny Znak

Marking requires discipline in product data and operating procedures. Codes must move correctly through production, purchasing, warehouse acceptance, sales, returns and write-offs.

Standard 1C configurations already support many marking scenarios. Most projects need configuration, data cleanup and process alignment rather than heavy custom development. Before connecting the exchange, we map scanning checkpoints and audit item cards so GTIN, HS codes and marking groups are complete.

• Chestny Znak account and qualified electronic signature for signing operations.
• Connected EDI operator for legally significant documents with marking codes.
• Current 1C release with product marking groups enabled.
• OMS/SUZ credentials, organization mapping and authorization token from GIS MT.
• 2D scanners and handheld terminals for warehouse checkpoints; POS equipment that supports the required fiscal data format.
• Complete GTIN, HS code and marking group data across the product catalog.

We configure marking groups, exchange with GIS MT and OMS/SUZ, code ordering and printing, aggregation, putting goods into circulation, EDI flows, sales, returns, write-offs and status checks.

The setup covers the full code lifecycle, from emission request to withdrawal from circulation, so statuses in 1C and GIS MT stay aligned at each step.

• OMS/SUZ connection: identifiers, token, exchange format, schedule, organizations and warehouses.
• Code emission requests based on production or supplier orders, with Data Matrix label templates by product group.
• Aggregation of individual units into boxes and pallets with group labels.
• Inbound acceptance through EDI documents where codes are matched to item cards automatically.
• POS sale and automatic withdrawal from circulation; returns through correction documents or return receipts.
• Write-off of damaged or unused codes with pre-operation status checks.

Most failures happen between warehouse, POS, EDI and 1C: a document carries the wrong codes, a status is not updated, a code is unreadable or stock balances diverge.

The common pattern is a gap between the physical operation and the accounting record. We make this visible in exchange logs, status checks and operational reports before the issue reaches shipment or sale.

• An EDI document is signed, but the codes are not registered in 1C, blocking sale or shipment.
• The document quantity and the number of transferred codes do not match.
• Duplicate codes appear in a document and GIS MT rejects the operation.
• A code is reported as unknown or owned by another participant because its status was not checked before shipment.
• Defects or returns are not written off correctly, so codes remain in circulation and diverge from stock.
• Exchange fails because of invalid OMS/SUZ credentials or expired authorization tokens.

Operations with marked goods become predictable: errors are visible before shipment or sale, warehouse and accounting teams understand where a failure happened, and 1C reflects the same lifecycle as GIS MT.

For the business this reduces manual checks, protects revenue from blocked shipments and lowers the risk of fines or confiscation caused by incorrect marking operations.

• Code statuses are visible in 1C before critical operations.
• Scanning at checkpoints reduces manual code entry and duplicates.
• Warehouse teams handle marking tasks with handheld terminals instead of separate manual registers.
• 1C stock balances reconcile with GIS MT statuses.
• Returns and write-offs receive correct code statuses and do not remain stuck in stock.

KT.Team has delivered marking and 1C integration work through loosely coupled architecture, observable exchanges and real operational metrics: a single API for 200+ 1C:Retail systems, e-commerce exchanges, stock synchronization, PIM and enterprise services.