The question of CarPlay certification validity is asked repeatedly. Many assume that once they have MFi approval, they are set forever – only to find new models cannot be produced the next year. The root cause is misunderstanding how Apple’s MFi system works.

1. Two Separate Layers – Membership vs. Product Approval

1.1 MFi Membership and Product Approval Are Not the Same

CarPlay does not follow the traditional certificate model – it sits within Apple’s MFi (Made for iPhone/iPod/iPad) licensing programme. Companies receive two distinct things:

·MFi Enterprise License – annual fee, signed agreement – gives access to CarPlay specs and the MFi Portal. This licence requires annual renewal – non‑payment = suspension.

·PPID (Product Plan ID) – each CarPlay product is individually submitted, tested at a CPTF lab, and approved by Apple with a PPID. The PPID has no expiry date – as long as the hardware design remains unchanged.

1.2 PPID Is Not "Permanent"

Saying the PPID is “long‑term valid” is true, but with conditions:

·Major hardware revision,

·Apple updates its Facets test system with a mandatory market‑compliance re‑check, or

·Random inspection finds production units differ from the approved sample –
Apple can revoke the PPID at any time. Compliance is ongoing – not a one‑time event.

  2. Annual Fees – What You Actually Pay

2.1 USD 99/Year – No Big Hidden Charges

The MFi base annual fee is USD 99/year – covers CarPlay and basic MFi spec access. The “USD 10,000/year” rumour confuses OEM partnership service fees with the standard membership – they are different items.
Revenue‑based discounts – none. The MFi Portal bill is fixed – no 10‑million‑revenue threshold for a reduction.

2.2 Renewal Cycle – Anniversary‑Based

The MFi year runs from your join date – not the calendar year. If you joined in May, renewal is next May.
There is no official 30‑day grace period in MFi terms – it’s an agent‑observed practice. Apple can suspend your access the day after the bill is overdue – the risk is yours.

2.3 Consequences of Non‑Payment – Worse Than You Think

The MFi agreement does not contain a clause like “you can restore within 6 months of arrears”. Companies have been formally terminated after just 2–3 months of non‑payment.
Once terminated, you must restart from scratch – new MFi agreement, new product plan, new CPTF tests. The cost is incomparable to simply renewing.

  3. When Your Product Changes – What Triggers What

3.1 Which Chip Is Actually Controlled

Wired CarPlay authentication uses the MFi Authentication Coprocessor – not the general USB‑C controller on your board. Replacing this coprocessor requires using a model on Apple’s MFi‑approved list – others are not accepted.
Ordinary USB‑C PD power‑management chips and USB hub chips are not controlled – don’t confuse them with the MFi crypto chip; a mistake here is costly.

3.2 Wired to Wireless – Not Always a Full Re‑Approval

Moving from wired to wireless CarPlay does not necessarily require a completely new PPID.

·If the same PCB already has Wi‑Fi and Bluetooth circuits and you just enable wireless CarPlay in firmware – file a change request – Apple may allow you to keep the existing PPID.

·If you add new wireless hardware modules, change RF circuitry, or replace the main SoC – that’s a new PPID application with full CPTF re‑testing.

3.3 Software Change Boundaries

·UI‑only changes with no CarPlay protocol‑stack impact – register in MFi Portal – no retest.

·Changes to CarPlay interaction timing, audio‑path strategy, or authentication flow – even with hardware unchanged – Apple may require retesting. The criterion is whether you changed CarPlay’s behaviour, not which code files you edited.

  4. Multiple SKUs – Don’t Copy Bluetooth Rules

4.1 No “Derivative Auto‑Exemption” for CarPlay

Multiple SKUs on the same hardware platform (new colours, different enclosures) can be filed as changes – but Apple does not have a “derivative PPID auto‑exemption” shortcut.
BQB allows derivative certification with only difference tests – CarPlay’s MFi system has no equivalent. Whether to bundle SKUs into one PPID or file separately is decided by Apple’s review – don’t plan based on Bluetooth rules.

4.2 Don’t Compare CarPlay with CE or BQB on “Strictness”

Some like to compare CarPlay with BQB or CE – it’s not meaningful.

·BQB: RF/protocol conformance.

·CE: EU directive compliance.

·CarPlay: cryptographic authentication, firmware interaction logic, MFi logo usage rights – completely different dimensions. Each system has its own rules – don’t mix them.

  5. How Long Does a CPTF Report Last?

5.1 Reports Are Long‑Term, But Not Inflexible

The CPTF report is tied to the PPID product plan – as long as hardware is unchanged, it remains valid – no fixed re‑test cycle.
However, if Apple releases a major Facets system upgrade (e.g., Facets 2 → Facets 3), new change applications must use the latest test suite. Existing products that haven’t changed can continue under the old spec – but Apple may request compatibility retesting with newer iOS versions during market checks.

5.2 When Standards Update – What Then?

Apple periodically updates CarPlay technical specifications. Products already approved do not need immediate re‑testing.
But for major changes – those change items must follow the current latest specification. Existing products can continue production under the old spec – there is no fixed cut‑off date (unlike EU EN standards with transition periods). But Apple does have its own update rhythm.

For CarPlay MFi compliance, contact BlueAsia at 13534225140 (King) or king.guo@cblueasia.com.