Auto Dealer Portal Development: From Catalog to DMS

When building a portal for an auto dealer, we encounter typical pain points: managers spend hours manually updating prices and inventory, customers leave to competitors due to slow photo loading, and trade-in appraisals are done by eye. Our experience shows that a properly designed portal can increase test drive requests by 40% and cut lead processing time by two-thirds. Compared to sites without integration, prices update 50x faster, and conversion to leads increases 2-3x.

What Problems Does an Auto Dealer Portal Solve?

Disconnect between storefront and actual stock. Vehicle availability data often differs from what the customer sees. A portal with DMS integration synchronizes inventory in real time via REST API or CommerceML file exchange. Errors are virtually eliminated.

Low search conversion. A typical filter by make and price doesn't help customers choose among hundreds of units. We add filters by engine type, drivetrain, mileage, color, along with sorting by arrival date and distance to dealer. In one project, this solution boosted lead conversion by 2.3x compared to a standard catalog.

Cumbersome trade-in. A manager can take up to 30 minutes to appraise a vehicle. Implementing an online calculator with CarPrice API integration cuts this to a minute — the customer gets a preliminary price on the site immediately. Automation saves up to 200 manager hours per month, reducing operational costs by 15%.

How Is the Vehicle Catalog Structured?

The catalog consists of cards for new cars and used cars. For new cars, a configurator is available: the customer selects engine, transmission, color, and options — the system calculates the final price including discounts and promotions. For used cars, each card includes up to 80 photos, VIN, history report (CarFax or Avtokod), and technical specs: engine displacement and power, transmission type, fuel consumption.

All information is stored structured in PostgreSQL, while full-text search uses Elasticsearch — ensuring response times under 200 ms for a catalog of 10,000 positions.

Search and Filters: What a Buyer Needs

All filters work without page reload, using debounce and client-side data caching.

Want to see how such a catalog works? Request a demo.

Test Drive and Service Booking

Booking forms integrate with CRM (e.g., Bitrix24 or AmoCRM). The customer selects a vehicle, a preferred time from available slots, and provides name and phone. The system automatically sends confirmation via email and SMS, and a reminder two hours before. For service, the type of work (maintenance, repair, tire fitting) and vehicle parameters are additionally transmitted.

Trade-In and Loan Calculator

The loan calculator asks for amount, down payment, and term — outputs monthly payment. The credit request is sent to partner banks (Sberbank, VTB, Alfa) via their APIs. The insurance calculator (CASCO/OSAGO) works similarly through aggregators.

How Is DMS Integration Done?

DMS (1C:Avtodyler, CDK Drive, or others) syncs vehicle data, prices, and statuses. We use CommerceML format or direct REST API. Frequency is every minute or on demand. This guarantees customers see only current inventory. Thanks to integration, the portal updates prices 50x faster than manual entry.

What Is Included in Turnkey Work?

• Analytics and design: interface prototype, user scenario map, technical specification for integrations.
• Development: frontend (React/Next.js, TypeScript), backend (Laravel/PHP 8.3+ or Node.js), responsive layout (Tailwind).
• Integration: CRM, DMS, banking APIs, history check services, mapping services.
• Testing: load (up to 1000 concurrent users), functional, acceptance.
• Deployment and support: cloud infrastructure (AWS/Selectel), monitoring (New Relic), 3-month warranty support.

How We Develop the Portal

Why Order Development from Us?

We have been building auto dealer portals for over 5 years and completed 12+ projects in Russia and Belarus. Our engineering team is certified in Laravel and React. We guarantee 99.5% uptime.

After the portal launch, the number of leads increased by 60%

Director of a dealer center, 5-year client

Assess the cost of your project: contact us and receive an estimate within two business days.

Development of Corporate Portals and Internal Systems

We specialize in developing corporate portals — CRM, ERP, LMS, and Intranet. Each project starts not with landing page layout, but with how business rules will be embedded into the architecture: who sees which data, how 1C and accounting systems sync, how 500 contacts turn into 500,000 without performance degradation. Over 7 years, we have delivered over 40 portals for companies with 50 to 5000 employees. We will evaluate your project in two business days — just contact us.

A public website can be launched without detailed design — iteratively improved based on feedback. With a corporate portal, this approach does not work: the cost of fixing architectural decisions after launch for 200 users is incomparably higher. Therefore, we spend 70% of our time on analysis and prototyping, and write code only after the role matrix and integration scheme are approved.

Three areas where bad decisions are often made: access rights model, performance on large data, and real-time updates.

How to build a role model for 30 departments?

