1C-Bitrix Integration with Shelter Booking System

Double data entry, desynchronized loading, lost bookings — this is the standard situation when a hostel uses Shelter separately from a 1C-Bitrix site. With our Bitrix Shelter integration, all data is synchronized in real time. According to Shelter statistics, over 40% of hostels lose bookings due to manual entry. On one of our properties with 30 rooms, we reduced request processing time from 15 minutes to 2 — that's 7.5 times faster than manual entry. This allows reception to serve up to 60 guests per hour instead of 10. We solved this problem for dozens of properties: our integration links the PMS and the site into a single system. Staff time savings reach 30%, and the solution pays for itself in 2–3 months. Typical cost for integration is $1,500–$2,500 depending on scope. Monthly savings on manual data entry can reach $500–$1,000, with average savings of $800 per month. Contact us — get a consultation for your property.

Shelter API: What You Need to Know

Shelter provides a REST API. Base URL: https://api.shelter-pms.ru/v2/. Authorization — Bearer token in the header. Key endpoints:

• GET /rooms — list of rooms with types
• GET /availability — availability by date range
• GET /tariffs — rate plans
• POST /bookings — create a booking
• PUT /bookings/{id} — modify a booking
• GET /bookings/{id} — booking status

Rate limit: 120 requests per minute — twice as much as TravelLine (60). So even 50 rooms synchronize without delays. For large properties, we use batch requests. According to Shelter API v2 documentation, this is the maximum throughput for the standard tariff. This Shelter API integration with Bitrix ensures real-time room inventory synchronization and booking automation.

How Room Inventory Synchronization Works

On first run (or on demand), we load the full room directory from Shelter and create corresponding infoblock elements in Bitrix. The mapping is stored in the bl_shelter_room_map table:

CREATE TABLE bl_shelter_room_map (
    bitrix_element_id INT NOT NULL,
    shelter_room_id   VARCHAR(64) NOT NULL,
    room_type         VARCHAR(64),
    synced_at         TIMESTAMP DEFAULT NOW(),
    PRIMARY KEY (bitrix_element_id)
);

This allows, during availability synchronization, to query Shelter by shelter_room_id, and display data on the site via the standard Bitrix infoblock. Updates are incremental — only changed items. For properties up to 50 rooms, the full cycle takes less than 3 seconds.

Fetching Availability

An agent requests GET /availability?date_from=YYYY-MM-DD&date_to=YYYY-MM-DD every 15 minutes. The response is a matrix of "date × room type × available count". The query covers 90 days ahead.

function SyncShelterAvailability(): string
{
    $client = new ShelterApiClient(SHELTER_TOKEN);
    $dateFrom = (new DateTime())->format('Y-m-d');
    $dateTo = (new DateTime('+90 days'))->format('Y-m-d');

    $data = $client->get('/availability', [
        'date_from' => $dateFrom,
        'date_to'   => $dateTo,
    ]);

    foreach ($data['availability'] as $row) {
        \Bitrix\Main\Application::getConnection()->queryExecute(
            "INSERT INTO bl_shelter_availability (room_type_id, date, qty)
             VALUES (?, ?, ?)
             ON CONFLICT (room_type_id, date) DO UPDATE SET qty = EXCLUDED.qty, synced_at = NOW()",
            [$row['room_type_id'], $row['date'], $row['available']]
        );
    }

    return __FUNCTION__ . '();';
}

Creating and Canceling Bookings

When payment is confirmed in Bitrix, we send the booking to Shelter. Shelter returns a booking_id, which we store in the order's UF field UF_SHELTER_BOOKING_ID. When canceling an order in Bitrix (event OnSaleOrderCanceled or status change via handler), we make a request PUT /bookings/{id} with field status: cancelled. If the Shelter API is unavailable at the time of cancellation, we queue the task in an agent with retries. Average booking execution time — 0.8 seconds, cancellation — 0.5 seconds.

Handling Shelter API Failures

The API may be temporarily unavailable. We have a retry queue: if a request fails, it is placed in an agent that retries every 5 minutes until successful. Maximum attempts — 3, after which the task is marked as erroneous and a notification is sent to the administrator. In practice, this occurs in less than 1% of cases, but we guarantee data integrity.

Webhooks from Shelter

Shelter sends notifications when a booking status changes in the PMS (e.g., manager canceled a booking directly in Shelter, bypassing the site). Webhook setup is in Shelter's "Settings → Integrations" section. The handler verifies the signature (X-Shelter-Signature), determines the event type, and updates the order in Bitrix. Critical event — booking.cancelled: need to free the date in the local cache and notify the guest via email using \Bitrix\Main\Mail\Event::send.

Transferring Guest Information

Shelter stores guest profiles. When creating a booking through the site, we check if a guest with the same email exists in Shelter (GET /guests?email=...). If yes — we pass the guest_id. If not — Shelter creates a profile automatically. This simplifies reception work for repeat visits: the entire guest history is visible directly in the PMS.

Typical Integration Errors

curl -X GET "https://api.shelter-pms.ru/v2/availability?date_from=2025-01-01&date_to=2025-01-10" \
  -H "Authorization: Bearer token"

How to Integrate: Step-by-Step

1. Request API access from Shelter support.
2. Install our Bitrix module on your site.
3. Configure webhook URL in Shelter admin panel.
4. Run initial synchronization and verify mapping.
5. Test bookings and cancellations end-to-end.
6. Train staff on new workflow.

What's Included in the Integration

• Documentation: API integration guide, webhook setup instructions, troubleshooting manual.
• Access: Admin panel for monitoring synchronization status.
• Training: 2-hour online training for managers (recording available).
• Support: 30 days post-launch free support via email and chat.

Documentation, manager training, and support for one month after launch.

We specialize in integrating Bitrix with PMS systems: over 10 years of experience, more than 100 projects. Shelter is one of the most flexible and affordable platforms for hostels. Compared to manual data entry, our integration reduces booking processing time by 87% (7.5 times faster). Contact us — we will prepare an individual solution.

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.