CarPlay hangs under Apple's MFi authorised programme, but it is not a traditional pass certificate. What a company actually receives are two things: the MFi membership licence (pay the annual fee, sign the agreement, get back-office access) and the PPID product approval (each model tested separately, Apple issues a number). These two are bound together but must not be treated as one. The membership governs whether you can enter the door and move things in the back office; the PPID governs whether this specific product may ship.
2. Membership Licence: Renew Every Year, but Front-Fit and Aftermarket Are Not the Same
Aftermarket products follow the standard MFi accessory programme, with a base annual fee of 99 US dollars.
(1) It runs on your membership anniversary, not the calendar year.
① The day you miss payment, Apple can cut your back-office access; the agreement grants no "few months grace" favour. I have seen the person owning this leave, nobody renewed, and the previous half-year wasted. Set a calendar reminder for the MFi annual fee renewal.
(2) Whole-vehicle front-fit is a different route.
① Front-fit carmakers engage the Apple Automotive Partner Programme, negotiating business directly with Apple's automotive team — it does not enter the MFi accessory programme at all, so there is no 99-dollar fee. People often mash the "whole-car maker special cooperation fee" together with the 99-dollar base fee; they are two separate bills. If you serve carmaker clients, do not get dragged into the MFi accessory programme by mistake — entering it is a wasted trip.
3. PPID Approval: No Expiry Date, but With Conditions
As long as the hardware scheme is unchanged, it stays valid.
(1) A major controller change, a forced Facets version review, or a mismatch between mass production and the submitted sample lets Apple revoke at any time.
① Do not think "once passed, set in stone" — compliance is continuous. Swapping the MFi certified coprocessor, even if you picked an Apple-listed model, still triggers a PPID change assessment the moment hardware moves; picking a listed part does not auto-waive review.
(2) Lapsing membership does not void all PPIDs.
① Missing payment blocks new applications and new changes. Already-shipping old PPIDs will not batch-expire overnight, but you cannot file changes, appeal, or get technical support, so later maintenance becomes impossible. Do not harbour the idea that "lapsed membership lets me freely edit old PPIDs."
(3) Facets is the test framework.
① CarPlay's automated test framework is called Facets, now at Facets 3, with cases auto-generated from the parameters you fill in the PPID. A major version upgrade may demand a fresh compliance review; do not expect one pass to last a lifetime.
4. There Is No "Three-Year Renewal"
The fixed-term model of CCC does not apply to CarPlay.
(1) As long as membership stays alive and the product is not substantially changed, the certificate stays valid across the product's whole lifecycle.
① Do not map SRRC's five years or CCC's five years onto this. SRRC, FCC, and CE-RED are regional wireless certifications that have validity periods — different from CarPlay.
(2) Keep the two validity clocks separate.
① CarPlay has no expiry; each country's wireless certificate does. Mixing FCC or CE-RED's five-year validity with CarPlay will confuse any client who hears it.
5. What Triggers Retesting
A major design change needs re-evaluation.
(1) Changing the main controller chip or the wireless communication scheme counts as major. Changing the housing or non-critical components — do not decide "not major" on your own; always submit to Apple for a change assessment; Apple decides whether retesting is needed.
① Most iOS major versions do not affect certified products; Apple will not force old PPIDs to retest on a normal system update, but it can initiate a review through market sampling and compatibility feedback, and that review can genuinely lead to retesting — it is not absolutely never.
(2) Wireless-scheme changes are the big one.
① Swapping Bluetooth or Wi-Fi modules definitely retests; do not gamble on luck.
6. Do Not Skip Packaging Review
Tests pass, but the packaging gate remains.
(1) What is checked is MFi mark usage and the compatibility statement.
① Generally 1 to 3 weeks; if projects pile up it stretches, so do not treat it as a hard deadline to lock the schedule. Wrong mark usage or an over-broad statement gets bounced back just the same.
(2) Mark rules are meticulous.
① Logo ratio and placement both matter. Send the packaging artwork to Apple for review first; do not wait until after printing to find it wrong.
7. Practical Advice
Materials in English, matching the sample; prepare three months ahead.
(1) Do not draw the bench wiring diagram too casually.
① BlueAsia provides one-stop certification and lines CarPlay up with HiCar and CE-RED in one window, testing what can be tested together to save both time and money.
(2) Test multiple ecosystems together.
① Android Auto, HiCar, and CarPlay can share the hardware schematic and BOM, but the three ecosystems' test reports and cases are completely non-interchangeable — do not assume documents can be borrowed across them.
CarPlay is a live permission, not a one-time stamp; keep membership current and treat every hardware move as a potential PPID event.
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!
相关新闻
