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.

Get a consultation (one-day assessment: $500) — we will assess your project and offer an optimal solution. Full integration from $2,000.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.