Channel Manager — the Main Technical Puzzle of a Hotel Website
A guest books through your site, the room must be blocked on Booking.com, Ostrovok, and in the PMS. Under the hood: two-way synchronization via Travelline or Bnovo API, handling of conflicts (two bookings in one second on different channels), seasonal pricing with dozens of rate plans. We build such solutions on 1C-Bitrix for hotels, hostels, and apartments. Order hotel website development — get an audit of your current booking channel and a roadmap to direct bookings. Contact us to discuss your project.
Why Do Hotels Lose Significant Revenue on OTA Commissions?
Booking.com charges a commission, Ostrovok as well. A hotel with 40 rooms and 70% occupancy pays about $60,000–$80,000 to aggregators each year. A custom Booking Engine on Bitrix solves three tasks:
- Direct bookings without commissions — even a 10% shift in booking flow recovers the site cost within 2–3 months.
- Best Rate Guarantee — a lower price than on aggregators encourages direct booking.
- Own guest database (aggregators do not share emails) and upselling: transfers, SPA, restaurant.
Example: An urban hotel with 40 rooms increased direct bookings from 15% to 40% within a quarter after implementing the engine. Overbooking dropped to zero. The payback period was under 6 months.
How Does a Booking Engine Work Under the Hood?
The booking module is not a "leave a request" form but an engine with business logic. A Booking Engine pays off far faster than paying aggregator commissions.
Search and Availability
The guest enters dates and category — sees real available rooms. Behind the scenes: an availability table in the info block with type booking_availability, date overlap check via SQL BETWEEN, minimum stay and check-in restrictions. We optimize queries with composite indexes to keep response time under 200 ms even for 50 room types.
Pricing
Seasonal pricing is the most painful part. We implement it via info block property PRICE_CALENDAR with prices per date, surcharges for weekends and holidays, discounts for long stays, corporate rates via promo code. The calculator recalculates on the fly using Bitrix\Main\Type\Date and custom agents that update cached prices every hour.
Multi-Room Booking
A family books two rooms in one request — without re-entering dates. We implement it via sale.basket with custom basket item properties that store room IDs and check-in/out dates. The basket validation checks availability for each room simultaneously.
What Additional Services and Payment Options Are Supported?
Transfers, breakfast, parking — added to the booking as linked products tied to dates. Payment: full prepayment, deposit (first night), or card holding with receipt generation according to Federal Law 54-FZ via sale.cashbox. We integrate with YooKassa, Sber, and other acquirers. The fiscalization process is automated: every successful payment triggers a receipt to OFD. No manual intervention needed.
How Does a Channel Manager Solve Overbooking?
Channel Manager — two-way synchronization via aggregator APIs. Travelline, Bnovo, Wubook are connected through their protocols:
- Booking on the site → room blocked on Booking, Ostrovok, Yandex.Travel.
- Booking on OTA → room blocked on the site.
- Price change → update on all channels.
Hurdle: Travelline API works via XML with a delay of up to 30 seconds. On peak dates we implement double-checking — before confirming a booking, we recheck availability via the PMS inventory. In a project for a chain of three hotels, this eliminated all overbooking in high season. The system processed over 8,000 bookings without a single conflict.
PMS Integration
Property Management System — the hotel's brain. We integrate via:
- Synchronization of room inventory and statuses (available, occupied, cleaning).
- Automatic creation of booking in PMS upon online order via webhook.
- Retrieval of statuses (confirmed, checked in, checked out) for guest digital profile.
The integration is based on REST API. We handle error states (e.g., PMS timeout) with queued retry logic and manual fallback.
Guest Digital Profile and Bitrix24 CRM — Loyalty Ecosystem
The guest profile is not just "order history." History of stays, loyalty program with points and statuses, saved preferences (high floor, pillow type) are stored in UF_* fields. A returning guest appreciates being remembered.
CRM based on Bitrix24 complements PMS. A guest card with spent amount, preferences, automated robot chains:
- Pre-arrival (3 days before check-in) — email with information, transfer offer.
- Check-out +1 day — thank you, review request.
- Check-out +30 days — personalized repeat offer (e.g., "Welcome back, 10% discount").
SEO and Mobile Version: Competing with Booking
Booking dominates organic search. The key to success is long-tail and local queries:
- Local SEO — optimization for "hotel in downtown with pool."
- Schema markup
Hotel,LodgingBusiness,Offerwith prices — rich snippets can increase CTR by 20–30%. - Google Hotel Ads — feed via Google Hotel Center, prices alongside OTAs.
- Content with guides and attractions.
Mobile version — the majority of bookings. Form in 3–4 steps, native date picker, autofill for returning guests, PWA with push notifications. Map integration — route to hotel in one tap.
Common Mistakes in Hotel Website Development
- Ignoring caching (
BX_COMPOSITE_CACHE) — booking pages load very slowly, causing a 30% bounce rate. - Not accounting for time zones — guests from other regions see incorrect check-in time, leading to confusion and cancellations.
- Single-table availability model without indexes — SQL queries on many rooms take seconds instead of milliseconds.
Fixing each mistake typically saves the hotel a significant portion of lost bookings — up to 15–20% recovery.
What's Included in the Deliverables
| Deliverable | Description |
|---|---|
| Technical specification | Detailed business process descriptions, integration schemes |
| Design prototypes | Wireframes for booking flow, admin panel |
| Source code | Git repository with custom modules, PHP 8.1+, HL blocks, migrations |
| API documentation | Endpoints, authentication, error handling |
| Test credentials | Access to test environment, error logs |
| Training | Video instructions for staff, access handover |
| Post-launch support | 30 days of bug fixes and minor adjustments |
Our Experience and Company Metrics
Over 12 years of building hotel websites on 1C-Bitrix. Completed 80+ projects for hotels, hostels, and apartment owners. Our team holds official 1C-Bitrix certifications. We have successfully integrated with Travelline, Bnovo, YooKassa, and major OTAs. Contact us to get a portfolio of similar projects.
Process Workflow
| Stage | Documentation and Artifacts |
|---|---|
| Analytics | Technical specification with business process descriptions, integration schemes |
| Design | Screen prototypes, database architecture, flow diagrams |
| Development | Source code in Git (Bitrix Framework + custom modules, PHP 8.1+, HL blocks) |
| Integration | API documentation, test credentials, error logs |
| Testing | Load testing (hundreds of parallel bookings), regression testing |
| Deployment and Training | Launch, video instructions, access handover |
Development Timelines
| Project Type | Timeline |
|---|---|
| Hotel website (without booking) | 2–3 weeks |
| Website with Booking Engine | 2–3 months |
| Full platform (booking + PMS + Channel Manager) | 3–5 months |
| Hotel chain (multisite + unified CRM) | 4–6 months |
The cost is calculated individually based on your requirements, room count, integration complexity. Contact us for a detailed estimate. Hotel website development on 1C-Bitrix is an investment in direct sales that pays off quickly — typically within 3–6 months.







