CPV 72267000

Software maintenance and repair services

Software maintenance and repair is the work of keeping software that already exists running: fixing bugs, applying patches and security updates, moving to new versions, and the ongoing support that wraps around a live system. Under CPV code 72267000, a contracting authority is buying upkeep, not a new build.

This is the workhorse of Software-related services (72260000). 7,896 awards carry the code (TED 2009-2026), the most of any software-services sibling, at a mean of about €1.4M across awards with disclosed values. France, Spain and Poland place the most. The volume follows from a simple fact: every deployed system needs maintaining, so these contracts recur on fixed cycles.

In practice the scope ranges from a narrow patch-and-helpdesk arrangement to a multi-year application maintenance deal that also folds in small enhancements. French tenders call the latter TMA, tierce maintenance applicative, or third-party application maintenance, and it is a common shape under this code, especially in France.

When to use this code

For buyers contracting authority

The mistake to avoid with 72267000 is mixing it up with Software support services (72261000). Support answers questions and resolves incidents; maintenance changes the code, patches it, and keeps it current. Many contracts blend both, so tag the primary CPV code by whichever dominates the statement of work.

Beyond that line the rule is simple: choose 72267000 when the contract keeps an existing system alive rather than creating something new. Bug fixes, version upgrades and support hours point here; a new feature set or a fresh application points to development (72262000).

One more trap: this code is for software, not hardware. Maintenance and repair of computer equipment is 50312000. Where a deal bundles software upkeep with licences or minor enhancements, keep it here as long as maintenance is the main purpose.

For suppliers bidding

This is steady, low-drama revenue with a strong incumbency effect. The firm that built or already maintains a system knows its quirks, and contracting authorities are wary of handing maintenance to a stranger, so switching risk is the challenger's main obstacle.

Against an incumbent, compete on response times, named engineers with the right product certifications, and a credible transition-in plan. Service-level commitments and clear escalation paths carry more weight than headline price.

Maintenance contracts recur and often carry renewal options, which compounds the incumbent's edge. Suppliers active under development (72262000) and support (72261000) bid here too, and the work pairs naturally with reselling licences. This is defensive, recurring revenue: unglamorous, but durable, and far harder for a rival to dislodge than a one-off build.

Industries and typical projects

Software development IT staff augmentation System integration Public sector IT

Commonly confused with

72261000: Support answers questions and resolves incidents; maintenance changes the code, patches it, and keeps it current.
50312000: That code covers maintaining and repairing computer hardware; 72267000 is strictly the software layer.
72262000: Development builds new software; pick maintenance when the work keeps an existing system running.

Example award titles

Negotiated Procedure for the Provision of a four (4) year Software Maintenance Agreement, for the ongoing support, maintenance, and new development of the MBR Online Registry System.
Single Party Framework Agreement for development, maintenance, upgrades, consultancy and technical support for PEMAC Care, i-Meeting and PEMAC Assets (GALW/BUILD1645/2023)
Provision of Software Maintenance Support Services for the EU LRIT DC, LRIT-IDE, and LRIT-Ship DB systems
Provision of Maintenance and Development of EUIPO Human Resources Management System Based on Allegro Software including Purchase of Licences
RFT for the provision of Support and Maintenance for Control-M Scheduling software
Care first professional software support services.