Brake pad product attributes

Brake pads are easy to mismatch because many pads that look nearly identical differ by a few millimetres, a sensor tab or a clip. The FMSI shape number gives a common reference for the pad outline, but it says nothing about friction compound, hardware, shims or whether a wear sensor is in the box. Those details usually sit on the carton, the edge of the pad or a separate spec sheet.

Friction data is the next layer. Suppliers describe compounds as ceramic, semi-metallic or low-metallic with no shared definition, while the edge code stamped on the pad carries a standardized SAE J866 friction classification. Regulatory data adds more fields: copper content levels under the LeafMark scheme matter for sales in some US states, and ECE R90 approval matters for European markets.

Axle position and set quantity round out the record. A pad set normally covers one axle, but vehicles with different front and rear calipers, or with performance and heavy-duty brake packages, can take several pad shapes on the same model. Storing position, pieces per set and fitment qualifiers as structured fields is what lets a counter rep quote the right set the first time.

The brake pads attribute template

18 candidate fields in 5 groups, ordered the way a record gets built: identify the item, capture its specifications, then record fit and the evidence behind any claim. 10 are marked Core: without them the item cannot be identified or filtered. Example values show the expected format only; they do not describe a real SKU.

Identity

Which exact item, variant and pack this record describes.

Check before use: Preserve leading zeros and punctuation, validate against the manufacturer record, and check the GTIN check digit and packaging level before linking.

Attribute	Type	Priority	Example format
FMSI Number fmsi_number	Identifier	Core	D1210
Manufacturer Part Number manufacturer_part_number	Identifier	Core	BP-1210C
Pieces per Set pieces_per_set	Number	Core	4
GTIN / UPC gtin_upc	Identifier	Core	081234512101

Technical specifications

Measured or rated values that must travel with their unit and test conditions.

Check before use: Store the number and unit separately. Convert only when the source unit and test conditions are known.

Attribute	Type	Priority	Example format
Pad Thickness (Inner / Outer) pad_thickness_inner_outer	Text · mm	Core	16.6 mm / 16.6 mm
Pad Height pad_height	Number · mm	Core	55.2 mm
Pad Width pad_width	Number · mm	Core	130.0 mm

Selection attributes

The type, material and option choices buyers filter and compare on.

Check before use: Map supplier wording to a governed vocabulary only after checking the source text and which variant it applies to.

Attribute	Type	Priority	Example format
Friction Material friction_material_composition	Controlled list	Core	Ceramic
Backing Plate Attachment Method backing_plate_attachment_method	Controlled list	Buyer decision	Mechanical retention
Wear Sensor Included wear_sensor_included	Controlled list	Buyer decision	Yes, 1 electronic sensor per set
Shim Type shim_type	Controlled list	Buyer decision	Bonded multi-layer shim

Fit & compatibility

What the item mounts to, mates with, replaces or works alongside.

Check before use: Keep model and series qualifiers. A similar-looking part is not a verified fit until a source says so.

Attribute	Type	Priority	Example format
Axle Position position	Controlled list	Core	Front
Vehicle Application (ACES) vehicle_application_aces	Text	Core	2015-2020 full-size pickup, front disc

Evidence & compliance

Listings, standards, classifications and origin claims that need a document behind them.

Check before use: Link the manufacturer document or label with its edition or date. Never copy a certification from a neighboring SKU.

Attribute	Type	Priority	Example format
Edge Code (as stamped) edge_code	Identifier	Buyer decision	XYZ 1234 FF
SAE J866 Friction Code sae_j866_friction_code	Controlled list	Buyer decision	FF
Copper Content Level (LeafMark) copper_content_level_leafmark	Controlled list	Channel / evidence	N (under 0.5% copper by weight)
ECE R90 Approval Number ece_r90_approval_number	Identifier	Channel / evidence	E1 90R-02A0123/4567
Country of Origin country_of_origin	Controlled list	Channel / evidence	Mexico

Normalize supplier values

The same value arrives in many spellings. Map each raw string to one governed value, and keep the raw text beside it so a reviewer can see what the supplier actually wrote.

Often missing from supplier files

These fields are commonly absent from price lists and basic feeds, even though the information usually exists in a datasheet, label or installation manual. Treat an empty value as a request for evidence, not as permission to fill it from a similar model.

• Backing plate attachment method
• Copper content level (LeafMark A / B / N)
• Wear sensor included
• SAE J866 friction code
• Hardware and clips included

Questions the record must answer

Buyers and counter-sales reps choosing brake pads ask questions like these. Each one needs a specific field, sourced for the exact variant.

• Does this box cover both front wheels, and is the wear sensor included?
• Is this pad ceramic or semi-metallic, and what is its friction rating?
• Will it fit my truck with the heavy-duty brake package, or only the standard brakes?
• Does this pad meet the copper limits for the states we ship to?

From supplier file to record

1. Resolve identity first. Link the supplier SKU, manufacturer part number and packaging identifiers without merging distinct variants or pack sizes.
2. Extract with the source attached. Pull values from rows, tables and datasheets, keeping the raw text, unit and page or row reference.
3. Map to your classification. Assign the ETIM, ECLASS, UNSPSC or internal class your company licenses, and keep the supplier's original terms.
4. Review, sync and watch. Hold conflicts and safety-related values for a category expert, write approved values to ERP or PIM, and recheck when the supplier sends a new file.

For the full method, see how to build a category attribute template and the category catalog gap audit.

FAQ