Secondary Software Licence Market: A Business Guide

The secondary software licence market can help organisations reduce acquisition costs while retaining the governance expected in professional IT procurement. The opportunity is not simply to buy a cheaper product key. It is to acquire a valid right to use a specific software copy, supported by evidence that the transaction fits the legal conditions applicable in the European Union and European Economic Area.

That distinction matters. A key may activate software without proving who first acquired it, where it entered the market, whether the original right was unlimited in time, or whether the seller stopped using the transferred copy. Conversely, properly documented pre-owned software can form part of a defensible licensing strategy. For procurement, IT, finance and compliance teams, the central questions are legality, traceability, technical suitability and total cost rather than price alone.

This guide explains the legal framework, the July 2026 ValueLicensing development, the practical evidence a buyer should request, and a repeatable due-diligence process for safer B2B procurement. It is general information, not advice on a particular contract or dispute; material purchases should be reviewed against their specific facts.

What is the secondary software licence market?

The secondary software licence market enables organisations that no longer need certain software usage rights to transfer eligible copies to another business. Supply may arise after cloud migration, workforce reduction, application consolidation, hardware retirement, a merger or a standardisation project. Demand often comes from organisations that need a stable on-premises version, want to extend an existing environment, or prefer a one-off purchase to a recurring subscription.

The transaction is more than delivery of an activation credential. A responsible supplier connects the entitlement to evidence of the product, quantity, original acquisition, territory, transfer history and seller declaration. This allows the buyer to assess the relevant copy and proposed deployment.

The market can offer savings and lifecycle flexibility when a business needs a compatible perpetual version rather than the newest release. Buyers can explore the Microsoft Office licence range, for example, while applying normal enterprise legal and technical checks.

Why lawful resale is possible in the EU and EEA

The core legal concept is exhaustion of the distribution right. Article 4(2) of Directive 2009/24/EC provides that the first sale in the EU of a copy of a computer program by the rightsholder, or with the rightsholder's consent, exhausts the distribution right in that copy, apart from the right to control further rental. The Directive also allows a lawful acquirer to perform reproductions necessary to use the program for its intended purpose, subject to the applicable conditions.

In its judgment of 3 July 2012 in UsedSoft GmbH v Oracle International Corp., C-128/11, the Court of Justice of the European Union held that exhaustion can apply to software originally supplied by download. The commercial label is not decisive. Where the download and an unlimited-duration right of use form an indivisible transaction for a price intended to remunerate the economic value of the copy, the operation can amount to a first sale for this purpose.

It is therefore more accurate to say that the distribution right in a particular software copy may be exhausted than to say that a licence is automatically “exhausted”. The analysis is copy-specific and fact-specific. It asks how the program was first supplied, what rights were granted, where the first authorised marketing occurred, and what is being transferred now.

Conditions a business should test

A procurement team should normally seek evidence supporting all of the following points:

• The asset is a computer program covered by the specialist software regime.
• The copy was first put on the EU/EEA market by the rightsholder or with its consent.
• The original transaction granted a right to use that copy for an unlimited period.
• A price was paid that reflected the economic value of the copy.
• The resale concerns the corresponding copy and entitlement, not a detached key or unrelated contractual benefit.
• The previous holder has stopped using the transferred copy and has made retained installations unusable.
• The quantity, edition, version and permitted deployment can be identified.
• The chain of title is sufficiently documented for the buyer to understand each transfer.

A contractual “non-transferable” label does not necessarily defeat exhaustion already arising under EU law. Yet not every product sold as perpetual is transferable. The agreement may clarify copy structure, territory, bundled services and deployment limits; substance matters more than the marketing name.

Perpetual rights, subscriptions and cloud services

The UsedSoft analysis centres on a right of use granted for an unlimited period. A genuinely perpetual software copy may satisfy that part of the test, but the word “perpetual” on an invoice is not enough on its own. Buyers should review the original terms and verify that continued use is not dependent on recurring payment, an expiring account or a service controlled by the publisher.

Monthly, annual and other fixed-term subscriptions are not automatically covered because they normally provide temporary access rather than a definitive transfer of a copy's economic value. Pure software-as-a-service offerings are further removed: the customer typically receives access to hosted functionality, not ownership of a program copy capable of independent resale. User accounts, cloud storage, administration portals and online services should not be assumed to transfer with an exhausted copy.

Corrections or updates already incorporated lawfully may form part of the copy in its resale state. Future maintenance, support, cloud benefits and later versions do not automatically accompany it. The purchase order should state what is included and excluded.

