Buying guide · Dealer websites
CMS for Car Dealerships: What a Dealer Website Actually Needs
A buying guide to choosing a CMS for car dealerships: inventory-first publishing, phone photos, leads in one inbox, cookieless analytics and multi-location.
Most CMS buying guides are written for people publishing articles. A car lot does not publish articles. It publishes cars, and a car is a very different kind of content: it has a VIN, twenty photos, a price that changes on Tuesday, and a lifespan of a few weeks before it leaves on a sale or a trade.
I spent time working at a dealership before I went back to software, and the tools we used to update the website were the most frustrating part of the day. That experience is the reason OctaneOS exists. This guide is what I would tell a dealer who asked me what to look for.
Start with inventory, not pages
A general CMS treats a page as the unit of work. A dealership CMS should treat a vehicle as the unit of work.
When the vehicle is the unit, adding a car means typing a VIN, uploading photos, setting a price and pressing publish. The system knows what a vehicle is, so it builds the listing card, the vehicle detail page, the search filters and the sitemap entry without you touching any of it.
When the page is the unit, adding a car means creating a page, filling in custom fields, uploading images to a gallery block and remembering to tag it so the inventory filter finds it.
Questions to ask any vendor:
- Does VIN decode fill in year, make, model, trim and engine, or do I type all of that?
- Are statuses built in (draft, available, pending, sold), or do I fake them with categories?
- Is there a limit on the number of listings?
- What happens to a car I delete by mistake?
In OctaneOS the answers are: yes, yes, no limit, and it sits in a 30-day trash.
Photos have to come from a phone
The person photographing cars is standing on the lot with a phone. They are not at a desk with a laptop and an image editor.
A dealership CMS should accept a batch of phone photos as they are, then handle the resizing itself. That means producing small, fast versions for the listing grid, larger versions for the detail page, and a social share image for when someone texts the link to their spouse.
If the vendor's answer involves "just resize them before you upload" or a separate image optimization plugin, that is work landing on your staff every single day. We resize everything automatically into WebP variants and generate the share image, because nobody at a dealership has time to do it by hand.
Publishing has to be instant
Many legacy dealer platforms still move inventory through a nightly feed. You change a price at 10 a.m., the website shows the old price until tomorrow morning, and a customer who saw the old number on their phone shows up wanting it.
The same delay works against you when a car sells. It stays on the site and people keep calling about it.
A modern dealership CMS pushes a change to the live website in about a second. There is no feed to wait on and no vendor ticket to open. We wrote more about this in why your inventory should update instantly.
Leads belong in the same tool
On a generic CMS, contact forms are a plugin, and the submissions go to an email address. Vehicle inquiries go to another email address, or the same one, and nobody can tell you afterwards which car the customer asked about or who followed up.
A dealership CMS should put every contact form and every vehicle inquiry in one inbox, attached to the car when there is one. From there you want:
- statuses (new, contacted, qualified, won, lost, spam) so a manager can see the pipeline at a glance
- assignment to a salesperson
- notes on the conversation
- an instant email to the dealer and an automatic reply to the customer
- a spam honeypot so the inbox is not full of junk
This is the part of a dealership website that actually makes money, and it should not be an afterthought bolted onto a blogging tool.
Analytics without a cookie banner
A dealer wants to know three things: how many people visited, which cars they looked at, and where the leads came from. None of that requires tracking individuals across the web.
Cookieless analytics answer those questions without a consent banner covering the homepage on a phone. OctaneOS reports visitors, vehicle views, lead counts and lead sources, and sends a digest email every Monday morning so you see the week without logging in.
Multi-location should be one dashboard
If you have two lots, a generic CMS usually means two sites, two logins and two sets of plugins to keep updated.
A dealership CMS should handle this natively: one dashboard, several lots, one website with a location filter so a shopper can see what is at the store nearest them.
Where WordPress falls short for a car lot
WordPress is a fine general CMS. It is good at what it was built for, which is publishing pages and posts.
The trouble for a car lot is that nothing about a vehicle is native to it. Inventory becomes a custom post type from a plugin. Photos go through a gallery plugin and an optimization plugin. Leads go through a form plugin. Vehicle pages depend on a theme that understands the inventory plugin. Each piece is maintained by a different party, and when one breaks after an update the dealer is the one who finds out.
| Need | Generic CMS (WordPress and similar) | Dealership CMS (OctaneOS) |
|---|---|---|
| Adding a vehicle | Custom post type plus fields | VIN decode, native statuses |
| Photos | Gallery plugin plus optimization plugin | Phone upload, automatic WebP and share image |
| Publishing changes | Depends on hosting and caching setup | Live in about a second |
| Leads | Form plugin sending emails | One inbox with statuses, assignment, notes |
| Analytics | Third-party script, usually a cookie banner | Cookieless, built in, weekly digest |
| Multi-location | Multiple sites or manual tagging | One dashboard, location filter |
| Logins | Username and password | Google or one-time email code, audit log |
None of this is a knock on WordPress. It is a question of fit. A tool built for articles feels like one when you point it at a lot full of trucks.
Things that are easy to forget
A few items that rarely make the sales pitch but matter a year in:
- Sold pages. When a car sells, its page should stay live and marked sold, so the URL keeps the Google ranking it earned. Deleting the page throws that away.
- Private listings. Sometimes a car needs to be in the system but not on the site yet. That should be a checkbox, not a workaround.
- Price display modes. Show the price, say call for price, or hide it, per vehicle. If you sell near the border, show CAD and USD.
- Promotions with dates. A weekend sale banner should turn itself off Monday morning without anyone remembering to do it.
- Team roles and an audit log. When a price changes, someone should be able to see who changed it and when.
- No passwords. Sign in with Google or a one-time email code. Dealership staff turn over, and a shared password on a sticky note is how sites get defaced.
How OctaneOS fits
OctaneOS is the inventory, leads, promotions and analytics platform behind dealership websites built by Designer Digital. Each dealer gets a custom-designed site on Vercel's global CDN and the dashboard at app.octaneos.net. The dealer never touches code.
It is a one-time design and build fee for the custom website, then one monthly subscription per dealership for the platform and no long-term contract. Pricing is quoted on a short call. If you want to see the dashboard before that call, the interactive demo walks through it.
For a wider look at cost, read how much a dealership website should cost.
Where to go next
- How it works: the site, the dashboard and how a change reaches the web in about a second.
- Contact us: a short call to talk through your lot and get a quote.