Claude for Dealers / Learn / AI for Used Car Managers
Variable Ops · Used Car Desk
AI for Used Car Managers: Descriptions, Aging Reports, and Appraisal Prep with Claude
Your inventory export already holds the answers. The problem is that nobody has two hours on Monday to read 180 rows and decide what to do about each one.
Attached: inventory export, 184 units. Build my Monday list. Rules are in the project.
| Stock | Unit | Days | Issue | Action |
|---|---|---|---|---|
| P4412 | 2021 Tahoe LT | 67 | No price change in 30 days | Reprice or wholesale decision today |
| P4533 | 2022 CR-V EX | 41 | 9 photos | Reshoot. Store standard is 30 |
| P4570 | 2020 F-150 XLT | 12 | Still in recon | Chase body shop. Day 12 of 5 |
| P4581 | 2023 Camry SE | 6 | Clean | None |
Used car managers use Claude for five jobs: writing accurate vehicle descriptions from build data, turning the inventory export into a prioritized aging action list, preparing appraisal summaries, chasing recon bottlenecks, and checking listings for missing photos, prices, and comments. Claude does not know what a car is worth. Market values must come from your pricing tool, and features must come from the build data.
- Best first project: the Monday aging action list
- Input: the inventory CSV you already export
- Descriptions use build data only. No invented features
- Market pricing comes from your pricing tool, never from Claude
- Plan needed: Claude Pro or higher
- Works with any inventory system that exports a spreadsheet
Where AI fits on the used car desk
Buying and pricing cars is judgment. Claude does not replace it. What Claude removes is the reading, sorting, and writing that sits around that judgment: the descriptions nobody has time to write well, the aging report nobody has time to study, and the recon spreadsheet nobody updates.
Job 1: Vehicle descriptions that are accurate
Generic AI descriptions are easy to spot. "This stunning SUV is ready for your next adventure." They also create risk when the tool invents a feature the car does not have.
The fix is a description Skill with two rules. First, features come only from the build data or window sticker you paste in. If it is not in the data, it does not get written. Second, your store voice comes from a knowledge file, so 184 descriptions sound like one store.
Write the vehicle description for the unit below. Use ONLY the features listed in the build data. If a feature is not listed, do not mention it. Lead with the three things a shopper for this model cares about most. No cliches. No "stunning," "loaded," or "won't last." 120 words. End with one line on our reconditioning standard from the knowledge file. BUILD DATA: [paste]
Job 2: The Monday aging action list
Export inventory. Give it to Claude with your rules. Get back a short list of the units that need a decision, sorted by urgency, with the reason next to each one.
The rules are the whole game. Write them down once:
- Photo minimum. For example, flag any unit with fewer than 30 photos after day 3.
- Reprice cadence. Flag any unit with no price change in the window your policy sets.
- Recon target. Flag any unit in recon past your target days.
- Exit policy. At your day limit, the list asks for a retail or wholesale decision.
- Missing data. No price, no comments, no VIN decode, stock photos.
Job 3: Appraisal prep
Before the appraiser walks the car, Claude can assemble what you already have into one summary: the history report you paste in, service history from your own RO export, your current stock of the same model with days on lot, and your recent sales of that model. It does not produce a number. It produces the page the appraiser reads so the number is better informed.
Job 4: Recon chase
Paste the recon tracker. Ask for a list by vendor and stage with days in stage. Claude drafts the chase message to the body shop or the detail vendor. One minute instead of fifteen, every morning.
Job 5: Merchandising QA
Give Claude the listing export and ask it to find problems: descriptions that mention a feature not in the build data, prices that differ between feeds, duplicate stock numbers, units with a sold status still listed. It reads every row. People skim.
- 01ExportInventory CSV from your system
- 02RulesYour turn policy in a project file
- 03ClaudeReads every row, applies every rule
- 04Action list10 to 20 units that need a decision
- 05You decideReprice, reshoot, chase, or wholesale
What Claude cannot do here
- Apply your written rules to every unit
- Write from build data
- Summarize history you provide
- Draft vendor chase messages
- Catch listing errors
- Guess a market value
- Invent features or packages
- Decide what to pay at auction
- Publish descriptions with no human read
- Replace your pricing tool
If you ask Claude what a 2021 Tahoe is worth, it will give you an answer that sounds confident and is not grounded in today's market. Bring the market data to it. Do not ask it to be the market data.
Common questions
Can Claude price my used cars?
No. Claude has no live market feed. Use your pricing tool for market values and bring that export into Claude if you want it included in the action list. Claude applies your rules to your data. It does not supply the market.
How do I stop AI descriptions from inventing features?
Make it a hard rule in the Skill: use only features present in the pasted build data, and if a feature is not listed, do not mention it. Then spot check ten descriptions a week against the window sticker.
What file format does Claude need for inventory?
A CSV or Excel export works. Include stock number, VIN, year, make, model, trim, days in stock, price, last price change date, photo count, and status. More columns are fine.
Can this run automatically every morning?
It can once the manual version is trusted. Start by running it by hand for two weeks. Then look at building it into an agent with a daily deliverable.
Does this work for new car inventory too?
Yes. The aging and QA jobs work the same way. Descriptions matter less on new, and allocation and incentive rules matter more, so the rule set changes.
Build Your Inventory Skills Live
Bring an export. Leave with a working action list. We are back in Atlanta January 5, 6, and 7, 2027.
Register Now →