As of September 2026, Mercedes-Benz is not one of the eight platforms we run remote OE sessions on, and there is no Mercedes-specific IMMO-OFF product on this site — what we do carry is checksum work on the Bosch MED17 and EDC17 families that appear in Mercedes applications, and a free specialist network where operators with the right tooling bid on the rest. That is a shorter answer than most sites give, and it is the accurate one.
We publish this rather than burying it because the alternative — letting a Mercedes owner pay for something adjacent and discover the gap afterwards — costs everybody more. If you want the general map of what we do not carry and why, our brands-we-do-not-cover post is the companion to this one.
What the coverage matrix actually says about Mercedes
Our coverage matrix is organised by controller family rather than by badge, and Mercedes appears in it indirectly: the Bosch MED17 and EDC17 entries list Mercedes among the manufacturers those controllers were fitted to, alongside VW, Audi, BMW and others.
For those entries the two statuses differ from one another, and that difference is the whole story. Checksum work on that family is live. The immobiliser side is not — it is listed as a development target, which in our vocabulary means it is on the roadmap and is not a product you can buy today. Our coverage status guide explains exactly what Live, Beta, Soon and Manual commit us to, because a status that means nothing is worse than no status.
“Mercedes is the brand where people are most surprised we say no. The assumption is that a big shop covers everything. Coverage is a controller-by-controller thing and the badge on the bonnet does not decide it.” — Bench technician, remote programming desk
Why there is no Mercedes remote session
Our flash pagecarries eight platforms: GM at $100; Ford/Lincoln, Nissan/Infiniti and Mazda at $150; Toyota/Lexus, Volvo, VW/Audi and Mopar at $250. Each one exists because we hold a current subscription to that manufacturer's own programming application and can drive it against your J2534 device over the internet.
A platform gets added when the demand justifies the standing cost of the subscription, not when somebody asks. That is the entire mechanism, and it is why our tier pricing tracks licence cost rather than difficulty — explained in full in our session pricing breakdown. Mercedes has not crossed that line here. Saying “we can probably do it” and then finding out on your customer's car is the outcome we are avoiding.
| Mercedes job | Route here | Price |
|---|---|---|
| Checksum repair on a MED17 / EDC17 application | File service | Per coverage matrix |
| Mercedes IMMO-OFF as a patched file | Not offered — post to the network | — |
| Remote OE programming session on Mercedes software | Not a platform we carry | — |
| Module that will not power up | Bench job, not a session anywhere | — |
| Anything else Mercedes-specific | Specialist network — free to post | You set the budget |
The network is the actual answer for most Mercedes jobs
This is not a consolation prize. Our specialist network exists for exactly the shape of problem Mercedes work presents: real demand, specialised tooling, and no sense in us pretending to hold a capability we do not.
Posting is free. You describe the vehicle, the controller and what you need; operators who genuinely work that platform bid; you pay only if you accept a bid. If nobody bids, you have lost nothing but the five minutes, which is a materially better outcome than paying a deposit to somebody who will “look into it”. Our guide to hiring an ECU specialist covers how to write a post that gets useful bids rather than vague ones.
For a locksmith with a Mercedes on a hook, our locksmith routing post covers the decision from a van, and the all-keys-lost routing guide is essential reading before you quote anything on a car with no working key — a fair share of those jobs are not sessions on any platform.
Writing a network post that gets real bids
Since the network is the route for most Mercedes work, it is worth five minutes on what separates a post that attracts competent bids from one that attracts silence or guesses.
- Identify the controller, not just the car. “2014 Mercedes” is a starting point. The controller part number from the module label is the actual question, and our label-reading guide covers which number that is. Photograph the sticker and attach it.
- Say what state the module is in. In the car and communicating, in the car and dark, or on your bench already. Those are three different jobs and operators bid differently on each.
- Say what read you have, if any. A usable read already in hand can halve a job. A read taken the wrong way is worse than none, which is why our read-method comparison is worth a look before you take one.
- Name the outcome, not the technique.“Car needs to start and run after a used ECU was fitted” lets an operator propose the right route. Asking for a specific operation by name pre-commits you to a plan you may not need.
- Be honest about the history. If somebody has already attached a tool and something went wrong, say so. Operators price uncertainty, and concealed history is the most expensive kind.
Our guide to hiring an ECU specialist covers judging the bids that come back, including what a suspiciously confident one usually means.
What to check before you assume it is a Mercedes problem
A surprising number of “Mercedes ECU” calls turn out to be one of three things that have nothing to do with the badge.
A donor module fitted without configuration.A used controller carries the previous car's identity, and the symptom is a no-start or a network storm rather than an obvious configuration complaint. Our swapped-ECU no-start guide covers the causes in the order worth checking, and the VIN-mismatch guide covers what the car does when identity is wrong rather than absent.
A hardware fault, not a software one. Internal processor faults, water ingress and cracked solder are repair jobs rather than programming jobs. Our P0606 guide walks through distinguishing the two, and a free DTC lookup is quicker than guessing.
A signed controller.On modern applications the bootloader validates a cryptographic signature before accepting a write. Where that is true, no tool and no vendor gets past it, and a vendor claiming otherwise is telling you something useful about themselves. Our catalogue lists VAG's Simos PCR2.1 as RSA-signed and unsupported for exactly this reason; the signed-bootloader post explains the mechanism.
The three Mercedes questions we can answer today
Rather than leave this at a list of noes, here is what a call about a Mercedes can usefully get from us right now.
Is this a programming problem or a hardware problem? That question is platform-independent and we answer it every day. A module reporting an internal fault that survives every reset, a unit with water ingress, a controller that is simply dark — those are repair jobs, and identifying them early stops you paying anybody for software that cannot reach the part.
Which controller is actually fitted? Photograph the module label and drop it into the free identifier. On a Mercedes that has been repaired before, what is fitted and what the VIN says should be fitted are frequently different, and knowing which family you are holding is what turns a network post from a guess into a brief.
Is the checksum side something we cover?For the Bosch families used in Mercedes applications, often yes. That is a narrower answer than “we do Mercedes” and it is a real one — check your exact variant on the coverage matrix rather than assuming either way.
Why we publish the gaps
A coverage page that only lists wins is an advertisement. The entries that say Soon, Manual or not supported are what make the Live entries worth believing, and they are the reason a returning customer trusts a yes from us.
It also saves both sides money. The most expensive outcome in this trade is not a job we turn away; it is a job somebody accepted optimistically, worked at for a week, and handed back with the car in a worse state than it arrived. Our provider red-flags post covers spotting that pattern in other vendors, and publishing our own limits is the only consistent way to make that advice credible.
The European context
Mercedes sits inside a wider pattern we wrote about in our European ECU service guide: European platforms concentrate their difficulty in access control rather than in the calibration work itself. Component protection on VAG, credentialed access on several premium marques, signed bootloaders across the newer generations — the pattern is consistent, and it means the question “can you do it?” is nearly always an authorisation question rather than a skill question.
Where a security gateway is the obstacle, our gateway post sets out the four legitimate routes past one and is explicit that there is no fifth. NASTF administers the registry U.S. technicians use for credentialed secure vehicle access, and SAE J2534 defines the pass-thru layer underneath all of it.
What would change this
Two things would move Mercedes from this post into the coverage matrix or onto the flash page: enough sustained demand to justify a subscription, or an IMMO-OFF operation reaching Live status on a controller family widely used in Mercedes applications. Both are real possibilities and neither is a promise.
In the meantime, the useful thing you can do is post the job. Real volume in the network is the evidence that moves a platform up the list, and it gets your car handled this week either way. The coverage matrixis the live document — it changes, and it is always more current than any blog post including this one.
We do not provide emissions defeat, delete files, or services intended to bypass emissions laws. Our services exist for tuning preparation, diagnostics, repair, motorsport, and off-road use where legally permitted. Customer is responsible for confirming legal use in their location and application.
That matters particularly on the diesel side, where a great deal of what gets requested under a Mercedes heading is emissions equipment removal. We decline it on every platform — our diesel post is the unambiguous version — and Section 203(a)(3) of the federal Clean Air Act is why that is not a negotiating position.
The short version
No Mercedes remote session, no Mercedes IMMO-OFF file. Checksum work on the Bosch families that appear in Mercedes applications is live — check the coverage matrix for the exact controller. Everything else routes to the specialist network, which is free to post to and costs nothing unless you accept a bid. Photograph the module label and run it through the free identifierfirst, because the controller family is what decides the answer — not the star on the grille.