How to manage Cars.com, CarGurus and other marketplace listings from one place

A used-car store that advertises on Cars.com, CarGurus, a couple of other marketplaces and its own website is not running one listing per car. It is running five or six, and every one of them is a copy that can go stale. The price you dropped on Monday is still the old price somewhere. The photos you reshot after detail are on your website and nowhere else. The truck that sold on Saturday is still pulling calls on Wednesday.

None of that is a marketplace problem. It is a copying problem, and it has a structural fix: one record per vehicle, with everything else reading from it.

Why listings drift

Edits happen wherever someone is logged in. A manager reprices a unit inside one marketplace's dealer portal because that is the screen in front of them. The other sites never hear about it.

Photos arrive in stages. A car goes up with lot photos, then gets reshot after reconditioning. The new set lands on one site and the old set stays on the rest.

Sold units come down by hand. Somebody has to take the car off every site the day it sells, and that job loses to a busy Saturday.

Descriptions are written once, for one site. Then they are pasted, trimmed or skipped everywhere else.

Each costs you differently. A stale price looks careless, or worse, like advertising one number and selling at another. Old photos undersell a car you paid to recondition. And a sold unit still listed can cost you the most: a shopper who came for a specific car and found it gone has made a wasted trip, and it was your store they called.

Make the inventory record the single source of truth

The fix is a rule before it is a tool: every change to a vehicle is made in one place, and every site that shows the vehicle reads from that place.

In practice, the inventory record holds the VIN, the photos, the price, the description and the status, and nobody edits a listing directly on a marketplace. Whatever software you use to manage listings across multiple car portals, judge it by whether it keeps that rule for you. Treat a marketplace portal as a place to read reports, not to maintain inventory: an edit made there does not carry to your other sites, and depending on the marketplace it may be overwritten the next time your own data is sent.

In DealersCloud, one record per vehicle carries the VIN decode, the photos, the price and the feeds, from the day it lands to the day it sells. That record lives in the inventory module, and the DealersCloud dealer website reads the same live inventory instead of keeping a separate catalogue.

What an inventory feed is, and what "real-time" means

An inventory feed is an automated export of your live inventory to marketplaces and listing sites: one record, carried out to several sites without being entered several times. A feed that lists a car well but does not carry the price change, the new photos or the sold status afterwards has solved only the easy half.

A feed sold as "real-time" runs on two clocks: how often your system sends your inventory, and how often each marketplace picks it up and refreshes your listings. A change is live everywhere only once both have run, and the second clock is set by each marketplace, not by you.

In DealersCloud, marketing feeds to Cars.com, CarGurus and other marketplaces are included with every plan, and inventory feed setup is part of system configuration during onboarding. Change the price in one place and the listings follow. How inventory feeds work in DealersCloud lists the marketplaces they reach.

Photos and descriptions

A feed makes merchandising quality visible. Whatever is missing from the record is missing everywhere: a unit with two photos and no description goes out that way to every marketplace at once, so descriptions belong to whoever owns inventory, not to marketing.

For photos, pick a consistent lead photo, such as a front three-quarter view, and shoot every unit the same way. When a car is reshot after reconditioning, replace the set on the record, not on one site.

For descriptions, the hard part is not writing one. It is writing one for every unit, every week. The AI description generator is included with every DealersCloud plan. Dealership text you set once, such as a warranty offer, an about-us story, a financing note or a disclaimer, can be added word for word to every AI-written description, so the AI never rewords your terms.

Whatever writes it, read a sample each week. A description is advertising, and it has to be true of the car it is attached to.

Keep prices consistent across sites

A shopper who sees one car at two prices on two sites starts to wonder which one is real, or calls to ask why. Three habits prevent it:

• One price, on the record. If one site gets a different number for a deliberate reason, make it a written decision, not the leftover of an edit nobody carried across.
• Reprice on a schedule. Price changes driven by your aging report happen on a fixed day, on the record, and flow out from there. That also makes "days since the last price change" a number you can trust.
• Know what an advertised price has to include. Which fees belong in it is a question for your compliance advisor, and check each marketplace's own dealer help pages, or ask your account representative, for what it expects in its price fields.

Take sold units down everywhere

Decide, as a store, when a unit stops being advertised: when a deposit is taken, when the deal is signed or when the car is delivered. Then make that status change on the record one named person's job, on the day it happens. A feed can only carry a status somebody has entered.

Then check. Once a week, take three units that sold in the last few days and search for each one on every marketplace. A unit that is still live means a status that was never changed or a marketplace that has not refreshed, and both are better found before a customer finds them.

The same logic applies to anything that answers shoppers on your behalf. DealersAI is the AI module of DealersCloud: it answers every lead instantly by text, email and web chat, 24/7, answers the phone when staff can't, and runs inside DealersCloud or alongside a dealer's existing DMS. It replies from live inventory, which is exactly why the inventory record has to be right.

Bring every marketplace lead into one CRM queue

Feeds are half the job. The other half is what comes back: if each marketplace's leads land in its own inbox or its own portal, you are back to working five systems.

The target is one queue. In DealersCloud, leads from the marketplaces land in the same CRM queue as leads from your website, the phone and the lot, with every email and text kept on the customer record. That queue lives in the dealer CRM. Whatever system runs it, two habits make a lead queue trustworthy:

• Lead source on every record. Lead source is the attribution that says which marketplace produced the opportunity. It is only as good as the capture, since leads re-typed by hand lose it quickly, and it is most useful tracked all the way to a sold deal and its gross rather than stopping at a lead count.
• Obvious duplicates merged. The same shopper often asks about the same car on two sites. DealersCloud has an optional auto-merge setting that combines obvious duplicate leads with the same phone and email, and every merge it makes can be undone.

Check each marketplace's own rules

Every marketplace sets its own rules for dealer listings, and those rules change. Before you rely on a feed or change how you list, read the current rules on each marketplace's own dealer help pages, or ask your account representative. For each one, confirm:

• Which photos it accepts, and how many.
• Which price fields it shows, and what it expects an advertised price to include.
• What happens to a unit that stops appearing in your feed, and how long that takes.
• How its leads are delivered, so they reach your CRM rather than an inbox nobody watches.
• Whether it takes a feed at all. Not every place a car can be advertised accepts one, and a site where cars are posted by hand needs its own removal routine.

Write the answers down next to the account login. Nobody remembers them six months later, and a short weekly check against them costs less than one customer who drove in for a car that sold on Saturday.