Honest Sign (Chestny Znak) Integration with 1C-Bitrix

We often encounter the task of integrating online stores on Bitrix with the "Chestny Znak" (Honest Sign) system. Mandatory product labeling covers many categories: medicines, tobacco, footwear, clothing, dairy products. The technical side involves receiving Data Matrix codes from suppliers, storing them, and transmitting them to GIS MT (State Information System for Monitoring the Turnover of Goods) upon sale. Errors at any stage risk blocking product turnover. We'll assess your project in one day for $500 and offer an optimal solution. Full integration starts from $2,000, saving you up to 40% on error-related fines.

What problems does integration with Chestny Znak solve?

The first and main problem is format mismatch. Marking codes come from suppliers in various formats: XML, CSV, and sometimes manually. We need to unify loading and verification of codes via the markirovka.nalog.ru API. The second is storing millions of unique codes in Bitrix. Standard infoblock properties are not designed for such load. The third is timely notification to GIS MT about product withdrawal from circulation. A delay or error in sending — and the product remains in circulation, risking fines.

Integration via 1C + Bitrix module

The standard path for most online stores: accounting of marked products is done in 1C, Bitrix serves as the storefront. Synchronization through the standard exchange module bitrix:catalog.import.1c (CommerceML).

With this approach, marking codes (Data Matrix) are stored in 1C and transferred to Bitrix along with stock via XML export. In CommerceML XML, fields for marking codes are not standardized—they are transmitted as additional product requisites:

<ЗначениеРеквизита> <Наименование>КодМаркировки</Наименование> <Значение>010460406000600021N4N57RSCBUZTJZ</Значение> </ЗначениеРеквизита> 

In Bitrix, you configure a catalog property MARKING_CODE and map the requisite in the exchange settings.

Direct integration with Chestny Znak API

For online stores working directly with GIS MT without 1C, a direct integration via the markirovka.nalog.ru API is needed. The API uses OAuth2 authorization with UKEP (qualified electronic signature).

The main API methods relevant to e-commerce:

• POST /api/v3/facade/identifyDocument — verify marking code
• POST /api/v3/facade/send — notify about product withdrawal from circulation upon sale

In Bitrix, you implement a service class for working with the API:

namespace Local\MarkingCode; class ChestnyZnakClient { private string $apiUrl = 'https://markirovka.nalog.ru/api/v3'; private \Bitrix\Main\Web\HttpClient $http; public function verifyCode(string $code): array { $this->http->setHeader('Authorization', 'Bearer ' . $this->getToken()); $response = $this->http->post($this->apiUrl . '/facade/identifyDocument', ['code' => $code]); return json_decode($response, true); } } 

You obtain the token via UKEP—this requires a cryptographic library (CryptoPro CSP) on the server.

How to store marking codes in Bitrix?

Each product instance has a unique marking code. Storing in a catalog element property (b_iblock_element_prop_m*) is not suitable—one product can have hundreds of instances with different codes.

Create a separate table via ORM D7:

class MarkingCodeTable extends \Bitrix\Main\Entity\DataManager { public static function getTableName() { return 'b_local_marking_code'; } public static function getMap() { return [ new \Bitrix\Main\Entity\IntegerField('ID', ['primary' => true, 'autocomplete' => true]), new \Bitrix\Main\Entity\IntegerField('PRODUCT_ID'), new \Bitrix\Main\Entity\StringField('CODE', ['size' => 200]), new \Bitrix\Main\Entity\StringField('STATUS'), // 'active', 'sold', 'returned' new \Bitrix\Main\Entity\DatetimeField('CREATED_AT'), ]; } } 

Upon product sale (event OnSaleOrderPaid), change the code status from active to sold and send a notification to GIS MT.

What to do when selling a product?

Upon successful order payment, notify the labeling system about withdrawal from circulation. This is an asynchronous operation—do not block the order placement process waiting for an API response.

Implement via agent or queue: upon OnSaleOrderPaid, write a task to a custom table b_local_marking_queue, an agent with a 1-minute interval processes the queue and sends requests to GIS MT.

Comparison of approaches: via 1C vs direct API

Direct API integration is 5–10 times faster than 1C exchange, but requires more development. We recommend it if you have >10,000 products and minimal latency is critical.

What is included in the setup?

Your investment includes a proven process backed by our certified team with over 7 years of Bitrix experience and 30+ successful labeling integrations. We guarantee a smooth rollout with minimal downtime.

Deliverables:

• Detailed project audit and architecture proposal
• Custom ORM table design for marking codes
• Full API client implementation (OAuth2, UKEP, CRUD operations)
• Event handlers for order lifecycle (payment, refund)
• Asynchronous queue agent for API calls
• Configuration of 1C exchange if applicable
• Testing on GIS MT sandbox environment
• Complete technical documentation and administrator guide
• Manager training session (up to 2 hours)
• 1 month of post-launch support

Integration roadmap (typical timeline)

Trust indicators: Our certified developers have completed over 30 projects. We provide a 30-day satisfaction guarantee on the integration. Contact us for a consultation today.