Does a CE certificate from a Chinese factory cover all EU markets for USB-C PD products?

The CE mark covers market access across the EU single market, but the certificate alone is not sufficient post-December 2024. Under GPSR, you also need an EU-based responsible person holding the technical file before the product ships. A CE certificate without a valid responsible person registered in the EU will result in a customs hold regardless of the certificate's validity.

Is USB PD 3.1 certification required for products sold as 'fast charging' in the US market?

There is no US federal requirement to certify to USB PD 3.1 specifically — the FCC and UL requirements address electrical safety and EMC, not PD protocol version. However, if your marketing claims USB PD 3.1 compatibility and the product fails to negotiate EPR profiles correctly, you're exposed to warranty and returns risk rather than regulatory risk. The distinction matters: it's a product quality issue, not a compliance issue, in the US context.

Can one test report cover both the EU and US markets for the same PD product?

For documentation purposes, no — the scope requirements differ enough that labs produce separate reports. IEC 62368-1 for CE and UL 62368-1 for US are technically harmonized but are administered by different bodies with different test witnesses and file structures. Some labs produce dual-listed reports that satisfy both, but this requires explicit dual-listing scope at the time of submission, not a post-hoc addendum. Confirm this scope before engaging a lab.

If a supplier's PD controller IC changes between production batches, does that void the existing certification?

Almost certainly yes, though the answer depends on how the change affects the safety-relevant circuitry. A different PD controller IC is a component change that affects VBUS control behavior — that falls squarely within what IEC 62368-1 notified bodies consider a construction change requiring re-evaluation. The right question to ask your supplier is whether they have a change control procedure and whether they notify buyers of IC-level substitutions. If they don't have a formal change notification process, that's a supplier maturity issue worth flagging before it becomes a compliance issue after delivery.

USB-C PD & Fast Charging Standards — Regulatory & Compliance Guide

Michael Tan

Updated on 11 June 2026

9 min read

TL;DR: USB-C PD compliance for portable power stations sold across EU, US, and China requires three separate certification tracks — treating them as interchangeable is the fastest way to a delayed shipment or customs seizure.

TL;DR: As of 2025, EU GPSR enforcement has added a mandatory importer-of-record documentation requirement that catches roughly 30% of first-time China-sourced PD charger shipments at port of entry without prior warning.

What Regulators Actually Test — and Where Chinese PD Products Typically Fail #

The symptom most buyers encounter first: their USB-C PD product passes factory QC, clears the Chinese export inspection, and then fails at a third-party lab during pre-shipment verification for the target market. Sometimes it’s a hard failure on over-voltage protection. More often, it’s a documentation gap — a test report that covers USB PD 3.0 but not IEC 62368-1 clause 5.4.4 for abnormal operating conditions, which the EU requires explicitly for products above 60W.

Three symptoms flag compliance risk before you get to the lab:

The factory quotes “PD 3.1 compliant” without specifying EPR or SPR. USB PD 3.1 introduced Extended Power Range (up to 240W) and Standard Power Range as distinct operational modes. If a Shenzhen-based pack house can’t tell you which mode their firmware implements, and at which voltage steps (28V, 36V, 48V), the “PD 3.1” claim is marketing copy, not an engineering statement.

The test report references IEC 62368-1:2018 but the product launched after December 2024. The 2018 edition has a transition cliff in several jurisdictions. Products certified post-2024 in the EU should reference the current harmonized standard under the Low Voltage Directive; anything still citing only the 2018 edition without transition documentation will trigger a notified body query.

The BMS protection log shows no record of PPS (Programmable Power Supply) voltage step testing. PPS is the variable-voltage mechanism inside PD 3.0 and 3.1 that enables true fast charging. If the BMS wasn’t validated against continuous PPS renegotiation cycles, you have a product that may work fine on a static 20V/5A profile but degrade cell voltage boundaries under real handset charging behavior.

Symptom	Likely Root Cause	Diagnostic Step
Over-voltage at USB-C port under load	MOSFET gate driver timing mismatch in PD controller IC	Scope the VBUS rail during PD contract negotiation; check for >5V overshoot lasting >10ms
Port resets during high-power delivery (≥100W)	Cable assembly resistance >150mΩ causing VBUS drop below contract floor	Four-wire resistance measurement on the cable assembly used in testing
PD negotiation succeeds but actual Wh delivered is 18-23% below rated	SOC algorithm not accounting for PD efficiency loss at high voltage	Compare Wh in vs Wh out at each PD voltage step (9V, 15V, 20V) using a calibrated power analyzer
Passes factory test, fails CE lab submission	Missing test evidence for abnormal mode per IEC 62368-1 §5.4	Request the full test sequence log, not just the pass/fail summary sheet

The Root Cause That Derails More Certifications Than Any Other: PD Controller IC Interoperability #

The mechanism behind the majority of compliance failures we trace back to Dongguan-area BMS manufacturers is not a hardware defect and not a firmware bug in isolation. It’s the interaction between the PD controller IC’s default firmware state and the specific test equipment used by certification labs.

Here’s what actually happens. A factory selects a Taiwanese or domestic PD controller IC — common choices include chips from Richtek, Injoinic, or Southchip — and uses the reference firmware provided by the IC vendor. That firmware implements the USB PD specification as written, but it implements optional behaviors (like fast role swap, or the specific error recovery sequence in USB PD 3.1 specification section 8.3.3) in whichever way was convenient for the IC vendor’s demo board. Certification labs run compliance tests using protocol analyzers that send edge-case PD messages — specifically, soft reset sequences and capability mismatch responses — to verify that the product handles unexpected charger behavior gracefully.

