Huawei HiCar is the smart-connectivity solution linking a phone to a head unit, and its certification documents are submitted in batches rather than all at once. They fall into four categories: company qualifications, product technical documentation, self-test reports and samples. Every material must keep company name, product model and specifications consistent front to back, with complete stamps. From 2026 Huawei uniformly requires the HiCar SDK 6.0+ template; older documents are rejected — a point factories routinely miss. BlueAsia works on connected-vehicle certification and sees many enterprises rejected over template-version mismatches; staged document submission is steadier than scrambling to assemble everything at once.
2. Company Qualification Files
Prove your eligibility to enter the ecosystem first.
Entry-Level Qualifications
(1) Business licence. The unified social credit code version, within validity, with the official seal. A business scope that mentions vehicle equipment or smart hardware smooths the review.
(2) Huawei developer enterprise membership. Register an enterprise developer account, sign the HiCar Ecosystem Cooperation Memorandum and the security-compliance agreement online, and complete ecosystem onboarding. This step and the hardware-test applicant must be the same legal entity — it cannot be swapped later.
(3) Quality system. Ordinary enterprises prepare ISO 9001; OEMs prepare IATF 16949. Huawei looks at system coverage.
① A consistent qualification entity front to back is the precondition for fewer rejections.
3. Product Technical Documentation
This is where version chaos and rejections cluster. The product specification must state the connection mode (wired, wireless or dual-mode), the main control chip model, the Bluetooth and Wi-Fi module models with firmware versions, the head-unit system version and the adapted vehicle list — and the document version must match the submitted sample. Design files cover the circuit schematic, PCB layout, structure description and EMC design report; hardware and software configuration lists are itemised separately for equivalent-test review, with parameters filled accurately. The user manual and function description verify conformity with HiCar design specifications.
4. Self-Test Report Is a Hard Gate
The self-test report is the ticket to book formal acceptance, and the requirement is rigid. The pass rate must be full: HiCar CTS cases must pass 100%, partial passes are not allowed, and anything short is rejected outright. The report carries complete test logs and screenshots; conclusions without logs are refused. Use the official template that matches the current SDK version — old templates are void. Test on a recent mainstream Huawei Mate or P-series flagship; the wrong handset invalidates the results.
5. Sample Requirements
Samples are a high-rejection step, with the quantity locked. Aftermarket head units need two complete benches (host, screen, power, microphone, GPS antenna, wiring harness) plus five samples pre-loaded with mass-production firmware; engineering samples are refused. Real-vehicle verification needs one commercially configured whole vehicle with a temporary plate valid over 90 days and full insurance; modified-configuration vehicles are refused. Front-install smart cockpits follow different bench and vehicle rules — do not apply the aftermarket template.
6. Extra Documents for Wireless Products
Products supporting wireless connection also need Bluetooth BQB and Wi-Fi Alliance certification reports. This stacks on top of connected-vehicle and wireless certification, so it is wise to secure those first and then submit HiCar, avoiding a stall on wireless compliance. Markets such as the Middle East add local mandatory testing, so list the documents early. Multi-ecosystem projects can share hardware documentation, but test reports do not cross over.
7. Linking to Connected-Vehicle Certification
HiCar is only one connectivity layer; whole-vehicle export also needs RED, FCC, RRA, ERA-GLONASS and the like. Coordinating the timeline early beats patching compliance at the harbour gate.
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!
