Vehicle comparisons that help dealership shoppers decide

Start with the decision the shopper faces

Ask what the shopper needs to understand before choosing between the vehicles. Someone considering a long commute may care about running costs and comfort, while another person needs accessible cargo space for a particular routine. The useful comparison is different in each case.

Keep those priorities visible beside the shortlist. If the shopper changes a requirement, update the comparison rather than defending the first recommendation. A good explanation should remain understandable even when the preferred vehicle changes.

Compare exact inventory records

A model name alone can hide differences in year, trim, powertrain, options and vehicle condition. Tie each comparison column to the actual inventory record and its stock identifier. Let the shopper open the corresponding listing to inspect the source details.

Normalize units before displaying differences. Distinguish a manufacturer specification from an optional feature or a fact verified for that individual vehicle. If the catalog does not establish a feature, show that it needs confirmation instead of filling the cell with a guess.

Explain the compromise in plain language

Suppose a shopper is comparing two SUVs for school runs and road trips. One might offer the seating layout they prefer, while the other better matches a stated budget. Describe that tradeoff using verified facts and let the shopper decide which priority matters more.

Do not produce a universal winner from a hidden score. Show why an option fits, where it falls short and which unanswered question could change the recommendation. This example illustrates comparison design; it does not describe measured customer behavior.

Keep unverified claims out of the table

A listing photograph may suggest a feature without proving its presence or condition. Likewise, an assistant should not turn a shopper’s rough payment preference into an approved financing offer. Give the team a clear question to resolve.

Treat freshness as part of the comparison. If an inventory update removes a vehicle, explain the change and help the shopper find an alternative. Test the experience with incomplete records so the system learns to reveal uncertainty rather than hide it.

Turn the shortlist into a useful visit

Use the comparison to prepare what the shopper wants to see in person: seating access, loading space, visibility or a driving impression. CDK’s research on test drives supports treating the visit as a meaningful part of the decision, rather than a generic final button.

Pass the selected vehicles and open questions to the dealership team. A visit request should say what the shopper hopes to learn. Confirm scheduling and vehicle availability through the actual process before presenting either as settled.

Reference: CDK Global: The Test Drive’s Enduring Value

Review decisions, not table activity alone

Comparison opens and clicks can show that a feature is used, but they do not establish that the shopper found it helpful. Combine those events with requested visits, resolved questions and team feedback where those outcomes are observable.

Begin with a small set of common comparison scenarios. Ask a salesperson to review accuracy and a new reader to explain the tradeoff in their own words. If the answer is unclear, simplify the comparison before adding more columns.

Common questions