In 2023, I approved a purchase order that I knew was risky. We needed 3,800 feet of medium-voltage cable for a pump station's main power supply. Nexans US quoted $54,900 with a note attached: the cable specification could not be confirmed until we provided the pulling path and bend radius. A reseller quoted $39,600 for the same written spec and did not ask a single question. The $15,300 difference looked like a win.
It was not. The cheaper cable arrived on time and matched the written specification. It still failed in the real world: the jacket did not survive the installation pull, and the splice kits did not fit the insulation diameter. We went back to Nexans US, paid for an expedited replacement, and waited six more weeks.
Adding rework labor and the second material order, the project cost about $78,600. The original Nexans quote was $54,900. My attempt to save $15,300 became a $23,700 overrun.
Before you call this an anti-reseller rant, I should be fair: the reseller did not lie. They quoted what we gave them. The problem was that our RFQ was incomplete.
I am a procurement manager at a 110-person electrical distributor. For six years I have managed about $1.2 million a year in cable, connector, and power-supply component spend, and I have documented every order in our cost tracking system. This is not an engineering post. It is a cost-control post.
The Surface Problem: I Was Comparing the Wrong Number
Most cable buyers assume the problem is price transparency. We think that if every quote lists the same voltage, same gauge, same jacket, and same approvals, the cheapest one should win. Then we treat differences as hidden fees: freight, minimums, rush charges.
Those matter. But the bigger issue is more subtle. In cable, the same written words can describe different products.
That sounds impossible until you realize how much of a cable specification is open to interpretation. Take an insulation class described only as high temperature. Does that mean 90 degrees Celsius continuous, 125 degrees Celsius at short circuit, 150 degrees Celsius, or something else entirely? The phrase defines nothing.
The same is true for terms that look like product names. I have read specifications with a note like Top Therm and assumed it was a known material. Now I treat it as a clue. Which standard? Which test? At what current? If the supplier cannot point to those details, there is no actual basis for comparison.
The Deeper Problem: You Are Comparing Interpretations, Not Cables
When I chose the $39,600 reseller quote, I compared the unit price, lead time, and voltage rating. I did not compare the installation method, the pulling tension, the minimum bend radius, or the physical fit of the cable accessories.
In other words, I let each supplier interpret an incomplete specification. The reseller interpreted it in the most direct way. The application engineer from Nexans US had a different reaction: they pushed back and asked a question about our conduit bend radius before quoting.
That question felt like a sales tactic at the time. It should have felt like a smoke alarm.
This is why the search for cheap cable can be dangerous. A cable manufacturer with engineering support will often quote differently because they are checking physics and installation realities. A parts reseller is not necessarily wrong for quoting what is written; they simply have less incentive to open the application question.
The deeper problem in cable procurement is specification ambiguity. Every quote is an interpretation of your spec. If the spec is loose, the range between supplier interpretations can be 20 percent or more. That large range is not pure market variation. It is risk being priced differently.
Here is a test I now use with any unexplained item. In an old spreadsheet, I once found a reference to 2660 flip. Nobody on the team knew if it was a cable style, a connector, or a note. The supplier could not tell us either. We lost a week before discovering it was an internal product family code that had nothing to do with the material we needed. That was a paperwork mistake, not a technical one, and it still cost money.
The Cost of an Incomplete Spec
What did my incomplete spec cost? First, $15,300 of apparent savings disappeared. Then the reorder and overtime added about $23,700. But the recorded numbers do not capture the most annoying cost: lost trust. After that project, our operations manager wanted to review every cable purchase I made. That extra review time was a hidden cost too.
The same pattern shows up in smaller orders. A connector that does not fit, a jacket that is too stiff for a tight pull, a test certificate that does not match the shipped lot: each one looks minor until it stops a crew. Then the cost of the cable stops mattering because the cost of the delay takes over.
The surprise, for me, was not that the cheaper cable was bad. It was that it met the specification. After that, I stopped sending suppliers a previous purchase order number and asking for the same thing. I now send application details and ask suppliers to confirm conditions before they quote.
What I Do Instead Now
The fix is not complicated, and it costs less than the problem.
- Before the RFQ, write the application conditions, not just the cable code.
- Ask every supplier to answer the same installation and test questions.
- Require a standard, a datasheet, and a test report for every claim.
Per FTC advertising guidance (ftc.gov), objective claims need evidence behind them. I use the same rule in procurement. A claim without a test method is not a specification; it is a hope.
Do I still use Nexans US? Yes. Not because Nexans is right for every project. I use them because their quote answered the installation question clearly. That is not a promise that any single manufacturer is always the best. It is a reminder that quality is easier to verify when the supplier has already thought about the application.
When I evaluate a cable manufacturer now, I do not start with price. I start with the assumptions behind the price. That applies to Nexans US, and it applies to a smaller factory I have never audited.
I still care about unit price. I just care about what the unit price includes first. Five minutes of verification is cheaper than five weeks of correction, and the checklist I built after that failed project has saved us far more than the $15,300 I tried to save that quarter.
