HOME / GUIDES

GUIDE · FITMENT DATA

What is an ACES overlap — and how do you clear them without losing coverage?

An ACES overlap is two or more application records for the same part type that claim the same vehicle — or vehicle configurations a receiver cannot tell apart. The classic case: one record maps a part at the BaseVehicle level (every submodel and engine included) while another record maps a different part to one specific submodel of that same vehicle. For that submodel, two parts now claim the fit, and nothing in the data says which one is right. Receivers flag it, marketplaces suppress it, and the shopper who sees two "fits your vehicle" results either guesses or leaves.

Why clean catalogs still develop overlaps

Almost no supplier sets out to publish conflicting fitment. Overlaps accumulate, usually through growth: a product line gets a Good/Better/Best tier and the new tiers get mapped on top of the old coverage; an acquisition merges two catalogs that each covered the same vehicles their own way; year-range expansions get entered broadly at the BaseVehicle level while the engineering team adds precise submodel records beside them. Each entry looked right on its own. Together they collide.

The most common accelerant is free-text notes. For years, the distinction between two applications lived in a note — "with heavy duty suspension," "from 03/2015," "except turbo." A human reading the catalog sees the difference. A receiver's validator does not read notes. As far as its overlap detection is concerned, the two records claim the same vehicle, and the flag is correct.

What overlaps actually cost a supplier

Overlap flags are not cosmetic. Receivers reject files or quietly suppress the conflicting coverage, which means the vehicles you cataloged hardest — the ones with tiered or position-specific parts — are exactly the ones that stop showing up. On marketplaces, conflicting fitment degrades your listing quality score, and buried listings do not sell. And when a shopper does buy from ambiguous fitment, the part that comes back as a return was often the right part listed the wrong way. We have watched a receiver tell a brand its data was "bad" over conflicts the brand could not even see in its own PIM.

How to clear ACES overlaps without losing coverage

There are only three honest resolutions for an overlapping pair, and the whole craft is choosing the right one per conflict rather than applying one rule to thousands of records.

1. One record is simply wrong. The part never fit that configuration, or the fit ended at a model-year break that the record ignores. The fix is a correction, not a deletion of coverage that was real.

2. Both records are right, and a structured attribute tells them apart. This is the majority. The distinction that lived in a note — submodel, engine, drive type, production date, a qualifier like front vs. rear — gets encoded where validators can read it: as a vehicle attribute reference or a coded qualifier from the qualifier database, not as prose. Once each record claims a distinct configuration, the overlap ceases to exist and the coverage is intact.

3. The granularity is mismatched. A BaseVehicle-level record and a submodel-level record are fighting over the same ground. The broad record gets re-expressed as the set of submodels it truly covers, leaving the specific record its territory.

The one resolution we refuse on principle: deleting applications wholesale until the flags go away. It is the fastest way to a clean validation report and the most expensive, because every deleted application is a vehicle you no longer sell against. When we cleared 61,437 overlap and duplicate flags to zero across a 541,990-application catalog, the brand's coverage count ended where it started — every conflict resolved by correction or differentiation, each one logged row by row, and the result proven with an official Auto Care VIP validation pass.

How to find yours before a receiver does

Group your applications by part type and vehicle, then look for any configuration claimed more than once. A spreadsheet can catch the exact collisions; the subtle ones — BaseVehicle versus submodel granularity, attribute combinations that intersect — need the same logic validators use. If you would rather see the answer than build the tooling, that is literally what our free graded audit returns: your file, a letter grade, and every overlap flag with the records behind it.

Frequently asked questions