Turnkey Automotive Portal Development on 1C-Bitrix

A visitor lands on your auto portal, enters a VIN – and sees empty fields instead of an automatic specification lookup. The platform loses leads, dealers waste time. Developing an automotive portal on 1C-Bitrix solves this: we build a system where catalog, filter, VIN decoder, and comparison work as one mechanism. In 45–60 days, you get a turnkey platform that converts visitors into buyers.

A typical scenario: a portal with 50,000+ listings but a filter that only includes make and model without generation. A user selects "BMW 3 Series" and gets hundreds of offers, unable to distinguish an F30 from a G20. Without generation-based data structure, it’s chaos. Our experience – over 15 projects for auto markets – shows that a proper catalog architecture reduces car search time by 40%.

Car Catalog – Data Structure

An automotive catalog is not a single infoblock but a linked system of directories:

• Makes – infoblock directory (BMW, Toyota, Hyundai…)
• Models – infoblock linked to make (3 Series, Camry, Tucson…)
• Generations – linked to model with production years (F30, XV70, NX4…)
• Trims – set of options for a generation
• Listings – specific car for sale, linked to make/model/generation

Listing properties:

Make and model directories are imported from open databases (e.g., auto.ru API, CarQuery) and updated when new models are released.

How the Filter Works on an Auto Portal

The filter is the main navigation tool. The user sets parameters, and the portal instantly shows match counts. For portals with 50,000+ listings, 1C-Bitrix documentation recommends the facet index, but Elasticsearch is 10x faster for queries over 50,000 records – it provides aggregations (how many BMW/Toyota/Hyundai in the current selection) without loading MySQL.

Multi-level filter implementation:

• Dependent selects: picked make → loads models → picked model → loads generations. AJAX requests to server or preloaded JSON directory.
• Ranges: year (from–to), price (from–to), mileage (from–to), engine displacement.
• Checkboxes: body type, transmission, drive, color, fuel.
• Geo-filter: city or radius from a point.

Saved searches – an authorized user saves the filter and receives push/email when new listings appear.

Filter Comparison

Why a VIN Decoder Matters

VIN code is a 17-character identifier containing data about the manufacturer, model, year, and trim (Wikipedia). Integrating a VIN decoder solves three tasks:

1. Auto-fill listings – the seller enters the VIN, and the system automatically fills in make, model, year, body type, and engine. This reduces form filling time by 70% and cuts errors.
2. History check – integration with services (Avtoteka, Avtocod) shows the buyer number of owners, accidents, liens, and odometer readings from service records.
3. Listing verification – if VIN data does not match the entered data, the system notifies the moderator.

Integration is done via REST API of service providers. The result is cached in the infoblock element properties – no repeat requests needed.

How to Implement Car Comparison

Comparison is a must-have feature. The user adds 2–4 cars and sees a table with all characteristics side by side.

• The comparison list is stored in the session (for guests) or in the database (for authorized users).
• The display component is custom, based on bitrix:catalog.compare.list.
• Highlighting differences: if one car has automatic transmission and another manual – the cells are highlighted.
• Comparison with a baseline: the user selects a base variant, others are compared to it.

Dealer Cabinets

A dealer is not an ordinary user. They have their own set of tools:

• Bulk listing upload from XML/CSV (format compatible with DMS exports).
• Dealer showcase – a dedicated page with branding, car catalog, contacts, and a map.
• Statistics – listing views, calls, messages, conversion to contact.
• Manager management – multiple dealer employees with differentiated permissions.
• Promotion – paid services: priority in search results, banner on a model page, branded showcase.

Dealer authorization is done via extended registration with legal entity verification. After verification, they are assigned to the "Dealers" group with appropriate rights to infoblocks.

SEO for an Auto Portal

An auto portal generates landing pages from filter combinations:

• /cars/bmw/3-series/ – all BMW 3 Series
• /cars/bmw/3-series/202X/ – specific year
• /cars/minsk/suv/ – SUVs in Minsk

Each landing has its own title, description, and H1 generated from templates. These are not doorways – the pages contain real content (listings plus model description from the directory).

Microdata Vehicle and Car according to Schema.org: make, model, year, mileage, price, image. It improves search snippets.

Sitemap – dynamic, split into files by category (makes, models, cities). Updated with every publication/removal of a listing.

What’s Included in the Development Process

• Audit of current processes and integrations.
• Designing catalog and filter architecture.
• Developing and configuring infoblocks, HL blocks, and user-defined fields.
• Integrating VIN decoder and history check services.
• Implementing dealer cabinets (bulk upload, statistics, management).
• Configuring tagged caching to reduce load.
• SEO optimization: microdata, dynamic sitemaps, meta-tag templates.
• Testing, staff training, and documentation handover.
• 6-month warranty support.

Additionally, we can integrate payment systems (YooKassa, Sber), set up Bitrix24 business processes for listing moderation, or parse data from external catalogs.

Case in point: On a project with 80,000 listings, we replaced the stock facet index with Elasticsearch. Filter query time dropped from 4 seconds to 0.2 seconds, and server load decreased by 70%. The client saw a 30% increase in user engagement within the first month. Total project cost ranged from $25,000 to $45,000, delivering a 300% ROI within six months.

Contact us to discuss your project. Order automotive portal development – get a ready platform that generates leads.

How a corporate portal on Bitrix24 solves the problem of information chaos?

Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.

We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).

What does the portal offer in daily work and why is it better than messengers?

In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.

Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.

Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.

Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.

HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.

Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.

Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.

How does integration with 1C and Active Directory accelerate HR management?

Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.

Types of corporate portals and key integrations

Additional integrations that deliver real value:

• Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
• IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
• Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
• EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.

Security and compliance with Federal Law 152‑FZ

The portal contains personal data, financial reports, strategic plans. We guarantee protection:

• role model via CGroup and section‑level permissions;
• two‑factor authentication (OTP, Yandex.Key, SMS);
• audit of all actions (b_event_log);
• TLS encryption for transmission and disk encryption;
• full compliance with Federal Law No. 152‑FZ "On Personal Data".

How is implementation carried out? Step‑by‑step plan

1. Audit — we record current processes, measure time losses.
2. Design — choose portal type, plan integrations.
3. Implementation — configure business processes, permissions, interface.
4. Test — pilot group tests scenarios, we fix issues.
5. Launch — connect all employees, train, hand over documentation.

What you receive after implementation

• Project documentation: architecture, integration scheme, business process diagrams.
• Configured portal with all integrations (1C, AD, telephony, EDI).
• Business process descriptions and instructions for administrators and users.
• 30 days of technical support after launch.
• Access to our knowledge base and migration scripts.

Post‑launch support: how to prevent the portal from becoming obsolete

After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.

Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.

Order a turnkey corporate portal implementation

Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.