There is a particular kind of gap that no report catches, because nothing in the system knows it exists.
A vehicle is delivered. It is parked on the lot. Anybody walking past can see it. But in the software it is still an order, because moving it from "on order" to "in inventory" is a thing somebody has to do, and that somebody is usually not the person who watched it come off the transporter.
Until that happens, the vehicle is in a strange position. It is not aging, because aging counts from the day it landed and the system has no landing date. It is not due for an audit, because audits apply to units on the ground. It does not come back when a salesperson searches inventory, because it is not in inventory. It is physically the most available vehicle on the lot and administratively it has not arrived.
Nobody notices, and that is the whole problem
This is not a failure of diligence. It is a gap with no alarm on it.
A missing invoice gets chased because a vendor sends another one. An unaudited unit turns up on an audit list. A vehicle that arrived but was never grounded produces no signal at all: it is absent from the lists that would show it as late, precisely because it is still filed as an order. The only way to find one is for a person to notice a vehicle in a row and think to check whether the system agrees it is there.
When this store went looking, they found several units sitting on the lot while still marked on order. One had been there about six weeks.
Six weeks of carrying a vehicle that no report counted as carried.
The scan is the event
The fix we shipped is not a report and not a reminder. It is a change to what happens when somebody scans a barcode.
Scan the window-sticker VIN of a vehicle that is still on order and it moves into inventory right then. Not queued, not flagged for somebody to confirm later. The record changes while the person is standing in front of the vehicle, and it is stamped with three things: that day's date in your timezone, the location being scanned into, and who scanned it.
It sounds different from an ordinary move. Walking a row, you hear one thing when a unit is confirmed where you thought it was, another when it moves from somewhere else, and a third, longer one when a vehicle has just joined inventory for the first time. A move corrects where something is. This changes what it is. The person holding the phone learns which happened without looking at the screen.
That matters more than it sounds, because the alternative is a screen somebody glances at while holding a phone at arm's length in the cold.
Why it has to be the scan and not a checkbox
The reason to attach this to scanning rather than to a form is the same reason the lot audit is attached to scanning: the record should be a by-product of something a person is already doing.
Nobody walks a row in order to update the system. They walk a row to find a vehicle, to check a row is where they think it is, or because a manager asked how much of the lot has been looked at this week. Grounding a newly arrived unit is not an extra task bolted onto that walk. It is what the walk already discovered, written down at the moment of discovery.
The alternative, an arrivals screen somebody works through on a Tuesday, is a second list to maintain. Lists that exist to correct other lists have a way of becoming the thing nobody gets to.
What it will not do
Two limits worth stating plainly, because a feature described without them disappoints on the first row.
A vehicle can only be grounded this way if its VIN is already on file. An order placed before the VIN comes through carries a placeholder, and there is no barcode in the world that matches a placeholder. Scan one of those and the app says it is not in inventory, which is the truthful answer. The vehicle becomes scannable once its VIN lands.
And the date it records is the day of the scan, which is correct for a vehicle scanned the day it arrives and wrong for one that has been sitting for six weeks. So a manager can correct the arrival date afterward, on the unit's own record. The scan is not the last word on when something arrived. It is the first moment the system knows it did.
The quieter benefit
Once arrivals land on the day they happen, a second thing becomes true that is harder to see: the aging numbers start meaning something.
A report that counts days on the lot is only as good as the day it counts from. If a third of the inventory was grounded on the day somebody got round to it rather than the day it arrived, every carrying-cost figure downstream carries that error, and nothing in the report says so. Fixing the moment of entry is what makes the rest of the arithmetic honest.
That is the case for doing it at the barcode. Not that it saves a few minutes, though it does. It is that the alternative quietly corrupts the numbers you make decisions with, and does it in a way no report can show you.
Positions and arrivals are recorded only when somebody audits or scans a unit with the app open. There is no background tracking and nothing follows a vehicle between scans.
See what else the app tracks on the features page, or what it costs.