Procurement notes

I Burned $47K on Ethernet Connectors. Here's the 7-Step Checklist Our Team Uses Now.

2026-11-12 · Jane Smith

I Burned $47K on Ethernet Connectors. Here's the 7-Step Checklist Our Team Uses Now.

I've been handling ethernet connector orders for 8 years. In that time I've personally made — and documented — 9 significant mistakes that totaled roughly $47,000 in wasted budget. Two of those were the kind that still come up in performance reviews.

What's below is the exact checklist our team at LinkScope Sourcing 36 now runs before any RJ45, custom, or IX industrial ethernet connector order goes out the door. Seven steps, about 45 minutes to run once you're used to it. It assumes you're the buyer or the engineer signing off on the order — not the salesperson pitching it.

Who this checklist is for

If you're sourcing RJ45 ethernet connectors, custom ethernet connectors, or IX industrial ethernet connectors for an OEM, a system integration project, or a distributor catalog — this is aimed at you. It's also useful for anyone who's ever been handed a spec sheet and told "just match the last order."

Total time: roughly 45 minutes for a standard order, closer to two hours for a custom tooling run. That investment has paid back for us many times over.

Step 1: Write down the standard number, not the product name

"RJ45" is a layman's term. The actual mechanical interface is defined by IEC 60603-7. The industrial connector family most people mean when they say "IX industrial" is defined by IEC 61076-3-124. If your spec only says "RJ45 ethernet connector," you've already lost the ability to compare quotes fairly.

In my first year (2017) I placed a PO for what the vendor called "RJ45 compatible" parts. They were pin-compatible but not IEC 60603-7 compliant — the tolerance on the latching tab was different, and about 8% of the batch wouldn't lock into our customer's jacks. That was a $4,200 lesson plus a three-week delay.

Checkpoint: Does your RFQ name the IEC standard and the performance category (Cat5e, Cat6, Cat6a)? If not, fix that before anything else.

Step 2: Put the environment on the requirement sheet, not just the datasheet

Most connector specs online are written for office environments. Industrial ethernet connectors live somewhere else. Before you send an RFQ, add four numbers: operating temperature range, expected vibration, IP rating, and mating cycles per connection.

I've seen a supplier quote a part as "industrial grade" that was only rated for 60°C continuous. Our customer's cabinet ran at 71°C in summer. That's not a quality problem — that was a me problem for not putting the environment on paper.

Checkpoint: Can you hand the environment sheet to two different suppliers and get comparable wording back? If one supplier ignores half the numbers, that's a warning sign about how they'll handle the production order too.

Step 3: Decide custom vs. standard before you send the RFQ

This one's a genuine fork in the road, and it's where I lost the most time early on.

I went back and forth between specifying a custom ethernet connector and sticking with an off-the-shelf RJ45 for almost two weeks on one project. Custom offered a 30% shorter cable management footprint in a tight enclosure, but standard had better lead time and 3× the number of vetted suppliers. Ultimately I chose custom because the enclosure couldn't fit the standard footprint — but I should have made that call in 48 hours, not 14 days.

The lesson I wrote into our checklist: decide custom or standard based on enclosure geometry and volume first, then budget. If you're going to tool up, you need volume to amortize it — most of our custom runs only made sense above roughly 5,000 units per year. Below that, a standard IEC 60603-7 part from a vetted ethernet connector supplier is usually the better answer.

Checkpoint: Is your annual volume high enough to justify tooling, and do you have six months of cushion if the first mold run slips?

Step 4: Turn the ethernet connector price into a total landed cost

Unit price is the smallest part of this decision. What matters is landed cost per good unit delivered to your line. That includes the quoted price, freight, duty, incoming inspection (sometimes 100%), scrap allowance, and the cost of the inevitable re-order if the first batch fails inspection.

The numbers said go with the cheaper supplier on one project in 2021 — about 18% lower per unit at the same stated spec. My gut said stick with the established one. I went with the numbers.

Two months later we were running 100% incoming inspection because the plating thickness was drifting batch to batch, and the "cheaper" supplier's lead time slipped from four weeks to nine. The real landed cost ended up 22% above the established vendor's quote. I didn't find a hidden reliability issue — I found that their stated lead time assumed materials already in stock, which wasn't disclosed until after we'd wired a deposit.

"Ethernet connector price" is a line item. "Ethernet connector landed cost" is the decision. They're rarely the same number.

