The WholeDealership onOne Platform

Kothari Hyundai, Pune.

A hand placing the final block on one connected dealership platform

How KDMS, a white-labelled TurboDMS, brings sales, stock, compliance and back office into one system that carries the dealership's own name.

Every Hyundai that leaves a showroom carries two histories: the deal and the car.

The deal moves through eight recorded stages: lead, enquiry, pre-booking, booking, docket, sale, RTO and delivery. The car has a story of its own. It is ordered, purchased, allotted, inspected, moved through the gate and handed over. In the status-quo dealership stack of an OEM-mandated DMS, Tally, Excel and WhatsApp groups, those two histories sit in different tools, and records diverge at each handover between them.

Kothari Hyundai, Pune needed one system that holds both histories together. The KDMS build reflects five requirements.

  • Coexistence. Live bridges to HI-Rise, NDMS and i-Crop move customer, enquiry and vehicle records between KDMS and the systems already in use.
  • One record per deal. A single Case record carries each customer from first visit to key handover.
  • Stock in the same system. Vehicles, orders, purchases, inspections and movements sit on the platform beside the deals they serve.
  • Adoption. Group chat, task management, WhatsApp Business and calling live inside the platform, so staff work in tools they already know.

Kothari's own name and ownership. The platform runs as KDMS, and Kothari owns the IP and the data.

Kothari's teams work in KDMS. Underneath, the engine is TurboDMS.

White-labelling here goes beyond a name on a login screen. It rests on three architectural properties of the Enabler framework that TurboDMS is generated from.

  • Multi-tenancy. Enabler supplies multi-tenancy as a seed module. The Super Administration module manages OEMs, products, schemes, dealerships and dealership admins as first-class entities, and support users receive module-wise access. A Hyundai dealership sits in that structure as its own dealership, linked to its OEM.
  • Configuration. The Easy Configurator shapes the platform to the client's forms, checklists, roles and processes, and role management with an Access Control List rule tree sets what each role sees and does.
  • Ownership. A code exporter hands over a documented JavaScript codebase, so the generated software becomes the client's property. TurboDMS is offered on two commercial models: subscription-to-ownership and IP buyout.

The result is a shared core with a client layer on top. The table shows how the two divide in the KDMS build.

Shared TurboDMS core

Case spine from lead to delivery; vehicle, stock and inventory management; four quotation types with offer approval; booking, docket, payment and delivery; PDI checks and gate passes; test drive management; show-room operations; vendors, orders and purchases; role-wise dashboards and reporting; Access Control List; audit management.

Kothari layer

Bridges to HI-Rise, NDMS and i-Crop; HI-Rise to Tally conversion utility; legacy data validation and analysis for insurance; insurance renewal module configured to the KCPL renewal process (200 hours); Hyundai showroom checklist under Fleet Management; price list upload (120 hours); group chat, task management and calling extensions; training and support programme.

A new dealership starts from the same core and receives a layer of its own. Kothari's layer remains Kothari's.

69 modules. 384 features. Four build layers on one foundation.

TurboDMS is generated from Enabler, which offers more than 180 reusable modules. The stack combines React and Node.js with a combined Mongo and SQL data layer, deployed in Docker containers. The application is a progressive web app, so one build serves desktop, tablet and phone on any operating system. Data is encrypted at rest, and the codebase is documented JavaScript that any full-stack JavaScript developer can maintain.

01

Platform and data foundation

Authentication, users, departments, branches, roles and teams, Super Administration, document management, logging, job scheduler, notifications, multi-factor authentication, bulk import and export, and the three legacy bridges.

02

Demand capture & deal construction

Product catalogue, vehicles and stock, QR codes, visits, leads, customers, enquiries, forms, quotations, offers and finance types.

03

Booking to delivery

Booking, dockets, sale, purchase, insurance, invoice, PDI checks, payment, audit, RTO docket, delivery and gate pass.

04

Operations & administration

Targets, incentives, showroom, checklists, claims, vendors, orders, test drives, fleet, inventory, accessories, assets, reports, third-party integrations and access control.

05

Commissioned extensions

Task management, calling, WhatsApp Business, group chat, e-sign, visitor management, pre-booking, price list upload, test drive vehicle tracking, insurance renewal changes and legacy data validation.

The central design decision is the Case spine. Lead, Enquiry, Pre-Booking and Booking are stages of one Case, which then continues through Docket, Sale, RTO and Delivery:

  1. Lead
  2. Enquiry
  3. Pre-Booking
  4. Booking
  5. Docket
  6. Sale
  7. RTO
  8. Delivery

Twelve object types (Vehicle, Lead, Customer, Enquiry, Form, Quotation, Booking, Docket, Sale, Purchase, Order and Test Drive) each carry explicit lifecycle management, so status is a recorded state visible to every authorised role.

Integration

Systems

Legacy dealership systems
We care about understanding the problem before touching the technology.
Identity and payments
Aadhaar and PAN verification; Razorpay
Communication
WhatsApp Business, telephony, email and SMS notifications
Documents and capture
Amazon S3 with signed URLs, e-sign PDF, phone camera, OEM QR scanning, dealership QR codes
Authentication
Google Authenticator, Duo Mobile, SMS authenticator
Accounting
File Conversion Management turns Hi-Rise data into Tally-compatible files. A direct Tally connector is parked.

