INDUSTRY FIELD GUIDE
Auto parts fitment data for testing AI catalog assistants
A catalog recommendation can look right when it matches the vehicle name but misses the engine, trim or installation position.
NAICS 441330 · Automotive Parts and Accessories Retailers
A catalog recommendation can look right when it matches the vehicle name but misses the engine, trim or installation position. The Auto Care Association distinguishes fitment information from product information through ACES and PIES. These standards make a useful basis for specifying an evaluation. They do not establish that a buyer is seeking a store’s order history. Auto Care Association standards FAQ · PIES overview
Keep the unanswered fitment question in the example
Use fictional vehicle variants and authorized product descriptions. Supply the customer request, available fitment conditions and two similar products. For one case, the assistant should identify the compatible option. For the other, it should ask which engine or installation position applies. Include the reason a plausible part is wrong and the reference that proves it. Keep the decision date and product reference version so a superseded part can be evaluated correctly.
Clear catalog access before sharing records
Manufacturer and catalog feeds may have license restrictions. Keep actual VINs, vehicle registrations, customer orders, addresses and pricing history outside the first sample. Use fabricated identifiers and a written scope before any real export. A qualified person remains responsible for an actual fitment or safety decision.
Describe the fitment ambiguity and the proof a reviewer can inspect. Describe a dataset
Original Fiund exercise
Vehicle name alone cannot distinguish engine and installation-position conditions
An original fitment fixture uses fictional vehicles, inert part aliases and no installation instructions. It contains no actual VIN, catalog feed, customer or safety recommendation.
| Record | Source | What it records |
|---|---|---|
| PFI1 | Practice fitment table v2 | Vehicle V/year Y: part P-A supports engine E1/front only; part P-B supports engine E2/rear only. Same family display name. |
| PFI2 | Request A | V/Y, engine E1, front position. Requested decision date falls within v2's stated interval. |
| PFI3 | Request B and old reference | V/Y with engine and position absent. Superseded v1 broadly says P-A for V but is explicitly replaced by v2; no exception supplied. |
Question for the model
Which part matches A under the supplied table, and can B be answered from vehicle name or the older broad reference?
Show the reference answer and checks
PFI1 and PFI2 match A to P-A through vehicle, year, E1 engine and front position. P-A's shared family name does not make it fit E2/rear. PFI3 omits B's engine and position, and its broad v1 entry is superseded. Request those missing conditions rather than choose a part from name alone. This fictional table checks evidence retrieval and does not determine real-world compatibility, installation or safety.
- Ignoring engine or position conditions after matching the vehicle name.
- Using a superseded broad fitment row to avoid asking for missing variant information.
Fields to preserve
- Vehicle, year, engine and position
- Defines applicability.
- Part and fitment-reference version
- Preserves the source.
- Missing condition and wrong-option reason
- Makes uncertainty useful.
Test another case
Change A to E1/rear, a combination absent from the table. Require no supported option instead of extrapolating either neighboring row.
Use fictional tables and authorized descriptions. Exclude VINs and licensed feeds; qualified staff retain actual fitment decisions.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.