Bitrix24 for Car Dealers: Funnels, Integrations, Robots

Setting up Bitrix24 for a car dealership solves the problem of losing leads from multiple sources: calls, website, Auto.ru, Avito, messengers. Without a single pipeline, applications get lost — the manager didn't call back, the lead went cold, the customer went to a competitor. Out of the box, Bitrix24 is configured for universal business, but without customization the system is useless: no fields for VIN, inappropriate stages, no integration with auto portals. We configure pipelines, integrations, and robots so that every application is processed on time. Average savings on operational costs are substantial, with return on investment within 2–3 months. Our configuration processes leads 1.7 times faster than the standard one — a 40% reduction in time confirmed by results from 50+ projects. We guarantee this result.

What funnels does a car dealer need?

At least two funnels: selling new cars and Trade-in/used cars. Stages for selling a new car:

New lead → Invitation to showroom → Test drive scheduled → Test drive completed → CP issued → Credit/installment → Contract signed → Car delivered

Each stage triggers an auto-action: on transition to "Test drive scheduled" — a task for the manager, on transition to "Credit" — a task to contact the bank, on delivery — an email to the customer asking for feedback.

How to integrate auto portals with Bitrix24?

Comparison of integration methods:

More details in the official Bitrix24 REST API documentation.

Car deal card

The standard deal card lacks fields for VIN, make, model, color, trim level. We add custom deal fields: UF_CAR_BRAND, UF_CAR_MODEL, UF_CAR_VIN, UF_CAR_YEAR, UF_CAR_COLOR, UF_COMPLECTATION, UF_TRADE_IN_CAR. For make/model fields — type "List" with populated values. This allows automatic filling of data from portal applications and building reports on sales of specific models.

How to set up integration with Auto.ru: step-by-step instructions

