Many USB-IF certification projects pass all tests and obtain reports – only to stall at document review. Incorrect file formats or conflicting parameters are rejected by USB-IF – causing 2–3 weeks of back-and-forth. This article provides a complete checklist of all required documents and their specifications.
1.1 Membership registration and corporate qualifications
Register on the USB-IF website – basic Adopter membership is free; Contributor requires annual fees. Submit business licence, contact information, and product category plan.
USB-IF qualification review: 3–5 working days. Most common rejections: registered entity name mismatch with the business licence, and use of personal email instead of corporate domain.
1.2 Product registration and VID application
Create a product listing in the USB-IF system and apply for a VID (Vendor ID). Typically one VID per legal entity; multiple subsidiaries can apply for separate VIDs. VID is free for members; non-members pay separately. PID is assigned by the manufacturer – each product model gets a unique PID. VID review: 1–2 weeks. If you already have a valid VID, new products only need new PIDs – no need to re-apply for VID.
1.3 Test plan document
After agreeing the test scope with the USB-IF authorised lab, produce a test plan – specifying model number, USB specification version (USB 3.2 Gen 2x2 / USB4 v1.0 / USB4 v2.0), interface type (Type-A, Type-C, Micro-B), and supported protocols (Mass Storage, DisplayPort Alternate Mode). Key distinction: USB4 v2.0 maximum 80 Gbps – there is no official "USB4 Gen3/Gen4" naming. Thunderbolt compliance belongs to Intel – not within USB-IF test scope.
2. USB-IF Test Reports
2.1 Electrical conformance test report
Issued by a USB-IF authorised ITL lab – covering signal integrity, eye diagrams, jitter, and transceiver conformance. USB4 v1.0/v2.0 add link training and retimer tests compared to USB3.2. The report must bear the authorised lab's seal and current calibration records – reports from non-USB-IF labs are not accepted.
2.2 Interoperability test report
To complete full interoperability verification, there are only two official paths: attend USB-IF member Compliance Workshops or use the USB-IF PIL platform lab. Ordinary authorised ITLs can only perform electrical conformance – they do not have the official reference device suite for full interoperability testing – confirm this before planning. Tests cover cross-pairing compatibility with mainstream hosts, hubs, and peripherals.
2.3 PD protocol test report
Products with USB PD must additionally submit a PD conformance test report – covering message interaction, power negotiation, role switching, and VCONN supply. PD3.1 distinguishes SPR (Standard Power Range) from EPR (Extended Power Range). Products up to 100 W do not need full EPR tests – only products up to 100–240 W EPR require corresponding tests.
3. USB-IF Compliance Declarations
3.1 DoC (Declaration of Conformity)
Self-declaration by the manufacturer – stating product model, VID/PID, applicable USB specification version, and authorised signatory. Signatory must be the legal representative or a person with formal written authorisation. In OEM scenarios, only the brand owner can sign – the contract manufacturer cannot. Without authorisation, USB-IF will not accept the DoC.
3.2 Product specification sheet
Complete specification – USB port count, specification version, supported Alternate Modes, maximum power, and data rate. All parameters declared must match the test report scope – conflicts are rejected.
3.3 BOM and schematic description
Misconception: BOM and schematics are mandatory at the application stage. Reality: they are not required for standard TID applications – only for QbS similarity assessments or USB-IF-initiated audits – when required, provide USB-related schematics and key-component BOM – USB controller, Type-C connector, PD chip models. Confidential documents can be managed and provided on request.
4. USB-IF Labelling and Trademark Documentation
4.1 USB trademark licence application
After tests pass, submit the trademark licence application – upload product photos and the USB logo placement drawing. The online "minimum logo height 3mm" is incorrect – strictly follow the USB-IF official Logo Usage Guide for print specifications – otherwise trademark review will fail. The logo must appear on the product body and outer packaging.
4.2 TID registration
After all tests are complete, a TID (Test ID) is assigned – the unique identifier in the USB certification database – there is no separate "certification number". Customers and partners can query certification status using the TID in the public database. TID registration requires uploading the final test report and the official DoC file.
5. Common USB-IF Document Submission Pitfalls
5.1 Report version mismatch
Lab issues a new version, but an old version is uploaded; or the report's firmware version does not match final production firmware. Check report date, firmware version, and sample serial number before submission.
5.2 Specification claims beyond test scope
Spec claims USB4 80 Gbps – but only 40 Gbps was tested. Capabilities claimed must not exceed test coverage – either remove the claim or supplement with corresponding tests.
5.3 DoC signatory authority insufficient
Signatory without formal written authorisation, or an OEM contract manufacturer signing – both invalid. Prepare the authorisation letter in advance and keep it on file.
5.4 Chinese/English documentation standards
All formal submission and declaration documents uploaded to the USB-IF system must be in English. Chinese spec sheets and BOMs are for internal retention only – do not upload them directly. Use translators familiar with USB technical terminology to avoid ambiguity.
For USB-IF certification documentation, contact BlueAsia at 13534225140 (King) or king.guo@cblueasia.com.
相关新闻
