RPO Decoder — bugs, missing codes, and feedback

One thread for everything to do with the RPO decoder — bugs, codes we’re missing, meanings that look wrong.

DecoderGM RPO Code Decoder — Read Your Chevy or GMC Glove Box Sticker
Databasehttps://fullsizechevy.com/tools/rpo-codes/

Something didn’t work

Tell me what you did and what happened. Phone or computer, and which browser if you know it. “I uploaded a photo and it just sat there” is a perfectly good bug report.

A code came back with no match

The tool logs these automatically, so I see them either way — but post it here if you know what it means. The code, your model year, and what the truck is.

If you know the meaning, say where it came from: a factory document, a build sheet, a dealer printout. There’s a real difference between a code we can prove and one that’s floating around the internet, and the tool tells people which is which, so I need the source to publish it properly.

A photo of your SPID label proves the code appeared on a truck. That’s useful on its own, even without a meaning. Cover your VIN before you post it.

A meaning looks wrong

GM reused these codes for forty years, so a code that means one thing on your truck can mean something unrelated on a different platform. If the tool showed you an era that doesn’t fit yours, flag it. Wrong meanings matter as much as missing ones.

Where it’s thinnest

Squarebody and GMT900. Coverage is strongest on GMT800, the 2016 K2XX range, and current T1XX. If you’re running a 73-87 or an 07-13 you’re the most likely to find a gap — and the most useful person to hear from.

I have updated the tables and the counters. Now if searching G80 with no year it brings back the latest record that we have.

I’ll try to get more description on the RPO’s from the Body Builder Manuals this week as well, and then onto the QR Code reader for anything 2018++

Decoder is currently not loading. Error message, “The interactive decoder could not load. The reference table further down this page still works.” I also see via the browser console that /wp-content/plugins/fsc-tools/data/rpo.v4.json returns an error 404, page not found.

Thanks for reporting this! I have it fixed now after a cache purge. I updated the database to add a few more 2019+ codes from body builder manuals. I verified it is working from an incognito browser and it is reading nicely now. I’ll keep an eye on the read counts today to make sure.

Thanks!!

1 Like

Thanks. It worked. It did flag a few codes as unrecognized. Good work.

1 Like

Thanks for letting me know it worked on your end! Yes I am logging codes that are unrecognized - unsure how to proceed but with likely approach GM at some point with a master list to ask about !