The industry already solved half of this
The aftermarket has encoded fitment for years. ACES ties a brand's part number and part type to a vehicle configuration, with qualifiers, a note, a position and a quantity. PIES describes the item.
Both are maintained by the Auto Care Association. ACES 5.0 and PIES 8.0 took effect on March 26, 2026. Marketplaces ingest them directly. Walmart's intake requires the brand ID, the manufacturer part number and a part-type ID.
Our read: nobody should rebuild this. The question is what survives the trip from the file to an AI answer.
What gets lost
The note. Free-text notes (“exc. HD brakes”, “w/ 2-piece rotor”) are a known problem. Auto Care's own conference material is about moving them into coded qualifiers to cut “the ‘did you mean’, interpretation of what was written”. A language model paraphrasing a note is exactly that interpretation.
The page. schema.org's isAccessoryOrSparePartFor points from one product to another. It cannot carry a vehicle configuration with qualifiers, position and quantity. If the application list lives only behind a vehicle selector, a crawler sees nothing.
The source. A marketplace fit badge matches against “part compatibility information within the listing”. Which file, which version and which date aren't shown to the buyer or an agent.
Today. Fitment lives in the catalog. Same-day stock lives in hubs and stores. Nothing standard joins the two for an assistant.
Fitment answers need different wording
“This will fit” is a promise only the seller can make. What an assistant can say is “the manufacturer lists this part for the 2021 F-150 3.5L, front, one set, per its ACES file dated September 30, with this condition: ‘Exc. Heavy Duty Payload Package’.” When the applications split on drive or brake package and the buyer hasn't said which, it asks. When nothing is listed, it says so, and doesn't call that “doesn't fit”.
An honest fitment answer names its source, its date and its condition.
Who's building
CarParts.com's assistant is described in a MACH Alliance case study as reachable through an MCP server, with fitment-check and VIN-decode tools. Algolia launched ACES/PIES-aware search in March. Partly is reported to have raised $50 million to build parts-data infrastructure.
The large sellers are covered. The brands and independent sellers whose part numbers the assistants talk about mostly aren't.
What we're building
Lehvel reads a parts business's own ACES and PIES data as sources and returns fitment with its source, its conditions word for word, and its date. It joins that with store availability when there's a current reading, and offers one request a person answers. It also checks what ChatGPT, Claude, Gemini and Perplexity say about the business's part numbers, including on vehicles the parts aren't listed for.