Cartware is a purpose-built record for every cart you sell
Meet the system of record for the modern dealership.
The lot in 3D, the day's work, and every photo, sheet and stage change
filed against the cart it happened to.
Trusted by dealerships running every lot from one archive
Product
Everything about one cart, on one page.
A cart is filed by its VIN the day it comes off the truck and by its sale number the day it sells, so the number on the paperwork is the number you search. Everything else hangs off it.
Walk the lot without walking the lot
Every cart in stock stands in a 3D yard, laid out by stage: unsold at one end, ready for delivery at the other, each one in its own paint. Tap a cart and the page flies to it.
Mark the damage on the cart itself
Spin the cart and drop a point where the problem is — service, factory defect or warranty claim — with the photo pinned to the spot it was taken. No more “scratch, rear left, near the panel”.
Photos and paperwork, filed against the cart
Photos from the lot and the delivery, the sales sheet, warranty and finance documents, and the paper QC sheet photographed and kept as it was signed. Every one stamped with who added it and from which store.
One line, six stops, nothing forgotten
Unsold, sold, service, ready, out, delivered. Every move asks first and writes itself into the cart's history, and a cart with work still open refuses to go out until somebody types a reason with their name on it.
The shelf, counted where it stands
Parts by number, category, supplier, cost and bin, counted per store. Finishing a task takes its part off the shelf and says which cart it went on.
The numbers, and the way out
How long a cart takes to sell, what is ageing on the lot, what went out on time. Carts and parts download as a spreadsheet or a PDF — and the same sheet goes back in again.
The day
A queue, not an archive.
Nobody signs in to browse a database. They sign in to find out what they are doing next — so that is the page they land on, and it is a different page for each of them.
-
Every cart walks one line
Unsold, sold, service, ready for delivery, out for delivery, delivered. The line is drawn under the cart, the stop it stands on is the stage it is at, and pressing the next stop is what moves it — from the cart's own page, or straight off the card in your day.
-
The rules refuse, they do not forbid
A sale with no customer on it, or a cart sent out with work still open, is refused where it was pressed. Anybody can push past it by typing a reason, and that reason lands in the cart's history with their name and the time on it. The record is what makes that safe, not a lock.
-
The week, and the shelf, in the same archive
Booked deliveries read as a schedule — a row per cart, a column per day, store by store. A task on a cart takes its part off the shelf as it is finished. Nothing is written down twice.
Three jobs, a page each
Whoever runs the store gets all three, one under the other. None of it is a permission: the page stops offering other people's work, it does not stop anybody doing it, and the record says who did.
Where it runs
On your infrastructure, at your pace.
One dealership on one small server, or a hundred stores on managed Postgres with point-in-time recovery. Same software either way.
Pricing
One price per store, not per seat.
Everybody on the floor needs an account, so charging for accounts just means people share one. Add the store, add the whole store — and the more stores you run, the less each one costs.
Plus a one-off $100 setup.
One lot, unlimited accounts, hosted by us.
Get started- Unlimited carts, photos and sheets
- Unlimited accounts
- Virtual lot, parts and analytics
- Nightly backups
Plus a one-off $100 setup per store.
Every lot in one archive, on your own hostname.
Get started- Everything in Single store
- Your own hostname
- Master admin across every store
- Managed Postgres with point-in-time recovery
Dealerships
Built next to the people using it.
Cartware started as one dealership's problem — a whiteboard, a shared drive and three phones — and it is still shaped by the floor rather than a roadmap.
“Placeholder quote. Replace with something a real customer actually said about running their lot on Cartware.”
“Placeholder quote. Replace with something a real customer actually said about running the day off it.”
“Placeholder quote. Replace with something a real customer actually said about running several stores.”
Resources
The questions dealerships actually ask.
Does anything I upload leave my server?
Mail, and nothing else. Password resets and invitations go out over SMTP, and if you switch on Sign in with Google there is one call to Google to turn a sign-in into an email address. No analytics, no error reporting, no model API, and no cart, customer or sale number sent anywhere. The map link on a delivery is your driver's own browser following a link, and it carries none of those either.
Do I have to change the QC sheet my techs use?
No, and nothing is read off it. Photograph the filled-in sheet and it is kept with the cart exactly as it was signed. The paper is the record a dealership actually wants — a machine guessing at a tick box on the document that decides whether a cart ships is worse than no machine.
Can a cart go out with work still open?
Only if somebody says so out loud. The move is refused where it was pressed, and pushing past it costs a typed reason that lands in the cart's history with a name and a time on it. Nothing here is locked — everything is written down, and a history is never edited or deleted.
Can I get my records out again?
Carts and parts download as a spreadsheet or a PDF, and the spreadsheet goes back in: the header of a download is the header of an upload, so fixing forty rows in Excel and sending the file back is the whole workflow. A single cart's facts, tasks and history download too.
What happens when somebody leaves?
Delete or demote the account and it takes effect on their next click. The sign-in cookie says who they are, not what they may do — that is re-read from the database on every request, so there is no window where a deleted account still works.
Can two dealerships share one deployment?
Yes, and neither can see the other. Each dealership signs in on its own hostname, which means its session cookie is never even sent to another dealership's pages, and every query is scoped to the dealership that owns the row.
How do backups work?
On Postgres they are the provider's job, with point-in-time recovery. On SQLite, snapshots are taken through the online backup API against a live app, every snapshot is integrity-checked and discarded if it fails, and the restore path is exercised on every build rather than assumed.
Stop losing the paperwork.
If your carts are tracked across a whiteboard, a shared drive and three phones, Cartware is the one place they were supposed to be.