Mitsubishi PLC Sourcing FAQ: Downloads, VFD Suppliers, and the Paperwork Nobody Warns You About

I'm a purchasing person, not an engineer. My slice of that is a roughly 180-person manufacturer where I handle the electrical category—Mitsubishi PLCs, controllers, VFDs, contactors, relays, timers. About $400K a year, spread across ten vendors, give or take.

These are the questions I get asked most often by the maintenance lead I work with. They're also the ones I wish someone had asked me before my first order in 2020.

What should I actually look for when buying a Mitsubishi PLC?

At the purchasing level? Honestly, not much—spec'ing the processor is your controls engineer's call, not yours. But three things need to come back to you in writing:

• The exact model and series. Not "Mitsubishi PLC." That's too broad to buy against. iQ-R, iQ-F, FX, and Q are different product lines with different lead times and different software.
• The programming software, and who owns the license. More on this below.
• Lead time, plus who's responsible for commissioning once it lands. This is the one that gets skipped.

Worth knowing: IEC 61131-3 defines the common PLC programming languages—ladder diagram, structured text, function block diagram, sequential function chart, instruction list. You don't need to understand them. You do need to know that language differences affect how long your engineer spends getting a new unit online.

How do Mitsubishi PLC downloads and licensing actually work?

This is the part that took me the longest to understand, because it sits in the gap between purchasing and engineering.

The short version:

• GX Works2 and GX Works3 are the main programming environments, and which one you need depends on the series.
• Downloads generally require registration—typically through a regional distributor or the official channel, not a random file host.
• Licenses are usually a separate line item. They don't ride along with the hardware.
• Trial versions tend to have functional or time limits.

So when you place the order, you're not asking for "a download link." You're asking for documentation that says which software, which license type, tied to which hardware. I'm not going to pretend I know every version detail—that's my controls lead's job. But I know how to get it right on the PO, and that's most of the battle.

What should I look for in a VFD supplier?

VFDs are the category where we have the most failures, so they're the category where supplier quality shows up fastest. My checklist:

1. Do they specialize in drives, or sell them as one of fifty SKUs? Parameter structures and commissioning tools shift between drive families. A generalist distributor often can't keep up.
2. Can they put a technical person on the phone before you pay? If the supplier can't route your engineer to someone technical pre-sale, that tells you what post-sale support will look like.
3. How do they handle failures—replace or repair? Turnaround and responsibility both need to be in the contract, not in a phone call.
4. Do they hand over parameter records? Some suppliers include a configuration backup sheet. Some don't. You'll re-do commissioning every time you swap or add a drive otherwise.

A supplier who says "this isn't our strength—here's who does it better" earns my trust for everything else they do carry.

One more thing on the spec side: ingress protection matters for where the drive lives. IEC 60529 is what defines IP ratings—IP20 and IP54 are very different installation realities. Let your engineer set the requirement; you just make sure it's written on the quote so nobody argues later.

Are OEM, private-label, and bulk programs worth it?

Yes, with a caveat: you're taking on more of the responsibility.

Standard branded product means the brand carries the warranty story. When it's OEM'd under your company name or a distributor's private label, that backing shifts. Which means parameter documentation, support path, and warranty terms all become your problem to nail down before the order, not after.

That's not a reason to avoid it. It's a reason to separate it from "the supplier has our back." Those are two different arrangements.

I have mixed feelings about private label in general. On one hand, the margins and turnaround can be genuinely better. On the other, when something goes sideways, you're the one explaining it to operations—not the manufacturer.

How do I keep invoices and documentation from becoming the problem?

This is where most of our headaches came from. Not the hardware.

We didn't have a formal approval chain for rush orders. Cost us when an unauthorized rush fee showed up on an invoice six weeks later and finance flagged it. The vendor had a verbal "sure, go ahead" from someone in the shop, and I had nothing to push back with.

The third time something like that happened, I finally built a three-line checklist:

1. Does the PO number match?
2. Were any rush or expedite fees pre-approved in writing?
3. Does the invoice line-item match what physically arrived?

Sounds dumb, right? It cut rejected expense reports from three or four a month to zero. Should have done it in year one.

I still kick myself for not documenting a verbal delivery promise from a supplier back in 2022. If I'd gotten the confirmed ship date in an email, we'd have had grounds to dispute the late fee. Instead I ate it out of the department budget.

Should I consolidate everything to one supplier?

Part of me wants the simplicity—one PO, one invoice, one contact. Another part remembers 2021 through 2023, when having a backup source is the only reason a line didn't stop. I compromise with a primary and a confirmed backup, which so far has been the right call.

What I'd watch for is the supplier who says yes to everything. We had one—quoted on PLCs, drives, safety relays, connectors, all of it. Two orders in, it turned out they were brokering most of it, marking it up, and missing dates they didn't control.

Compare that to the one who told us "safety PLCs aren't our strength—talk to someone who specializes." We moved everything else to them that same quarter.

Specialists who know their edges beat generalists who promise everything. Every time.