Same Brand, Same Series — Still Not Interchangeable: Why Ide

Same Brand, Same Series — Still Not Interchangeable

Two modules from the same brand, in the same series, with adjacent part numbers, are not automatically interchangeable. The same outline, the same screw holes and the same connector family can hide a different firmware lineage, a different role inside the rack, and a different group configuration requirement. This is the rule that catches buyers who source by photograph or by a note that says "same family as the old one".

By Mei Lin (sourcing desk, aoctrl.com). Data through September 2026. Last updated: September 2026.

The buyer's question that triggers this article

A buyer who works in a panel shop or a repair workshop will often phrase it like this in Russian, and then again in English when they write the request:

«Модули WAGO 750 — можно ли купить частями? Один и тот же артикул у поставщика, а у нас в шкафу другой — это вообще то же самое?»

EN gloss: "WAGO 750 modules — can I buy them in parts? The supplier has one part number, but the one in my cabinet is a different one. Is it actually the same thing?"

The question sits at the top of the buyer-intent ladder because the answer is rarely "yes, drop it in". It is almost always "depends on which axis you check". Two part numbers that differ by a single letter suffix are often deliberately split by the manufacturer so the firm can charge differently, ship regionally, or run a phased rollout without rewriting documentation. Knowing why that split exists is what stops you from installing a module that the PLC will either reject on power-up or, worse, accept but configure wrong.

If you are weighing this question against an installed module in your cabinet, send your BOM (including the existing part number, the suffix, the firmware label and a photo of the rating plate) to our sourcing desk at /inquiry. We will quote each line separately, mark the condition per line, and flag every axis we cannot confirm.

Why same brand + same series is not a safe substitute rule

Industrial automation catalogues are built around three pressures that push manufacturers to keep splitting part numbers instead of consolidating them:

Regional and regulatory packaging. A manufacturer can ship the same physical module with different suffix letters (-J, -EU, -CN, -US) so the label, the certificate declaration on the box, and the manual bundle can be customised per market without re-running EMC testing on every variant. The hardware is usually the same; the printed declarations are not.
Phased migration without breaking installed base. When a manufacturer rolls out a new firmware or hardware revision, they often keep the old part number orderable for a defined window and assign a new suffix to the new version. The two coexist on the same rack for years. The datasheet lists them as one family; the firmware files, the device description files (GSD/GSDML/EDS), and the programming environment will treat them as different devices.
Functional splitting inside one family. A family like the Panasonic FP2 series covers power supplies, CPUs, communication masters and configuration modules. Every member sits in the same backplane, but two FP2 part numbers can serve completely different roles. FP2-CAN-S is a CAN bus master; FP2-DEV-S is a development and configuration module. Same series, same outline, same connector — different firmware family, different role, different rack resource reservation.

So when a buyer asks "the supplier has FP2-something-S, my panel has FP2-something-else-S, can I swap them?", the answer has to walk through at least five of the twelve substitution axes before the swap is safe. We are required by our own methodology to leave unknowns visible, not paper over them. Two of the most common unknowns in this scenario are firmware version and certification scope; both are items the buyer, not us, has to clear.

The twelve axes, applied to same-brand-same-series cases

For full replacement decisions we use a twelve-axis framework. For the narrower question of "same brand, same series, adjacent part number" only some of those axes change between two adjacent SKUs, and the ones that change are the ones that bite. Below are the six axes where same-series part numbers most often diverge, with the verdict we typically record against each when we compare two FP2-family or two NA-family SKUs in our catalogue.

Firmware, hardware version and engineering-software compatibility. Almost always differs or UNKNOWN between two same-series part numbers that differ by suffix. The manufacturer publishes separate firmware files for each. The programming environment (Control FPWIN Pro for the FP2 family, for example) will reject the older firmware if the rack is configured for the newer one, and the reverse case leaves you running on a module the system expects to behave like the newer one. UNKNOWN on this axis means we will not propose a swap.

Function and I/O specification. Two modules in the same series can share the chassis width and the connector family but split by function: a communication master (FP2-CAN-S) versus a development module (FP2-DEV-S), or a diffuse-reflective sensor (NA40-4) versus a separate through-beam sub-family (NA2-N8-PN). The points count and the channel type diverge. Verdict: differs for the FP2 role-swap case; differs for the NA reflective-vs-through-beam case.

Terminal and interface assignment. Adjacent part numbers in the same family typically keep the same connector pinout, but the bus address, the channel numbering and the rotary switch positions are usually different. Verdict: differs. Wiring is not interchangeable between two communication modules even when both use the same connector.

Electrical parameters. Same series usually means same supply voltage class, but the current budget per slot and the inrush profile are often different. The rack power supply budget calculation has to be redone if you swap one module for another in the same family with a different current draw. Verdict: differs or matched depending on slot position — verify per slot.

