The short answer: look for software that executes your workflow instead of just tracking it. The features that separate real recon platforms from status boards are workflow automations with escalation, vendor portals, digital inspections tied to the vehicle record, multi-level customization, in-depth reporting, and deep integrations with the systems your store already runs. The platform must be configurable to the way actual work happens in your operations, so ask questions specific to your processes. Here is what each one actually means, and how to test for it in a demo.
Does it execute, or just track?
Almost every reconditioning software will show you where a car is. The good ones move it. Look for real automations: when a step completes, the next person or vendor is assigned and notified automatically. Look for escalation thresholds you can set yourself, so a car that sits past its time budget raises its own hand, first to the stage owner, then to the manager. Look for alerts you can personalize by role, so your detail manager and your UCM are not drowning in each other's notifications.
Demo test: ask what happens the moment a tech marks a task done. If the answer is "the status updates," it tracks. If the next stage gets assigned, notified, and put on the clock, it executes.
Do vendors get their own portal, or just their own column?
Every platform says "vendor communication." The feature to look for is a vendor portal: your PDR tech, glass guy, detail shop, and sublet mechanical each log in and see only their assigned tasks, with the VIN, location, photos, and comments attached, and they update tasks themselves. No phone calls, no group texts, and no all-access accounts floating around your system.
The second half of the feature is vendor performance tracking: the software should show you exactly how long each vendor holds cars, so "the glass guy is slow" stops being a feeling and becomes a number you can manage with.
Demo test: ask them to dispatch a job to an outside vendor, then show you what that vendor sees and how they move the car along from their side.
Are inspections and condition reports built in?
The multi-point inspection is where recon decisions get made, so it should live inside the platform, not on paper or in a separate app. Look for customizable multi-point inspections and checklists you can build to your store's standard, with photos and findings documented directly on the vehicle record. In some cases, more than one inspection may be needed. For example, one at intake when a manager is doing a quick walkaround and selecting needed vendor work, and another that your technician completes when the car is up on the lift. Every flagged item should become a trackable task with an owner, and the finished digital condition report should follow the car, useful for everything from approval decisions to backing up your recon story on a unit months later.
Demo test: run an inspection on a real car during the demo, flag two items, and watch whether they turn into assigned tasks or just notes.
Can you physically find the car and the keys?
Nobody puts this on a comparison chart, and it eats more hours than almost anything else on this list. A recon platform should know where the vehicle physically is, through GPS location tracking, and connect to your key box so key location and access are tied to the vehicle record. A car nobody can find is a car nobody is working on, and tracking down a key can quietly add a day to a unit.
Demo test: ask how a porter finds a specific car and its keys using only the software.
How many levels deep does customization go?
"Customizable" is the most abused word in the category, so start with the minimum bar. Every vehicle should carry three separate levels of information at the same time: a status showing where it is in your process, a physical location of the vehicle, and a list of tasks that still need to be completed for it to reach the frontline. If a platform collapses those into one field, it cannot represent how a real lot works.
From there, depth means multiple levels: unlimited steps in any order, separate workflows for new and used inventory, a different path for an individual vehicle when it needs one, user roles and permissions set per department, and your own alert and escalation thresholds per stage. Almost any tool lets you build a list of steps; a spreadsheet can do that. If the platform can only customize the step list, you will be bending your store to the software within a month.
Demo test: bring your real process and ask them to build it live, including one wholesale unit that skips half your retail steps.
Does reporting get granular, or just show averages?
Every recon tool reports time-to-line; that is table stakes. The reporting worth paying for gets specific: dwell time per stage so you see exactly where cars sit, with transit steps, recon steps, and even multiple frontline steps separated out, plus vendor performance, team and task completion rates, inventory age, and bottlenecks surfaced in real time instead of discovered at month end. The difference is accountability. An average tells you there is a problem; per-stage and per-person reporting tells you whose problem it is. If you want the background on the metric itself, we broke down time-to-line and how to measure it separately.
Demo test: ask to see which stage held cars longest last month, in two clicks.
Does the AI actually do anything?
AI is on every feature sheet now, so apply one filter: does it act on your vehicles, or is it a sticker? Useful AI in recon works per vehicle, surfacing tips, predictions, and flags on the specific unit in front of you, based on what the data on that car shows. If the vendor cannot show you AI output attached to a real vehicle record, it is marketing.
Demo test: pull up a vehicle and ask what the AI has to say about that specific car.
Does it connect to what you already run?
Recon does not happen in a vacuum. Look for integrations across your DMS, your inventory management system, your CRM, key boxes, photo and inspection platforms, and parts ordering, so vehicle data flows in automatically and what happens in your other systems updates your recon workflow on its own. The integration list is also a proxy for the criterion you cannot demo: whether the platform is still shipping. A vendor adding integrations every quarter is building; one with the same list as two years ago is coasting.
Demo test: ask which of your specific systems they connect to today, not on the roadmap, and what integration shipped most recently.
How to run the evaluation
Set your criteria before the first demo, hold every platform to the same list, and make them use your process, your vendors, and your real cars as the example. One more note on evaluating: fast to start is realistic, but be skeptical of anyone promising your entire custom workflow perfectly tuned on day one. Molding the platform to your store takes a few weeks of iteration, and that tuning is normal.
We put the main platforms side by side against criteria like these in our reconditioning software roundup, and the stage-by-stage background lives in the used-car recon process.
And if you want to run these demo tests on your own inventory, book a Cartuul demo. Bring your hardest process and your slowest vendor. That is the point.