A code names a system. It does not name a part, and treating it like a parts list is how repairs go wrong.
A check-engine light comes on when the car's computer detects something outside its expected range and stores a code describing where. That code is genuinely useful information, and it is also incomplete — several different failures can trigger the identical code, and only testing separates them.
A code that reads as a misfire on a specific cylinder could mean a failed ignition component, a fuel delivery problem, or a mechanical issue inside the engine itself. Reading the code tells you where to look. It does not tell you what to replace.
A shop that reads the code and orders the part it usually corresponds to is making an educated guess, and educated guesses are sometimes right. When they are wrong, you have paid for a part that was not the problem and the light comes back, because the actual cause was never addressed.
Live data pulled while the car is running, sometimes while reproducing the condition that triggers the light, and a physical check of the wiring, connectors and components in the suspected system. It takes longer than reading a scanner. It is the difference between a fix and a guess.
A light that comes on and then goes off on its own did not fix itself — the code is usually still stored even after the light clears, and a shop can pull it. Do not wait for it to become constant before getting it looked at.
A steady check-engine light is usually fine to drive on carefully to a shop. A flashing check-engine light means the engine is at risk of damage right now and is worth stopping for as soon as it is safe to do so.
Tell us what the car is doing and we will match you with a shop that tests before it quotes.
Get Matched With a ShopA rough description is plenty — we will follow up to match you with a shop and confirm timing.