Fitment data
Fitment editor
Per-SKU additions, exclusions, notes and universal flags.
Supplier data is never perfect and tags go stale. The fitment editor is the overlay that sits on top of every source: it is applied after the union, which is what lets a single exclusion beat a feed that is confidently wrong.
What you can do#
- Add a vehicle
- a fit a source missed. Behaves exactly like a mapping from any other source.
- Exclude a vehicle
- remove a fit a source wrongly claims. Wins over every source, always.
- Flag universal
- cleaner, tools, hardware, anything that fits everything. Never filtered out by a vehicle, never marked as no-fit.
- Attach a note
- per SKU or per SKU-and-vehicle. Shown on the product page and in the fitment table: "Requires trimming", "Not with factory tow package", "Front axle only", "Rubbing at full lock".
Overlays survive everything#
Edits are stored separately from source data and re-applied on every index run. Re-upload a CSV, resync a vendor, change plans — your corrections persist. This is the property that makes the editor safe to use as a daily tool rather than a last resort.
Working through the queue#
The editor lists products by fitment status, so the useful workflow is:
- Filter to no fitment and sort by revenue. Fixing your top sellers first is worth more than fixing everything alphabetically.
- Filter to recently changed after a vendor sync to see what a supplier added or removed.
- Search a SKU directly when support forwards you a complaint.
Every change is timestamped with who made it, so "who said this fits a Rubicon" is answerable.
Bulk edits#
Select multiple SKUs to apply the same addition, exclusion or universal flag in one action — useful when a whole product line shares a platform. Bulk changes are still individual overlays underneath, so they can be undone one SKU at a time.
An exclusion suppresses a claim; it does not fix the source. If a vendor feed keeps re-adding the same wrong vehicles, tell us — an adapter-level fix helps every shop on that supplier, and your exclusion keeps working meanwhile.
When to use the editor versus a source#
| Situation | Use |
|---|---|
| One SKU, a handful of vehicles | Editor |
| A supplier is wrong about a platform | Editor exclusion, then tell us |
| Hundreds of new mappings | CSV or a sheet |
| A note for shoppers | Editor — no other source carries notes as well |
| A whole product line is universal | Editor bulk flag |
Support is answered by the people who wrote this code — not a ticket queue.