Integrate Wubook with 1C-Bitrix: Real-Time Sync via Zak API

Integrate Wubook with 1C-Bitrix: Real-Time Sync via Zak API

A hotel owner configured Wubook as a PMS and channel manager, but the Bitrix website operates separately. Bookings from the site don't reach Wubook, availability isn't synchronized — overbooking and lost orders become the norm. Our team has developed a proven solution: an integration guaranteeing stable operation.

Wubook is an Italian PMS with a channel manager. Unlike Russian property management systems, it actively works with European properties but is also used by independent Russian hotels, especially those managing Booking.com and Airbnb through a single channel manager. The goal of integrating with Bitrix is to replicate Wubook's online booking engine on the website without abandoning the PMS, and to synchronize data in both directions. According to our estimates, the integration pays for itself in 3–4 months by reducing manual entry and eliminating duplicates. The average cost of such integration varies, but time savings on booking processing reach 80%.

How Zak API Simplifies Booking Management?

Wubook provides two APIs: XML-RPC (legacy, but still functional) and Zak API (REST) — modern, JSON, base URL https://wubook.net/api/zak/. For new integrations, we recommend Zak: it's faster, easier to debug, and supports OAuth 2.0. Key differences:

Retrieving a session key for XML-RPC:

$client = new \PhpXmlRpc\Client('https://wubook.net/xrws/');
$msg = new \PhpXmlRpc\Request('wired.acquire_token', [
    new \PhpXmlRpc\Value(WUBOOK_USER),
    new \PhpXmlRpc\Value(WUBOOK_PASS),
    new \PhpXmlRpc\Value(WUBOOK_PROVIDER_KEY),
]);
$response = $client->send($msg);
$token = $response->value()->scalarval();

For Zak API, authorization uses Authorization: Bearer {access_token}, obtained via OAuth 2.0. According to official Wubook documentation (https://wubook.net/api/zak/), Zak API handles up to 1000 requests per minute without limits.

Why Real-Time Availability Synchronization Matters?

Wubook's channel manager distributes rooms across channels: Booking.com, Airbnb, direct website. If a room is booked on one channel, Wubook automatically reduces availability for others. The issue is that an agent polling every 15 minutes may not update quickly enough, and a guest from the website might get confirmation for an already occupied room. The solution is webhook notifications. Wubook supports push notifications (notifications) via POST /properties/{id}/notifications/subscribe. Upon receiving an availability_changed notification, we immediately invalidate the cache and make a targeted availability request for the affected dates and room types.

Zak API method GET /properties/{id}/rooms returns room types. Method GET /properties/{id}/availability returns availability for a range. The response structure includes rooms (array of types) and for each — an array of dates with avail field (number of available rooms). We write to bl_wubook_availability:

foreach ($availData['rooms'] as $roomType) {
    foreach ($roomType['dates'] as $dateEntry) {
        WubookAvailabilityTable::addOrUpdate([
            'ROOM_TYPE_ID' => $roomType['id'],
            'DATE'         => new \Bitrix\Main\Type\Date($dateEntry['date']),
            'QTY'          => (int)$dateEntry['avail'],
        ]);
    }
}

How We Create a Booking via Zak API?

POST /properties/{id}/reservations:

$payload = [
    'checkin'   => $dateFrom,
    'checkout'  => $dateTo,
    'rooms'     => [['id' => $wubookRoomId, 'amount' => 1]],
    'customer'  => [
        'name'  => $guestName,
        'email' => $guestEmail,
        'phone' => $guestPhone,
    ],
    'amount'    => $totalAmount,
    'currency'  => 'RUB',
    'channel'   => 'WEB',
    'notes'     => 'Order #' . $orderId . ' from website',
];
$result = $zakClient->post('/properties/' . WUBOOK_PROPERTY_ID . '/reservations', $payload);

Wubook returns reservation_id (numeric) and reservation_code (string, for display to guest). Both are saved in the Bitrix order.

Booking Cancellation and Error Handling

DELETE /properties/{id}/reservations/{reservation_id} or PUT with status cancelled. Wubook immediately releases the slot for other channels. In Bitrix, the order status handler on transition to "Cancelled" calls the cancellation API. On network error, we save a retry job in bl_wubook_pending_ops and process it via agent. Each failed operation stores the attempt count (max 5). An agent retries failed requests every 2 minutes. After 5 attempts, the record is marked as erroneous and an administrator notification is sent. This scheme ensures delivery guarantee even with temporary Wubook network issues.

Step-by-Step Integration Setup

1. Register application in Wubook – obtain client_id and client_secret for OAuth 2.0.
2. Get Bearer token – make POST request to /oauth/access_token.
3. Create HL-blocks – bl_wubook_availability and bl_wubook_pending_ops.
4. Set up agents – availability sync agent (5 min interval) and queue processing agent.
5. Subscribe to webhooks – register URL for availability_changed and reservation_created notifications.
6. Test – verify booking creation on a test property and availability synchronization.

What's Included in the Work

• Setup of Zak API and OAuth 2.0 – application registration, token retrieval.
• Synchronization of rooms and availability – HL-blocks for data storage, agents for periodic sync.
• Two-way booking management – create, modify, cancel from site and from Wubook.
• Webhooks and push notifications – event subscription, real-time processing.
• Retry queue for failed operations – guaranteed delivery on failures.
• Logging and monitoring – request recording for debugging.
• Testing on your property – verification with real data.

Timeline and Experience

Our experience in PMS and Bitrix integrations: 10+ years of development, over 50 successful projects for hotels and hostels. We guarantee stable synchronization with no data loss and provide operational documentation. Contact us to assess your project — we'll calculate the exact scope of work within one day. Get a consultation to learn how Wubook with 1C-Bitrix integration will reduce overbooking and manual entry.

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.