Coding: the features you already paid for

Coding is not tuning. Tuning rewrites how the engine behaves. Coding changes the parameters the car's modules already understand, switching on behaviour the platform was built to do and left disabled for a market, a trim level or a launch deadline.

The list is longer than most owners expect. Video in motion where it is legal to enable, folding mirrors on lock, seat belt chime behaviour, gauge cluster layouts, ambient lighting zones, camera views that exist in software but were never mapped to a button, comfort access thresholds, digital speed display. On some platforms, hardware that is physically installed on the car is waiting for a line to be flipped.

What turned this from a favour into a service line is that owners now arrive knowing the vocabulary. They have read the module names. They want three specific changes, and they want them documented, so that the next person who touches the car knows what was altered and can put it back.

That documentation is the whole quality question. A coder who keeps a before state and hands you a list of what changed is doing service work. A coder who plugs in, clicks through a tool and hands the keys back has left you with a car nobody can diagnose cleanly, including the dealer. Ask for the list. Ask whether the original coding is saved.

Two honest limits. Some changes affect systems that are legally required to behave a certain way in your jurisdiction, and a serious shop will decline those rather than argue about them. And some retrofits genuinely need parts, not a laptop: if a car was never built with the camera, no amount of coding will invent it.

Treat it like any other work on the car. Written scope, written record, somebody who will answer the phone if a warning light appears next week.