Describing Warning Lights and Known Issues in Listings
A dash light in the ad is easier to sell than a dash light in the driveway. How to describe warning lights and known issues in listings so buyers, reps and the desk use the same words.
A buyer pulls up on Saturday with a printed listing. The description says "clean, inspected, ready for the highway." He starts the car. An amber light sits on the dash like it has been there all week. The assigned associate has never seen the car running. The used-car manager now has two jobs: diagnose in public, and explain why the ad did not mention it.
Describing warning lights and known issues in listings is not a confession that kills the deal. It is how you stop the deal from dying in the driveway. Marketplace shoppers treat silence as a clean bill of health. If the light is on, if a window is dead, if the A/C is weak, or if recon left an item open, the listing either waits or it uses the same sentence the desk will use when the buyer arrives.
This article is for GMs, used-car managers, and posting staff. It is operational guidance on wording, placement, and ownership. It is not a diagnostic manual and not legal advice. Disclosure duties and as-is rules vary. Confirm required language with counsel or state regulators, and check current Meta commerce policies on accurate listings.
Describing Warning Lights and Known Issues in Listings: Decide Before You Write
Copy is the last step. The first step is a store decision: repair, hold, or retail with disclosure. Mixing those three in the same paragraph is how you get "minor light, probably nothing" in an ad for a car you have not scanned.
Repair when the cost is smaller than the conversation
Many drivability lights are cheaper to scan and fix than they are to explain for a week of messages. If your retail standard is "no unexplained lights," do not make an exception because the unit has aged. Posting around a light to "see if anyone wants it" trains buyers to negotiate from the screenshot.
Hold when you do not know what the light is
Do not describe a mystery. If nobody has scanned the car, you do not have a known issue. You have an unknown issue, and unknown issues do not belong in public copy. Keep the unit in recon or in draft until you have a code, a technician note, or a written decision to sell it as-is with a specific disclosure.
For the posting-side version of this hold-or-disclose fork, see writing about warning lights and known issues before posting. This article assumes you have already chosen to list the car, and now you need language that will survive an appointment.
Disclose when you will sell the car with the issue
Disclosure is a complete sentence with three parts:
- What the buyer will see or experience.
- What you know about it (scan result, technician note, or "not diagnosed").
- What you are not claiming (no implied repair, no implied warranty).
Example pattern: "Check-engine light is on. Scanned on [date]; code related to [system as written on the printout]. Not repaired. Sold as-is; see buyers guide." If you do not have a scan, you should not be in this branch.
Where the Known-Issue Sentence Belongs
Burying the light in paragraph four, after the option list and the "call today" line, is how you get a wasted drive. Phone shoppers often read two lines.
First two lines, then the details
Lead with identity and the issue:
- Line 1: year, make, model, mileage, price context if you use it.
- Line 2: the known issue in plain language.
Then, later in the body, you can add the scan date, the work you already did, and how to see the printout at the desk. Do not open with "beautiful, loaded, must see" and close with the airbag light.
Title field vs. description vs. photos
- Title: use it for year, make, model, and a fact a searcher needs (mileage band, 4WD). Do not stuff "CHECK ENGINE" into the title as a gimmick, and do not write "perfect" in the title of a car with a light.
- Description: this is where the disclosure lives, early and specific.
- Photos: if your process includes a dash shot, show the cluster with the light in the state a buyer will see at a cold start. A photo of a dark dash taken with the key off is not evidence that the light is off. Photographing the odometer and dash lights accurately is the companion habit.
Chat cannot be the first disclosure
If the listing is silent and the rep "mentions it when they ask," you have not disclosed. You have delayed. Train reps to paste the same sentence from the listing, not a softer version. "It's just a sensor" is a mechanical claim. Leave diagnosis to the printout.
Wording That Holds Up at the Desk
The goal is language a buyer, a tech, and a manager would all recognize as the same fact.
Name the light the way the dash names it
Write "check-engine light," "ABS light," "airbag light," "tire-pressure light," or "maintenance required" as the cluster labels it. Do not write "the dummy light" or "a little amber light." Do not translate a light into a repair you have not done ("needs a gas cap").
Separate known from unknown
| Situation | Weak line | Stronger line |
|---|---|---|
| Light on, scanned, not repaired | Runs great, small light | CEL on; scan dated [date]; not repaired |
| Window inop | Minor cosmetic | Passenger rear window does not go down |
| A/C weak | Ice-cold A/C | A/C cools but not to our retail standard; not repaired |
| Noise on test drive | Solid drivetrain | Light tick on cold start; went away after warm-up; not diagnosed further |
| Incomplete recon | Needs nothing | Front brakes remaining; awaiting pads; not yet retail-ready |
If you cannot fill the "stronger line" from a sheet in the jacket, you are not ready to describe the issue. You are ready to hold the unit.
Do not offset the issue with a superlative
"Check engine on but this truck is a beast" asks the buyer to ignore the first half. "Needs a little work but nothing major" is a conclusion. Pair the disclosure with facts you can support: recent tires, a documented timing-belt service, a clean title. Let the buyer weigh those facts. Do not weigh them in the same sentence as the light.
Align as-is or warranty language with as-is vs warranty disclosure in online listings so the known-issue paragraph does not accidentally sound like a promise to fix it after the sale.
Describing Warning Lights and Known Issues the Same Way on Every Rep's Script
Inconsistency is how a good disclosure dies. One associate says "we disclosed it." Another says "we can probably take care of that." The buyer has both messages.
One owner of the condition note
- Recon or the used-car manager writes the canonical sentence.
- That sentence lives on the inventory record, not in a private chat.
- Posting staff copy it. They do not improve it.
- If the light is repaired, the sentence is deleted and the listing is updated the same day. A stale disclosure is as bad as a missing one.
A short checklist before the post goes live
- Is there an open light or known defect on the recon sheet?
- If yes, is the canonical sentence in the first two lines?
- Does any other sentence contradict it ("no issues," "highway ready")?
- Does the dash photo match the current state of the cluster?
- Does the buyers guide and as-is language match the listing?
If item 3 fails, rewrite. "No issues" and "CEL on" cannot share a description.
After the appointment, close the loop
If the buyer still feels surprised, the listing failed even if the sentence was technically present. Review whether it was too low, too vague, or contradicted by the title. Then fix the template, not just that one unit.
How PostToMarket Automates This
Known-issue language fails when it lives in someone's head: the tech told a manager, the manager told a rep, and the associate who posted used last week's template. You need the condition note attached to the vehicle, the copy edited before it posts, and a queue owner who can be asked why the light was or was not mentioned.
- AI-generated descriptions from the vehicle's specs give a unique draft. Your edit pass is where the known-issue sentence goes, in the same place on every unit, instead of a cloned "runs great" block.
- Edit before posting so "no issues" cannot ship on a car with a light. The draft status exists for that review.
- Inventory statuses (draft, posting, posted, sold, failed) keep unscanned units in draft until recon writes the sentence or clears the light.
- Manager assignment and per-rep queues put disclosure-sensitive units with people who have seen the car, not with whoever is free.
- Team queue view lets a manager release a claim if the assigned person is about to post around an open work order.
- Facebook photo picker so a current dash or defect photo can lead, rather than a beauty shot that implies a finished car.
PostToMarket is independent and is not affiliated with, endorsed by, or sponsored by Meta. No tool can guarantee a listing will be received as complete disclosure. The workflow reduces the operational mistakes that leave lights and defects out of the ad.
Get Known Issues Out of the Driveway Argument
Every unexplained light on a live listing is a future Saturday you will spend negotiating from a screenshot. Describing warning lights and known issues in listings up front, in the same words the desk will use, is cheaper than diagnosing in the driveway.
PostToMarket gives you unlimited inventory, AI drafts you can edit, bulk import with row-level errors, and queues so the person who knows the car owns the post. The Starter plan is $59 per month for one login. The Dealership plan is $299 per month for up to 13 team logins.
Start your 10-day free trial with secure Stripe checkout. Load the units that currently have open issues, put the canonical sentences in the drafts, and post only what you are willing to defend in the driveway. Cancel anytime.