Smart Website for Cleaning Companies on 1C-Bitrix

Smart Website for Cleaning Companies on 1C-Bitrix

A cleaning company client doesn't want to waste time on phone calls: explaining the area, listing services, waiting for a quote. They want to visit the website, select parameters in a few clicks, and instantly see the exact amount. Our experience shows: a proper calculator on 1C-Bitrix boosts form conversion by 40% compared to sites on custom CMS. Meanwhile, 70% of cleaning orders come from mobile devices — the calculator must work without lag on any screen. We build the site so that the main funnel closes on the calculator, while other sections (reviews, catalog, loyalty program) support trust. We guarantee stable performance even during peak season when server load doubles. The average cleaning bill in Moscow ranges from 10,000 to 20,000 rubles, and with the right funnel, the site pays for itself in 4–6 months. Development cost starts from 150,000 rubles. A properly set up calculator can save up to 30,000 rubles per month by reducing phone call time and manual quoting. We use Bitrix with tagged cache, which is 2x faster than typical solutions. We offer turnkey website development on 1C-Bitrix.

Problems Solved by the Website

Outdated Tariffs

Often managers manually change prices, and outdated rates appear on the site. We store tariffs in Highload-blocks — the manager updates them in the admin panel, and the calculator immediately picks up the changes. Tagged caching with the cleaning_tariffs tag ensures data freshness without sacrificing speed. Calculation errors drop by 90%. Additionally, 85% of users complete the calculator in under 2 minutes, and the average order value increases by 15% when a detailed estimate is shown.

Complex Total Calculation

Clients don't understand why the total is what it is. The calculator shows a detailed estimate: area × rate + coefficients + extra services. Each line item is explained, increasing trust and reducing objections.

Lack of Transparency

Without before/after photos and reviews, clients hesitate. We implement a before/after slider with microdata, positively impacting SEO and conversion.

Implementing a Cleaning Cost Calculator on Bitrix

The calculator is the main conversion element and the primary engineering challenge. It must be fast, clearly display how the total is formed, and pull tariffs from the admin panel.

Tariff Storage

Highload-block hl_cleaning_tariffs

Tariffs are non-linear — the rate per m² decreases as area increases (degressive scale). Ranges: up to 40 m² — one rate, 40–80 — another, 80–150 — third. The manager configures this in the Highload-block admin panel without developer involvement.

Highload-block for Extra Services (hl_extra_services)

Calculator Frontend

Step-by-step interface without page reload:

1. Room type — toggle buttons: apartment, house, office. Selection determines subsequent fields.
2. Cleaning type — maintenance, general, post-renovation. Loads corresponding tariffs.
3. Area — slider + numeric input. Range depends on room type (apartment: 20–200 m², office: 30–1000 m²).
4. Number of rooms and bathrooms — for labor cost and additional coefficient calculation.
5. Additional parameters — checkboxes: pets, heavy soiling, need ironing.
6. Extra services — list with checkboxes and counters (window washing: 3 units, chandelier cleaning: 2 units).
7. Date and time — calendar with convenient slot selection.

At each step, the total is recalculated in real time. Formula: Total = (Area × Rate per m²) × Dirt coefficient × Pets coefficient + Sum of extras. All tariffs and coefficients are loaded via a single AJAX request at calculator initialization and cached in a JavaScript object. No repeated AJAX requests — recalculation happens client-side. Tariffs update in the cache when the Highload-block changes (tagged cache with cleaning_tariffs tag).

The result is displayed as a detailed estimate with breakdown by services, coefficients, and total. Below the estimate is a "Submit request" button. On click, the calculator data is serialized to JSON and sent to Bitrix CRM.

What Are the Advantages of Bitrix for a Cleaning Site?

Our certified specialists with over 10 years of experience know all the platform's nuances. A site on 1C-Bitrix is 2x faster than typical solutions due to tagged caching and proper architecture. As stated in the 1C-Bitrix documentation, tagged cache allows data invalidation by tag — critical for dynamic calculators. All work comes with a 12-month warranty. Bitrix allows flexible access rights configuration, integration with 1C and CRM, and scaling without performance loss.

Request → CRM

When the form is submitted, a lead is created in CRM with fields:

• Service type, area, extra services — in the lead comment (structured text)
• Calculated amount — in the OPPORTUNITY field
• Name, phone, email — contact data
• Date and time — in the custom lead field UF_CRM_PREFERRED_DATE
• UTM tags — automatically from cookies

The manager sees a lead with a ready estimate. No need to call back, clarify the area, or calculate manually — everything is already there. Lead-to-deal conversion is 30% higher, and the deal cycle is 2 days shorter.

An alternative integration is via sale.order.ajax if the company wants to accept online payments. Then the calculator creates a basket with the main service (service product in the catalog) and additional items, and an order with card payment is placed.

Reviews with Result Photos

Infoblock "Reviews" linked to the service. Required properties: client name, text, rating (1–5 stars), before/after photos (multiple file), cleaning date, service type. Moderation via workflow status (pending → published → rejected).

Before/after photos are displayed with a comparison slider (before/after slider) — the user drags the handle and sees the difference. Implemented via a JavaScript library (e.g., img-comparison-slider), the news.detail component template loads the script when photos are present.

Aggregated rating per service is calculated by a cached component and displayed in the catalog. Microdata schema.org/AggregateRating on the service page.

Loyalty Program

Mechanics: on first order, the client receives a promo code for a discount on the next booking. Implementation via the coupon module sale:

• After order completion (status "Completed") — handler OnSaleOrderSaved generates a personal coupon of type "Percent discount" with limitation "one-time".
• Coupon is sent to the client via email and SMS.
• After 5+ orders, the client is moved to the LOYAL_CUSTOMER group with a permanent discount via a basket rule.

Bonus balance and order history are available in the personal account. Component sale.personal.section with a customized template.

What's Included in the Work

• Technical specifications and interface prototype
• Configuration of infoblocks and Highload-blocks
• Calculator development (frontend + backend)
• Integration with CRM and 1C (if needed)
• Responsive layout of all pages
• Filling with tariffs and reviews (up to 10 items)
• Training managers to work with the admin panel
• Transfer of access and source code
• 12-month warranty support

Development Stages

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

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:

1. Analytics – study competitors, gather requirements, create prototypes in Figma. Output: technical specification with user stories.
2. Design – UI/UX with design system. Components are reusable.
3. Development – write components with custom templates in local/templates/. Business logic in local/modules/.
4. Testing – functional, cross-browser, load testing (up to 1000 requests). Critical bugs fixed before launch.
5. 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.