1C-Bitrix Integration with Mercury System: eVSD Automation

Integrating 1C-Bitrix with the Mercury system is mandatory for legal trade in animal products. Every day, millions of eVSDs pass through FSIS, and manual processing leads to delays and fines of up to 150,000 rubles. We automate the exchange using REST API and asynchronous queues, reducing the receiving time for a single batch by 5 times. We'll evaluate your project in 2 days — just contact us.

Integration of 1C-Bitrix with Mercury

Mercury provides a REST API (https://api.vetrf.ru/schema/platform/v2/). Authorization is via an API key issued after enterprise registration. Main operations: retrieving incoming documents, extinguishing eVSD, and checking application statuses. It's important to consider asynchronicity: each request creates an application that must be processed with a separate call. According to FSIS Mercury documentation, up to 10 requests per minute are allowed per API key. Therefore, we implement a queue with retries.

Typical document lifecycle:

Supplier → shipped goods with eVSD to Mercury
  → Store receives goods → extinguishes incoming eVSD (acceptVetDocument)
    → Warehouse storage: accounting unit with eVSD ID
      → Order placed → sale to individual
        → Write-off via transfer receipt transaction (transferReceiptTransaction)

When selling to an end consumer (individual), a new eVSD is not required — you only need to extinguish the document for the sold quantity.

PHP client implementation:

class MerkuryClient
{
    private string $apiUrl = 'https://api.vetrf.ru/schema/platform/v2';
    private string $apiKey;
    private string $issuerId;

    public function __construct(string $apiKey, string $issuerId)
    {
        $this->apiKey   = $apiKey;
        $this->issuerId = $issuerId;
    }

    public function getIncomingDocuments(string $enterpriseGuid): array
    {
        return $this->request('GET',
            "/enterprises/{$enterpriseGuid}/vetDocuments",
            ['status' => 'CONFIRMED', 'type' => 'INCOMING']
        );
    }

    public function extinguishDocument(
        string $enterpriseGuid,
        string $vetDocId,
        float  $quantity,
        string $unit
    ): string {
        $response = $this->request('POST',
            "/enterprises/{$enterpriseGuid}/vetDocuments/{$vetDocId}/extinguish",
            [
                'returnedQuantity' => $quantity,
                'returnedUnit'     => $unit,
                'operatorId'       => $this->issuerId,
            ]
        );
        return $response['application']['applicationId'];
    }

    public function processTransaction(
        string $enterpriseGuid,
        string $transactionId
    ): array {
        return $this->request('POST',
            "/enterprises/{$enterpriseGuid}/applications/{$transactionId}/process"
        );
    }

    private function request(string $method, string $path, array $params = []): array
    {
        // ... HTTP request with header 'apiKey: {KEY}'
    }
}

Storing eVSD in Bitrix

Each batch of goods in the warehouse is linked to one or more eVSDs. We store them in a separate ORM table:

class VetDocumentTable extends \Bitrix\Main\ORM\Data\DataManager
{
    public static function getTableName(): string { return 'local_merkury_vet_docs'; }

    public static function getMap(): array
    {
        return [
            new \Bitrix\Main\ORM\Fields\IntegerField('ID',          ['primary' => true, 'autocomplete' => true]),
            new \Bitrix\Main\ORM\Fields\IntegerField('PRODUCT_ID'),  // product in catalog
            new \Bitrix\Main\ORM\Fields\StringField('VET_DOC_ID'),   // UUID of document in Mercury
            new \Bitrix\Main\ORM\Fields\StringField('ENTERPRISE_GUID'), // enterprise GUID
            new \Bitrix\Main\ORM\Fields\FloatField('QUANTITY'),      // warehouse stock
            new \Bitrix\Main\ORM\Fields\StringField('UNIT'),         // unit: kg, piece
            new \Bitrix\Main\ORM\Fields\StringField('STATUS'),       // 'active', 'extinguished'
            new \Bitrix\Main\ORM\Fields\DatetimeField('EXPIRE_DATE'), // expiration date
        ];
    }
}

When a batch arrives, a record is created with the eVSD ID and quantity. Upon sale, the quantity decreases; when depleted, the status changes to extinguished.

Automating Extinguishing

If you extinguish manually, you can easily miss a deadline — then the certificate is revoked, and the goods become illegal. Fines for trading without an eVSD are up to 150,000 rubles. Automation eliminates human error and complies with 54-FZ requirements. Additionally, the Mercury API works asynchronously: a request creates an application that must be processed with a separate call. We implement a queue with retries to ensure no document is lost.

Comparison: Manual vs. Automated Approach

The data shows: automation speeds up the process by 5 times and reduces operational risks.

Case Study: Farm Products Store

Our client is an online store selling meat and dairy products from 15 farms. Volume: ~250 orders per week. Before us, receiving a single batch took 15 minutes of manual entry into Mercury, and extinguishing on sale was not done at all — risky.

Solution: we automated receiving (via Bitrix admin panel: the warehouse worker enters the receipt ID, the system automatically finds incoming eVSDs from the supplier in the last 24 hours and suggests extinguishing). For shipping, we use a two-step model: when an order is placed, an extinguishing request is created; a cron handler runs every 2 minutes calling processTransaction. Stock synchronization runs every hour.

Time savings on receiving: 80% — about 40 hours per month. Additionally, fines for missing extinguishments are eliminated.

Stock Synchronization

Periodic reconciliation is mandatory. Stock in the local_merkury_vet_docs table is compared with enterprise stock in Mercury (GET /enterprises/{guid}/stockEntries). Discrepancies are logged and notify the administrator. This is an extra safeguard against desynchronization.

What's Included in Turnkey Integration

• Registration in Mercury, obtaining an API key (we guide you through every step)
• PHP client development: work with incoming documents, extinguishing, application processing
• eVSD storage table in Bitrix linked to products
• Receiving interface in the admin section (fast, with hints)
• Automatic extinguishing on shipment with queue and automatic retries
• Scheduled stock synchronization (cron), discrepancy monitoring
• Operational documentation, staff training, post-launch support

Timeline: 6 to 10 weeks depending on the number of suppliers and accounting complexity. We have over 5 years of Bitrix integration with government systems and more than 50 successful projects. Order an audit of your project — get an integration plan in 2 days.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.