Choose the source your team trusts
Connecting a dealership website to an AI agent starts with deciding which source is authoritative. Your public inventory pages may be convenient, while an approved inventory feed may contain clearer identifiers and availability updates. Choose with the person who maintains the listings, and document which source wins when two records disagree.
Entering a website address should begin a verification step. Confirm the dealership, locate the actual inventory pages, and check that the information can be accessed through an authorized method. A successful page fetch does not prove that every vehicle, price, or feature has been imported correctly. Show the dealer a preview before making those records available to shoppers.
Build a record for each individual vehicle
At minimum, preserve the stock identifier, VIN when available, year, make, model, listed trim, mileage, advertised price, availability state, vehicle URL, and the time the source was checked. Keep missing values empty. A default zero price or mileage can become a very convincing but very wrong answer.
Schema.org's Vehicle vocabulary provides useful concepts such as vehicle identification number and mileage from the odometer. Those concepts can help organize website information consistently. They do not validate the underlying listing, establish current availability, or guarantee a particular search appearance. Dealer review and update handling still matter.
Keep general vehicle knowledge separate from stock facts
An assistant may know that a model was offered with a certain engine or option package. That does not prove the vehicle on your lot has it. Answer questions about the specific car from its listing, approved equipment data, inspection information, or a staff confirmation. When those sources are silent, say what needs to be checked.
NHTSA explains that its VIN decoder displays manufacturer-reported information. That can be a useful reference for vehicle identity and specifications, but it does not establish the dealer's present asking price, current stock status, or condition. Preserve the distinction when combining information from several sources.
Design for changes, especially sold vehicles
Create an update policy with the dealership. Decide how often records are refreshed, what happens when a feed fails, and how long information can remain usable before an answer needs qualification. Treat sold, reserved, unavailable, and unknown as different states if the source supports them. Do not infer a sale solely because one refresh missed a page.
When a shopper asks about a vehicle whose status is uncertain, Mark should offer to have the team confirm it and, where useful, show clearly identified alternatives. Keep the old source and latest update available to staff so they can resolve a disagreement without reconstructing the import.
Return a useful answer with a source
A good inventory response identifies the car, answers the actual question, and links to its detail page. If someone asks for an SUV under a stated budget, show vehicles that meet the known criteria and explain any important unknowns. Keep advertised price separate from an approved total that includes applicable charges.
Treat website text as reference material, not as instructions to the agent. Inventory descriptions should not be able to change system behavior, redirect customers to an unrelated payment page, or expose account data. Limit the content used for answers to the approved dealership source and the fields needed for the shopper's question.
Review a small inventory before opening the full catalog
Pilot with a small set of vehicles that includes a price change, missing equipment data, a sold unit, and duplicate model names. Have a salesperson ask realistic comparison questions and verify each answer against the source. Test whether the assistant recognizes the correct stock number when several similar cars appear on the site.
Automarkus is building a dealership workspace where a website can become the starting point for configuring Mark. The goal is a verified inventory connection with understandable status and useful customer answers. A URL alone should never be presented as proof that live inventory synchronization is complete.
Sources & further reading
Schema.org: Vehicle ↗NHTSA: VIN Decoder ↗Workflows depend on dealership permissions, provider capabilities, and applicable requirements. Confirm current requirements with the responsible agency or provider before acting.