Access rights model. "A manager sees only their own clients, a department head sees the entire department, a director sees the whole company, but financial data is visible only to the CFO and above." This is not three roles — it's a matrix of roles, permissions, organizational units, and record ownership. Implementing it with if ($user->role === 'manager') in controllers will make the code unmaintainable after six months.

The correct approach: Spatie Laravel Permission for basic role model + Policy classes for object-level permission (can('view', $deal) checks not only the role but also ownership). For complex hierarchical structures — ABAC (Attribute-Based Access Control) instead of RBAC.

Performance on large data. CRM with 500,000 contacts, filtering by 10 fields, sorting by activity — a naive implementation yields 15-second queries. Composite indexes, denormalization of aggregates (last_activity_at on the record itself instead of MAX over related table), Elasticsearch for full-text search on contacts.

Real-time updates. Multiple employees working on the same document or task. Without WebSocket — constant setInterval with polling every 5 seconds, extra server load, update delays. Laravel Broadcasting + Pusher/Soketi or a custom WebSocket server on Node.js — for notifications and real-time changes.

CRM Systems

Typical set: contacts, companies, deals, activities, sales funnel, reports. Technically straightforward. The complexity lies in the details.

Pipeline with custom stages. Every company wants its own funnel. Stages must be configurable without deployment. Table pipeline_stages with position, color, is_final, probability — and drag-and-drop for reordering on UI (React DnD or dnd-kit).

Change history. Who and when changed a deal status, reassigned a responsible person, added a note. Audit log via Observer or spatie/laravel-activitylog. On UI — timeline with filtering by activity type.

Email integration. IMAP/SMTP for connecting corporate mailbox, automatic linking of incoming emails to contacts by email address. This works reliably only with proper handling of bounces, spam, auto-replies — filtering is required.

Why is ERP not about code but about data?

ERP is when CRM, warehouse, production, accounting, and HR are unified into a single system. Full ERP from scratch is rare (usually integrating with existing systems), but modular systems for specific businesses are common.

Key principle: financial operations must be immutable. Not UPDATE orders SET status = 'cancelled' — but creating a new record order_cancellations with a reference to the original order. This is the immutable ledger principle, which simplifies auditing and reconciliation.

Integration with 1C is almost always part of an ERP project. Two-way synchronization: from 1C to portal (directories, balances, prices) and from portal to 1C (orders, documents). RabbitMQ as an event bus between systems is more reliable than direct HTTP interaction — if 1C is unavailable, messages wait in the queue.

How are LMS structured: learning platforms?

Learning Management System — courses, modules, lessons, tests, certificates, user progress.

Video content is the most demanding part of an LMS. Storing video on your own server and serving via Nginx is a bad idea: expensive, slow, no adaptive bitrate. Correct approach: upload to S3/Cloudflare R2, transcode via AWS Elemental MediaConvert or Mux, HLS playlist for adaptive streaming via Video.js or Plyr.

Viewing progress — periodic sending of watch_position from the frontend (every 10–30 seconds), storage in Redis with periodic synchronization to PostgreSQL. Do not save every second to the database — it will kill performance.

SCORM compatibility — if integration with corporate training materials is needed. Separate module, there are ready libraries (scorm-again).

Intranet and HR Portals

Corporate intranet: news, documents, organizational structure, HR processes (vacations, requests, KPIs).

Organizational structure in the database is a hierarchical structure. Adjacency list (parent_id on each record) is simple to implement but slow for recursive queries. Nested Sets or Closure Table are faster for reading hierarchies, more complex for changes. In PostgreSQL — recursive CTEs (WITH RECURSIVE) with adjacency list — a balance between simplicity and performance.

Document and request approval — workflow engine. Simple linear approvals (employee → manager → HR → accountant) can be done without a special engine. Non-linear (parallel branches, conditional transitions, delegation) — consider ready solutions: Temporal.io for workflow orchestration or a custom state machine based on the state-machine pattern.

What is included in the work

When ordering a corporate portal development, you receive:

• Architectural documentation (ER diagrams, integration scheme, role matrix)
• Full code in a Git repository with CI/CD
• Access to infrastructure (hosting, databases, storage)
• Training for administrators and key users (2–3 sessions)
• Warranty support for 3 months after launch

Our design principles rely on official Laravel documentation on authorization (Policies) and recommendations for working with queues.

Technical Stack for Portals

Timeline Estimates

The cost is calculated individually after a detailed analysis of requirements and role model. To get a preliminary estimate, contact us — we will analyze your task and offer an optimal turnkey solution.