Who this is for: This analysis is most relevant to independent repair shops, dealers and owners handling China-market Chinese-brand EVs outside China, especially where local software, configuration or diagnostic support is limited.
π Dataset at a Glance
Dataset period: 18 August – 26 September 2026 · Q3 2026 snapshot · Published September 2026
| Metric | Result |
|---|---|
| Requests classified as Software Service | 16 of 34 (47%) |
| Reporting period | 18 August β 26 September 2026 |
| Countries represented | 11 |
| Submitted by repair shops | 10 (63%) |
| Submitted by vehicle owners | 4 (25%) |
| Submitted by dealers / 4S stores | 2 (13%) |
| Chinese-brand vehicles | 15 of the 16 |
| ENET cable reported available | 12 (75%) |
| Smartlink-C reported available | 6 (38%) |
π What We Analysed
This article is a focused analysis of the 16 Software Service requests identified within the 34-request Q3 2026 dataset. The full dataset and the cleaning method behind it are covered in Chinese EV Remote Support: 34 Real Service Requests from 19 Countries. That article covers all 34 requests.
In short: the database held 55 request records. We removed 21 internal test submissions and analysed the remaining 34 genuine requests, received between 18 August and 26 September 2026 through the NEV Fix remote support request form.
"Software Service" is the category selected in the request form. The term describes how the request was classified; it does not mean that every issue was confirmed to be caused by software. The sub-groupings below are our manual reading of the request descriptions, not database fields, and they overlap.
Two limits apply to everything below. The request table records what customers asked for, not what was resolved β so every item here is a request, not a completed repair. And the counts are small enough that no brand-level or country-level rate can be derived from them.
We removed all identifying information. No VIN, customer name, phone number, email address, workshop name or precise location appears in this article. Countries are given as regions, and one request that concerned a non-Chinese model is noted as such.
π§Ύ What the 16 Software Service Requests Were About
The request form asks submitters to pick the software items they need. That field allows multiple selections, and the free-text descriptions often describe more than the selected item does. We therefore also read every description by hand.
| Request area | Requests mentioning this area | Examples of reported needs |
|---|---|---|
| OTA and system updates, version state | ~8 | "needs OTA upgrade", "rear screens not updating", "can we update it?" |
| Keys, accounts, apps and connected services | 4 | "master account", "mobile app control and key creation", "Bluetooth key stopped working" |
| Language and interface localisation | 3 | "change language to English or Spanish", "localisation causes interface problems" |
| Configuration or coding after hardware work | 2 | "need to write VIN after changing OBC", "configuration got wiped" |
| Owner-level settings and convenience functions | 2 | "change the time on the multimedia screen", "rear monitors not updating" |
| Charging or driveability with a suspected software cause | 2 | "says READY but does not move", "needs module update after losing charge" |
These areas are not mutually exclusive. A single request may appear in more than one row, so the counts above do not add up to 16. Fifteen of the 16 requests concerned Chinese-brand vehicles. One concerned a Chevrolet Spark EV, which we have kept in the totals rather than quietly dropping it.
| What the workshop or owner asked for | Type of software support |
|---|---|
| OTA or version update | Software update |
| Phone key not working after an update | Connected and key support |
| Master account change | Account support |
| Change the interface language | Localization |
| Replacement module needs the VIN written to it | Module configuration |
| Vehicle configuration lost | Configuration recovery |
| Diagnostic and update software for the workshop | Workshop tooling |
Who asked for what
| Requester | Requests | Software needs mentioned in the requests |
|---|---|---|
| Repair shops | 10 | Configuration and coding after hardware work, OTA and version updates, language change, diagnostic and update tooling |
| Vehicle owners | 4 | Accounts, keys and app control, update paths for China-market cars, convenience functions |
| Dealers / 4S stores | 2 | Localization and navigation, post-update function loss |
Within this dataset, software support demand was workshop-led, while the owner-submitted requests concentrated on access, apps and convenience functions. That is an observation about these 16 requests, not a statement about the wider market.
Which vehicles appeared most often
Zeekr, part of the Geely group, appeared in 4 of the 16 requests β more than any other brand in this subset. Leapmotor appeared in 3. The remaining requests each involved a different model.
On brand counts: four requests is four requests. This reflects where NEV Fix already has customers and visibility. It is not a ranking of which Chinese brands have the most software problems.
π» Five Recurring Patterns in the Software Requests
1. Language and interface localisation
Three requests asked for language or interface work, and they came from three different situations.
A dealer in Central Asia described a China-market Zeekr 7X running OS 6 with a third-party localisation already installed; according to the submission, the existing localisation was causing interface problems, and the request asked about an official update path. A workshop in South America wanted a Leapmotor C11 running LeapOS changed to English or Spanish, and reported that it had not been able to do it. A third request, from Eastern Europe, combined a language change with an update request on a Zeekr 001FR.
One further request in this subset concerned a clock setting rather than a language: a workshop asked to change the time shown on the multimedia screen of a Neta GT. Together these show that "localisation" covers everything from a full interface language change down to a time-zone setting.
Whether a language change is possible at all depends on the brand, the market the car was built for, and the installed software version. In this dataset we can say only that people asked; we did not record which requests were completed.
2. Keys, accounts and connected apps
Four requests concerned access rather than faults: a BYD Sealion 06 DM-i owner asking for a master-account change, an Xpeng Mona M03 owner asking for app control and key creation across six vehicles, a Zeekr 007 reporting that the phone Bluetooth key stopped working after a system upgrade, and a Leapmotor C11 workshop reporting that keys had been programmed incorrectly.
These requests focused on access and connected functions rather than conventional fault repair. What the owner or workshop could not do was use a particular vehicle function β unlock it, start it, or reach it from a phone. For overseas owners of China-market cars, these access and connected-function issues can arise even when the immediate concern is not a conventional vehicle fault.
3. Configuration and coding after hardware work
Two requests arrived after a component had already been replaced, with the remaining problem sitting in configuration rather than hardware.
A Russian workshop had replaced the on-board charger on an SAIC Rising R7 with a used unit and needed the VIN written to the replacement module. A workshop in Eastern Europe reported that a key-programming operation on a Leapmotor C11 had been carried out incorrectly and that the vehicle configuration had been wiped as a result.
A similar pattern appears in the wider dataset. In our first article we described a Geely Lynk & Co Z10 whose configuration was lost after an interrupted software operation, and a GAC Aion bZ3X that had arrived with a donor-vehicle configuration. In these requests, replacing a component was not necessarily the end of the service process; the remaining issue involved vehicle-level configuration, component matching or fault-code interpretation.
4. OTA updates and version state
Roughly eight requests touched updates, though often indirectly. Some submitters asked for an update outright. Others described a symptom and suspected the software version: a Li Auto L6 workshop reported a LiDAR fault and asked whether an OTA upgrade would correct it; a NIO ET9 owner reported rear entertainment monitors that would not update; an Avatr 12 owner in the Middle East listed the installed versions and asked whether an update path existed for a China-market car.
One request came from a workshop in the Middle East that did not want a one-off fix at all β it wanted the manufacturer's diagnostic and update software running on its own laptop, so it could service Zeekr vehicles itself. That is a different kind of request, and it points at a capability gap rather than a fault.
5. Owners asking directly
Four of the 16 requests came from vehicle owners rather than workshops, compared with 9 of the 34 across the full dataset. In this subset, owner requests were concentrated around access and convenience β accounts, apps, screens and keys β while workshop requests more often involved configuration, updates and tooling.
One owner in the Caribbean asked for app control and key creation on six vehicles and, in the same request, noted that they had neither an ENET cable nor a Smartlink-C interface and wanted advice on which to buy. That combination β a software task and no diagnostic hardware yet β is worth flagging for anyone planning remote support.
π οΈ Five Real Software Requests, in Detail
1. A China-market SUV with a third-party localisation β Zeekr 7X, Central Asia
A dealer submitted a company-owned Zeekr 7X, China-market version, currently running OS 6 with a third-party localisation already installed. According to the submission, the existing localisation was causing interface problems. The request covered language, navigation and update work in one submission, and asked about a longer-term arrangement rather than a single fix.
What we can say publicly: the request existed, and it came from a business building its own in-house capability rather than a workshop stuck on one car. We are not publishing the localisation method, the software source, or the company name.
2. A wiped configuration after key programming β Leapmotor C11, Eastern Europe
A workshop reported that a tool had been used incorrectly during a key-programming operation on a Leapmotor C11 extended-range model. According to the submission, the keys were programmed incorrectly and the vehicle configuration was wiped as a result. The workshop reported having a Smartlink-C interface.
This is the clearest example in the subset of a software-state problem created by a service operation rather than by a failure. The case illustrates why model and software-state verification matters before key or configuration work.
3. A Bluetooth key that stopped working after an update β Zeekr 007, Middle East
A dealer reported that after a system upgrade on a Zeekr 007, the phone Bluetooth key no longer worked and the doors could not be opened with the phone. The submitter asked whether the function could be restored and what it would cost.
We are describing the request, not the remedy. Post-update function loss on a specific module is a diagnosis problem, and the correct next step depends on a scan of the vehicle's current software state.
4. An owner listing software versions β Avatr 12, Middle East
An owner of a 2025 China-market Avatr 12 submitted the installed software versions directly β HarmonySpace 5.0.0.105 and AVATR.OS 4.7.0 β and asked about an update path. The request named the market the car was built for, an important factor when determining whether an update path may be available. The request did not establish whether an update was available or appropriate.
This is a useful template for anyone submitting a software request: model year, market version, and current software version. These three fields are the most useful information to include when submitting a software request.
5. A LiDAR fault and a request for an OTA upgrade β Li Auto L6, Caucasus
A workshop reported a fault code on a Li Auto L6, recorded in the request as c17d644-08, and stated that the LiDAR was not working normally. The submitter asked for an OTA upgrade to correct it.
We cannot say from the request whether an update was the correct remedy. We have published a separate case involving module failure after an OTA update on a Li Auto L9, which is a useful counterweight: updates can fix software-state faults, and they can also expose hardware that was already failing.
π What This Means for Overseas Workshops
- Software Service was the largest single request category in this dataset, accounting for 16 of 34 requests (47%).
- Access problems arrive before fault problems. Keys, accounts and apps accounted for four of the 16 requests, and they usually reach us from owners.
- Expect configuration work after parts are replaced. Two requests in this subset arrived after a component had been swapped, with the remaining issue in configuration or coding.
- Diagnostic hardware availability was uneven. ENET cables were reported as available in 12 of the 16 requests (75%), but Smartlink-C in only 6 (38%).
- Some workshops want the tooling, not the answer. One request asked for manufacturer software on their own laptop β a capability question, not a repair question.
For NEV Fix this shapes how a remote diagnostic support session starts. Before a remote software-support session, we need the model year, the market the car was built for, and the current software version β the three fields the Avatr request happened to include and most others do not.
NEV Fix's workshop equipment guide covers the hardware typically needed for software and configuration work, and Parts Lookup can help confirm the correct part once a diagnosis points to a replacement component.
βοΈ What This Dataset Cannot Tell Us
- It is not a market survey. These are requests received by NEV Fix, not a representative sample of Chinese vehicles overseas.
- It cannot establish failure rates by brand or model. Sixteen requests across eleven countries is far too small.
- It does not show outcomes. We recorded what was asked for, not what was resolved, so no success rate appears anywhere in this article.
- Category boundaries are imperfect. The areas above are our reading of the request text, and they overlap.
- Six weeks is a short window. Software and update behaviour changes with release cycles, which this period does not capture.
These limits matter because the dataset describes NEV Fix's incoming service requests, not the wider Chinese EV market. That is what allows another workshop to use the numbers properly.
π§ How to Prepare
- Record the three fields before you ask. Model year, market version, current software version. These three fields are among the most useful pieces of information to provide when submitting a software-support request.
- Capture a full scan before any software operation. Two requests arrived after a configuration had already been changed or lost.
- Confirm your interface covers the model. Smartlink-C was reported as available in only 6 of the 16 software requests.
- Do not treat an update as a diagnosis. One request asked for an OTA upgrade to clear a fault code. An update may resolve a software-state or compatibility issue, but it should not be treated as proof that a hardware fault has been repaired.
For workshops handling Chinese-brand vehicles regularly, developing in-house software and diagnostic capability may be useful alongside remote support. NEV Fix runs EV repair training programmes in Guangzhou for workshops building that capability.
You can read the full dataset analysis in our Q3 2026 service request article, and browse further first-hand cases in the tech blog β including the GAC Trumpchi S7 remote diagnosis case and the BYD Seal 05 charging fault diagnosed in Iraq.
β Frequently Asked Questions
How many Chinese EV software support requests did NEV Fix receive?
NEV Fix recorded 16 requests classified as Software Service in the request form, out of 34 genuine overseas service requests between 18 August and 26 September 2026. That is the same number as fault-repair requests (11) and fault-diagnosis requests (5) combined.
What kinds of software work do overseas workshops ask for?
In this dataset: OTA and system updates, key and account access, language and interface localisation, configuration after component replacement, and owner-level settings such as screen time and entertainment functions.
Can a China-market car be changed to English or another language?
It depends on the brand, the market the car was built for and the installed software version. Three requests in this dataset asked for language or interface work. We recommend submitting the model year, market version and current software version so the answer can be given for your specific car.
Why do software problems appear after a part is replaced?
Because the replacement module may need to be matched or configured to the vehicle. Two requests in this subset arrived after a component had been swapped, with the remaining issue in configuration rather than hardware β including one where a used on-board charger needed the VIN written to it.
Do I need special hardware for software and configuration work?
Often yes. In this subset, ENET cables were reported as available in 12 of the 16 requests (75%), but Smartlink-C in only 6 (38%). Coverage varies by brand and model, so it is worth checking before booking a session.
Is this data representative of all Chinese EVs overseas?
No. It is a snapshot of requests received by NEV Fix between 18 August and 26 September 2026. It is not a statistically representative market survey and cannot establish failure rates by brand or model.
Need Software or Configuration Support for a China-Market EV?
Send us the model year, the market the car was built for, the current software version, and any fault codes or error messages available. NEV Fix runs remote diagnostic sessions using your existing workshop equipment and the vehicle's own diagnostic interface.