Requirements by buying scenario
Each truck headlight housing scenario starts with a documented part requirement, not an assumed universal fit. Mounting holes, adjuster interfaces and connectors must be restated against the vehicle application.
- Parts wholesale
- Clarify catalog references, packing units, left/right assortment and reorder expectations. Keep empty housings separate from complete assemblies and ask whether bezels, brackets or harness branches travel with the unit. Gross package weight and minimum order quantity, if quoted, belong next to the packing unit rather than in marketing copy. Kit versus individual lines must stay on separate comparison sheets until both bills of materials are written down.
- Workshop distribution
- Clarify mounting position, included hardware and vehicle application range. Mounting-hole pattern, connector family and side designation should be restated against the chassis family and model year. A workshop stocking a mixed aftermarket assortment still needs vehicle fitment coverage written down, not inferred from lens shape or OE reference used for identification only.
- Fleet purchasing
- Separate vehicle configurations and planned quantities by application. Truck platforms may share a housing outline while differing on connector pin count or adaptive control support. Keep sample approval distinct from later batch traceability; a signed sample identifier is not automatic proof that the next production lot matches. Agree which checks repeat on the batch and how mismatches are handled.
- Special project inquiry
- Document altered interfaces and request supplier confirmation before accepting alternatives. Custom brackets, harness adapters or market-specific optics designations are project changes, not catalog swaps. Ask for Incoterms, destination ZIP code and warranty scope on the same sheet as the altered interface description.
Trade-off reminder: a complete assembly kit is not comparable with an individual housing until packing-unit contents are listed; sample acceptance does not automatically certify every later batch.