Mini PC Certification Maintenance: Keeping CE and FCC Valid

Most B2B buyers treat certification as a box to tick at the start of a program — get CE, FCC and RoHS, file the reports, ship. Then, eighteen months later, a memory supplier runs dry, the factory proposes an "equivalent" Wi-Fi module, someone approves it by email, and the whole shipment lands at customs holding a certificate that no longer describes the product. Mini PC certification is not a one-time event; it is a maintained state, and in 2026 the cost of getting that wrong went up sharply.

This guide covers what happens after the first certificate: which changes force re-testing, which are paperwork-only, who should hold the certificate, and the new US rule that resets the clock on any hardware iteration.

The 2026 Rule Change You Need to Know First

From 13 October 2026, the US Federal Communications Commission's revised rules expanded the scope of the Covered List from finished equipment down to logic-bearing hardware components inside a device. In practical terms: components that generate or use more than 9,000 sequential pulses per second, or that perform RF computation, storage, or data transmission digitally — main control chips, MCUs, wireless modules, baseband and encryption chips — now fall within scope.

Two things matter for importers of mini PCs:

• The rule applies to new equipment authorization applications filed after the effective date. Products with an existing FCC ID are not retroactively affected; they remain importable and sellable.
• But any hardware iteration resets it. If an existing product changes its main control chip or swaps its wireless module after that date, the manufacturer must submit a complete new FCC application — under the new covered-list rules. A "drop-in equivalent" module is no longer a procurement detail; it is a re-certification trigger.

That single change turns component change control from a quality preference into a compliance obligation. Procurement teams that previously approved substitutions by email now need a written, certification-aware approval gate.

How Long Does a Mini PC Certificate Last?

There is no fixed expiry. An FCC ID or an SDoC declaration carries no official one-, three-, or five-year validity, and there is no annual renewal or re-registration. The certificate stays valid as long as (a) the product does not materially change, and (b) the applicable standard has not been revised with a transition period that has now closed. The same logic applies to CE: the declaration of conformity is valid while the technical file matches the product actually being placed on the market.

The risk is not expiry — it is mismatch. Market surveillance and customs checks compare the certificate's product photos, model designation, and technical file against the physical unit. If they diverge, the certificate is treated as invalid regardless of its "validity period."

Change Classes: What Triggers Re-Testing

Certification bodies sort product changes into tiers. The practical map for mini PCs:

Tier 1 — Documentation only (no re-test)

• Colour, silkscreen, and logo changes that do not touch electrical design, PCB, or RF.
• Replacing a power adapter with an identical-specification one that already holds its own approval.
• Packaging and manual revisions, label layout adjustments.

Tier 2 — Delta testing, original certificate retained

• Antenna type change, or a modest gain change, handled as a Class II permissive change (C2PC) with supplemental testing — the FCC ID number itself is retained, with a change record added.
• Transmit power or operating band adjustments evaluated against limits.
• RF chip replacement where the pin-out is fully compatible, RF output parameters and matching circuit are unchanged.
• Timeline: typically 2–3 weeks when documentation is complete and no hardware rework is needed; 4–6 weeks if samples need rework or the review body's queue is long.

Tier 3 — New application, new ID

• RF architecture change, power amplifier change, or matching network redesign.
• Full RF board re-layout; a product that moves from module to host integration; two separately certified modules combined into one new product.
• Firmware that can alter RF parameters — transmit power, channel, modulation, or DFS behaviour — either through OTA update or user-accessible configuration. If RF parameters are software-locked and only UI or functional features change, the certificate generally survives.
• Timeline: realistically 4–7 weeks with clean documentation, extending to 6–10 weeks in difficult cases.

The pattern is simple: anything that can change RF behaviour, safety insulation, or energy performance is a certification event. Housing colour is not. A Wi-Fi module is.

Building a Change-Control Gate That Actually Works

Three documents, agreed before the first production run, prevent most certification incidents:

1. An approved BOM, signed and version-controlled as a contract annex. Every component that appears in the technical file — wireless module, antenna and its gain, power IC, PCB revision, enclosure material and its flammability rating — is listed explicitly.
2. A written substitution procedure. Any proposed change goes through a single gate: the factory submits the proposed part, the buyer's engineering contact and the certification body assess the tier, and the change is only implemented after written approval and, where required, completed delta or full testing.
3. A pre-shipment verification step. Before each production batch ships, confirm model designation, PCB revision, and the wireless module part number against the approved BOM and the certificate's technical file. This takes minutes and prevents the most expensive kind of surprise.

