1C-Bitrix Bnovo Integration: Automate Bookings

Overbooking due to manual reservation transfers is a classic revenue loss scenario for hotels. According to our statistics, up to 15% of bookings are lost due to delays or errors during double entry. A manager receives a request via the website on Bitrix, manually enters the reservation into Bnovo, then manually updates room availability back to the website. Two sources of truth—two places for errors. We've encountered this dozens of times. Our goal is to make the booking system and CMS communicate directly, without human intervention. This not only speeds up the process by 3 times, but also completely eliminates the risk of overbooking. Admin time savings reach 70%, and the cost of processing one booking is reduced by 2–3 times. For a typical hotel with 50 monthly bookings, admin time savings amount to about €300 per month, reducing costs by €3,600 annually.

Our bitrix bnovo integration leverages bnovo rest api for seamless data exchange between the PMS system for hotels and the website's bitrix booking module, ensuring bnovo webhooks handle real-time updates.

Bnovo is a PMS system for hotels with its own channel manager and REST API. Authorization is via the hotel's API key in the X-Api-Key header. Main entities: rooms, reservations, rates, availability. Direct integration via API is 3 times faster than ready-made modules—no need to wait for vendor updates. We guarantee no overbooking and stable synchronization.

Solving manual entry problem with 1C-Bitrix and Bnovo integration

Integration architecture

Bnovo provides a REST API (https://online.bnovo.ru/api/v1/). Data flow directions:

1. Bnovo → Bitrix: synchronization of room availability and rates—so the widget on the site shows current occupancy.
2. Bitrix → Bnovo: transfer of new reservations created via the site.

We avoid intermediate storage—data is transferred directly via API with caching on the Bitrix side.

Availability synchronization

Bnovo returns availability via GET /api/v1/availability?hotel_id={id}&date_from=YYYY-MM-DD&date_to=YYYY-MM-DD. The response contains an array of dates with the number of free rooms for each type.

A Bitrix agent runs every 10 minutes and updates the local availability cache in the bl_bnovo_availability table:

CREATE TABLE bl_bnovo_availability (
    room_type_id  INT NOT NULL,
    date          DATE NOT NULL,
    qty_available SMALLINT NOT NULL DEFAULT 0,
    synced_at     TIMESTAMP NOT NULL,
    PRIMARY KEY (room_type_id, date)
);

The online booking widget on the site queries this table—without calling the Bnovo API in real time. This reduces dependency on external service availability and speeds up form response. API response time is under 500ms on average.

Creating a reservation in Bnovo from Bitrix

After successful order payment (event OnSalePaymentEntitySaved when IS_PAID = Y), the handler forms a request to Bnovo:

$response = $bnovoClient->post('/api/v1/reservations', [
    'hotel_id'   => $this->hotelId,
    'room_id'    => $roomId,
    'date_from'  => $booking->getDateFrom()->format('Y-m-d'),
    'date_to'    => $booking->getDateTo()->format('Y-m-d'),
    'rate_id'    => $booking->getRateId(),
    'guest'      => [
        'name'  => $order->getPropertyValueByCode('NAME'),
        'phone' => $order->getPropertyValueByCode('PHONE'),
        'email' => $order->getPropertyValueByCode('EMAIL'),
    ],
    'amount'     => $payment->getSum(),
    'source'     => 'website',
]);
$bnovoReservationId = $response['reservation']['id'];

reservation_id from the response is saved in the order's UF field UF_BNOVO_RESERVATION_ID—this is necessary for subsequent operations (cancellation, date changes).

Webhooks from Bnovo

Bnovo can send webhooks when the status of a reservation created inside the PMS (not via the site) changes. Setup is in the "Integrations" section of the Bnovo control panel: specify the handler URL on the Bitrix side.

Handler /api/bnovo-webhook.php:

$payload = json_decode(file_get_contents('php://input'), true);
// Signature check: HMAC-SHA256 of request body + secret key
$expectedSign = hash_hmac('sha256', file_get_contents('php://input'), BNOVO_WEBHOOK_SECRET);
if (!hash_equals($expectedSign, $_SERVER['HTTP_X_BNOVO_SIGNATURE'] ?? '')) {
    http_response_code(403);
    exit;
}

switch ($payload['event']) {
    case 'reservation.created':
        // Create an order in Bitrix or notify the manager
        break;
    case 'reservation.cancelled':
        // Cancel the order in Bitrix
        BnovoSyncService::cancelOrder($payload['reservation_id']);
        break;
    case 'availability.updated':
        // Invalidate availability cache for affected dates
        BnovoCache::invalidate($payload['room_type_id'], $payload['dates']);
        break;
}

Source: Bnovo REST API documentation.

Why direct REST API integration is better than ready-made modules?

Ready-made modules from the Marketplace often do not cover hotel specifics: unique rates, complex cancellation rules, integration with cash registers. Direct REST API gives full control. Our team has 8+ years in hotel automation and 1c-bitrix hotel projects, and has implemented 50+ integrations with PMS systems. We write code for your scenario, not adjust your business to a module. Secure bitrix data exchange ensures consistency across all channels.

Rates and seasonal prices

Bnovo stores rates—pricing rule sets. The GET /api/v1/rates method returns a list with conditions: minimum nights, date restrictions, meal type. We sync rates into the bl_bnovo_rates table once an hour—they change rarely.

On the booking form on the site, rates are loaded via AJAX: the user selects dates, the site requests current rates with prices via GET /api/v1/rates/prices?room_id=X&date_from=...&date_to=... and displays accommodation options.

How to set up integration in 6 steps

1. Obtain an API key from Bnovo via the control panel.
2. Create the bl_bnovo_availability table in the database.
3. Set up a Bitrix agent for availability synchronization (period 10 minutes).
4. Implement the OnSalePaymentEntitySaved event handler to transfer reservations.
5. Configure webhook notifications in Bnovo (reservations, cancellations, availability updates).
6. Test synchronization on a staging site and perform load testing.

What's included in the integration work?

Implementation timeline

The cost is calculated individually. We'll evaluate your project after getting familiar with your current site architecture. Get a demo access to the integration or order a pilot project. Contact us for a consultation. We guarantee stable synchronization operation: we monitor all critical channels together with your team.

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.