1. Install the connector from Bitrix24 Marketplace: "Auto.ru — CRM integration".
2. Authorize on the Auto.ru portal via API key (issued in the dealer's personal account).
3. Select the pipeline and stage for new leads (e.g., "New lead").
4. Configure field mapping: VIN → UF_CAR_VIN, make → UF_CAR_BRAND, etc.
5. Test: create a test application on Auto.ru — it should appear in CRM with fields filled.

If the connector doesn't work (rare case), use an email parser: set up an IMAP mailbox where notifications from Auto.ru arrive, and the parser creates leads via REST API.

Robots and automation

Key robots for a car dealer:

• Reminder about test drive booking 2 hours before (SMS + task for manager).
• If a deal stays in "Invitation to showroom" stage for more than 3 days without activity — task for the supervisor.
• After car delivery, after 7 days — auto call with NPS assessment.
• On transition to "Contract signed" — create a task for document preparation.

Automation reduces manual processing time by 40%, yielding significant savings per year for a department of 5 managers. Our certified engineers configure robots considering working hours and priorities.

Stages of Bitrix24 setup for a car dealer

Get a consultation with an engineer on Bitrix24 setup for your car dealership.

Timelines and what's included in the setup

Basic setup of pipelines, fields, robots, and integration of 3-4 sources takes from 2 to 3 weeks. Included:

• Design of pipelines and stages according to business processes
• Addition of custom fields and lists
• Configuration of robots and business processes
• Integration of telephony, website, auto portals, messengers
• Testing and training of employees
• Configuration documentation

Our team has over 10 years of experience and has delivered 50+ projects for car dealerships. Submit a request for Bitrix24 setup for your car dealership — get a consultation with an engineer and a commercial proposal within a day. Contact us to discuss the details of your project.

B2B Portal Development on 1C-Bitrix

A dealer in Krasnoyarsk enters 50 SKUs, needs an instant invoice with his own price, credit limit, and delivery from the nearest warehouse. A retail catalog won’t cut it. We build such portals on 1C-Bitrix — with personalized price matrices, dealer cabinets, and real-time 1C integration. Over 50 B2B portals launched, 12-month warranty, certified 1C-Bitrix specialists with 10+ years in development. Submit a request for a free audit of your current pricing system — we will analyze your structure and propose a tailored architecture.

How does pricing work in a B2B portal?

Retail has one price. B2B has a matrix: price types in b_catalog_price multiplied by user groups, cumulative discounts, currency conversions, contractual conditions. A mistake here sinks the project.

Price types and user groups. Bitrix sets types via CCatalogGroup. Standard set: retail, small wholesale, wholesale, dealer, distributor. Each counterparty belongs to a user group, the group to a price type. Reality is more complex: one dealer may see wholesale prices for electronics and distributor prices for accessories. That requires custom logic in the OnSaleBasketItemBeforePriceSave handler.

Discounts — progressive by volume (from 100 pieces → minus 5%, from 500 → minus 12%), cumulative over a period, seasonal, category-based. Combined through priorities in b_sale_discount. With 20+ rules, debugging becomes a quest.

Credit limits. The counterparty gets a shipping credit threshold. Current debt syncs from 1C via the register РасчетыСКонтрагентами (Settlements with Counterparties). Exceeding the limit blocks order placement.

Contract prices — the price list is tied to a specific contract: validity period, number, prolongation conditions. Expiration switches prices to base ones automatically. Implemented through order custom fields and the OnSaleComponentOrderProperties handler.

Currency — mandatory for foreign trade. Conversion at the Central Bank rate (CCurrencyRates::ConvertCurrency()) or a fixed contract rate.

Compare CommerceML and REST for price sync: CommerceML is simpler but 4x slower on catalogs over 10,000 items, and it can’t handle credit limits. REST API via 1C HTTP service is 3x faster and fully flexible but requires 1C-side modifications. According to the 1C-Bitrix Developer's Guide, real-time sync of directories and balances is critical for B2B portals.

What does the dealer cabinet include?

• Orders — full history with filtering by statuses, dates, amounts. Repeat previous order in one click — saves hours for regular purchases.
• Finances — balance of mutual settlements, reconciliation statement, payment history. No more waiting three days for accounting — data available instantly, pulled from 1C via REST or CommerceML.
• Documents — invoices, waybills, sales invoices, UPD, certificates. Generated in 1C, PDF pushed to the portal via integration. One-click download.
• Dealer employee management — admin creates accounts with role permissions: purchasing manager places orders, accountant sees only finances, director sees the big picture. Extended standard Bitrix user groups.

Quick order: SKU + quantity = invoice

A B2B client doesn’t browse beautiful cards. They need a form: SKU, quantity, next line.

• Quick order form — auto-suggest of name and price when entering SKU. AJAX search by b_iblock_element.XML_ID or PROPERTY_ARTICLE. 50 items in 3 minutes.
• Import from Excel/CSV — client exports from their system, uploads to the portal. Auto-matching of SKUs, availability check, order generation. Parsing via PHPExcel or PhpSpreadsheet.
• Basket with full information — weight, volume, number of packages, estimated delivery cost before checkout.

Why is 1C integration critical for a B2B portal?

Without up-to-date data from 1C, the portal is useless. Manager changed the price of nails — in 15 minutes a dealer in Krasnoyarsk sees the new price.

We often use a hybrid: CommerceML for catalog, REST for prices, stocks, and documents.

EDI: legally significant paperless exchange

For large B2B projects:

• Providers — Kontur.Diadoc, SBIS, Kaluga Astral. Invoices, certificates, waybills in electronic form with legal force.
• CEP — qualified electronic signature. The counterparty signs right in the cabinet.
• Roaming between operators — without it, half of partners with a different EDI operator are left out.

Multi-branch operation

• Regional warehouses — client sees stock of the nearest warehouse and can choose the shipping one. Product available in Novosibirsk but not in Moscow → portal shows both options with different lead times.
• Automatic manager assignment — dealer from Krasnodar works with Ivan, from Yekaterinburg with Marina. Based on UF_REGION in the counterparty card.
• Local conditions — minimum order amount, delivery terms, lead times — differ by region.

B2B Portal Development Process

B2B portal development includes five stages.

What is included in the work

• Complete project documentation (terms of reference, architecture diagram, integration protocols)
• Server environment setup and deployment (On-Premise or cloud)
• Migration of all user data and configurations
• Portal administrator training (2 online sessions)
• Warranty support for 12 months with response within 4 hours

After launch — technical support and development. A B2B portal is a living system that evolves with the business.

Average time savings for a manager on order processing — up to 20 hours per week, which translates to approximately $15,000 annual savings per dealer. A self-built portal typically takes 6 months to develop, while a Bitrix-based solution is ready in 2 months.

Typical mistakes to avoid at the start

1. Verify price types and user groups before going live.
2. Keep discount rules to a minimum (3–4) — 20+ rules cause debugging nightmares.
3. Test 1C integration on real data during pilot.
4. Grant dealer access only after load testing with 50 concurrent users.

Contact us to discuss your project — we will prepare a preliminary estimate and propose the optimal solution. Get your free audit of pricing mechanics today.