ACES tells the buyer it fits. It never tells them why yours.

A customer enters a 2018 Silverado 1500 in the year/make/model picker and asks for front brake pads. The catalog does its job perfectly: four sets come back, all validated, all genuinely correct for the vehicle. Fitment data worked.

Then the page goes quiet. Nothing on it explains that one set is a low-dust ceramic for a commuter, one is a carbon-metallic built for a truck that tows 9,000 pounds twice a month, one is the value line, and one is the same compound as the value line with a longer warranty. The customer picks the cheapest, tows a trailer in August, cooks the pads, and returns them.

Fitment did not fail. Fitment was never the layer that decides the sale.

Two different jobs, one conflated

The aftermarket built extraordinary infrastructure for the first job. The Auto Care Association's ACES and PIES standards encode vehicle application and product information respectively, sitting on shared reference databases — VCdb for vehicle configurations, PCdb for part terminology, PAdb for product attributes, Qdb for fitment qualifiers — and the association pushed ACES 5.0 and PIES 8.0 in March 2026 with expanded coverage and an API model supporting daily refresh.

This is a genuine achievement and no other distribution vertical has anything as mature. It is also, by design, a compatibility standard. Its question is whether this part is applicable to this vehicle configuration. That question has a right answer, which is exactly why it could be standardized.

The second job has no standard because it has no universal right answer. Which of the four compatible parts should this particular buyer purchase? depends on what the vehicle does, how long they plan to keep it, whether they are doing the work themselves, and what they are optimizing for. That question is merchandising, and it is where the money is.

Data networks in this space distribute the first layer beautifully. Shared aftermarket catalogs hand every member dealer validated ACA fitment, VIN lookup, on-page fit validation, spec blocks, and image links. What they cannot hand over is the second layer, because the second layer is different for your buyer than for the dealer two states away receiving the identical file.

What the second layer actually contains

Merchandising attributes are unglamorous and specific. They are the facts that make one compatible part obviously correct and the other three obviously wrong, for a stated use case:

• Compound and rating fields. Friction compound, low-dust rated, tow/haul rated, load index. All four pad sets fit; only one is rated for the trailer.
• Included and not-included hardware. Does the hub assembly integrate an ABS tone ring. Are longer U-bolts in the box. Is the sensor port present. These are the facts that turn into returns when absent.
• Installation reality. Special tools, press required, book time, re-torque interval at 500 miles. The DIY buyer and the shop are both making a schedule decision, not a parts decision.
• Regulatory status. CARB EO number, 50-state versus 49-state versus off-road-only. In several states this is the entire purchase decision, and it is frequently absent from distributed records.
• Fit under modification. Lift requirement, max tire diameter, backspacing, clearance at stock ride height. ACES describes the factory vehicle. A large share of this industry sells to vehicles that are no longer factory.
• Longevity economics. Warranty term, rebuild kit availability, service interval. The fleet buyer is not comparing prices, they are comparing cost per mile across nine trucks.

Read that list against a typical distributed record and the pattern is consistent: these facts exist, but they exist in an install PDF, in a footnote, in a marketing sentence, or in a forum thread. They do not exist as fields. Anything that is not a field cannot be filtered on, cannot be compared, and cannot be read by a machine.

Why this decides AI visibility, not just conversion

The failure mode used to be a shopper bouncing. Now it is not being cited at all.

Answer engines take a question like "best front brake pads for a 2018 Silverado that tows" and expand it into sub-questions — compound differences, fade resistance, dust, warranty — then compare candidate sources fact by fact rather than ranking whole pages. A catalog with perfect fitment and a generic description has nothing to contribute to that comparison. It is compatible with the vehicle and irrelevant to the question.

Worse, if you and four thousand other dealers published the same network file, you are all equally irrelevant to it, and the model cites whoever added the one paragraph that addressed towing. That is a very cheap thing to lose on.

Fixing it without rebuilding fitment

The order matters, because most catalogs try to fix this by rewriting copy, which is the last step, not the first.

Start from questions, not fields. Pull the site-search queries that return a wall of undifferentiated results. Pull the top ten return reasons by SKU family. Pull the recurring one-star themes. Each is a merchandising attribute your schema is missing, named by the buyer.

Propose the attribute before you fill it. Tow-rated (boolean), friction compound (enum), ABS tone ring integrated (enum), lift required in inches. This is a schema change, and treating it as one is what keeps it from becoming another free-text field that means three things.

Govern the values immediately. Compound should be ceramic | semi-metallic | organic | carbon-metallic and nothing else, across every brand in the catalog, or the facet you just built returns partial results and buyers stop trusting it.

Mine the values from documents you already have. The install manual has the re-torque interval. The submittal has the load rating. The brand's own PDF has the EO number. These are already in your possession, unreadable, attached to the record as links. Extraction is the cheapest fill available and it comes with a citable source.

Then rewrite the copy, so the page leads with the decision the buyer is actually making rather than with superior performance and premium components.

Across a full item file that loop does not scale by hand, which is what Anglera automates — reading the signals that name missing attributes, proposing and governing the fields, mining values out of supplier PDFs with a citation per value, and writing it back to your PIM so the next supplier reissue does not quietly undo it.

Fitment is the price of admission and the aftermarket has solved it about as well as an industry can. It gets your part into the room with three others that fit just as well. Everything that happens after that is merchandising data, and it is still, for most catalogs, missing.