A car wash owner faces two key problems: different pricing by car class and the need for online booking without overlaps. The customer wants to find the price for their SUV and book a bay in 40 seconds, while managers must prevent double bookings. We develop websites on 1С-Bitrix that solve these tasks at the architecture level: we use SKU offers for services and Highload-blocks for slot distribution. We have completed over 50 projects for car washes, including chains with 12 bays.
Why 1С-Bitrix is suitable for a car wash website?
The platform provides ready-made modules for pricing and cart, and the flexibility of infoblocks and Highload-blocks allows adapting logic to any format. For example, pricing by car class is implemented through trade offers without hacks. And Highload-blocks for scheduling ensure fast queries even with 300+ appointments per day.
How to implement online booking without failures?
The key component is a Highload-block "Schedule" with fields: bay ID, date, time, status, client. Slot generation is done by an agent every night. Protection against double booking — transactional status check. After confirmation — SMS notification and a deal in CRM.
Comparison of scheduling implementation approaches
| Characteristic |
Standard infoblocks |
Highload-blocks |
| Write speed at 5000 rows |
2.3 sec |
0.4 sec |
| Transaction support |
No |
Yes |
| Ease of date query |
Requires filtering |
Indexed fields |
| Status model flexibility |
Limited |
UF_STATUS column |
Highload-blocks process requests 5-10 times faster than standard infoblocks for similar data volumes.
According to official 1С-Bitrix documentation, Highload-blocks are optimized for fast access to rows with a single-field filter (dev.1c-bitrix.ru).
How is the price formed for different car classes?
We use trade catalogs with SKU offers for each car class (sedan, SUV, minibus). For complex services, we use a "Composition" property of type element binding. This allows the manager to quickly change the price for a specific class without code edits. The customer sees the current cost in the cart.
What is included in car wash website development
- Technical specification: detailing functionality, integration descriptions, mockups of key pages.
- Prototyping: interactive prototype of booking and service catalog.
- Design concept: responsive design for mobile devices.
- Layout and programming: implementation on Bitrix Framework, custom scheduling components.
- Integrations: connecting 1С, payment systems, SMS services, CRM.
- Testing: functional and load testing.
- Staff training: instructions and video tutorials.
- Technical support: 3 months of warranty service.
Technical implementation details
Architecture of linking infoblocks and Highload-blocks
The service catalog is built on an infoblock with SKU offers. Each car class is a trade offer with its own price. For complex services, a "Composition" property of type element binding is used.
The schedule is a Highload-block with indexes on date and bay. An agent creates slots for 14 days ahead. During booking, UF_STATUS is checked via a transaction, guaranteeing uniqueness.
Work process
- Analytics — studying car wash business processes, gathering requirements.
- Design — database architecture, component selection.
- Implementation — development of infoblocks, highload-blocks, components.
- Integration — connecting 1С, payment systems, SMS.
- Testing — checking booking and pricing scenarios.
- Launch — data migration, agent setup, caching.
- Support — bug fixes, enhancements.
Development timeline
| Stage |
Duration |
| Analytics and specification |
from 3 days |
| Design |
from 2 days |
| Development |
from 10 days |
| Integration |
from 5 days |
| Testing |
from 3 days |
| Launch |
from 2 days |
Our track record
- Extensive experience in 1С-Bitrix development.
- Over 50 projects for car washes completed.
- Average project load: 3000 appointments per month without failures.
Savings and benefits
Implementing online booking reduces order processing time by 70%, saving the owner significant costs annually. Our clients save an average of 40% of their budget by using ready-made Bitrix modules instead of custom development. Get a consultation for your project — we will help calculate the budget and timeline. Order car wash website development today to start automation.
How to properly design infoblocks?
When developing a 1C-Bitrix website, we see dozens of projects where poor infoblock structure slows down the site. Typical scenario: the client asks for a "product catalog." The developer creates one infoblock catalog, puts 15 properties in it. Six months later – 40 properties, 8 of which are used only for one category. The filter lags, the b_iblock_element_property table grows to millions of rows, CIBlockElement::GetList runs for 3 seconds. Consequences – conversion drop, loss of customers, additional optimization costs. In one project after catalog refactoring, page generation time dropped from 4.2 to 0.8 seconds, and annual support costs were reduced by over $10,000 through eliminated redundant queries and agents.
Our approach: design infoblocks before writing a single line of code. Separate infoblocks for entities (products, categories, brands), dictionary properties via highload blocks, trade offers for SKUs. This builds performance for years. If you want a preliminary audit of your infoblock schema, contact us for a free review of common mistakes and recommendations.
Why 1C-Bitrix outperforms most CMS for business
The choice of CMS is dictated by business needs, not preferences. Native 1C exchange via catalog.import.1c provides two-way synchronization of products, prices, balances, and orders through CommerceML without third-party modules — five times faster than developing custom exchange on OpenCart or WordPress, saving hundreds of thousands of rubles. Proactive security module includes WAF, file integrity control, SQL injection protection, and two-factor authentication; it's certified for FSTEK requirements. Modular architecture lets you enable only needed modules — iblock, catalog, sale, search — reducing DB queries per hit. Regular patches close vulnerabilities faster than open-source projects (average CVE fix time two weeks). Official documentation is maintained on the vendor's site.
What highload blocks are and how they speed up the catalog
Highload blocks are an alternative to extended infoblock properties when the list of values can grow to thousands of entries. Typical example: manufacturers, countries, colors. If stored as list properties in an infoblock, each filter triggers a full scan of b_iblock_property_enum table. With HL-blocks, selection uses indexes – filter response time drops from 1–2 seconds to 50 ms. We use HLB component and custom queries via Bitrix\Highloadblock\DataManager. This is critical for catalogs with 100,000+ items.
From our practice: an online store with 500,000 items. Standard filter by brand took 4 seconds. The server couldn't handle 50 concurrent requests – pages crashed. We moved the brand directory to an HL-block, added tagged caching for 15 minutes, and set up an agent to clear cache on change. After optimization, filter time was 120 ms, average LCP was 1.8 seconds. The project runs stable without failures.
What integrations are critical for 1C-Bitrix stores
Each e‑commerce project requires reliable connections with payments, fiscalization, logistics, and CRM. We integrate YooKassa, CloudPayments, Tinkoff, Apple Pay, Google Pay for payments; ATOL and OrangeData for 54-FZ compliance via sale.cashbox; CDEK, Boxberry, PEC, Russian Post, Yandex.Delivery for logistics; Bitrix24, amoCRM, Roistat, Calltouch, Mindbox for analytics and CRM. All integrations are configured with proper error handling and fallback logic.
What's included in 1C-Bitrix website development
Each project includes a full set of documentation and artifacts to prevent knowledge loss after handover.
- Technical specification – user stories, infoblock diagrams, integration schemas.
- Source code in Git – with commit history, release tags, branching rules.
- Administrative documentation – description of custom components, deployment instructions, list of agents and events.
- Staff training – up to a 3-hour webinar: admin panel, order management, price settings. Recorded for later review.
- Access to staging during development – test before production deployment.
- Warranty support – bug fixes for 30 days after launch. Post-warranty support packages with SLA (response 2 hours, resolution 8 hours).
Our process and technologies
| Project type |
Timeline |
Complexity |
Key features |
| Corporate website |
from 1 month |
Medium |
Catalog, news, forms, CRM integration |
| Online store |
from 2 months |
High |
54-FZ, marketplaces, 1C exchange, SKU |
| B2B portal |
from 3 months |
Very high |
Personal prices, document flow, Bizproc |
| Landing page |
from 2 weeks |
Low |
LCP < 2s, composite cache, static |
| Multisite structure |
from 1.5 months |
High |
Separate content, shared catalog, hreflang |
Tech stack: mobile-first markup, tested on physical devices (iPhone, iPad, Android). Use BrowserStack for Safari on iOS. Performance goals: LCP < 2.5 s, FID < 100 ms, CLS < 0.1. Enable composite site (composite module), CDN, tagged caching, WebP/AVIF, lazy loading. SEO: Schema.org via JSON-LD, auto-generation of sitemap.xml via seo module, canonical and hreflang for multilingual versions. robots.txt blocks /bitrix/ from indexing. CI/CD: Git, auto-deploy via GitLab CI, staging. DB migrations: sprint.migration module with versioning.
Process:
-
Analytics – study competitors, gather requirements, create prototypes in Figma. Output: technical specification with user stories.
-
Design – UI/UX with design system. Components are reusable.
-
Development – write components with custom templates in
local/templates/. Business logic in local/modules/.
-
Testing – functional, cross-browser, load testing (up to 1000 requests). Critical bugs fixed before launch.
-
Launch – deploy to production, monitoring via UptimeRobot, alerts in Telegram. Fixes for first 48 hours.
Multilingual support and redesign
Full localization via language files lang/ and SITE_ID mechanism. hreflang for each version. Regional versions with different prices and content – IP detection (main.geo) or manual selection. Multidomain – unified management of multiple domains.
Redesign without losing rankings: performance audit (PageSpeed, WebPageTest), SEO (Screaming Frog). New template in local/templates/ with preserved URL structure. 301 redirects only if URL changes significantly. Kernel update, migration to D7 ORM, infoblock restructuring, migration via sprint.migration with Git.
Guarantee and support
We have been working with 1C-Bitrix for 12+ years, completed 500+ projects. Certified developers on staff. Fixed price in contract – no surprises. Warranty period covers code errors. After warranty, subscription packages with SLA (response time 2 hours, resolution 8 hours). 24/7 availability monitoring, alerts in Telegram. Get a consultation and preliminary estimate: contact us via the form on the website or chat – we'll respond within an hour. Order turnkey development – we'll design infoblocks, integrate 1C, and speed up the catalog. If you already have a site on another CMS, order a performance audit and migration to Bitrix.
