Published 2026-10-08 · DIYCarPlay Engineering Team
CarPlay for Cars Without CarPlay: Sizing the Retrofit Market by Head Unit Generation
CarPlay for cars without CarPlay is not one product but a parc of vehicles, and the parc is only countable by head unit generation rather than by model year. A distributor who orders against model years ends up with stock that fits nothing; a distributor who orders against head unit platforms ends up with inventory that fits the cars that are actually still on the road without CarPlay.
The distinction matters because the eligible population is defined by what the car left the factory with, not by what the badge suggests. A 2014 car and a 2019 car from the same model line can need different modules, and in some cases the newer car is the harder retrofit because it already carries a wired CarPlay input that has to be replaced rather than added. What follows is the structure a buyer needs to size that population: how to classify a vehicle, what to verify on a sample before scaling, and which commercial terms decide whether the programme is viable.
On the phone side, Apple documents what CarPlay expects from a vehicle in its CarPlay support documentation, and the CarPlay entry on Wikipedia sets out how the interface has moved between generations. Neither describes the module that does the retrofit work, and neither is the basis on which modules should be selected.
What actually counts as a car without CarPlay
The phrase covers three different technical situations, and they carry different margins, different installation times and different failure modes. Treating them as one product category is the most common reason a retrofit programme stalls after the first shipments.
- No CarPlay hardware at all. The head unit predates the CarPlay standard and has no CarPlay input on the factory connector. This is the cleanest case: the module supplies the missing function and the factory screen, menu, steering-wheel controls and reversing camera all stay in place.
- A wired CarPlay input that is not populated. The head unit has the port but the vehicle was not ordered with the CarPlay option, or the dealer did not enable it. The module drives that input rather than emulating a new one.
- A wired CarPlay input that is already occupied. Some later head units accept a CarPlay device on the factory USB port and hold a persistent pairing. Adding a second source to that head unit means displacing the existing function rather than extending it, which is a different installation job.
The third case is where volume expectations go wrong. It is not a bigger market; it is a smaller and more technical one, and the modules built for it are not interchangeable with the ones built for the first case.
Sizing the eligible parc by year band
The table below is an approximation, not a fitment list. Head units were phased in mid-model-year across overlapping platforms, so a build date matters as much as a model year. Its purpose is to size a market, and a specific vehicle still has to be checked against the fitment data before it is counted.
| Model year band | Typical factory infotainment | CarPlay from the factory | Retrofit position |
|---|---|---|---|
| 2006–2011 | BMW CIC, COMAND NTG4.0, Audi MMI 2G, Volvo Sensus VO-1, Porsche PCM 3.1 | Not fitted | Core eligible population |
| 2012–2014 | BMW NBT, COMAND NTG4.5, Audi MMI 3G, Volvo Sensus VO-2, Land Rover/Jaguar JR-1 | Not fitted, or wired only on some trims | Core eligible population, highest fitment clarity |
| 2015–2017 | Audi MIB2 and MIB3, COMAND NTG5.x, BMW EVO, Porsche PCM 4, Mercedes HU6 | Wired on most, wireless on some | Eligible; the wired input may already be occupied |
| 2018–2020 | MBUX, MIB3, PCM 4.0 and 5.0 | Wireless CarPlay standard | Retrofit demand shifts to camera and 360° passthrough |
| 2021–2025 | MBUX, MIB generations, latest head units | Fitted as standard | Largely outside the retrofit category |
Coverage behind this spans model years 2006 to 2025 and more than 300 vehicle models and series. The commercially useful part of that range is the first three bands, because that is where a vehicle without CarPlay is still a normal vehicle rather than a trimmed variant. The fitment finder maps an individual vehicle to the platform it carries.
Why head unit generation, not model year, picks the module
Every head unit generation needs its own firmware. The LVDS timing, the wake-up handshake, the reverse-trigger logic and the controller protocol all differ between them, which is why a BMW CIC module and a BMW NBT module are separate articles rather than one product with a software switch. Model year is a proxy for the platform and a poor one: mid-year changes mean a single model year can contain two platforms.
That is also why a broad order across many model years is more fragile than a narrow one across a confirmed platform. The head unit identification guide sets out the physical tells for each platform family, and the identification step is worth doing on a real vehicle rather than inferring from a registration year.
Two commercial consequences follow. First, stock has to be held per platform, so the cost of a misjudged platform is paid twice: once on the unit that does not fit, and again on the return freight. Second, the platform list is the part of the specification that has to be exact in a quotation, because a module described only by brand is not a product.
What to verify on a sample before scaling
A sample order is cheap relative to a first production run, and it is the only point at which several assumptions can be tested against real cars. The checks that catch real problems are specific rather than general.
- CAN wake-up. If the module does not wake with the ignition, the result is a dark factory screen that reads as a dead head unit.
- Reverse trigger. A module that back-feeds the video path at the wrong moment corrupts the picture the driver expects when reversing, which is a safety complaint rather than a cosmetic one.
- Display timing. Driven at the factory timing for that specific generation, not at a generic setting. Wrong timing produces visible artefacts that customers describe as a cheap display.
- Controller protocol. The rotary controller or touch interface exercised through the full menu, including the return path to the factory system.
- Two-way audio. Microphone and speaker paths both confirmed. A microphone path that only works in one direction produces echo complaints instead of an obvious failure, and echo is much harder to diagnose in the field.
- Wireless handover. Pairing, reconnection after ignition cycling, and behaviour in a multi-storey car park.
These are the checks a factory should be running on every unit before packing, not only on samples. A supplier that runs them only on samples is charging the customer to find out whether the production run works.
The hardware that decides the return rate
Return rate is the line item that decides whether an import programme is viable, because a returned unit costs far more than its margin: the module is written off, the customer relationship is spent, and freight is paid in both directions for nothing. Two specification choices do most of the work in keeping it down.
The first is the chipset. These modules run an embedded Linux configuration on an automotive-grade chipset from Taiwan's Sunplus, a supplier building for sustained in-vehicle operation across temperature and voltage ranges. Smoothness comes from the silicon rather than from allocated system resources, because the operating system layer is fixed. That is the same reason premium factory infotainment systems stay fluid after years of service: the computers behind those panels are themselves Linux machines.
The second is the wireless link. Phone mirroring is a continuous video transfer, so the modules use dual-band WiFi across 2.4GHz and 5GHz, with the 5GHz band carrying the stream where conditions allow. The 2.4GHz band is congested in multi-storey car parks and underground structures; the 5GHz band is where the headroom is. A single-band module that drops the link in a concrete basement generates a support call that costs more than the hardware saved.
The operating system choice is the third factor, and it is the one that separates this category from a different product altogether. An aftermarket Android head unit requires replacing the factory screen, and it accumulates cached data as it runs, so a unit that feels quick on day one is not the same unit in year three. A Linux-embedded module that keeps the original OEM screen does not accumulate in the same way, because there is no general-purpose application layer being asked to run an interface it was never sized for. The module catalogue lists what exists per platform today.
Platform families that move volume in practice
Demand in this category is not evenly spread across the 300+ models and series. A handful of platform families carry most of the volume in the European, North American and Australian retrofit markets, because those are the platforms with the deepest parc and the clearest fitment.
| Platform family | Why it carries volume | Watch for |
|---|---|---|
| BMW CIC / NBT / EVO | Three overlapping generations across a very large parc, all built before wireless CarPlay | EVO and NBT are not interchangeable despite sharing a model range |
| Mercedes COMAND NTG4.0 / NTG4.5 / NTG5.x | Long production runs across several chassis families | Audio 20 versus Audio 30 changes the harness, not just the module |
| Audi MMI 2G / 3G / MIB | Very high fitment clarity and strong dealer familiarity | MIB spans both retrofit and already-CarPlay vehicles |
| Volvo Sensus / Land Rover and Jaguar | Two large, well-defined retrofit-only populations | Bose and Harman audio variants need separate harnesses |
| Porsche PCM 3.1 / 4.x | Retrofit-only across early and mid generations | PCM 4.0 arrived after CarPlay became common, so demand falls off sharply |
Starting a programme on two of these families is generally a better use of a first production run than spreading the same units across six, because the platform-specific setup cost is amortised over fewer distinct builds. The first-container SKU guide works through how to build that order shape.
Commercial terms for this product category
The terms below are the ones that decide whether a first container is a reasonable test or an expensive mistake. They should be fixed in writing before a purchase order is issued rather than agreed in an email thread afterwards.
| Term | Structure | Why it matters to a buyer |
|---|---|---|
| Stock MOQ | 10 pcs, mixed models allowed | Lets a new distributor test several platforms without committing to volume on one |
| Private label | 500 pcs per model | Logo on device, packaging, manual and warranty card |
| Full OEM | 1000 pcs per model | Custom firmware interface, boot logo, language packs, hardware revision where required |
| Sample lead time | 7–15 days by DHL or FedEx | Sample cost is deductible from the first large-volume order |
| Volume lead time | 15–20 days for 500+ pcs | Starts from cleared payment, not from the enquiry |
| Payment | 30% deposit, 70% against a copy of the bill of lading by T/T; PayPal for samples | Sets the cash cost of the first order, not just the unit price |
| Quotation | Within 12 hours | Slow quotation is a signal about order handling |
Incoterms sit alongside these and are the line most often skipped in an email thread, which is how they become a dispute. FOB, CIF and DAP place freight and insurance on different sides, and the incoterm guide for car electronics importers sets out where each one bites.
Questions that settle a retrofit programme early
Seven questions resolve most of the ambiguity, and all of them can be answered in writing before money moves.
- Which head unit platforms are covered, at which firmware version, for this quotation?
- Is the platform list based on head unit generation, and does it name the variants within each generation?
- For a vehicle that already has a wired CarPlay input, does the module extend it or displace it?
- Which of the bench checks are run on every unit, and which only on samples?
- What is the sample lead time and the production lead time stated separately?
- Is the sample cost deducted from the first large-volume order, and is that written down?
- What return rate is assumed, and what is the claims process?
The third question does more to predict whether a programme works than any pricing question. A supplier who answers it precisely has thought about the head unit rather than only about the module.
Common questions
Can any car get CarPlay added?
No. The car has to have a factory head unit platform that a module exists for, and it has to be a platform where the module can reach the display and the vehicle bus. Large parts of the 2006–2025 model range qualify; the rest do not, and no module changes that.
Does the factory screen get replaced?
No. The module sits behind the head unit and feeds the screen already fitted to the dashboard. The panel, the factory menu, the steering-wheel controls, the rotary controller and the original reversing camera all remain in the car.
Is wireless CarPlay the same as a wired retrofit?
The wireless link is a dual-band WiFi connection using 2.4GHz and 5GHz, with the 5GHz band carrying the video stream where conditions allow. A wired retrofit uses the factory CarPlay input instead. Both approaches keep the original screen; they suit different vehicles and different customer expectations.
Will the unit slow down after a year of use?
The modules run a fixed embedded Linux configuration on an automotive-grade Sunplus chipset, with no application layer accumulating cached data. Behaviour after a year of daily use stays close to behaviour on day one, which keeps the aftersales load proportional to units sold rather than growing with the age of the fleet.
What is the smallest sensible first order?
Ten pieces with mixed models allowed. That entry point is deliberately cheap, because its purpose is to establish which platform generations actually move volume in a given market before any tooling or firmware work is funded. The wholesale programme page sets out all three tiers in full.
Request a quotation
Send the target vehicle list, the head unit generation for each entry, the quantities being planned and the target market. A quotation comes back within 12 hours, stating module fitment, MOQ tier, lead time and payment terms for the platforms named. The inquiry form is the fastest way to get a figure; we will tell you plainly if a vehicle on your list has no module.
Need the Module From This Guide?
Wholesale from 10 pcs (mixed models OK), samples in 7–15 days (DHL/FedEx express). Fitment confirmation within 12 hours.
Request Pricing Check FitmentRelated Resources
- CarPlay Collections — browse by marque family (German, British, Italian, Japanese, luxury)
- CarPlay Fitment Checker — find the module for your car
- CarPlay Decoder FAQ — 34 answers on compatibility, install and wholesale
- CarPlay Retrofit Buying Guide — platform identification & selection
- Wholesale, Private Label & OEM Program — MOQ, lead times, payment terms
- All installation & technical guides