Inventory search is the beginning of the branch
Finding the right unit does not finish a dealership conversation. It creates the next set of questions: can we open the vehicle page, show an offer, compare payments, print a presentation, send a short link, start a task, or bring the unit into a chat room? In many systems those actions live in separate menus that know nothing about the search result the employee just selected.
That separation turns the VIN or stock number into a manual relay. The employee copies it, searches again, and hopes the second tool sees the same inventory source and store. The more useful design is to treat the vehicle card as the point where the conversation branches because that is the last moment the application knows exactly which unit created the next question.
Make the unit unmistakable
The first design change was not a menu. Vehicle surfaces received clearer stock and VIN treatment so employees can distinguish a dealership’s working identifier from the full vehicle identity. Sorting labels became plain language: Highest Price, Newest Year, Lowest Mileage. That is clearer than arrows whose meaning changes with context. Non-numeric values such as call-for-price are handled deliberately rather than being sorted as though they were zero-dollar vehicles.
These details matter because every action inherits the employee’s confidence in the selection. A fast quote handoff is not useful if the card makes two similar units easy to confuse. Dense design can remain dense, but the identifiers that carry the decision forward need enough hierarchy to survive a quick scan.
Actions belong on the record that gives them meaning
LotPro’s inventory action bar attaches the next paths to the selected unit. A quote route can receive the vehicle state directly instead of forcing a redundant fetch. VDP, offer, print, share, chat, and task paths can begin from the same record. Store settings can control which actions appear and how dealership-specific URL templates are formed.
Configurable actions solve a real variation problem: dealerships do not all use the same website paths, offer providers, or presentation habits. The product should provide a governed place to describe those paths without hard-coding one dealership’s behavior into every card. At the same time, an action template is not trusted merely because it exists; provider URLs and store configuration still need validation.
- Open a current VDP or configured offer path
- Carry the selected vehicle into Quote
- Create print, share, chat, or task context from the unit
- Let authorized store settings determine available actions
Preserve the search while the decision moves
An action should not destroy the inventory work that led to it. Filter, view, and selection state need to remain understandable when the employee returns. A pinned shortlist can hold the strongest candidates while a single vehicle moves into a quote or conversation. URL search state can preserve a selected model or unit across related views where the route supports it.
The result is not simply ‘fewer clicks.’ It is a shorter and more reliable decision chain. The employee can answer the next customer question from the known unit and return to the comparison without rebuilding the search. Inventory becomes the source of downstream context rather than a disposable page that every module interprets again.
Evidence and remaining work
The cited build includes inventory handoffs, store-configurable action behavior, clearer identifiers, sorting fixes, and event-propagation work that prevents action-bar interactions from accidentally triggering the card itself. Some later action work was recorded at pull-request or build status rather than verified as a complete live dealership flow.
Real provider responses, dealership URL templates, permissions, and failure states still require rollout validation. The honest claim is that LotPro is designing the vehicle card as a decision launch point. It is not yet evidence that every provider or every configured action will behave correctly without onboarding and review.