Sequencing matters: change applications must be completed before the modified product enters mass production. Producing first and applying for the change afterwards leaves you shipping non-compliant goods in the interval — and if a market inspection lands in that window, the certificate is judged invalid for the whole batch.

Who Should Hold the Certificate?

One of the most consequential decisions in an OEM program is the named applicant. When the factory holds CE/FCC files under its own name:

• You cannot switch factories without re-certifying, because the files belong to the other party.
• You cannot prove your own importer-of-record position during a customs or marketplace audit.
• You inherit the risk if the factory's certificate covers a "similar" model but not your configuration — a common and expensive gap.

Where the market allows, name your own entity as the certification applicant and hold the test reports. It costs the same testing money and buys you portability and control.

Recordkeeping and the Details That Get Missed

• Retention: keep the complete FCC technical file and test reports for at least ten years after the product is discontinued; SDoC test reports and declarations for a comparable period. Customs, marketplaces, and the regulator can request the file at any time.
• Agent details: for US filings, the agent of record must remain contactable, and changes should be updated promptly (within 30 days is the working expectation). Re-check the agent status at least annually.
• Marking: the FCC ID must be permanently marked on the product; electronic labels must follow the relevant FCC guidance and must remain retrievable after firmware updates — an e-label that disappears after an OTA update is a marking non-compliance.
• Channel requirements are stricter than the law. Large retail and marketplace buyers sometimes require certificates against newer standard versions even when older certificates remain legally valid. Treat channel requirements as a separate compliance line, not the same one.

Frequently Asked Questions

Does an FCC ID or CE certificate expire?

No. Neither carries an official fixed validity period, and there is no annual renewal. Both remain valid while the product is unchanged and the applicable standard has not been revised past its transition period. The real risk is not expiry but mismatch between the certified configuration and the product actually shipped.

Can I change a mini PC's Wi-Fi module without re-certifying?

Usually not. Changing the wireless module, antenna, RF matching circuit, or transmit power is a substantive RF change — typically a Class II permissive change with delta testing, or a new FCC ID if the RF architecture or matching network changes. Pin-compatible chip swaps with unchanged RF output may qualify for a permissive change.

What changed in the FCC covered-list rules in 2026?

From 13 October 2026, coverage extends to logic-bearing hardware components inside the device, not just finished equipment. Existing grants are unaffected, but any hardware iteration — such as changing the main chip or wireless module — now requires a complete new FCC application under the revised rules.

Who should be named as the certification applicant?

Where the market allows, name the importing brand or distributor rather than the factory. Holding the test reports means you can change manufacturers without re-certifying and can prove your own compliance position during customs or marketplace audits.

How long does a delta change or new certification take?

Plan on 2-3 weeks for a well-documented Class II permissive change (4-6 weeks with rework or queue delays), and 4-7 weeks for a new FCC ID application, extending to 6-10 weeks in difficult cases. Complete change applications before modified units enter mass production.

Call to Action

Need a certification partner who treats compliance as an ongoing discipline? Shenzhen Liyu Electronic Co., Ltd. supports OEM/ODM mini PC programs with held CE, FCC and RoHS documentation, version-controlled approved BOMs, and a written change-control gate — so a component substitution never silently invalidates your certificate. Email linda@liyuelec.com or message WhatsApp-WeChat: linda4851 to request our compliance pack. Review the platforms: the MX-APB03 high-performance mini PC, the MX-ANP09 mini all-in-one PC, and the full Mini PC product catalog.

Note: Liyu Electronic serves B2B clients only — distributors, brands, and corporate buyers. Minimum order quantities apply; we are unable to respond to individual, donation, or sponsorship requests.

About Liyu Electronic — Shenzhen Liyu Electronic Co., Ltd. (founded in 2019) is an OEM/ODM manufacturer of mini PCs, tablet PCs and laptops based in Shenzhen, China, with CE, FCC and RoHS certified products shipped to 40+ countries.