The SuperCharge access channel is the Device Partner digital-energy platform, but do not reverse the order: first register an enterprise account in the Developer Alliance, complete real-name authentication, and sign the ecosystem framework cooperation agreement — only then does the platform entrance open to you. The Developer Alliance line governs ecosystem ties like HiCar and HiPlay; do not confuse the two.
On the agreement: SCP is Huawei's private fast-charge protocol, starting with the 22.5 W of the 2016 Mate 9, then 40 W, 66 W and 100 W. Before certifying, set the tier — different tiers mean completely different cables, interfaces and test requirements.
22.5 W has two implementation versions: the early 4.5V/5A or 5V/4.5A low-voltage high-current with a 5A cable; later there is also a 10V/2.25A version whose current stays under 5A and thus needs no 5A cable. Do not blanket-write "22.5 W with 5A cable" — first see which version.
The 40 W tier runs on a USB-A port via D+/D- analogue-level handshake, with a 10V/4A cable. 66 W and above must handshake over the CC channel with private messages; USB-A has no such channel, so 66 W and 100 W can only land on Type-C. Set the interface by the channel logic at project launch.
There is also FCP, an early protocol at 9V/2A about 18 W, plus a 22.5 W tier. Old-project maintenance meets it; new projects basically all take SCP.
Platform onboarding and agreement signing are step one; this stage's length depends on enterprise-qualification completeness, usually estimated in weeks. Already-onboarded enterprises adding a product line move faster; new onboarding takes longer. During review, fill enterprise qualification and product-line scope completely once; mid-way supplements re-queue.
Scheme review is often underestimated. The charging scheme must use a Huawei-authorised-list solution; third-party chips are not unusable, but must be on the list or hold a module or protocol authorisation. A scheme outside the list means later testing is wasted.
Document preparation often takes two to four weeks. Technical specification, circuit diagram, BOM, cable specification, label and manual are all needed. For cable-bearing products, the original matched cable cannot be fully exempted from submission, but the document page count can be simplified — no need to submit the full independent-cable-certification set.
The most common reason for rejection is the specification not matching the actual sample. Self-check against it before submission; this one pass saves a whole round of rework. For multi-tier products, each tier must be checked separately.
The formal test itself is usually one to two weeks, depending on tier and number of test items. Multi-tier compatible products and kits with several cable types add markedly more items, so widen the schedule.
After testing there are two more gates: Huawei's backend document review, by industry norm seven to ten business days — often omitted from estimates; then technical evaluation, estimated in weeks. Failed evaluation means retest or supplementary material, the biggest variable in the cycle. Smoothly, two to three months to certificate; with repeated remediation, four to six months.
After evaluation passes, listing completes and trademark authorisation takes effect at this step. Many enterprises think testing done means they can use the mark; in fact authorisation takes effect after listing, and during this gap they cannot pre-print — packaging and promotional material both open for printing only after this node.
On the certificate, the industry common saying is two years valid, counted from Huawei's official issuance date, not the test-completion date; apply for renewal proactively before expiry, with the exact term per the current backend notice. After expiry the backend certification status disappears and the device may fall back to ordinary slow charging; the certificate also hangs under the framework agreement, so if the agreement lapses both sides must be watched.
These projects are best handled by locking the cable-spec-to-tier correspondence before submission; these two are high-rework zones, and a first pass saves a round.
For products doing multiple fast-charge ecosystems at once, BlueAsia's one-stop testing and certification merges testing and documents, recording each party's protocol requirements separately rather than mixing.
8. A Note for Project Leaders
Do not write interoperability on the old framing. The Unified Fast Charging standard 1.0 interop power is about 40 W; version 2.0, published May 2025, targets raising it to 44 W, and is not yet at full adoption.
Contact: King Email: king.guo@cblueasia.comAddress: Building C, Hongjingda Industrial Park, No. 107 Beihuan Road, Shiyan Street, Bao'an District, Shenzhen, China BlueAsia delivers more than service!
Related News