Volume agreements and the ValueLicensing judgment

Volume licensing requires careful analysis because “volume” can describe materially different structures. UsedSoft directly addressed a model involving one server copy with access rights for a specified number of users. The Court held that the first acquirer could not keep using the central installation while carving off and reselling unused user rights. That remains a strong warning against splitting a single copy or functionally indivisible multi-user entitlement.

A newer development concerns multiple independent copies acquired together. On 7 July 2026, the Court of Appeal of England and Wales issued its judgment in ValueLicensing v Microsoft, [2026] EWCA Civ 872. It concluded that UsedSoft's anti-division reasoning does not necessarily turn several independently installable Windows or Office copies into one indivisible copy merely because they were acquired together under an Enterprise Agreement.

The judgment is important but must be described precisely. It is persuasive UK case law, not a ruling of the Court of Justice and not binding on courts in the EU or EEA. It addresses preliminary copyright and jurisdiction issues in continuing competition litigation, not a final damages award or a new pan-European rule.

The Court did not decide that Office suite components can be sold separately or grant a general right to bypass activation controls. The narrower distinction is between one indivisible copy, which should not be split, and genuinely independent copies that may merit separate analysis. Organisations should document that independence.

Why traceability matters more than an activation key

Activation demonstrates that a technical system accepted a credential at a particular moment. It does not, by itself, establish a valid licence or exhausted distribution right. Keys may be duplicated, misdescribed, regionally unsuitable, connected to subscriptions, withdrawn from an organisation without authority, or supplied without the corresponding acquisition record. A low price and successful installation cannot replace provenance.

Traceability gives the buyer a coherent history from the first authorised acquisition to the present transfer. Depending on the transaction, this may include the original invoice or agreement, product description, quantity, purchasing entity, EU/EEA market evidence, transfer documents, declarations of non-use and any records identifying intermediate owners. The objective is not to collect paperwork for its own sake; it is to connect the copy being deployed with a defensible entitlement.

A complete chain of title for used software licences can shorten approval and audit work by giving finance, IT, security and compliance teams one coherent record.

A safe B2B procurement process

A practical process should allocate responsibility across procurement, IT and compliance rather than leaving the decision to whoever receives the key. The following sequence is scalable for a small order and can be expanded for a major estate purchase.

1. Define the deployment before requesting a quote

Record the product, edition, version, platform, quantity and device or user model. Confirm compatibility and identify requirements such as downgrade, reimaging, virtualisation or remote-access rights. A cheap licence for the wrong deployment is not a saving.

2. Classify the licence structure

Determine whether the proposed asset is an unlimited-duration copy, a fixed-term subscription, SaaS access, a device licence, a user right, or part of a central multi-user installation. For volume acquisitions, ask whether the units are independently installable copies or fractions of one shared entitlement. Escalate ambiguous structures before purchase.

3. Verify origin and territorial history

Request evidence that the first authorised marketing occurred in the EU or EEA. A copy first sold outside the EEA should not be assumed to create European exhaustion. Identify the original customer, seller and transaction date as far as the evidence reasonably permits, and check that the party offering the asset has authority to transfer it.

4. Review the evidence package

Match documents across product names, quantities, entities and dates. Look for unexplained gaps, conflicting editions or redacted fields that prevent meaningful verification. Ask how the supplier validated the chain and whether it will provide a clear invoice plus transfer documentation. For larger orders, sample individual units rather than accepting a generic statement covering an unidentified pool.

5. Confirm cessation of use

Obtain a seller declaration that the transferred copies have been uninstalled or otherwise made unusable and will not remain in simultaneous use. ValueLicensing reasoned that later retention by a seller does not retroactively undo exhaustion and that the retained copy may instead be infringing. Because that interpretation is British rather than binding EU/EEA authority, proof of deinstallation remains a prudent control for European procurement.

6. Validate delivery and activation safely

Use trusted installation media and security controls. Keep delivery instructions separate from legal evidence, and do not confuse activation support with provenance. Test a representative sample when appropriate, but avoid broad deployment until product identity and documentary review are complete. Contractual remedies should cover material discrepancies, duplicate supply and inability to deliver the described entitlement.

7. Build an audit-ready asset record

Store the invoice, licence description, legal evidence, declarations, deployment assignment and activation record together. Protect and retain the file through the software lifecycle, updating it when installations or assignments change.

