Integrate 1C-Bitrix with Dikidi Online Booking

A beauty salon or clinic uses Dikidi for appointments — clients book via the app, stylists see the schedule. The Bitrix website lives separately: service catalog, prices, promotions, but booking is only possible by phone or via the Dikidi widget. Integration is needed so that the site and booking system work as a single unit: up-to-date schedule on the site, booking without leaving for an external service, client data landing in CRM. Our team has completed over 50 integrations with external services for Bitrix — experience allows us to anticipate all nuances and guarantee stable data exchange.

Typical scenario: a client wants to book a haircut but only sees prices on the site. They have to either call or switch to Dikidi. On a call, the admin spends 5 minutes manually checking slots. Switching to Dikidi makes the user leave the site, and booking data doesn't reach CRM. Integration solves both problems: a booking form right on the site, synchronized schedule, client data automatically saved in Bitrix24.

We have integrated Dikidi with Bitrix websites over 15 times. In this article — the architecture of the solution, pitfalls, and what the business gets.

What is the Dikidi API?

Dikidi provides a REST API (documentation available via support) that allows management of services, staff, schedule, and bookings. Main endpoints:

• GET /api/v2/company/{id}/services — list of services with prices and duration
• GET /api/v2/company/{id}/masters — masters with schedule
• GET /api/v2/company/{id}/schedule — available slots for a specific master and service on a given date
• POST /api/v2/company/{id}/booking — create appointment (master, service, date, time, client data)
• GET /api/v2/company/{id}/booking/{id} — booking status

Authorization is via API key in the Authorization header. The key is issued when a plan with API access is activated. Restriction: not all Dikidi plans include API. On the basic plan, only the widget (iframe) is available. API is on 'Business' plan and above. Clarify before starting work.

Which integration option to choose?

If you need a quick solution — just embed the Dikidi iframe widget. The embed code is one line in the component template or page editor:

<iframe src="https://dikidi.net/widget/{company_id}" width="100%" height="700" title="Embedded content from dikidi.net"></iframe>

This works in 10 minutes, but you lose UX control, the design is external, data doesn't reach CRM, and SEO value is zero. The widget is suitable as a temporary solution, but for a full-fledged business, a custom API integration is better. It gives full control over appearance, data transfer to CRM, and analytics capabilities.

Why choose custom integration?

Custom integration turns Dikidi into a schedule backend, and the booking form becomes part of the site. You control every user step, the design of each step, and can add your own fields (promo codes, booking notes). Appointment data syncs with Bitrix24 CRM, allowing managers to see the full client history, not just website bookings. Such integration pays off quickly: reducing slot selection time by 80% and eliminating double bookings.

How does custom integration with Dikidi work?

Architecture:

1. A daily cron script (CAgent) fetches the list of services and masters from Dikidi API and stores them in a highload block or infoblock. This ensures that the service catalog pages work without requesting Dikidi API on every hit.
2. Custom component custom:dikidi.booking on the service page:
   • Step 1: select master (data from HL-block)
   • Step 2: select date and time — AJAX request to Dikidi API /schedule (real-time; slots cannot be cached as they change every minute)
   • Step 3: client contact details
   • Step 4: confirmation — POST /booking
3. Response handling. On successful booking, Dikidi returns a booking_id. We save it in the HL-block DikidiBooking linked to the Bitrix user (if authenticated) and to the CRM record.

What does synchronization with Bitrix24 CRM provide?

Booking through the site creates a lead or deal in CRM:

• On booking confirmation — REST request crm.lead.add or crm.deal.add with data: client name, phone, service, master, date/time
• Lead source — 'Website booking (Dikidi)' (add to source dictionary via crm.status.add)
• In the deal UF field, we store the Dikidi booking_id for cross-reference

Reverse synchronization: if a manager cancels a deal in CRM, a webhook calls DELETE /booking/{id} on Dikidi API. Implemented via a CRM robot on the 'Cancelled' stage.

Webhook from Dikidi: how not to lose a single booking

Dikidi supports outgoing event notifications (if configured): new booking, cancellation, change. The endpoint on the Bitrix side is a PHP script at /local/tools/dikidi_webhook.php, which:

• Verifies request signature
• Creates or updates the record in the HL-block
• Creates a lead in CRM (if the booking was made through the Dikidi app, not the website)

This covers the reverse scenario: client booked via the Dikidi app — the site and CRM know about it.

What's included in the work

Implementation timelines

Dikidi is a closed ecosystem, and integration quality depends on API availability on your plan. We will assess your project for free — contact us for a consultation. Our over 8 years of experience in Bitrix development guarantees that the integration will work stably and without surprises. Order integration today — get a working prototype within a week.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.