When after module replacement is an online procedure or coding needed, and when the problem starts much earlier

This is the most important sequence. If the module has no power, is not visible in the topology, or the part number does not match the car's configuration, no online procedure will fix the fundamental problem.

That's why we start such cases with ECU topology, communication, and power supply diagnostics, not with a promise that 'we'll program something right away.'

First, we check if the new module is electrically and logically alive at all. Whether it responds on the bus, whether it appears in the Gateway or topology, whether there is a conflict with the part number, equipment, generation, or software variant.

In VAG, an important element is Component Protection, i.e., pairing modules by MAC address. Without access to ODIS or an online session, a replacement module (e.g., steering column, instrument cluster, key) simply will not work. This protection requires an active session with the manufacturer's server and VIN confirmation. Conversely, after replacing a throttle body, EGR valve, or swirl flaps, Basic Settings and channel adaptation are necessary. Adaptation values are stored in the controller's RAM, not in the module's flash itself, so their absence after replacement means incorrect system operation until recalibration.

Only when this is correct can you sensibly assess whether adaptation, assignment, component protection, or a full OEM online procedure is needed.

Because it's not an honest description of the service. The scope depends on the brand, OEM account, online access, controller type, and the specific repair case. Publicly promising 'flashing everything' suggests a reach that cannot be reliably guaranteed.

It's much more honest to say: we check the case, confirm the conditions, and qualify it for the procedure if the manufacturer and the car's architecture actually allow it.

The new module does not respond, the car doesn't see it, a cascade of `U` errors appears, the controller disappears from the topology, or power-related symptoms appear after plugging it in. These are signals that you first need to go back to the circuit and communication layer.

This is also well illustrated in the article about CAN, DoIP, and Gateway, because that's very often where the real problem after module replacement begins.

If the electrical, logical, and compatibility conditions are confirmed, an online procedure makes sense. If not, the more honest and cheaper move is to stop at diagnosis, fix the basics, and only then return to the topic.

That's exactly how we treat MaxiFlash and VCMI2: as procedural tools after confirming conditions, not as a marketing shortcut to 'flashing everything.'