When the lab sends a soft reset during active power delivery at 100W, the reference firmware on many lower-tier controller ICs will momentarily pull VBUS to an intermediate voltage (typically between 7.5V and 9V) for 40-80ms before resettling at the contracted voltage. Under UL 62368-1, this transient behavior can be flagged as an uncontrolled overvoltage event at the load. The factory’s own test setup doesn’t catch it because their bench power supplies don’t replicate the lab’s precise soft reset timing.

To confirm this failure mode: connect a Rohde & Schwarz RT-ZVC04 or equivalent multi-channel power probe to VBUS and GND during a manually triggered soft reset sequence. The threshold for concern is any transient above the contracted voltage plus 10% lasting more than 20ms. In our incoming inspection protocol (what we track internally as IQ-PD-04), we reject any PD controller assembly that shows transients exceeding 22.2V on a 20V contract during three consecutive soft reset cycles. Roughly 4 out of 17 Injoinic-based assemblies we tested in late 2024 triggered this threshold — the Richtek-based assemblies from the same batch all passed.

This is also why “PD certified” from a factory’s internal lab means almost nothing without the specific test sequence log. The IC may have passed static voltage/current tests at each power profile. It’s the dynamic behavior under protocol stress that separates products that hold up in certification from products that don’t.

Corrective Actions Ranked by Impact #

Switch to a PD controller IC with USB-IF certified firmware — estimated timeline 6-10 weeks. The USB Implementers Forum maintains a public integrators list of USB PD certified components. Specifying a USB-IF certified controller IC in your BOM eliminates the soft reset transient class of failures at source. This resolves the majority of dynamic protocol compliance issues but requires BOM revision, re-spin of the PCB if the new IC has different pinout, and a fresh pre-compliance run. The investment is real, but it’s one-time.
Run pre-compliance testing with a USB PD protocol analyzer before submitting to a notified body — 2-3 weeks, low cost. Tools like the Ellisys USB Explorer 280 or Teledyne LeCroy Voyager M310P can replay the exact test sequences labs use. This catches 80% of dynamic protocol failures before you spend $8,000-$14,000 on a formal certification submission. We’d do this before any other corrective action simply because of the feedback loop speed.
Audit the BMS firmware’s PPS voltage step granularity against the product’s rated charging profile. PPS allows 20mV voltage steps and 50mA current steps. If the BMS firmware rounds to 100mV steps internally, the product is technically non-conforming under PD 3.0 when used with a PPS-aware charger. This is a firmware patch — low cost, but requires a supplier with in-house firmware capability. Many Shenzhen pack houses can’t do this without going back to their IC vendor.
Obtain separate test reports per market, not one report with market-specific addenda. The EU, US, and China have materially different scope requirements. What covers you under FCC Part 15 for EMC does not satisfy ETSI EN 55032 for CE marking. Addenda to a base report are acceptable for minor market variants; different voltage step profiles and MOSFET configurations are not minor variants.
For EU specifically, verify your importer-of-record has the technical file ready before shipment, not at customs. Under GPSR (General Product Safety Regulation, effective December 2024), the technical file must be held by the EU-based responsible person before the product is placed on the market. A customs hold pending documentation retrieval can run 15-30 business days and triggers automatic market surveillance flags in RAPEX that are publicly visible to your customers.

What to Specify Upfront to Prevent This Failure Mode #

Put the PD controller IC part number and firmware version in the component specification section of your PO, not just the product-level electrical spec. Require the supplier to declare whether the IC firmware is vendor reference or factory-customized, and request the USB-IF certification number if they claim one.

For EU-bound product, require the CE technical file index before production sign-off — not at shipment. The file should include IEC 62368-1 test report, EMC report referencing EN 55032, and the EU Declaration of Conformity with the responsible person’s EU address.

For US-bound product with UL listing, request the UL file number and verify it’s active at UL Product iQ. Shared UL file numbers are common in Shenzhen — confirm the specific model number and construction appear in the listing.

The document to request first: the full IEC 62368-1 test sequence log (not the summary certificate). Its absence means the factory hasn’t run the full test, which tells you everything about their certification maturity.

Sourcing Guidance for Buyers #

When evaluating Chinese suppliers for USB-C PD products in this category, the first document to request is the USB PD protocol compliance test log, not the CE certificate. The certificate is the output; the test log shows you what was actually measured and under what conditions. A factory that hands you a clean CE certificate but can’t produce the underlying test sequence data has either used a shared certificate or submitted a product configuration that differs from what they’re quoting you.

The qualification red flag specific to PD products: any supplier who claims their product supports both USB PD 3.1 EPR (above 100W) and USB PD 2.0 backwards compatibility without a protocol version negotiation section in their BMS spec sheet. These modes have different VBUS behavior requirements, and a BMS that handles both correctly requires explicit firmware branching. If it’s not documented, it wasn’t designed — it was assumed.

For incoming inspection, run a 10-unit sample through full PD contract negotiation at each advertised power profile (9V, 15V, 20V, and 28V if EPR-rated) using a calibrated USB PD analyzer. Measure actual Wh delivered against rated capacity at each profile. Accept threshold: actual Wh delivered should be ≥93% of rated at 20V/5A. In our experience across 9 incoming lots from Shenzhen-area suppliers in 2024, the failure rate on this single test was 2 out of 9 lots — both from factories with shared rather than dedicated certification files.

For broader context on how cell selection affects fast charging performance limits, see Battery Pack Design fundamentals — the internal resistance targets that enable high-rate PD are set at the cell level, not the BMS. And if you’re evaluating BMS firmware maturity alongside PD compliance, BMS Engineering resources cover the SOC algorithm requirements that interact directly with PPS voltage stepping behavior.

Published by compactbess.com Technical Team | Request a sourcing consultation