Spark plug automotive
Organize spark plug automotive requirements by buyer channel so engine codes, heat-range codes and packing units stay attached to each scenario instead of a generic catalog family.
Requirements by buying scenario
| Decision point | Buyer / supplier question |
|---|---|
| Parts wholesale | Clarify catalog references, electrode families, packing units, assortment mix and reorder expectations. A wholesale carton of nickel plugs is not the same line as an iridium retail blister when comparing spark plug price on a per-piece basis. |
| Workshop distribution | Clarify installation position by cylinder, included boots or wires and the vehicle application range. Workshops should state whether gap is expected factory-set and which heat-range code the technician will verify against the manufacturer listing. |
| Fleet purchasing | Separate vehicle configurations and planned quantities by engine code. Fleet programs often mix model years; keep each configuration’s thread, reach and heat-range note on its own line so one purchase order cannot silently substitute another. |
| Special project inquiry | Document altered interfaces, aftermarket terminal adapters or dual precious-metal requests and ask suppliers to explain differences before accepting alternatives. Project samples do not authorize later production lots without a repeated check. |
Channel notes feed the inquiry catalog. When heat-range coding is still open, use the fitment guide.
What to send
Buyer channel, engine application, electrode preference, quantity by position and destination for spark plug automotive orders.