Body Control Module (BCM) replacement used to be straightforward on combustion vehicles — swap it in, program with your J2534 passthrough, done. On modern EVs, the BCM is deeply integrated with the BMS, the HV contactor control and the immobiliser system. A replacement BCM that isn't properly paired will prevent the vehicle from entering Ready mode entirely.
Legacy immobilisers used a transponder in the key that communicated with a standalone immobiliser ECU. Most modern EVs use a distributed security architecture: the key fob communicates with the Body Domain Controller (BDC), which validates credentials against a security token shared with the VCU (Vehicle Control Unit) and BMS. Replace any one of these modules and the token needs to be re-established across all three.
On top of this, the fob itself stores encrypted session tokens that expire — which is why "I bought a spare key online" almost never works without programming even if the fob is physically correct.
BYD uses a cloud-authenticated key learning process on all models from 2020 onward. The sequence requires:
The actual programming takes 3–5 minutes once the cloud session is established. The most common failure point is an unstable internet connection during the server handshake — use a wired connection or confirmed-stable mobile hotspot.
NIO uses NFC-based key cards in addition to fobs and phone-as-key. The key card pairing is handled entirely via the NIO app and requires the vehicle owner's NIO account credentials — there is no OBD-level programming path for NIO key cards. Workshops cannot add or remove NIO key cards without owner involvement.
For NIO key fob replacement (separate from key card), the process requires NIO's dealer tool. Third-party support is limited as of 2025.
VW's MEB platform uses the standard VW Group key learning procedure, compatible with ODIS (dealer) and VCP Pro (third-party). The process is straightforward compared to Chinese-market EVs:
The ID.4, ID.3 and ID.Buzz all follow the same procedure. BCM (module 09) replacement requires online authorisation via the VW Parts Portal — this is the locked step for non-ODIS users.
Tesla's key management is entirely cloud-based and tied to the owner's Tesla account. Adding a key card, phone key or fob requires the owner to authorise it via the Tesla app or an existing authenticated key. There is no OBD-level key programming path for Tesla, and Tesla's Service Mode key management functions require IRP credentials.
Workshop policy recommendation: Require the vehicle owner to be present for any key programming job — regardless of platform. This protects you legally and simplifies the cloud auth process on platforms that require owner credentials.
Supports BYD BDMS, VW MEB and selected GM/Ford platforms for key learning and BCM initialisation.
Get B2B Catalog →