Mileage Edge Cases: Odometer Replacements and Exempt Units
Replaced odometers, TMU, and exempt units break a simple mileage field. How to handle mileage edge cases on Marketplace without guessing a number you cannot support.
The odometer on a 2004 work truck reads 42,310. The cluster was replaced last year after a failure. The jacket has a note. The DMS still shows 198,000 from the last appraisal before the swap. A rep posts 42,310 because "that's what it says on the dash." Another rep on a different day posts 198,000 because "that's what we have in the computer." Both numbers are on paper. Only one can be the advertised mileage, and neither may be the whole truth without a disclosure.
Mileage edge cases — odometer replacements and exempt units — are where a clean integer field meets a messy history. Marketplace wants a number. Some vehicles do not have a number you can stand behind without context. Guessing to fill the box is how you create advertising and title problems, wasted visits, and Messenger threads you cannot win.
This article is operational guidance for used-car managers and internet directors. Odometer law is regulated and varies by jurisdiction. This is not legal advice. Confirm disclosures, exempt categories, and branding with counsel or your state regulator. Check current Meta commerce policies and Marketplace rules for how mileage is expected to appear in listings.
Why Mileage Edge Cases Break Ordinary Listings
Most units are simple: read the dash, enter the number, photograph the cluster. Edge cases fail that routine.
The field implies certainty
A mileage box filled with 42,310 reads as "this vehicle has 42,310 miles." If the true history is TMU, cluster replacement, or exempt, the integer without context is the problem. Buyers, and often your own paperwork, will treat the field as the odometer statement.
Common sources of a bad number
- Cluster replacement with or without a programmed reading.
- Five-digit mechanical odometers that rolled, or were replaced, on older trucks.
- Instrument work in recon that was not written back to the DMS.
- Exempt or TMU titles still carrying an old appraisal miles figure in the export.
- Rounding "to make the ad look cleaner." Do not round down. Do not round at all.
Why VIN Accuracy Decides Whether Your Marketplace Listings Perform is the identity layer. Mileage is the usage layer. Both have to match the vehicle and the jacket.
High miles vs. unknown miles are different problems
A true 220,000-mile truck with a working original cluster is a merchandising problem. Unknown miles is a disclosure problem. Do not solve unknown miles by picking a flattering number. For honest high-mile copy when the reading is known, see Writing Descriptions for High-Mileage Vehicles.
Mileage Edge Cases: Odometer Replacements and Exempt Units
Handle each class with a written rule. Do not improvise in the Facebook form.
1. Working original odometer (the default)
- Enter the current reading as shown.
- Photograph the cluster in a way that is readable. Photographing the Odometer and Dash Without Glare covers the shot.
- Update the DMS when you post if the export is stale. A two-week-old miles figure on a driven lot car is already a lie.
2. Replaced odometer, reading known and documented
When a cluster was replaced and your records state the mileage at replacement plus miles since, you may have a supportable advertised number. That support lives in the jacket, not in memory.
Operational checklist:
- Find the replacement invoice, odometer statement, or title brand/notes.
- Confirm whether the new cluster was set to the old reading or started at zero.
- Do not advertise the new cluster's raw reading if it reset to zero and the true accumulated miles are higher.
- Put the advertised number only if it matches what you will put on sale documents.
- State in the description that the cluster was replaced and point to the documentation you will show on site.
If you cannot complete those steps, treat the unit as unknown miles until a manager and compliance resource say otherwise. Do not "split the difference" between old and new readings.
3. True mileage unknown (TMU) and similar brands
When the title or your compliance process says mileage is unknown, do not invent a clean integer to satisfy the form.
- If the form requires a number, follow counsel's process for your store. Some desks use the reading on the dash plus a TMU statement; some cannot advertise a number at all. This article will not pick a number for you.
- The description must say that mileage is not guaranteed as true accumulated miles, in language your attorney has approved.
- Photos of the dash are still useful as "what the cluster shows," labeled as such.
- Price and merchandising should assume a skeptical buyer. TMU is not a rounding error.
4. Exempt units
Some jurisdictions treat certain older vehicles as odometer-exempt. Exempt is a legal category, not a merchandising slogan.
- Do not label a vehicle exempt because it is old and you would rather not deal with miles.
- If it is exempt under your state's rules, follow those rules on paperwork and advertising. Confirm with counsel. This is not legal advice.
- If Marketplace still asks for mileage, enter what your process allows and explain exempt status in the description with approved language.
- Do not use "exempt" to hide a replaced cluster on a non-exempt vehicle.
5. Inoperable clusters and blank screens
If you cannot read miles, you cannot advertise a precise reading. Repair or diagnose before posting when the unit is otherwise retail. If you must list it as-is with a dead cluster, say the odometer is inoperative and do not type a remembered number from an old appraisal unless counsel says that number is still the correct statement.
Description, Photos, and Title Language
The field, the photo, and the paragraph have to tell one story.
Description pattern (illustrative, have counsel review)
- Known replacement: current advertised miles, date or miles at cluster replacement if you have them, that documents are in the jacket.
- TMU: cluster reading if shown, that true accumulated miles are unknown, invite on-site document review.
- Exempt: that the vehicle is treated as exempt under applicable rules, plus whatever miles you are allowed to state.
Do not bury the exception under three paragraphs of options. Put it high enough that a skimming buyer still sees it.
Titles
Putting "low miles" in a title on a replaced-cluster or TMU unit is how you pick a fight. If you use miles in titles at all, use them only on clean original-cluster units.
Photos
- Always shoot the cluster for retail units.
- For replacements, a photo of the cluster plus a photo of any in-car warning or sticker (if present and legitimate) can reduce "what does it actually show?" messages.
- Do not crop out an obvious odometer discrepancy sticker to make the dash look cleaner.
Floor Controls So Edge Cases Do Not Ship
| Control | Owner | Failure if skipped |
|---|---|---|
| Jacket flag for TMU / replacement / exempt | Used-car manager | Rep posts dash reading only |
| Miles in DMS match advertised miles | Inventory clerk | Two numbers in the wild |
| Description template for each edge class | Internet director | Free-text guesses |
| Manager approval before queue | Manager | Associate posts the easy integer |
| Sold/archive when the unit leaves | Anyone who closes | Stale miles remain live |
If a unit is in recon for cluster work, it should stay draft until the reading and the paperwork agree. Posting during the gap is how 42,310 and 198,000 both become public.
How PostToMarket Automates This
Mileage edge cases go public when a stale DMS number or a dash photo is enough to hit Post. The operational need is a vehicle record that can sit in draft, copy you can edit with disclosure language, a photo picker for the cluster, and a queue with a manager in the loop.
PostToMarket will not decide legal odometer language for you. It keeps the unit, the draft, and the photos together so a replacement or TMU flag can be handled before AutoPost. It is not affiliated with Meta.
Keep disputed miles out of the live aisle
- Inventory statuses (draft, posting, posted, sold, failed) so TMU and cluster-replacement units stay draft until approved.
- Bulk import with row-level error logs when miles are blank, non-numeric, or obviously inconsistent.
- Mark as sold and archive so an old miles figure does not keep advertising.
Edit the words that carry the disclosure
- AI-generated descriptions from specs, editable before posting. Insert counsel-approved TMU or replacement language on the edit pass. Do not expect the generator to know a cluster was replaced unless that fact is in the specs you provide.
- Facebook photo picker for a readable odometer frame.
Who is allowed to post the hard units
- Managers assign associates; reps self-queue ordinary units; team queue view to pull back a claim.
- Chrome extension, one at a time, human-like delays, server-enforced daily limits.
- Leads inbox when mileage questions repeat — that is a process smell.
No tool can guarantee that Facebook will distribute a listing, and no tool replaces odometer compliance. The product reduces the operational mistake of posting the easy integer because the form demanded a box.
Do Not Invent Miles to Satisfy a Form
A replaced cluster and an exempt title are not rounding problems. Mileage edge cases — odometer replacements and exempt units — need a jacket flag, a manager, and words that match the paperwork. The Marketplace field should never be more certain than your documents.
PostToMarket gives you draft status, editable copy, photo selection, and role-based queues so those units do not bypass review. Starter is $59 per month for a solo seller with one login. Dealership is $299 per month for up to 13 logins.
Start your 10-day free trial through secure Stripe checkout. Import, hold edge-case units in draft, and post only when miles and the jacket agree. Cancel anytime.