The clearest way to see KDMS is to follow a single vehicle through it.

The walkthrough below traces a typical path through the platform as designed, using the features in the KDMS build.

Step

What happens in KDMS

  1. 1. Order and purchase

    The dealership raises an order and a purchase, each tracked through its own lifecycle, with vendor and contract records alongside. The vehicle enters the catalogue and stock with its Ordered state.

  2. 2. Stockyard check

    A stockyard PDI checklist records the condition of the car. Vehicle in/out records and gate passes log every movement.

  3. 3. A customer walks in

    The visit is logged as a Buyer or Visitor record. A sales consultant is assigned by availability, and the enquiry captures need analysis on the Case.

  4. 4. Test drive

    The consultant schedules a test drive against car availability. An OTP, location record and photos accompany the drive, and a gate pass records the departure.

  5. 5. Quotation and offer

    Standard, finance, accessories and exchange quotations sit on the same Case. A discount request raises an approval task for the manager, who approves or rejects it on the record.

  6. 6. Booking

    The booking applies the vehicle's minimum booking amount and waiting period. The vehicle moves to Allotted.

  7. 7. Docket and payment

    Aadhaar and PAN verification, finance, down payment, balance and receipts, documents stored on S3, and e-signatures on generated PDFs build the docket.

  8. 8. RTO

    RTO Docket Management handles the docket and RTO passing.

  9. 9. Showroom PDI and delivery

    A showroom PDI checklist precedes handover. Delivery closes with a feedback form and a key handover photo, and the vehicle moves to Delivered.

At every step the record belongs to the Case and to the vehicle, so the sales team, the stockyard, accounts and the manager see the same facts.

Stock is where a dealership's capital sits.

A system that tracks customers and leaves vehicles to a spreadsheet manages half the business. KDMS treats the vehicle as a managed record with a lifecycle, a procurement trail, physical controls and commercial rules.

Stock question

How KDMS answers it

What do we hold?
Product catalogue, vehicle records (create, edit, list, activate and deactivate) and stock records (create, edit, list). A price list upload extension (120 hours) loads pricing in bulk.
Where is each vehicle in its life?
Vehicle lifecycle management tracks four states: Ordered, Allotted, Delivered and Fleet.
What is on order and what has been bought?
Order Management and Purchase Management each carry lifecycle management. Vendor, contractor and contract records sit alongside them.
Is the vehicle ready to hand over?
Separate PDI checklists for the stockyard and the showroom.
Who moved it, and when?
Gate Pass Management, showroom vehicle in/out and material in/out records.
What about demo, fleet and trade vehicles?
Test drive car availability, gate pass, OTP, location, photo and vehicle tracking integration. Fleet Management adds trade insurance, trade certificate and driver assignment.
What about accessories and assets?
Inventory Management, Accessories Management and Asset Management extend the same records to accessories and showroom assets.
How does bulk data get in?
Bulk import and export in .CSV and .pdf with downloadable sample formats, plus OEM QR code scanning that saves data from the code.

Commercial rules live on the vehicle record. Minimum booking amount, special discounts and waiting period are configured per vehicle, so the terms that apply to a car stay attached to the car when a salesperson builds a quotation or takes a booking. Daily, weekly, monthly, quarterly and yearly reports, customizable executive reports and real-time configurable reports cover these records.

Each role opens KDMS to a dashboard built for that role.

01

Sales consultant

Sees assigned enquiries and a daily calling list with call status. Logs visits, records need analysis, builds four quotation types, runs test drives and messages the customer through WhatsApp Business or a call from the platform.

02

Sales manager

Receives discount approval tasks and decides on the record. Follows sales targets and incentives, and reads reports on daily to yearly cycles.

03

Stockyard and PDI team

Maintains vehicle and stock records, completes stockyard and showroom PDI checklists, and issues gate passes for vehicles and materials.

04

Accounts and back office

Tracks down payment, balance, finance and receipts, raises invoices, and manages vendors, contractors, contracts, orders and claims. Hi-Rise data converts to Tally-compatible files.

05

Owner and leadership

Reads executive reports and audit reports, and uses the Access Control List rule tree to set what each role may see and do.

Group chat collaboration is the largest single extension in the build at 1,000 hours. It sits beside task management (200 hours), calling integration (180 hours) and WhatsApp Business integration (24 hours), so the working conversation and the working record live in one place. Test Drive Management adds fifteen features covering availability, scheduling, OTP, location, photo, forms, gate pass, feedback and home visits with call records.

What the KDMS model offers other dealerships.

01

One record for every deal and every vehicle

The Case spine and vehicle lifecycle put sales and stock on the same platform.

02

A path from existing systems

Bridges to Hi-Rise, NDMS and i-Crop keep current tools connected during adoption.

03

A platform under the dealership's name

White-labelled, configured to each dealership's process, and owned by the dealership.

Share this read

Sign up to our Newsletter for all latest updates.

The AI everyone wants.
The foundation almost no one has.

Connect with us →
Write to us at:
Call us: