Development of Automotive Portal on 1C-Bitrix
A buyer goes to an auto portal, selects "BMW 3 Series, 2018–2022, gasoline, automatic" — and gets 800 results without ability to compare by real characteristics: trunk volume, city fuel consumption, maintenance cost. Has to open each listing, manually compare. An automotive portal that doesn't solve the selection problem is just a classifieds board with a make filter. A proper auto portal on 1C-Bitrix is built around a catalog with deep data structure, comparison tools, and industry service integrations.
Automobile Catalog — Data Structure
Automotive catalog is not one info block. It's a connected reference system:
- Makes — reference info block (BMW, Toyota, Hyundai...)
- Models — info block bound to make (3 Series, Camry, Tucson...)
- Generations — bound to model with release years (F30, XV70, NX4...)
- Trims — option set for generation
- Listings — specific car for sale, bound to make/model/generation
Listing Properties:
| Group | Properties |
|---|---|
| Main | Make, model, generation, year, mileage, price |
| Engine | Type (gasoline/diesel/hybrid/electric), volume, power |
| Transmission | Type (manual/auto/CVT/robot), drive |
| Body | Type (sedan/hatchback/SUV...), color, VIN |
| Condition | New/used, owners by title, accidents |
| Media | Photos (up to 30), video (YouTube link) |
| Seller | Individual / dealer, city, contacts |
Reference makes and models are imported from open databases (e.g., auto.ru API, CarQuery) and updated with new models.
Filtering and Search
Filter is the main navigation tool. User sets parameters, portal instantly shows match count.
Implementing Multi-Level Filter:
- Dependent lists: selected make → loaded models → selected model → loaded generations. AJAX to server or pre-loaded JSON reference
- Ranges: year (from-to), price (from-to), mileage (from-to), engine volume
- Checkboxes: body type, transmission, drive, color, fuel
- Geo-filter: city or radius from point
Facet Index accelerates filtering at large volumes. For portals with 50,000+ listings, Elasticsearch is additionally recommended — it provides aggregations (how many BMW/Toyota/Hyundai in current selection) without MySQL load.
Saved Searches. Authorized user saves filter and gets push/email when new listings appear.
VIN Decoder
VIN is a 17-character code containing info about manufacturer, model, production year, trim, and serial number. VIN decoder integration:
- On listing submission — seller enters VIN, system auto-fills make, model, year, body type, engine. Reduces errors, speeds up form
- History Check — integration with verification services (Avtoteka, Avtocod, Carfax). Buyer sees: owner count, accidents, liens, service mileage
- Listing Verification — if VIN data doesn't match listing info (e.g., year), system alerts moderator
Integration through REST API of provider services. Result cached in element properties — no re-request needed.
Comparison Tool
Comparison is mandatory for auto portal. User adds 2–4 cars and sees table comparison by all characteristics.
Implementation:
- Comparison list stored in session (for guests) or DB (for authorized)
- Display component — custom, based on
bitrix:catalog.compare.list - Highlight differences: if one has automatic and other manual — cells highlighted
- Compare to baseline: user selects base variant, others compared to it
Dealer Cabinets
Dealer is not a regular user. Has own tool set:
- Bulk Upload of listings from XML/CSV (format compatible with DMS export — dealer management system)
- Dealer Showcase — separate page with branding, car catalog, contacts, map
- Statistics — listing views, calls, messages, lead conversion
- Manager Management — multiple dealer employees with different rights (publish, edit, view stats)
- Promotion — paid services: priority in output, page make banner, showcase branding
Dealer authorization is through extended registration with legal entity verification. After verification — assigned to "Dealers" group with appropriate rights.
Automotive Portal SEO
Portal generates landing pages from filter combinations:
-
/cars/bmw/3-series/— all BMW 3 Series -
/cars/bmw/3-series/2020/— specific year -
/cars/minsk/suv/— SUVs in Minsk
Each landing has own title, description, H1 generated by template. Not doorway pages — real content (listings + model description from reference).
Structured Data Vehicle and Car per Schema.org: make, model, year, mileage, price, image. Improves snippets in search results.
Sitemap — dynamic, split by categories (makes, models, cities). Updated on each listing publish/remove.