This page is intended for Partners who work with a System Integrator (SI). Google strongly recommends partnering with an SI. Fast Pair adopters without a SI/SOC partner should contact your Google Technical Account Manager or [fast-pair-integrations@google.com](mailto:fast-pair-integrations@google.com "MailTo link for the Support group.") for support. ## Background This workflow, implemented Q2 2022, has SoC partners integrate Fast Pair solutions and help OEM and ODM partners on Fast Pair project development and certification. The primary System Integrator (SI) partners supporting this flow are: | SI Name | Contact | |---|---| | Airoha | sales@airoha.com | | Bestechnic | Email: [Jennifer Li, Dir. of Business Development](mailto:jennifer@bestechnic.com) | | Qualcomm | [Qualcomm Contact Form](https://www.qualcomm.com/support/contact/forms/contact-sales-audio) | | Realtek | rtksi@realtek.com | | Jieli | yukaikai@zh-jieli.com | ## Role and Responsibilities in the Ecosystem  The Fast Pair integration process with partners includes the tasks listed in Figure 1 and must be completed before official certification in 3rd Party Labs. OEMs are responsible for the following tasks: - **Model ID Registration** : Register your device on the [Device console](https://developers.google.com/nearby/devices "Link to the Nearby console.") to obtain a unique model ID for your device (a project can have multiple Model IDs). This is required to request project activation in the business proposal before the integration and development process for Fast Pair. Fast Pair devices (each with a unique model ID) need to be associated with one or more Google Cloud projects. For additional information, see the [the Model Id page](https://developers.google.com/nearby/fast-pair/specifications/service/modelregistration#CreateModelId "How to register a Fast Pair Model ID."). - **Business Proposal** : You will need to complete a [business proposal submission](https://docs.google.com/forms/d/1-QLoVRkxZQQtk14lGvgs88laM9zC1p35pzYwXBLosFk/viewform "Link to the Business Proposal submission form.") to notify the Google Business Development team to confirm the necessary contracts are in place, and choose System Integrator (SI) partners to collaborate with. Your SI or SoC partners will help you submit an issue tracker kickoff proposal in the Google issue tracker to confirm the project scope. For additional information, see the [certification process](https://developers.google.com/nearby/fast-pair/certification-process#preparing_for_certification_via_self_testing "Link to the self-test section.") section. - **Fast Integration** : Work with your SI or SoC partners on product development and Fast Pair solution integration in Bluetooth (BT) firmware. If you have any questions, reach out to your SI partner. For more information, see the [Fast Pair technical guidelines](https://developers.google.com/nearby/fast-pair/fast-pair-certification-guideline "Link to the Fast Pair Certification Guidelines page."). - **Self-Test** : Run and submit the results of the calibration test and end-to-end integration test with the Validator app. For more information, see either the [BT Classic](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/Bluetooth_Classic_-_Google_Fast_Pair_Self_Test_Report_10142020.zip "Link to the Fast Pair Bluetooth Classic Self-Test Report sheet.") or [BlueTooth LE Audio](https://developers.google.com/static/nearby/fast-pair/downloads/self-test-reports/LE_Audio_Dual_mode_-_Google_Fast_Pair_Self_Test_Report_2025_Q4.zip "Link to the Fast Pair LE Audio Self-Test Report sheet.") Self-Test Report forms, depending on implementation. Once you have completed the self-test, submit the Self-Test Report to your SI or SoC partner who will apply for technical approval so that Google can evaluate your self-test results. See the Fast Pair [certification process](https://developers.google.com/nearby/fast-pair/certification-process#preparing_for_certification_via_self_testing "Link to the self-test section.") for more details. - **Apply for Technical Approval** : Work with your SI or SoC partners who will submit the technical approval request in the Google issue tracker system. For more information, see the [certification process](https://developers.google.com/nearby/fast-pair/certification-process#preparing_for_certification_via_self_testing "Link to the self-test section.") section. - **Official Certification at a Third-Party Lab** : Once Google has informed your SI or SoC partner on the technical approval request ticket (also can be known as pre-certification) that your project is ready to start the certification process, contact a third-party lab in order to proceed with the official certification. Google may request for you to ship samples to Google as needed. For more information, see the [Shipping Devices to 3rd Party Labs](https://developers.google.com/nearby/fast-pair/shipping-devices-to-3pl "Link to the page for shipping devices to 3rd Party Labs.") page. - **Receipt of Technical Approval** : You will receive a Technical Approval letter along with Fast Pair enablement on the [Nearby console](https://developers.google.com/nearby/devices "Link to the Nearby console."). - **Post Launch OTA** : Work with your SI or SoC partner on post-launch OTA update requests. For more information, see the [certification process](https://developers.google.com/nearby/fast-pair/certification-process#preparing_for_certification_via_self_testing "Link to the self-test section.") section.