Searching Delphi 600 Steering Box Isn't an RFQ: A Quality Manager's View on Delphi Ignition Coil Searches and Vague Part Requests

I received an email in February 2025 with the subject line “RFQ: Delphi 600 steering box.” The body contained those words and nothing else. No vehicle. No model year. No OE part number. No drawing. I replied asking which steering box the customer meant. The answer came back: “the Delphi one.”

That is not a specification. It is a search query with a full stop added.

I’m a quality manager. I review parts before they go out the door, roughly 200 unique part numbers a year. Maybe 180—I’d have to check our system. In 2024 I rejected about 4% of first deliveries because the paperwork did not match the agreed requirement. Sometimes the parts themselves were fine, and the documentation was wrong. Either way, they didn’t ship.

Here is the uncomfortable part: by the time a bad part reaches my desk, the real mistake has usually already happened in the wording of the request.

Everyone Wants To Blame Counterfeit Parts. I Start With Vague Searches.

Counterfeit automotive parts absolutely exist. I would never tell you otherwise. We’ve seen stamped housings that imitate well-known ignition coil brands, complete with plausible logos and slightly wrong wall thickness. If you search for a “Delphi ignition coil” and buy the first page of results, you are relying on the seller’s honesty instead of your own specification. That is a risky position.

But counterfeiters do not create the real vulnerability. The vulnerability is vague sourcing. A fake part only gets a chance when the buyer cannot say exactly what genuine looks like.

Here’s what overrides a lot of conventional wisdom in my experience: counterfeiters are extremely loyal to brand names, and not very loyal to part numbers. They can stamp a logo. They can copy a box. They rarely reproduce the engineering traceability behind a number. The popular advice is “buy the known brand.” In practice, that advice is exactly what counterfeiters are counting on.

Brand Names Describe a Source. Part Numbers Describe a Product.

Let’s take the phrase “Delphi ignition coil.” It tells me who presumably built it, and it tells me the product category. It does not tell me which engine family it belongs to, which connector layout it uses, which bracket geometry fits, or which OE reference it replaces. A Delphi ignition coil can be the right coil for one vehicle and useless for another. The name alone cannot make that distinction.

Part numbers exist for exactly this reason. They are a shorthand engineering contract. They encode the geometry, the material expectation, the revision level and, through the OE catalog, the vehicle application. When you replace that with a phrase like “Delphi 600 steering box,” you are removing the contract and hoping the supplier can read your mind.

I honestly cannot tell you, from memory, whether “Delphi 600 steering box” refers to a gear assembly, a steering column, or something a previous supplier labeled that way. Not a guess. I would have to check the application data. And that hesitation is the point: a supplier who pretends otherwise is guessing with your money.

Consider “spark plug rc12yc” as another example. There is a genuine product behind that string, with real dimensions and operating characteristics. But typing it into a search engine does not tell you whether a Delphi equivalent exists, or whether the equivalent matches your engine’s heat range and reach. That decision belongs in an application table, not in the title text of a marketplace listing. I won’t quote an equivalent from memory, because “from memory” is not an engineering source.

The same logic applies to “best LED headlight.” “Best” is an opinion until you define the vehicle, the bulb category, the housing geometry and the legal beam pattern. I have seen purchasing teams send an RFQ that literally said “best LED headlight” as the description. They were not asking for a specification. They were asking for a recommendation dressed up as a purchase order.

And then there is the phrase that still shows up in our website logs: “refrigerator defrost thermostat.” It has almost nothing to do with automotive metal components, but the search term lands on our pages anyway. That is what happens when brand recognition spreads across categories: it borrows trust from one industry and deposits it in another. A good buyer should ask whether the standard behind the product actually applies to their application.

Vague Requirements Are Paid For Twice

Vague requirements are not cheaper. They are paid twice: once when the supplier interprets them, and again when the customer corrects the supplier.

In my first quality role, I made the classic inspector’s mistake. A vendor sent a certificate of conformance with an official-looking stamp, and I took it at face value. I did not trace the certificate back to the specific batch number on the floor. The batch had been mixed with material from another production run. We caught it only after 1,000 parts had already been kitted for assembly. Sorting those parts by hand took three days and taught me a lesson I still use: a certificate that is not tied to a physical batch is just a piece of paper.

Later, I saw the same pattern from the buying side. A supplier was chosen for an LED headlight heat sink program because they promised fast delivery and their salesperson nodded confidently at every question. The contract described the part as “like the sample” and the material as “aluminum.” When the first production batch arrived, the alloy could not pass thermal cycling. The parts looked identical. They failed where it mattered. The rework cost more than the original order, and the launch schedule slipped by weeks.

Vague language always finds the lowest common denominator. If the requirement says “aluminum,” the supplier can justify any aluminum. If it says “like the sample,” they can justify any deviation that looks similar under a quick visual check. Quality departments are then left to discover the difference after money has moved.

What a Good Requirement Actually Looks Like

The fix is not complicated. It just feels slower at the start.

If you need a replacement for a Delphi ignition coil, send the OE reference or the VIN. If the part is a Delphi 600 steering box, send the application and any markings from the original unit. If you are asking for a spark plug rc12yc equivalent, provide the vehicle and let someone verify the cross-reference from a real catalog. If you want LED headlight components, define the socket type, the available housing space and the thermal requirement.

For metal parts, send a drawing. If no drawing exists, send a physical sample and agree on the critical characteristics before production begins. Name the material grade. Name the finish. Name the tolerance that matters. Oh, and name the batch traceability requirement—that is the part that saves you later.

At our shop, we would rather ask a question than win an order based on a misunderstanding. The supplier who says “this needs more information” feels less convenient at first, but they are the one who is actually protecting your timeline and your reputation.

Search results are a menu. An RFQ is a contract. Don’t confuse the two. When the specification is clear from the beginning, the quality department doesn’t have to be suspicious. And that is a much better way to run a supply chain.