Evaluating Automotive Solution Suppliers: What to Ask Customer References

Evaluating Automotive Solution Suppliers: What to Ask Customer References

A polished supplier presentation cannot tell you how a partner handles missed delivery windows, inconsistent component quality, or engineering changes before launch. For automotive solution reference buyers, conversations with existing customers can reveal the gap between promised capability and actual performance. Whether sourcing lightweight wheels, high-performance tires, or intelligent lighting systems, procurement teams need questions that uncover measurable results—not just reassurance.

The useful question is rarely “Would you recommend them?” A customer may recommend a supplier because its prices are attractive, while quietly maintaining extra inventory and assigning engineers to chase unresolved issues. You need to understand what makes the relationship work, what it costs to maintain, and whether those conditions match your own program.

Choose references that resemble your actual sourcing risk

Before scheduling calls, ask the supplier what each reference actually buys, from which manufacturing site, and at what stage of the product lifecycle. A satisfied aftermarket distributor cannot fully validate an OEM launch process. Likewise, experience with conventional headlamp assemblies does not establish competence in matrix lighting software integration.

Try to speak with customers covering different operating conditions: a recent launch, an established production program, and, where available, a relationship that experienced a significant quality or delivery problem. Supplier-selected references are naturally favorable; that does not make them useless, but it does make specificity essential.

Start by asking: “Which plant and product family do you use, how long have you worked together, and what responsibilities does the supplier own?” Clarify whether the supplier designs the component, manufactures to a drawing, integrates electronics, or simply manages subcontractors. Otherwise, you may credit it for capabilities delivered by somebody else.

Respect confidentiality. Redacted records, broad performance ranges, and descriptions of processes can be sufficient. A reference who refuses to share proprietary drawings is behaving appropriately, not obstructing diligence.

Ask how quality failures were contained—not whether quality is “good”

“Tell me about the most recent nonconforming shipment” is more revealing than asking for a general quality rating. Follow the sequence: who detected the problem, when the supplier acknowledged it, how suspect material was identified, and how production continued while the cause was investigated.

For aluminum wheels, the discussion might involve casting porosity, runout, coating defects, or traceability to a production batch. For sunroof systems, ask about water leakage, wind noise, mechanism operation, and the division of responsibility between component performance and vehicle installation. These are different failure modes; a generic rejection rate can conceal the issue that matters most to your program.

Useful follow-up questions include:

• Could the supplier identify affected lots without placing all inventory on hold?
• Who arranged sorting, replacement stock, and any necessary on-site support?
• Did the corrective action eliminate recurrence, or merely tighten final inspection?
• Were process changes reflected in the control plan and relevant production documentation?

If a reference mentions an 8D report, ask what evidence supported closure. A completed form is not proof that the corrective action worked. Where disclosure is permitted, request a redacted example showing containment, root-cause verification, and subsequent effectiveness checks.

Separate documentation readiness from genuine approval capability

Ask: “Were approval submissions complete when promised, and how many clarification cycles were needed?” For programs using the Production Part Approval Process, explore whether measurement results, material evidence, process studies, and sample parts represented the intended production process—not a specially prepared prototype run.

A quality-management certificate does not establish that a particular wheel, tire, lamp, or sensor meets your application requirements. Product compliance depends on the component, configuration, destination market, and applicable rules. Lighting requirements, for example, can differ between markets using relevant UN regulations and the United States framework, including FMVSS No. 108.

The reference cannot approve your future product. What it can tell you is whether the supplier understood market-specific requirements, supplied traceable test evidence, and flagged changes that could require renewed assessment. Verify current certificates, approvals, and test scope separately with the supplier and appropriate issuing sources.

Put delivery claims under operational pressure

“They usually deliver on time” needs a definition. Ask whether performance is measured against the original purchase-order date, a later confirmed date, shipment from the factory, or receipt at the customer’s dock. Those measures can produce very different impressions of reliability.

Then ask what happened when demand changed. Did the supplier distinguish available capacity from capacity requiring new tooling, labor, or subcontracting? Could it support a revised build schedule without borrowing inventory allocated to another customer?

One particularly useful question is: “How much inventory do you carry specifically because of this supplier?” A strong delivery record supported by unusually large customer-held buffers is not equivalent to a stable replenishment process. Ask who paid for premium freight, whether warning came early enough to protect production, and whether recovery dates were credible.

For cross-border supply, distinguish factory execution from transport and customs performance. Responsibility depends on agreed delivery terms, but visibility still matters. A supplier may not control a port disruption; it should nevertheless communicate exposure and realistic alternatives.

Find out what engineering support looks like after nomination

Technical responsiveness often changes once the business is awarded. Ask the reference who actually answers engineering questions, whether that person understands the product, and how quickly issues reach someone authorized to make decisions.

Within the exterior and vision categories covered by AEVS, many purchasing risks sit at system interfaces. A low-drag wheel must still work with brake cooling and packaging constraints. A headlamp’s thermal performance affects sustained operation. Tire selection involves trade-offs among rolling resistance, wet grip, load capability, wear, and noise—not one headline specification.

Ask references how the supplier handled those trade-offs. Did engineers identify limitations early, propose testable alternatives, and explain the consequences? Or did they agree to every request until validation exposed the conflict?

For sensor switches and electronically controlled assemblies, probe hardware and software configuration control. “How did you know which revision was installed in the affected vehicles?” can reveal more than a long discussion about innovation. Changes to calibration, materials, tooling, or sub-suppliers should follow the agreed notification and approval process.

Use one late-change question to test several capabilities

Ask: “Describe a change requested close to launch. What happened to validation, tooling, price, and delivery?” A credible answer usually includes constraints. The supplier may have needed additional testing or refused an unrealistic implementation date. That can be a better sign than unconditional agreement, provided the explanation was timely and technically sound.

Expose the costs that never appeared in the quotation

References can help distinguish a low unit price from a manageable total cost. Ask which expenses emerged after nomination: tooling maintenance, extra inspection, packaging changes, software support, test repetition, expedited transport, or warranty administration.

For components exposed to aluminum or rubber cost movements, ask whether price adjustments followed an agreed mechanism. Do not request confidential rates. You need to know whether changes were explained, supported, and handled consistently rather than introduced as unexpected conditions for continued supply.

Also clarify tooling ownership and access. Could the customer obtain maintenance records, identify tool location, and understand transfer arrangements? For aftermarket programs, check replacement availability, fitment-data accuracy, and claim handling. A capable production supplier may still lack the service infrastructure your distribution model requires.

Turn the conversation into conditions for award

Record findings as evidence, limitations, and required follow-up—not simply positive or negative impressions. A reference praising rapid replacements may also reveal recurring defects. Another reporting a difficult launch may describe a supplier that accepted responsibility and established effective controls.

Give greater weight to recent experience with the same manufacturing site, technology, and responsibility scope. Compare answers across references, then take discrepancies back to the supplier without disclosing confidential customer information. Reference calls should complement audits, sample validation, capacity reviews, and contractual safeguards, not replace them.

Close each call with: “What would you put into the contract or launch plan if you were starting again?” The answer often points directly to a practical requirement: named escalation contacts, change-notification rules, traceability expectations, agreed recovery plans, or clearer warranty responsibilities.

Before awarding business, convert material concerns into verifiable actions with owners and deadlines. If the reference evidence leaves an important safety, compliance, or continuity question unresolved, do not average it away with favorable comments about price and service. Resolve that question before committing the program.