A dealership website has to keep its stock and its sales conversation connected.

01Start with the buying task

The website can prepare a showroom visit without taking the whole sale online.

Consider a buyer comparing two used vehicles on a phone. Before calling, they need to know which exact vehicle they are looking at, whether the information is current, what remains to be checked and how to arrange the next step. A large showroom photograph answers only a small part of that question.

Cox Automotive's 2025 Car Buyer Journey study, released in January 2026, surveyed roughly 2,300 U.S. vehicle buyers. It reports that 63% preferred a mixture of online and in-person steps. That is useful context for connecting the two experiences. It is neither a forecast for Turkey or Persian-speaking customers nor evidence that a particular button increases sales.

Our recommendation for an independent dealer is to define a useful online-to-sales handoff first. Decide what the buyer should understand before contacting you, what the salesperson should receive and which details the team must confirm personally. Online payment can be a later, separate business decision.

• Research: Cox Automotive's 2025 Car Buyer Journey study

02Our case / Delux

The brief connected vehicle discovery, trust and three languages.

Delux is a car dealership in Istanbul. Our website work connected vehicle browsing, company information, contact and the team's updating workflow. The public interface provides English, Persian and Turkish language controls, links to the vehicle directory and routes to WhatsApp, contact and selling a car.

The important design question was what a Persian-speaking customer needed to understand before contacting an Istanbul business. Vehicle information and the explanation of the dealer's process belong in the same journey. The existing case study describes the delivered work; it does not report a measured increase in leads or sales.

The capture below shows the current directory controls. We checked the public page for this guide and keep its observed state separate from what the implementation is designed to support. No vehicle-specific live inquiry was exercised because no cars were displayed during this inspection.

• Inspect Delux's current vehicle directory

03Specify the stock record

A vehicle needs one identity across cards, detail pages and inquiries.

Before drawing cards, agree on the data each real vehicle will have. A model name is not enough when several cars share that name. Use a stable stock reference and keep the page, photographs, condition information and inquiry associated with it. Decide who can publish, correct, reserve and retire a record.

This is a proposed content specification for a small dealership. It should be adjusted to the dealer's actual stock and disclosures. Unknown condition or pricing information should remain explicitly unconfirmed; a blank field must not silently become a reassuring claim.

04External examples / Shortlisting

Borrow the reason a filter exists; size the interface for your stock.

CarMax's inventory exposes structured details such as mileage, price and stock identifiers alongside search and filtering. Porsche Finder gives visitors model-series entry points and distinguishes new, pre-owned and approved stock. These are observable approaches to shortlisting, not evidence of their conversion performance.

For a dealer with a small selection, readable vehicle cards and a few useful filters may do the job. A huge empty filter panel creates choices the inventory cannot answer. Start from the questions the sales team actually receives, then choose brand, body type, budget or other supported criteria.

Test the no-match state as carefully as a full result set. Show active filters and a clear way to remove them. A buyer should be able to return from a vehicle detail page without rebuilding the shortlist. Certification, warranty and finance statements on another dealer's site cannot be imported into your offer.

• Example: CarMax's vehicle directory
• Example: Porsche Finder GB

05The vehicle detail page

Photographs and facts should describe this car, not a generic model.

A useful detail page answers the questions a listing card cannot. Show the actual vehicle from consistent exterior and interior angles. Add close views where they clarify relevant details. Keep the stock reference, year, mileage, price state and location understandable without requiring someone to open every photograph.

Separate equipment from condition. A feature list explains what the model offers; inspection information explains what is known about this particular vehicle. If a report can be shared, make its meaning and date clear. Do not use a generic inspection badge as a substitute for the records the business can actually provide.

Give the buyer a practical next action: ask about this vehicle, confirm availability or arrange a visit. An installment illustration needs the dealer's own verified terms and assumptions. If those are not available, invite a conversation about terms instead of inventing an attractive monthly figure.

06The sales handoff

