How to choose vehicle storage software: an evaluation checklist

Most software sold to vehicle storage businesses was built for self-storage and relabelled. That is not a criticism of self-storage software — it is very good at what it does, which is renting interchangeable empty boxes on recurring billing. It is a criticism of the fit. A storage unit does not have a condition. It does not have a battery that goes flat, an owner who wants photographs, or a history that someone will dispute in eighteen months.

The evaluation below is designed to surface that difference quickly, before you have moved two years of records into something that cannot hold them.

Start from the questions you get asked

Feature lists are a poor basis for comparison, because every vendor's list is long and most of it is undifferentiated. A better starting point is the set of questions your business actually has to answer, ordered by how expensive it is to get them wrong:

1. 01Where is this specific vehicle right now?
2. 02What condition was it in when it arrived, and can I prove it?
3. 03What care has it received, when, and by whom?
4. 04What has the owner asked for, and what did we agree to?
5. 05What is due today, and who is doing it?
6. 06What are we owed, and how long has this vehicle been here?

Only the last question is a billing question. Self-storage systems answer it extremely well and the other five poorly or not at all. If a demo spends most of its time on invoicing and rate plans, you are being shown a billing system. That may still be the right purchase — but you should know that is what you are buying, and plan for where the other five answers are going to live.

The demo questions that actually separate products

Ask these during a live demo, and insist on seeing them performed rather than described. Vendors are consistently willing to say yes to a capability question and consistently unable to demonstrate the workflow behind it.

Show me a check-in, starting from an empty screen

Watch how long it takes and how many decisions the staff member has to make. A check-in that runs to eleven minutes and requires judgement about which fields matter will be skipped on a busy Saturday, and a process that gets skipped is worth nothing. The article on what a check-in has to produce sets out the baseline it should meet.

Now show me that damage six months later

This is the single most revealing request. Plenty of systems capture photographs happily and then bury them in an attachments tab under filenames like IMG_4471. What you want to see is damage marked against the vehicle, in position, with the photograph attached to the mark, and the date and staff member attached to both.

Move a vehicle from one bay to another

If this takes more than a few seconds, bay data will drift out of date within a month, because staff move cars faster than they update forms. Location is only useful if it is current, and it is only current if updating it is nearly free.

Show me everything due today, across the facility

Recurring care is the workload that quietly defines long-term storage. If the answer involves opening each vehicle individually, the system does not really model care — it stores notes about care. The difference is covered in structuring recurring care schedules.

Show me what the customer sees

Ask for the actual owner-facing view rather than a marketing screenshot. If there is no customer surface at all, you will keep answering status questions by phone and you will keep sending photographs by text message. What a portal should and should not include is worth reading before you judge one.

Red flags

• Condition photographs are stored as generic file attachments rather than against the vehicle and the specific damage.
• Bay or location is a free-text field. Free text means typos, which means failed searches, which means a car nobody can find.
• Care tasks exist only as calendar reminders, with no record of completion or of who completed them.
• The customer portal is described as coming soon, in a product that has been shipping for years.
• Per-vehicle pricing that makes growth expensive, or per-user pricing that discourages giving floor staff access. Staff without logins will use paper.
• No export path. If you cannot get your vehicle records, photographs and history out in a usable format, you are not a customer so much as a hostage.

Price the migration, not just the licence

The subscription cost is the visible number and rarely the decisive one. The real costs of changing systems are the ones that never appear on a quote:

• Getting existing vehicles, owners and agreements into the new system.
• Historical condition evidence — usually the hardest part, because it lives in phone camera rolls and email attachments.
• Staff time during the window when both systems are running.
• The gap where new records go into the new system and old records stay behind, which is where most migrations quietly fail.

A workable approach is to migrate active vehicles fully, archive historical records in a readable form, and set a hard date after which nothing new is written to the old system. Migrations that let both systems stay live indefinitely tend to produce two incomplete records instead of one complete one.

Weight the criteria honestly

If you score vendors, score them against what your business actually is. A twenty-vehicle classic facility and a two-hundred-vehicle mixed operation have genuinely different priorities. As a starting weighting for premium and classic storage:

• Condition evidence and vehicle history — highest weight. This is the risk that ends businesses.
• Location accuracy and speed of update — high. It is the daily friction everyone feels.
• Recurring care scheduling — high for long-term and classic storage, low for short-term transit storage.
• Customer portal — moderate and rising. It is increasingly the visible difference between operators.
• Billing sophistication — moderate. Important, but the area where almost every product is already adequate.
• Reporting dashboards — low. Impressive in demos, rarely opened weekly.

The feature that sells the software is rarely the feature that keeps you using it three years later.

Where CarMarket24 sits

We are building CarMarket24 around the first four questions in this article — vehicle record, condition, location and care — because that is the part existing tools handle worst. It is in active development, and we would rather say so plainly: there is no pricing page and no customer list, because there are no customers yet. If you run a facility and want to shape what gets built, the pilot programme is open, and the vehicle storage software guide covers the category in more depth.