Vehicle Coverage Find a Distributor Support Global / EN
Article

Why Your OBD2 Scanner Can't Program Keys: A $3,200 Mistake I Documented

Posted on 2026-09-18 by Rafael Ibarra

The Surface Problem: It Reads Codes, So Why Won't It Program a Key?

I've been handling shop equipment orders for 8 years. I've personally made (and documented) 6 significant mistakes, totaling roughly $4,800 in wasted budget. Now I maintain our team's checklist to prevent others from repeating my errors.

The mistake that keeps coming back? Assuming an OBD2 scanner is an OBD2 scanner.

In September 2022, I approved a $3,200 order for three scanners because the product page said they were 'universal' and 'all-system.' We needed one for Chevy VIN decoding and another for key programming on a batch of used fleet vehicles. The scanners read codes. They showed live data. They even cleared a P0300. But when my tech tried to program a key, the menu stopped at 'function not supported.'

That error cost $890 in return shipping and restocking fees, plus a 1-week delay. Worse, we had to tell a customer their vehicle would stay in the bay longer. (Ugh.)

If you're searching for what OBD2 scanner can program keys, the short answer is: not every OBD2 scanner can. And the word 'universal' on a product page does not mean it will work on your exact vehicle.

The Deeper Reason: OBD2 Is a Language, Not a Skill Set

Here's what took me too long to understand. OBD2 is a communication standard. It tells you how a scanner talks to a vehicle. It does not tell you what the scanner is allowed to do once it's connected.

Put another way: OBD2 gives you the phone line. It doesn't give you the passwords to every room.

Key programming requires more than reading fault codes. It needs security access to the immobilizer or body control module, bidirectional control, and manufacturer-specific protocols. A generic code reader might read emissions-related codes. It often cannot touch security functions.

This is where the Foxwell NT716 OBD2 scanner and other tools get misunderstood. The NT716 is a capable OBD2 scanner for many vehicles. But if your goal is key programming, don't buy any scanner based on the brand name alone. You must check the function list for your exact make, model, and year.

Most buyers focus on 'does it read codes?' and completely miss 'does it have security access for this module?' That's the blindspot. The question everyone asks is 'which scanner is best?' The question they should ask is 'which functions are supported for my specific VIN?'

VIN decoding adds another layer. A Chevy VIN code reader can help you identify engine, transmission, trim, and module configuration. That's useful. But VIN decoding is not the same as reading BCM codes or programming a key. One is identification. The other is authorization.

The 'Universal' Trap: My Bike Rack Taught Me the Same Lesson

Last summer I bought a universal 2 bike hitch mount tilting rack. The box said universal. The reviews said universal. Then I tried to install it on my 1.25-inch receiver. It was built for a 2-inch receiver. (Surprise, surprise.)

Universal means 'fits many.' It does not mean 'fits all.' The same logic applies to OBD2 scanners. A Foxwell OBD2 scanner might cover a broad list of vehicles, but the coverage list is not infinite. It has gaps, exceptions, and model-year cutoffs.

It took me 4 years and about 200 equipment orders to understand that 'supported functions' and 'supported vehicles' are two different columns. You need both.

What It Actually Costs When You Guess

Everyone told me to always check the vehicle coverage list before approving an equipment order. I only believed it after skipping that step once and eating a $3,200 mistake.

The direct costs are obvious: returns, restocking fees, shipping, lost time. The indirect costs are worse. Your techs lose confidence in the tool. Your customer wonders why a job that should take 2 hours is now a 3-day wait. You start borrowing equipment from another shop, which adds its own risk.

We've caught 47 potential errors using our pre-check list in the past 18 months. That's not because we're smarter now. It's because we stopped trusting marketing labels and started verifying functions.

I'm not a diagnostic engineer, so I can't speak to the security algorithms inside a Chevy BCM. What I can tell you from a shop equipment buyer's perspective is how to vet the claim before you spend money.

The Checklist I Wish I Had Before Buying

This is the short version. It is not glamorous. It works.

  1. Start with the exact VIN. Not '2018 Chevy.' Not 'Silverado.' The exact VIN. A good vendor should let you check coverage by VIN or at least by year, model, engine, and trim.
  2. Separate code reading from key programming. If key programming is required, confirm the tool lists immobilizer or key programming for that exact vehicle. Do not assume a Foxwell NT716 OBD2 scanner or any OBD2 scanner can do it.
  3. Check bidirectional control and all-system coverage. Key programming often needs commands, not just reads. If the tool only reads generic OBD2 codes, it's not enough.
  4. Verify VIN decoding separately. A Chevy VIN code reader function is useful, but it does not equal module programming.
  5. Ignore the word 'universal.' Treat it like my bike rack. It means many, not all.
  6. Ask for the coverage list in writing. If a vendor cannot provide it, that is your answer.
  7. Check firmware and updates. Vehicle support changes. A tool that worked on a 2020 model may need an update for a 2024 model.

That's it. Five minutes of verification beats five days of correction.

What the FTC Says About 'Universal' and 'Supports' Claims

This is not just a shop problem. It's a truth-in-advertising problem. Per FTC Business Guidance on Advertising (ftc.gov, accessed January 2025), advertising claims must be truthful and not misleading, and must be substantiated with evidence.

FTC advertising guidelines require that claims be: Truthful and not misleading; Substantiated with evidence; Clear about endorsements and testimonials. Source: FTC Business Guidance on Advertising.

So when a product page says 'universal' or 'supports key programming,' those words should have evidence behind them. Your job as a buyer is to ask for that evidence before you order.

The Real Fix: Prevention Over Cure

The solution is not a secret scanner. It's a pre-check. Know the VIN. Know the required function. Know the tool's coverage. Then buy.

If you need a Foxwell OBD2 scanner for general diagnostics, it can be a solid choice. If you need key programming, verify that specific function for your specific vehicle. If you need Chevy VIN decoding, verify that too. Don't let the label do the thinking for you.

I learned that lesson the expensive way. You don't have to.