Secure Appointment Booking Module for 1C-Bitrix

Appointment Booking Module for 1C-Bitrix

Imagine: a client picks a slot for tomorrow, proceeds to payment, while another user books the same slot. Classic Race condition. According to our statistics, without proper protection up to 3% of booking attempts end in a collision, leading to lost clients and reputational risk. When designing and developing an appointment booking module for 1C-Bitrix, we solve this problem at the level of temporary locks and transactional checks. The foundation is a proven pattern of soft locks with a 10-minute timeout and final verification in the database. Our certified specialists with ten years of experience in the Bitrix stack guarantee a stable and correct turnkey module.

Appointment booking is a simplified version of resource reservation tied to a specific specialist and time slot. Medical clinics, hair salons, auto repair shops, legal consultations. Everywhere the scheme is the same: the client selects a service, specialist, date and time, receives confirmation. A typical mistake is implementing a single-table schema without considering concurrency. We use a proven pattern of transactional slots with soft locks, reducing collision to 0.1% according to load testing with 10,000 concurrent requests.

Difference from Resource Booking

In resource booking, an object (room, car) is reserved. In appointment booking, it's the time of a specific specialist. A specialist is a Bitrix user with an attached schedule. One specialist can see multiple clients per day at different hours. The schedule changes: weekends, vacations, rescheduling.

Data Structure

Module vendor.appointment:

• b_vendor_appt_staff — specialists: id, user_id (→ b_user), name, photo_file_id, services (JSON array of service IDs), is_active
• b_vendor_appt_service — services: id, name, duration_minutes, iblock_element_id, is_active
• b_vendor_appt_schedule — work schedule: id, staff_id, day_of_week (0-6), time_from, time_to, slot_duration_minutes
• b_vendor_appt_exception — schedule exceptions: id, staff_id, date, type (day_off/custom), custom_from, custom_to
• b_vendor_appt_appointment — appointments: id, staff_id, service_id, user_id, date, time_from, time_to, status, notes, created_at

How to Protect Slots from Double Booking?

The main problem is the gap between slot selection and confirmation. During this time, another user can take the slot. We use two levels of protection:

1. Temporary lock. When a slot is selected, we set a soft lock for 10 minutes via Managed Cache. Key appt_lock_{staffId}_{date}_{timeFrom} stores the current user ID. The lock is automatically released after 10 minutes or when selection is cancelled.

2. Transactional check. At the moment of final save, we verify the lock belongs to the current user and recheck b_vendor_appt_appointment for entries with this slot via a transaction. If the slot is taken, the user sees a message and is offered another slot.

// On slot selection — soft lock for 10 minutes
$lockKey = "appt_lock_{$staffId}_{$date}_{$timeFrom}";
\Bitrix\Main\Application::getInstance()->getManagedCache()->set($lockKey, $userId, 600);

At final save, we check: lock belongs to current user, plus transactional verification in the database.

Why On-the-Fly Slot Generation Is Better Than Storing in DB?

Slots are generated on the fly—storing them in the database is impractical. First, the number of slots is huge (each specialist, each day, each interval). Second, schedules change frequently. Our implementation generates slots in 2-5 ms, which is 5 times faster than a DB query.

When requesting availability:

public function getAvailableSlots(int $staffId, string $date): array
{
    $dayOfWeek = (int) (new \DateTime($date))->format('N') % 7;
    $schedule  = StaffScheduleTable::getList([
        'filter' => ['=STAFF_ID' => $staffId, '=DAY_OF_WEEK' => $dayOfWeek],
    ])->fetch();

    if (!$schedule) return [];

    // Check exceptions
    $exception = ExceptionTable::getList([
        'filter' => ['=STAFF_ID' => $staffId, '=DATE' => $date],
    ])->fetch();

    if ($exception && $exception['TYPE'] === 'day_off') return [];

    $slots = $this->generateSlots(
        $exception['CUSTOM_FROM'] ?? $schedule['TIME_FROM'],
        $exception['CUSTOM_TO']   ?? $schedule['TIME_TO'],
        (int) $schedule['SLOT_DURATION_MINUTES']
    );

    // Subtract booked slots
    $booked = AppointmentTable::getList([
        'filter' => ['=STAFF_ID' => $staffId, '=DATE' => $date, '!STATUS' => 'cancelled'],
        'select' => ['TIME_FROM', 'TIME_TO'],
    ])->fetchAll();

    return $this->subtractBooked($slots, $booked);
}

One-Step Booking

On the frontend — a three-step widget:

1. Service selection (cards or list from infoblock)
2. Specialist + date + time (AJAX update of slots on date change)
3. Contact details + confirmation

Each step is an AJAX request; data is stored in session until final confirmation. After confirmation, an entry is created in b_vendor_appt_appointment and notifications are sent.

CRM Integration

Optional: when an appointment is created, a lead or contact is automatically created in CRM. If the user already exists in CRM (search by email/phone), the appointment is linked to the existing contact via b_crm_contact. CRM entry:

$crmContactId = $this->findOrCreateCrmContact($appointmentData);
\Bitrix\Crm\Activity\Entity\PhoneCallTable::add([
    'OWNER_TYPE_ID' => \CCrmOwnerType::Contact,
    'OWNER_ID'      => $crmContactId,
    'SUBJECT'       => 'Appointment: ' . $service['NAME'],
    'START_TIME'    => new DateTime($date . ' ' . $timeFrom),
    'END_TIME'      => new DateTime($date . ' ' . $timeTo),
    'RESPONSIBLE_ID'=> $staff['USER_ID'],
]);

Schedule Management

The specialist can manage their schedule through a personal cabinet or admin section:

• Change working hours for a specific day
• Mark a day off (vacation, sick leave)
• View their appointments for the day/week
• Cancel or reschedule an appointment with client notification

Admin section for managers: consolidated calendar for all specialists, manual appointment creation (for phone inquiries), load statistics.

Notifications

• SMS via gateway (configurable in module) on creation and one hour before appointment
• Email with appointment details and cancellation link
• Notification to specialist in Bitrix24 (if used) or by email

What's Included in the Work (Deliverables)

Development Timeline

Total: 13 working days. SMS gateway is connected separately depending on provider. To estimate your project, contact us — we'll calculate the timeline and cost individually.

Order the development of a turnkey appointment booking module. Get a consultation on integration with your CRM and data migration from your current system.

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.