Communication protocol. Two FP2 modules can both sit on the same backplane but speak different protocols to the CPU (CAN versus a configuration channel, for example). Verdict: differs for any cross-role comparison. Never assume protocol parity between two modules with adjacent part numbers.

Form, fit and outline / mounting. This is the one axis where same-series part numbers usually do match. Same chassis, same width, same DIN-rail clip, same panel cut-out where relevant. Verdict: matched is the common case here, and this is precisely the trap — the buyer looks at the outline and concludes the modules are interchangeable. Outline parity is necessary, not sufficient.

For the six remaining axes (dimensions, mechanical parameters, environmental class and EMC, ingress and temperature range, materials and construction, certifications and lifecycle), the typical verdict between two adjacent same-series part numbers is matched or UNKNOWN. They rarely diverge in those axes; the manufacturer keeps one mechanical platform and one EMC profile across a long run. But we still record each axis explicitly. Skipping an axis is what makes a cross-reference report unusable when something goes wrong on the shop floor six months after commissioning.

What we will not do, and what we will do, when a buyer asks for a same-series swap

We are an independent industrial automation distributor, not an authorized distributor or partner of any manufacturer named in this article. When a buyer asks us to swap one same-series part number for another, we will not propose the swap if any of the following holds:

The two modules serve different roles in the rack (CPU versus communication master versus development module, for example). The chassis match is irrelevant.
The buyer cannot tell us the firmware version expected by their existing program. We will not propose a swap that might require rewriting a program the buyer has not budgeted to rewrite.
The two modules are split into different regional variants and the buyer's installation is subject to a different compliance regime than the variant we can supply. We do not make compliance calls. The decision belongs to the buyer's quality system and to the importer of record.
The two modules sit on a path whose integrity the buyer has certified externally (operator-guard circuits, certified protective-stop paths, certified stop categories per IEC 60204). We do not propose substitutes on those paths. That decision belongs to the buyer's safety engineer and is outside the scope of an independent sourcing desk.

What we will do, in this scenario, is quote each line of the buyer's bill of materials separately, with the part number, the suffix, the firmware version we can read from the existing module's label or from the buyer's photograph, and any UNKNOWN axis flagged as UNKNOWN rather than guessed. The buyer or the buyer's engineer then decides whether the two are interchangeable for that specific application. We carry the part. We do not carry the engineering sign-off.

Verifying before you buy — the checks that actually catch the difference

If a buyer wants to verify two same-series part numbers before they commit to a swap, we recommend the following three checks, in order. None of them requires equipment we do not already use in our own pre-dispatch workflow.

Read the firmware label. The label on the side of the module carries the firmware version as printed text, usually near the serial number. Photograph it next to the existing module's label. If the suffixes match and the firmware strings match, you can usually proceed to step two. If either string differs, stop and check the engineering environment's compatibility list for that firmware.
Read the device description file. GSD, GSDML, EDS or ESI files are manufacturer-published and version-stamped. The version that the programming environment expects must match the version the module reports. Two same-series modules with different firmware versions will load different device description files.
Read the wiring diagram from the datasheet, not from the panel drawing. Panel drawings are version-controlled at the time the cabinet was built; the manufacturer datasheet is version-controlled at the firmware release. When the two disagree, the datasheet wins. Compare terminal numbering, supply polarity and shield grounding from the datasheet for both part numbers side by side.

If all three checks align, a same-series swap is usually safe for a non-safety-rated function. If any check fails, do not proceed on the basis that "the chassis matches". This is the situation where an independent sourcing desk earns its keep — by telling the buyer the truth about what is unknown, rather than papering over the difference to close the order.

How this shapes what you will see on a quotation from us

Every line we quote for a same-series question will carry, in the line notes:

The exact part number as ordered, with the suffix spelled out (FP2-CAN-S is not the same line item as FP2-CAN).
The condition of the module we can supply at that line — new surplus, refurbished (with bench-test record) or used (no test claim unless the quotation line states one). The three words are not interchangeable; condition is stated per line, not aggregated across the order, and we do not sell used parts under a refurbished label.
The axis on which the comparison differs, if the buyer has asked for a cross-reference against an existing installed module. UNKNOWN stays UNKNOWN. We do not write "compatible" where the manufacturer does not publish the answer.
The verification check we recommend the buyer run before installation, if the buyer has asked for a same-series swap.

A quotation that reads "compatible" with no axis notes, no per-line condition note, and no verification recommendation is not a quotation we will issue. If you receive one from another desk, ask for the per-axis record behind the compatibility claim.

Where a same-series swap is the wrong answer

There are at least three situations where even a verified same-series swap is the wrong answer, and we will say so in writing:

