Two Brake Pad Part Numbers for the Same Truck
A retail customer returns a set of front brake pads for a 2017 half-ton pickup, bought yesterday, saying they are too small to fit over the rotors. The invoice shows the pads were selected from year, make, model plus "4x4, V8." The catalogue lists two pad part numbers for that model year; the split is a heavy-duty payload package that uses a larger-diameter rotor and a taller pad abutment. The customer does not know whether his truck has the package. Two more customers are at the counter and the phone is ringing. Store policy allows unopened returns within 30 days with a receipt; opened boxes carry a 15% restocking charge.
1. What do you check to confirm the correct part number, and how do you handle this customer right now?
Read the worked answer
Year/make/model/engine is not enough because it does not capture the build options that change brake hardware. The catalogue itself is telling you there is a split - that is a flag, not a detail.
Verification sequence:
- Decode the VIN - full 17 digits, not just the year and engine. VIN decoding gives the build configuration and often the brake option.
- Check the build/service parts label - glovebox SPID or door-jamb sticker lists the option codes; the payload package code is what the catalogue is keyed to.
- Measure - rotor diameter with a caliper (the two options differ by roughly 14 mm on this application) or compare the old pad abutment height against the new pad. Physical measurement settles it when the label is missing.
- Compare the removed pad to the new one before it goes back out.
Right now: acknowledge the error, take the customer's name and phone number, and ask him to read the VIN off the dash or bring the truck by. Do not guess and hand over the second part number - a second wrong trip costs more goodwill than a two-minute wait. If he is waiting, pull both numbers and hold the correct one at the counter.
2. The box is opened and the pads show handling marks. How do you process the return, and what do you document?
Read the worked answer
Classify the return before applying the rule. The 15% restocking charge exists to recover costs when a customer changes his mind or orders the wrong part. Here the part was wrong because an option split was not captured at the point of sale - that is a store selection error, not a customer error.
Processing:
- Inspect first: if the friction surface is contaminated, the pad has been clamped in a caliper, or hardware is missing, it is not resaleable and must be handled differently even if the store was at fault.
- If resaleable, take it back at full credit and waive the restocking charge, noting the reason as "wrong application - build code not verified."
- Exchange into the correct number, verified by VIN or measurement before it leaves the counter.
- If the correct part is not in stock, credit the return and order it, so the customer is not holding your inventory error.
Document: reason code, the VIN, the option code found, the original wrong part number, and the staff member who wrote the original invoice. Tag the returned pads so they go back to the right bin and are not re-shelved under the wrong number - a mis-binned look-alike will cause the next failure.
3. What do you change so this does not happen again on this part family?
Read the worked answer
Fix the system at three points, because counter pressure will always exist.
- Point of sale: make the VIN a required field for brake, suspension, and driveline lookups on vehicles with known option splits. A free-text note field that nobody fills is not a control.
- Catalogue/item master: flag both part numbers as look-alikes with a hard-stop note - "verify HD payload package / rotor diameter" - and cross-reference each to the other so the second number surfaces whenever the first is selected.
- Physical: keep both numbers if both move, but bin them apart with labels showing rotor diameter and the option code, not just the part number. Adjacent bins of near-identical parts is how picks go wrong.
Also: brief the counter staff on the specific split and put the note in the shift log. Then watch for repeats - if the same part family generates a second return, the control is not working and needs to move from a note to a mandatory prompt.