Kenro Kenro
Kenro WhatsApp us

Kenro Dealership

Your pre-owned showroom, end to end.

Every car from the first phone call about buying it to the RC landing in the customer's hand — purchase approvals, refurbishment, bookings, loans, insurance, RTO and delivery, in one system your whole floor works from.

Liverunning a Delhi showroom in production
17roles, from procurement to RTO agent
3surfaces — phone, desktop, owner console

The whole life of a car

Fifteen steps, and none of them live in someone's head.

This is the part other software skips. A pre-owned car is not sold in one motion — it is bought, moved, inspected, repaired, photographed, financed, registered and delivered, by different people, over weeks. Kenro Dealership holds all of it.

01 Procurement lead Someone hears about a car. It gets logged, not remembered.
02 Owner approves the buy Nothing is purchased on somebody's word alone.
03 Purchase paperwork RC, insurance, forms — captured against the car.
04 Pickup A driver is tasked; the car arrives with a record.
05 Inspection Physical check, condition graded, damages marked.
06 Refurbishment Jobs go to vendors, with proof photos and invoices back.
07 Ready for sale Inventory flips the stage; the floor can see it.
08 Photos & listing Media shoots it, copy is written, it goes to the website.
09 Enquiry Instagram, Facebook, WhatsApp, the website, or a walk-in.
10 Booking Raised by sales, approved by the owner.
11 Loan Bank pipeline, subvention, escalation — tracked to disbursal.
12 Insurance Policy arranged, renewal remembered.
13 RTO Transfer, HPA, agent, state rules.
14 Delivery Scheduled, checklisted, odometer and fuel recorded.
15 RC in hand The case closes only when the document is on file.

What runs in it

Built around the parts of the business, not the software.

Buying cars

  • Procurement leads with owner approval before money moves
  • Purchase documents captured against the car, not a drawer
  • Driver tasked for pickup, with proof of collection
  • Physical inspection, condition grade and damage marking
  • Bulk upload when you buy a batch

Getting it ready

  • Refurbishment jobs assigned to vendors, with a QC gate
  • Vendor invoices and payments tracked against each job
  • Proof photos required before a job counts as done
  • Media shoot, showcase stories and website listing sync
  • Stage machine — procured, inspected, refurb, ready, booked, delivered

Selling cars

  • Leads from Instagram, Facebook, WhatsApp, your site and walk-ins
  • Lead locking so two executives never work the same buyer
  • Test drives, follow-ups and a compliance view of who is behind
  • Bookings raised by sales, approved by you
  • Edit requests — sales asks, you approve the field change

Money and paperwork

  • Loan pipeline per bank, with subvention and escalation
  • Insurance policies and renewal reminders
  • RTO cases, HPA release and agent handoff
  • Your own sale paperwork generated with the right signatories
  • Fancy number plates reserved, released and tracked

Handing over

  • Delivery scheduled with a handler and a checklist
  • Driver tasks for pickup, drop, RTO runs and the final delivery
  • Odometer and fuel captured at handover, not remembered
  • Post-sale follow-up, referrals and buyback interest

Running the place

  • One approvals queue — purchases, bookings, loans, edit requests
  • Full audit log: who did what, when, on which car
  • Team health cards and follow-up compliance per person
  • Reports — sales funnel, leaderboard, ageing, loan pipeline
  • Branch scoping, so two showrooms stay two showrooms

Three surfaces, one system

Your staff get a phone. You get a console.

Staff

The phone

Every role works from their phone — procurement, drivers, refurb, sales, RTO. They see the screens their role owns and nothing else.

The floor

The desktop

The same system on a bigger screen for the people who sit down to work — heavy data entry, documents, long lists.

You

The console

The owner's view across every branch: approvals, activity, audit trail, reports, staff and settings. This is where the business is actually run.

Built from a real showroom

Configured around how you work, not the other way round.

Every one of these exists because a working dealership asked for it, and the system bent rather than the business.

One person, several hats In a real showroom nobody does one job. A user can hold several roles at once, and be granted a module without changing their role.
Two branches, one business The live deployment runs two showrooms. Staff are pinned to a branch, data is scoped to it, and the owner sees across both.
Prices off the internal screens That showroom's owner did not want car prices visible to staff on internal screens — money is an input for the customer's paperwork, not a number on every desk. So it came off, without touching loans, insurance or refurb costs.
Your paperwork, your signatories Sale documents are generated from your own templates, carrying your purchasing company and its directors — not a generic receipt with your logo on top.

Talk to us

Tell us how your showroom runs today.

One branch or several, ten cars a month or a hundred — describe the floor and we will tell you honestly whether this fits. It is installed, your records are moved in and your team is trained; you are not handed a login and wished luck.

Kenro