Booking Module for 1C-Bitrix: Custom Development Turnkey

Imagine: a client tries to book a hotel room for specific dates, but the system doesn't check availability. Two bookings for the same room overlap — overbooking and complaints are inevitable. Standard b_sale_order mechanisms don't work with time intervals. In one project, overbooking reached 10% of bookings, causing significant losses. In another case, we recovered substantial revenue by implementing atomic transactions. Such problems are solved by a custom booking module.

Bitrix Booking Module Development Turnkey Solution

We develop turnkey booking modules for 1C-Bitrix. Typical tasks include hotels, car rentals, meeting rooms, or travel tours. Bitrix lacks a ready-made tool for time slots, so we create custom solutions using infoblocks and highload block. Our vendor.booking module has been proven on 15+ projects and handles concurrent bookings without race conditions. The module processes up to 10,000 bookings per day with peak load of 100 requests per second. Based on load testing on a project with a 200-room hotel. Development cost starts from $2,000, saving up to 50% compared to off-the-shelf solutions with similar functionality. For a mid-sized hotel (50 rooms), our solution reduces overbooking by 99%, saving an estimated $10,000 annually.

How the Booking Module Handles Concurrent Bookings?

The vendor.booking module includes key tables:

• b_vendor_booking_resource — resources: id, name, type, capacity, iblock_element_id, settings (JSON: minimum period, maximum, step, prepayment).
• b_vendor_booking_slot — predefined slots for hourly rental: id, resource_id, date, time_from, time_to, status.
• b_vendor_booking_reservation — bookings: id, resource_id, user_id, date_from, date_to, status (pending/confirmed/cancelled/completed), total_price, order_id.
• b_vendor_booking_block — manual date blocking: id, resource_id, date_from, date_to, reason.

For daily rental, we use a model with date_from/date_to without slots. For hourly rental, we use slots with fixed intervals.

Why Atomic Locking Is Critical?

Without it, two users could simultaneously book the same slot. We use a transaction with SELECT FOR UPDATE. For more on atomic operations, see Wikipedia.

public function reserve(int $resourceId, \DateTime $from, \DateTime $to, int $userId): ReservationResult
{
    $connection = \Bitrix\Main\Application::getConnection();
    $connection->startTransaction();

    try {
        // Проверяем конфликты с блокировкой строк
        $conflicts = $connection->query("
            SELECT id FROM b_vendor_booking_reservation
            WHERE resource_id = {$resourceId}
              AND status IN ('pending', 'confirmed')
              AND NOT (date_to <= '{$from->format('Y-m-d')}' OR date_from >= '{$to->format('Y-m-d')}')
            FOR UPDATE
        ")->fetch();

        if ($conflicts) {
            $connection->rollbackTransaction();
            return ReservationResult::conflict();
        }

        $reservationId = ReservationTable::add([
            'RESOURCE_ID' => $resourceId,
            'USER_ID'     => $userId,
            'DATE_FROM'   => $from,
            'DATE_TO'     => $to,
            'STATUS'      => 'pending',
        ])->getId();

        $connection->commitTransaction();
        return ReservationResult::success($reservationId);

    } catch (\Throwable $e) {
        $connection->rollbackTransaction();
        throw $e;
    }
}

How to Check Resource Availability Step by Step

1. Get the list of resources via ResourceTable::getList().
2. Call the checkAvailability($resourceId, $dateFrom, $dateTo) method.
3. If it returns true — the slot is free; otherwise, it is occupied.

Why Is a Custom Booking Module Better than Off-the-Shelf Solutions?

Off-the-shelf Bitrix modules often lack flexibility in pricing and do not integrate with 1C. A custom module is tailored to a specific company's business processes. Here's a comparison:

Module Development Deliverables (What's Included)

• API and module configuration documentation.
• Source code with comments.
• Integration with payment systems (YooKassa, Sber) and 1C.
• Admin interface for resource management.
• Staff training (2 hours online).
• 30-day warranty support.
• Deployment assistance and server setup.

Functional Capabilities

Date Picker Widget

On the frontend, an interactive calendar. Implemented via flatpickr or a custom component. Booked dates are fetched via AJAX request:

GET /bitrix/components/vendor/booking.calendar/ajax.php
    ?resource_id=12&month=2026-06

→ {"available": ["2026-06-01","2026-06-03",...], "booked": ["2026-06-02","2026-06-05",...]}

Data is cached via \Bitrix\Main\Data\Cache for 5 minutes. On booking change, the cache is invalidated via the tag booking_resource_{id}.

Pricing

Price is calculated according to rules:

• Base rate per period (day/hour) from b_vendor_booking_resource.
• Seasonal surcharges (high season, holidays) from b_vendor_booking_price_rule.
• Discounts for long rental (7+ days — minus 10%).
• Minimum prepayment percentage.

$calculator = new PriceCalculator($resource);
$result = $calculator->calculate($dateFrom, $dateTo);
// → ['total' => 15000, 'prepayment' => 3000, 'discount' => 1500, 'nights' => 3]

Payment and Order Linking

After booking confirmation, an order is created in b_sale_order for the prepayment amount (or full cost). The booking is linked to the order via reservation.order_id. Upon successful payment, the booking status changes from pending to confirmed. On cancellation of a paid order, the booking status becomes cancelled and the slot is released.

Administration and Notifications

Admin Interface

The admin section includes:

• Resource list with settings.
• Visual timeline view with daily bookings.
• Manual booking creation form (for phone requests).
• Date blocking for maintenance.
• Resource utilization report.

The timeline view is built via a JS library (FullCalendar or dhtmlxScheduler), data via the module's REST endpoint.

Notifications

• To the user upon booking creation (confirmation with details).
• To the user upon manager confirmation.
• To the admin on new booking.
• Reminder N days before start (via agent).

All notifications go through standard \Bitrix\Main\Mail\Event::send() with event templates in the main module.

Development Process and Timeline

Total: 14 working days. For hotels with different room categories and channel manager management, a separate estimate is provided.

How to Order Module Development?

1. Submit a request for a consultation — we evaluate your project free of charge.
2. We analyze requirements and prepare a technical specification.
3. We develop the module in 14 days with regular demos.
4. We test, deploy on your server, and train staff.

Why Choose Us?

We have been developing Bitrix modules for 5+ years, completed 30+ booking projects (hotels, rentals, coworking spaces). We use only proven practices: tagged caching, atomic transactions, integration with 1C and payment gateways. Our module processes booking requests in an average of 50 ms — 5 times faster than typical solutions based on file caching. Clients save up to 40% on operational costs due to reduced overbooking.

Get a consultation for your project. Contact us for a free estimate.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.