Checkpoint: Ask every supplier two things in writing — freight terms (DDP or DAP?) and the specific lead time assumption behind their quote. If they won't put a lead time assumption in writing, discount that quote heavily.

Step 5: Get IX industrial ethernet connector samples — and test them, don't just look

For IX industrial ethernet connectors (IEC 61076-3-124), skipping sample testing is the most expensive shortcut I've personally taken. The connector looks fine on the bench. It fails in vibration and mating-cycle testing.

The IX industrial disaster happened in September 2022. We ordered 12,000 connectors for a factory automation customer and skipped the first-article vibration test because the supplier had sent us a nice reference sheet. On the third shift, line workers started reporting intermittent drops. The retention force had been measured to a spec that looked right on paper but was measured on a different mating interface — the connector had been tested against an older-generation jack, not the one our customer used.

That one was a $9,800 rework, a two-week line slowdown, and a customer conversation I'd rather not repeat.

Checkpoint: For every IX industrial order, run at minimum: a retention force test to IEC 61076-3-124, a 500-cycle mating test, and a vibration test to the customer's environment. If the supplier can't provide the test reports, run them in-house before the production PO.

Step 6: Review the supplier's engineering change notification process — this is the step most people skip

This is the one that wasn't on our list for the first five years, and it's the one that's saved us the most since.

An ethernet connector manufacturer's ability to quietly change something is enormous. Plating thickness, insulation material, mold revision, even the drawing file — all of it can change without the part number changing. If your supplier doesn't have a documented engineering change notification (ECN) process, you won't know until a batch behaves differently.

Ask for their ECN policy in writing. Specifically: what triggers an ECN, how much notice they give, and whether they'll hold the old revision with a last-time-buy option. Any serious ethernet connector supplier will have this documented. The ones that "just handle it case by case" are the ones I no longer work with.

Checkpoint: If a supplier can't produce an ECN policy within a week, treat that as a no.

Step 7: Put a second set of eyes on the PO before it goes out

The last step isn't glamorous, but it's the one that's caught the most errors. Before any connector PO leaves our team, someone who didn't build the spec reads the RFQ, the quote, and the PO side by side. Not a peer review of the decision — a literal line-by-line comparison of three documents.

We've caught 47 potential errors with this cross-check in the past 18 months. Wrong quantity units (pieces vs. reels), wrong cable-side gender, a custom print that referenced an obsolete drawing, one supplier who quoted a part number that didn't match the drawing revision we'd approved. None of those were caught by the person who built the spec, because of course they weren't — they already knew what they meant.

There's something satisfying about a rushed order going out the door with zero exceptions because the cross-check caught the problem in the office instead of on the line. After all the noise of the early years, that quiet confirmation is the payoff.

Notes, caveats, and the common mistakes that still happen

  • Don't skip sample testing on repeat orders. I catch myself relaxing on this. If it's been more than six months since the last order from that supplier, treat it as a new supplier and rerun Step 5.
  • "RJ45 ethernet connector manufacturer" is not a search result, it's a screening task. Plenty of trading companies present as manufacturers. Ask to see their production line or at least an ISO 9001 scope that matches the product. A genuine manufacturer will usually have a facility tour ready. A trader will usually have a story.
  • Price quotes are reference numbers, not commitments. Prices move on copper, plating materials, and freight. Our own references are re-verified every quarter. Take any figure you read online (including in this article) as directional, and confirm against a current written quote with a validity window.
  • The "we can do it faster" quote is a red flag, not a win. Every time I've taken a lead time significantly under market, it has slipped. The market lead time exists for a reason.
  • Don't let one person own both the spec and the cross-check. That's the whole point of Step 7. Rotate the reviewer monthly if you have to.

I have mixed feelings about how rule-heavy this checklist has become compared to how we worked in 2018. Part of me misses the speed of "just call the vendor and order it." Another part remembers the third rejection notice that landed in Q1 2024 — the one that made Step 7 permanent. I reconcile those feelings by reminding myself that the checklist is what lets us keep moving fast without those rejections. The speed is still there. The chaos isn't.

Some fundamentals haven't changed since I started: know your standard, know your environment, test before you commit. What's changed is how fast a small spec drift becomes a real production problem. If you're running these seven steps every time, you're already ahead of where my team was for the first five years.


Public comments are not collected on this note. A live connector brief goes through the factory quote form.