Operator-protection paths. Stop wiring, guard circuits, light curtains and the modules certified to drive them are not candidates for same-series swaps sourced independently. The certification belongs to the installed configuration, not to the individual module. We do not propose substitutes on those paths.
Programmed configuration with no engineering support. If the buyer cannot re-run the programming environment to load a new firmware or to update the device description files, the swap is the wrong answer. The buyer should either budget the engineering time, source the exact original part number, or stay on the existing module until a planned migration window.
Compliance-critical installations. Medical device manufacturing (non-implantable boundary), installations subject to notified body oversight, and installations covered by customer-specific quality agreements are situations where the buyer must consult their own quality and regulatory functions before any same-series swap. We will not write "suitable for medical use" or "compliant with" on a quotation line. That decision is not ours to make.

The same answer applies to any cross-brand substitute that claims parity because the outline looks right. Same-series is the case where the outline match is most convincing and the engineering gap is widest. The harder cases are the ones where the buyer, the buyer's engineer and the buyer's quality system have to all sign off before the module goes into the rack.

Data Notes

The Panasonic FP2 family reference (FP2-CAN-S, FP2-DEV-S) is drawn from the manufacturer's published datasheet for the FP2 backplane I/O family; cross-reference verdicts stated above are based on the datasheet comparison we record against each quotation, not on assumption.
The NA40-4 and NA2-N8-PN comparison draws on the manufacturer datasheets for the NA-series photoelectric sensor families.
The condition vocabulary (new surplus, refurbished, used) is per quotation line, per the site quality page at /quality; we do not aggregate condition across an order.
This article carries no external source links; evidence URLs are tracked internally in the editorial record.
This article is editorial methodology, not a compatibility certificate. Compatibility decisions remain the responsibility of the buyer's engineering team, supported by the manufacturer datasheet and the buyer's own qualification process.

The takeaway

Same brand and same series is a starting point for a cross-reference check, not the conclusion. The check has to cover at least the six axes named above — firmware, function and I/O, terminals, electrical, protocol and mounting — and to leave UNKNOWN visible on the axes we cannot verify from the catalogue or the datasheet. If you are weighing a same-series swap, send your BOM (with the existing part number, the suffix, the firmware label and the application) to our sourcing desk via /inquiry. We will quote each line separately, mark the condition per line, and flag every axis we cannot confirm. The final call on whether to swap belongs to your engineering team, supported by the manufacturer datasheet and your own qualification process — verify against the original manufacturer datasheet and your own qualification process before any module goes into the rack.

FAQ

Same brand same series — is it always safe to swap modules?

No. Same brand and same series means the outline and the connector family usually match, but the firmware lineage, the I/O role inside the rack, and the protocol are frequently different between two adjacent part numbers. The swap is only safe after a per-axis check of firmware version, function and I/O, terminals, electrical, protocol and mounting, with any axis we cannot verify left as UNKNOWN. The final call on whether to swap belongs to your engineering team.

What does the suffix on a part number actually mean?

A suffix letter or string (for example -J, -EU, -CN, -US on regional variants, or -S versus -DEV on role-split modules in the same family) usually denotes a regional packaging, a hardware revision, a role inside the rack, or a firmware split that the manufacturer publishes separately. Two modules with different suffixes are typically different line items on the bill of materials, not interchangeable SKUs.

Which axis is most often missed when comparing two same-series modules?

Firmware, hardware version and engineering-software compatibility. The chassis matches, the connector matches, the supply voltage class matches, and the engineering environment still rejects one of the two because the firmware strings differ. This axis is the one that bites buyers who source by photograph or by a note that says "same family as the old one".

Can a same-series swap ever be safe?

Yes, when the buyer has verified that the firmware label matches, the device description file version matches, and the wiring diagram in the manufacturer datasheet matches for both part numbers side by side. The swap is then safe for a non-safety-rated function, provided the buyer runs their own qualification process against the original manufacturer datasheet before installation.

Why does a quotation list condition on every single line?

Because condition (new surplus, refurbished with bench-test record, or used without a test claim) is a per-line fact, not an order-level fact. Two adjacent lines on the same quotation can carry different conditions, and condition is stated per line for each line. A quotation that aggregates condition across the order is not a quotation we will issue.

What if the buyer's existing module's firmware version is unknown?

We record the firmware axis as UNKNOWN and we will not propose a same-series swap on that line. The buyer has two paths forward: read the firmware string from the existing module's label (photographed in good light, next to the serial number) and send it to us, or stay on the exact original part number until the firmware question is answered. Guessing the firmware version is the most common cause of a same-series swap that fails on power-up.

Do you ever substitute across brands?

Cross-brand substitution is a separate exercise and follows the same twelve-axis framework with a higher proportion of UNKNOWN axes. We will not write any one-to-one swap claim on a cross-brand line. The buyer, supported by their engineering team and the manufacturer datasheet, makes the final call. Our role is to surface what is matched, what differs, and what we cannot verify, and to carry the part if the buyer decides to proceed.