Buyer due-diligence checklist

• Business need: Is the requested version technically suitable and supported for the intended workload?
• Duration: Does the original transaction grant use for an unlimited period?
• EU/EEA origin: Is there credible evidence of first authorised marketing in the relevant territory?
• Product identity: Are edition, version, platform and quantity unambiguous?
• Copy structure: Are the units independent, or would the deal split one central or indivisible entitlement?
• Chain of title: Can the entitlement be followed through prior owners and transfers?
• Cessation of use: Has the seller declared that transferred copies are no longer used?
• Excluded services: Are support, maintenance, cloud access and future upgrades clearly addressed?
• Technical delivery: Are media, downloads and activation methods legitimate and secure?
• Supplier accountability: Are warranties, assistance and remedies documented?
• Record keeping: Can the complete file be retrieved promptly during an audit?

How to assess savings without weakening compliance

Measure savings against a relevant alternative, not an unrealistic list price. Compare the acquisition cost with a suitable new product or the expected subscription cost over the planned use period, adding review, deployment, support and compatibility costs.

A controlled purchase may generate useful budget flexibility, but no responsible supplier can guarantee a universal percentage or claim that every secondary licence is lawful. Price varies by product, version, quantity, documentation and availability. Very large discounts combined with thin provenance should trigger more scrutiny, not less. The strongest commercial case combines a competitive price with evidence that reduces future audit and operational costs.

Businesses with unused perpetual entitlements may also consider whether those assets can be sold rather than written off. The guide to selling surplus software licences outlines the seller-side preparation required, including inventory reconciliation and cessation of use. Buyer and seller controls are two sides of the same transaction.

Common red flags

• A seller offers only a key and refuses to identify the underlying licence or source.
• The product is described as perpetual, but use depends on an active subscription or personal account.
• The first market territory cannot be established, or evidence points outside the EEA.
• Quantities in invoices, transfer statements and the quote do not match.
• A central multi-user entitlement is being divided without evidence of independent copies.
• The seller promises automatic transfer of support, cloud services or future upgrades.
• The documentation is generic and cannot be tied to the specific products delivered.
• The supplier guarantees legality in every circumstance without reviewing the licence history.
• Activation methods require bypassing controls, using unexplained infrastructure or sharing credentials.
• The buyer is discouraged from retaining documents or involving its compliance team.

Frequently asked questions

Is buying used software licences legal in the EU?

It can be. Under EU software law and UsedSoft, the distribution right in a particular copy may be exhausted after an authorised first sale in the EU/EEA when the relevant conditions are met, including an unlimited-duration right of use. Legality depends on the copy, transaction, territory and evidence; it should not be assumed from a product key alone.

Can any perpetual licence be resold?

No. “Perpetual” is a useful indicator, not a complete legal conclusion. The buyer should confirm the original authorised sale, unlimited duration, EU/EEA origin, identity of the copy, transfer history and cessation of use. Contractual and technical characteristics may also affect whether the proposed asset is what the buyer needs.

Can subscriptions or SaaS accounts enter the secondary market?

They are not automatically covered by UsedSoft. Fixed-term subscriptions usually provide temporary rights, while SaaS generally provides access to a service rather than a transferable software copy. Accounts, hosted storage, support and future services do not automatically transfer through exhaustion.

Can a volume licence be split?

Not as a general rule. UsedSoft prevents splitting rights tied to a single central or functionally indivisible copy. ValueLicensing suggests that independently installable copies are not necessarily indivisible merely because they were bought together, but that UK judgment is persuasive rather than binding in the EU/EEA. Each structure needs specific review.

What documents should a business retain?

A buyer should generally retain invoices, original acquisition evidence, applicable licence terms, product and quantity details, chain-of-title records, transfer declarations, evidence of EU/EEA origin, seller non-use or deinstallation statements, delivery records and internal deployment assignments. The appropriate file depends on the transaction.

Does successful activation prove that a licence is valid?

No. Activation is a technical event, not conclusive legal proof. A valid procurement file should connect the activated software to an eligible copy and a documented entitlement. Technical testing is important, but it complements rather than replaces provenance and compliance review.

Make the business case auditable

The secondary software licence market is most valuable when savings and governance reinforce each other. Start with a precise technical requirement, distinguish copies from services, verify EU/EEA origin and unlimited duration, review the chain of title, document cessation of use, and retain an audit-ready file. Treat recent UK case law as informative, not as a shortcut around established EU/EEA analysis.