Your automotive component already has an E-mark approval. Then your PCB supplier changes. The antenna is replaced. A chipset becomes unavailable. The firmware is updated.

The engineering team says:

“The function is the same. We should be able to keep the existing approval.”

The certification team asks:

“Can we still use the old test report?”

And suddenly, a small engineering change becomes a compliance risk, production delay and potential retesting cost.

This is a situation I see repeatedly with manufacturers of automotive communication devices, navigation systems, displays, gateways and wireless electronics.

The wrong question is:

“Did the product change?”

The better question is:

“Did the change affect anything that the existing approval or test evidence actually evaluated?”

That distinction is the foundation of good Automotive Compliance Change Management.

1. An Approved Product Is Not a Frozen Product

Automotive products inevitably change during their lifecycle.

Components become obsolete. Suppliers change. PCB layouts are optimized. Firmware evolves. Antennas are replaced. Manufacturing locations move.

The existence of an approval does not mean that engineering changes are prohibited.

But it also does not mean that every change can automatically be covered by the original evidence.

For UN Regulation No. 10, modifications to a vehicle or ESA type are subject to an approval process. The Type Approval Authority may determine that a modification has no appreciable adverse effect, or may require further testing or additional checks.

This is why “no functional change” is not sufficient as a compliance argument.

The real issue is impact.

2. The Automotive Compliance Change Impact Matrix

A useful first-level screening looks like this:

This matrix is not a rule that every change requires retesting.

It is a way to decide what needs deeper technical review.

3. PCB Changes: “Same Schematic” Does Not Mean “Same EMC”

A PCB revision can look minor from a functional perspective.

For example:

• Moving a high-speed interface.

• Changing a ground plane.

• Re-routing a power trace.

• Changing the position of a DC/DC converter.

• Modifying shielding.

• Changing connector placement.

• Adjusting antenna matching components.

The product may still boot, communicate and perform exactly the same functions.

But the RF and EMC behavior can change.

For an automotive wireless ECU or gateway, the compliance review should therefore compare at least:

Power architecture → Grounding → High-speed interfaces → RF path → Shielding → Antenna circuit → Clock sources → Cable/connector interfaces

If none of these materially affect the approved/tested configuration, evidence reuse may be possible.

If they do, the manufacturer should determine whether additional validation is necessary.

4. Changing the Antenna Is a Bigger Deal Than Many Teams Expect

Antenna changes deserve their own review.

Changing from Antenna A to Antenna B can affect:

• Gain and radiation characteristics.

• Matching.

• RF efficiency.

• Frequency response.

• Conducted/radiated performance.

• Coexistence with other radios.

• Interaction with the vehicle installation.

The same applies when the antenna itself is unchanged but its location, orientation or surrounding enclosure changes.

For products containing Bluetooth, Wi-Fi, cellular or other RF functions, the question should not simply be:

“Is the new antenna certified?”

It should be:

“Does the existing compliance evidence represent the new RF configuration?”

That is a much more useful question.

5. What About Replacing a Chip or Supplier?

This is where engineering and compliance teams often disagree.

Engineering may say:

“It is a drop-in replacement.”

From a compliance perspective, “drop-in” does not automatically mean “compliance-equivalent.”

You should compare:

• Electrical characteristics.

• Clock frequency and harmonics.

• Power consumption.

• Switching behavior.

• RF architecture.

• Output power.

• Interface timing.

• Operating modes.

• Firmware interaction.

• Thermal behavior.

For a passive component with no meaningful impact on the relevant compliance characteristics, the risk may be low.

For an RF chipset, DC/DC converter, oscillator, transceiver, antenna matching network or other EMC/RF-critical component, the change deserves much deeper review.

The component's position in the compliance-critical path matters more than its purchase price or supplier name.

6. Firmware Changes Can Also Trigger a Compliance Review

Firmware is often treated as a software-only change.

For connected automotive products, that assumption can be dangerous.

A firmware update may:

• Enable a previously disabled radio function.

• Change transmission duty cycle.

• Change RF power or channel behavior.

• Modify Bluetooth/Wi-Fi operating modes.

• Change communication interfaces.

• Alter power-management behavior.

• Change startup or recovery conditions.

• Introduce a new operating mode.

If the firmware only fixes an unrelated user-interface issue and does not affect the tested compliance functions, the impact may be limited.

But if the firmware changes how the radio, power system or external interfaces operate, the existing evidence needs to be reviewed.

7. Five Questions to Ask Before You Order Any Retest

Before automatically booking a complete retest, ask:

1. What exactly changed?

Create a documented comparison between the approved version and the new version.

2. Which compliance-critical functions are affected?

RF? EMC? Power? Interfaces? Antenna? Software-controlled operating modes?

3. Does the original report actually cover the new configuration?

Do not assume it does.

Compare the test setup, hardware revision, antenna, firmware, accessories and operating modes.

4. Can engineering analysis demonstrate equivalence?

For some low-risk changes, a documented technical assessment may provide sufficient evidence for the next decision.

5. Does the approval authority or OEM need to confirm the change?

This is critical.

A laboratory can help evaluate technical impact and perform additional testing, but the final determination regarding an approval amendment or extension belongs to the applicable approval authority under the relevant regulatory procedure.

8. Build a “Compliance Configuration Baseline”

For manufacturers already shipping automotive electronics, I strongly recommend maintaining a Compliance Configuration Baseline.

At minimum, link the following:

Product Model
↓
Hardware / PCB Revision
↓
RF Module / Chipset
↓
Antenna Model & Position
↓
Firmware Version
↓
Accessories / Harness Configuration
↓
Test Report
↓
Approval / Certificate
↓
Production Version

This simple traceability chain can prevent a very common problem:

The factory is already producing Version B, while the certification team is still referring to the test report for Version A.

By the time someone discovers the mismatch, production has already started.

9. How BlueAsia Labs Can Support Change Impact Assessment

At BlueAsia Labs, we work with manufacturers of automotive communication devices, navigation systems, displays, gateways and wireless electronics.

Our RF, EMC, Bluetooth and product-testing capabilities allow us to support the technical side of Automotive Design Change Impact Assessment, including:

• Comparing old and new hardware configurations.

• Reviewing RF and EMC-sensitive design changes.

• Assessing antenna and wireless configuration changes.

• Reviewing existing test reports and identifying evidence gaps.

• Determining where additional testing may be technically justified.

• Organizing version and configuration records.

• Supporting communication with certification and approval stakeholders.

Our role is not to say “every change requires a full retest.”

It is to help determine whether the change is:

Low impact → Existing evidence may remain relevant

Medium impact → Targeted verification may be appropriate

High impact → Additional testing and/or approval authority review may be required

That distinction can save both testing cost and production time.

Final Thought: Treat Compliance as a Lifecycle Process

An automotive approval should not be treated as the end of compliance work.

It should become the baseline against which future engineering changes are assessed.

PCB revisions, antenna substitutions, component changes, firmware updates and supplier changes are normal parts of automotive product development.

The risk comes when those changes are made without understanding what the original approval actually covered.

For automotive manufacturers and Tier 1 suppliers, a strong Automotive Compliance Change Management process can help prevent:

Uncontrolled changes → Evidence mismatch → Unnecessary retesting → Production delay

Before your next PCB, antenna, chipset or firmware change, ask one simple question:

“What part of our existing compliance evidence could this change invalidate?”

If you have an approved automotive product undergoing a design or supplier change, contact BlueAsia Labs to review the change against your existing RF/EMC evidence and target-market requirements.