What does upgrading mean?
Upgrading captures managed post-sale improvement, where a product is enhanced rather than simply repaired, maintained, or replaced.
A post-sale improvement that can enhance the functionality, performance, capacity or aesthetics of a product.
Upgrading captures managed post-sale improvement, where a product is enhanced rather than simply repaired, maintained, or replaced.
Do not call every service event an upgrade. Repair corrects faults, maintenance preserves function, refurbishment restores performance, and upgrading improves functionality, performance, capacity, or aesthetics.
In ESPR, upgrading is not routine maintenance and not repair. It concerns enhancement of functionality, performance, capacity, or aesthetics, which can support longer useful life or improved product value.
Record the baseline state, upgrade action, changed capability, date, actor, and evidence. For software-dependent products, keep software update records linked but not automatically equivalent to upgrading.
Regulation (EU) 2024/1781 establishing a framework for the setting of ecodesign requirements for sustainable products
actions carried out to enhance the functionality, performance, capacity, safety or aesthetics of a product;
Reference: Article 2, point 17
Implementation records should capture the upgrade event, enhanced function, baseline condition, post-upgrade evidence, product identifier, service actor, hardware/software/configuration change, and distinction from maintenance, repair, refurbishment, or replacement.
Upgrading is a post-sale improvement control: the evidence consequence is that enhanced functionality, performance, capacity, or aesthetics can be recorded separately from actions that merely preserve or restore expected function.