The salesperson should know which vehicle started the conversation.

A general WhatsApp button is useful on the homepage. On a vehicle page, a more useful handoff prepares the vehicle name, reference and page link. The buyer can add a question rather than explaining which car they saw. Delux's implementation includes vehicle-specific messages for price, reservation and similar-vehicle requests; this is delivered behavior, not a measured sales result.

Make the action's meaning clear. Opening WhatsApp or preparing a message does not mean the buyer sent it. A reservation inquiry does not mean the vehicle has been reserved. Confirmation belongs to the business process that actually accepts the request.

For an on-site form, ask what the first reply needs and label every control. W3C's form guidance explains how labels are associated with controls. Test contact using fixtures or a staging inbox so development checks do not become fake customer leads.

• Accessibility reference: W3C on form labels

07Current observation / The updating state

A catalogue needs a useful answer when it cannot show vehicles.

When we inspected Delux's public vehicle directory on 25 October 2026, it finished loading with no cars displayed and a message saying the online inventory was being updated. It offered a direct WhatsApp route to ask about today's stock. The screenshot records that state. It does not establish that the business had no vehicles, and it does not diagnose why the directory showed none.

The transferable lesson is to distinguish an updating catalogue, no filter matches, a sold vehicle and a technical failure. Each needs different language and a useful next step. A buyer should never have to guess whether an empty grid means there is nothing to buy.

Give someone operational ownership of these states. Agree how a sale changes the public record, who checks incoming stock and how the website behaves if an update is delayed. A polished launch cannot replace that daily responsibility.

• Source: the public Delux inventory page

08A multilingual dealership

Keep the stock facts consistent even when the explanations change language.

Persian, Turkish and English content can explain the process differently while referring to the same vehicle. Store the stock reference, status, price and photographs consistently. Translate the explanation, labels and relevant process information. Do not let a sold car remain available in one language because someone forgot a second record.

For a new multilingual implementation, our recommendation is stable language URLs with links between equivalent pages. Google's documentation explains how to identify localized equivalents. This is independent implementation guidance: seeing Delux's language controls does not by itself prove that every language has a separate production URL.

On a Persian page, test mixed Latin model names, numbers, currencies and telephone links on a phone. The language switch should retain useful context where an equivalent exists. A visitor comparing a specific car should not unexpectedly return to an unrelated homepage.

• Technical reference: Google's localized-page guidance

09An owner's release test

Try the journey with real stock and awkward states.

Before approving a dealership website, ask the person who will maintain it to run these tasks on a phone. Record what they could complete, where they needed help and what the sales team actually received. This is a proposed acceptance exercise, not a claim that these tasks were user-tested for this article.

• Publish one real vehicle with its reference, photographs and confirmed facts; correct a mistake without changing its identity.
• Find it through an appropriate filter, open its page and return to the shortlist.
• Prepare an inquiry about that vehicle and verify that its reference survives the handoff without sending a production test lead.
• Mark it reserved or sold and check the card, detail page and language versions.
• Try a no-match filter, an updating catalogue and an unavailable detail link; each should explain what to do next.
• Use keyboard navigation and check readable labels, contact links and image loading on a narrow screen.

10Scope and learning

Buy the operating basics first, then investigate what buyers still need.

A focused first release can include maintained stock records, useful detail pages, genuine business/process information, clear contact, an updating workflow and the languages the team can support. Cost grows with stock feeds, multiple branches, different staff permissions, finance integrations and the amount of content that must stay synchronized. A price estimate needs those decisions, not just a page count.

To judge whether the site helps, connect website observations to the sales team's records. A stock-page visit, a WhatsApp click, a received message, a useful sales conversation, an appointment and a completed sale are different events. Count them separately. Ask which information was missing when a relevant buyer called.

We have not published attributable commercial results for Delux. The work and examples here support practical design decisions; the effect of a future change still needs to be measured. You can use the content specification and release tasks above with your current supplier, your own team or a new project.