Loading.
Point us at the feed you already send to the listing sites. Every car on your lot gets a page, your team gets a proper inventory manager and a lead inbox, and nobody has to retype a price into a website again.
This is the hard part, and it is the part most inventory tools get wrong. When somebody edits a price, a description or a photo by hand, the feed stops overwriting that one field — but if the feed later carries a genuinely different value, you are shown it and can accept it in one click. Nothing drifts silently, and nothing is silently reverted.
Everything listed here is built and running today. Nothing on this page is a roadmap.
Every publishable car gets its own page with a photo gallery, the full spec, and a contact form that lands in your inbox. Shoppers filter by make, model, body style, price and mileage. The sitemap, the structured data search engines read, and the "sold" handling all follow the same one rule about what is public, so nothing can disagree with anything else.
Change a price, rewrite a description, reorder the photos. That field is now yours: the feed will not overwrite it. If the feed later sends something genuinely different, it is shown to you next to the car with an Accept button, so you find out from us rather than from a customer. Every change is logged with who made it and when, and price history is kept separately.
Type or scan a VIN and the year, make, model, trim and drivetrain fill themselves in. The check digit is validated first, so a mistyped VIN is refused rather than quietly decoding into a different car. Decoded values sit below your own edits in priority — a decode never overwrites something a person corrected.
Upload a CSV and map its columns to ours once; the mapping is remembered. Before anything is committed you see exactly what would change, what would be blocked by a lock, and what was rejected for being unparseable — and a run that moves prices too far is refused rather than applied. Every committed run can be rolled back, and a rollback will not undo a hand edit made afterwards. Exports go out as CSV, TSV, JSON or XML in a layout you define.
Three steps, and the longest one is waiting for a certificate.
Step 1: Pick your address and pay
Choose the name your dealership will live at, tell us who you are, and pay. The card is checked by Stripe — we never see the number.
Step 2: Your dealership is created
A minute later there is a dealership: your web address, staff roles, a lead funnel, and an owner account in your name. You get an email to set your password.
Step 3: Connect your feed, or start typing
Point us at the inventory feed you already produce, upload a spreadsheet, or add cars by hand or from the phone app. All three work together from day one.
We are not quoting a public price at the moment. Send us an email and we will tell you exactly what it costs — there is nothing complicated behind this, and no sales process to sit through.
No. The feed is treated as one source among several. When a person edits a field by hand, that field stops accepting feed writes — but the feed’s new value is still recorded and shown to you as a suggestion you can accept in one click, so you always know when your site and your DMS disagree.
It comes out of the inventory grid, the filters and the sitemap immediately, and its page keeps working. Sold vehicle pages are some of a dealership’s most-visited URLs, so throwing that traffic away would be a mistake — but advertising them to search engines as fresh inventory would be worse.
Nothing automatic. Feeds routinely carry sold units for days, so a sold vehicle returning in a feed raises a suggestion rather than un-selling itself. You decide.
Sign up online and your dealership exists a minute later — your own web address, your own inventory manager, your own lead inbox. Or send an email and talk to a person first.
Website enquiries land in a shared inbox with stages you name yourself, an assignee, a timeline of everything that has happened, and tasks with due dates. People are deduplicated on email or phone number — not email alone — so an opt-out follows the person rather than one of their two records.
Photograph a car where it stands, scan the VIN, create the vehicle, accept a feed proposal, all from an Android phone. Photos upload in the background and survive a bad signal in the back corner of the lot. The iPhone build comes from the same codebase.
You get a working web address the moment you sign up. When you are ready to point your own domain at it, that is a setting — the old address keeps working and redirects, so nothing you have already printed stops working.
Keyboard navigation, real labels on every control, visible focus, and colour contrast checked against whatever brand colours you pick. Dealership websites are among the most-sued categories in the US for accessibility, and the galleries, filters and lead forms that get sued over are exactly what this builds.
Yes. You get a working address the moment you sign up, and your own domain can be added afterwards. Both keep working, with one marked as the canonical address so search engines are not shown the same page twice.
Your staff, and nobody else’s. Every table in the database is separated by dealership at the row level, and a shopper’s view of your website is served by a small set of read-only functions that take a hostname and can only ever return that dealership’s published cars. There is no query anywhere that could return another dealership’s data by accident.
Nothing extra. It is included, and it is installed directly onto your team’s Android phones rather than through an app store.
Yes, at any time, and your subscription stops at the end of the period you have paid for. Ask us and we will export your inventory and your leads to a spreadsheet — the export tools are part of the product, not a favour.
That is fine and it is the normal way this goes. Send an email and a person will answer — there is no queue and no demo booking system.