A part number is a promise about fitment.
Nobody searches for a brake rotor. They search for a rotor that fits a 2015 Civic — and if your catalogue cannot answer that in a structured way, the part is not ranked badly. It is absent from the lookup entirely.
- part_number
- 2874-XL-BR
- description
- BRAKE ROTOR VENTED FRONT
- brand
- TorqLine
- price
- 84.00
- qty
- 40
- fitment
- not supplied
- pies_attributes
- not supplied
- digital_assets
- not supplied
PIES fields required · disc brake rotor
- Vertical
- Aftermarket parts
- Specimen
- 2874-XL-BR
- Standards
- ACES · PIES
- Classification
- PCdb 1684
- Completeness
- 5 / 47
Five fields is a price list
It tells a distributor what to charge. It cannot tell a mechanic whether the part fits, which is the only question being asked.
"VENTED FRONT" is not an attribute
It is three attributes flattened into a description string: vane type, position, and by implication a rotor class. None are queryable.
No ACES application record
Without year, make, model, engine and sub-model bindings, this part is invisible to every fitment lookup in the aftermarket.
Disc Brake Rotor, Vented, Front
- part_number
- 2874-XL-BR
- description
- BRAKE ROTOR VENTED FRONT
- brand
- TorqLine
- price
- 84.00
- qty
- 40
- fitment
- — not supplied —
- pies_attributes
- — not supplied —
- digital_assets
- — not supplied —
3 of 8 fields empty · none of the empty ones are optional
Five usable fields · no fitment · this part cannot be found by the query that would sell it
5
Fields in the supplier feed as it arrives.
47
Fields a typical receiver requires for this part type.
Two decades old, and most catalogues still fail them.
ACES and PIES are not new, obscure or optional. They are what every receiver in the aftermarket validates against.
ACES describes which vehicles a part fits. Not as prose — as a structured application record binding the part to base vehicle, engine, sub-model, drive type and position.
Every fitment lookup a shopper or counter person uses is reading ACES. A part without application records does not fail to rank; it fails to exist in the lookup entirely.
Year · Make · Model
Trim-level qualifier where fitment differs
Displacement, cylinders, fuel type
Front / Rear / Left / Right
Per-vehicle quantity — 2 for this rotor
Free-text exceptions, used sparingly
Six ways a parts catalogue costs money quietly.
The wrong-part return
A rotor that fits a 2015 Civic but not the Si trim. The sub-model qualifier existed in the manufacturer's data and was lost somewhere between their PDF and your catalogue. The customer fits it, discovers the caliper clearance is wrong, and returns it — with labour.
Invisible in the lookup
You stock the part, it is priced competitively, and it never appears — because a fitment search queries ACES applications and yours has none. This is not a ranking problem, and no amount of SEO addresses it.
Receiver rejection
A distributor's validator requires PIES segments you did not populate for that part type. The feed is rejected wholesale rather than partially, so one bad part type stalls the entire submission.
Quarterly drift
VCdb releases quarterly. New model years appear, configurations get revised. Applications built last year quietly become incomplete, and nothing tells you.
Interchange gaps
You cannot answer "what replaces this discontinued OE number" because supersession was never recorded as a relationship — it lives in a spreadsheet somebody maintains by hand.
Safety values buried
Minimum thickness, torque specs and service intervals sit in manufacturer PDFs. They are the values a professional buyer actually needs and the ones least likely to reach a listing.
Minimum thickness on a brake rotor is a value somebody uses to decide whether a car is safe to drive. It exists in the manufacturer’s documentation and almost never survives the journey into a distributor listing. We treat it as a safety-class attribute — sourced or absent, never inferred from a comparable part.
What the first six weeks actually contain.
Written for the evaluation, not the pitch. The right-hand column is what you have to supply, which is the number that usually kills these projects.
Coverage audit
We measure your current ACES application coverage and PIES completeness against the part types you actually sell, per receiver.
A parts file export · your receiver list · no integration
Fitment resolution
Applications are built from manufacturer documents and validated against the current VCdb release, with confidence per application.
Access to whatever manufacturer PDFs and files you hold
Receiver validation
PIES output is validated against each receiver's required subset in dry-run, so rejections surface before submission rather than after.
One test connection per receiver, read-only
Quarterly re-validation
Every VCdb release triggers re-validation. New configurations extend coverage automatically; revised ones raise a drift event.
Nothing — this is the part that stops being your problem
Note what is not in that list: a taxonomy workshop, a data-governance committee, or a request that your suppliers change how they send files. If a vertical rollout plan opens with reformatting your suppliers, it is not a rollout plan — it is your project with a vendor attached.
How many of your parts have no applications?
Send a parts file. We will measure ACES application coverage and PIES completeness against the receivers you actually sell through, and return the list of part numbers that currently cannot be found by a fitment search — ranked by what you hold in stock.
One parts file · No integration · Coverage report in 10 working days