When a supplier changes the deal: retirement, price, licence or terms
Due diligence does not end at signature. When an existing supplier announces a retirement, a price rise, a new licence or new terms, these are the questions that decide whether you act before the date or pay for not having acted.
Most supplier changes arrive as an email with a date in it, and most of the damage comes from reading the email and not the change. This list is for the week after the notice arrives. The first section establishes exactly what is changing and when; the second establishes what your contract lets the supplier do and what it lets you do; the third and fourth deal with your data and your money; the fifth is for software whose licence is the product, such as open-source and open-weight releases; the last makes sure somebody owns the decision. It applies whether the supplier is retiring a product, re-pricing it, re-licensing it, rewriting its terms or being bought.
What exactly is changing, and when
A notice is written by the supplier, for the supplier. Pin down the facts before deciding anything, because every later answer depends on them.
What is the effective date, at what time, in which time zone — and is it the same date for every product, plan and region you use?
Deal-stopperRetirements and price changes are often scheduled to an hour in the supplier's own time zone, and a staggered rollout can mean one of your subscriptions changes weeks before another. A day's misunderstanding is the difference between exporting in time and not.
Ask for: The supplier's own lifecycle, pricing or terms page for the change, read directly rather than summarised, with the date and time copied into your record.
Red flags
- The notice gives a month but not a day
- Different pages from the same supplier give different dates
- The change is described only in a partner's or reseller's summary
Which of your products, plans, add-ons and seats are in scope, and which are explicitly not?
ImportantA notice about one product is often read as being about a family. Knowing what is not affected is as useful as knowing what is, because it tells you where you can move to without a new procurement.
Ask for: A list of your own subscriptions, mapped line by line against the supplier's statement of scope.
Red flags
- The notice names a product family rather than the specific plans
- Your account manager cannot say whether a given add-on is affected
What does the notice leave out that you need to know — allowance sizes, overage prices, the new licence text, the new owner's plans?
Deal-stopperAn announcement that introduces metering without the size of the allowance, or a new version without its licence, tells you a change is coming but not what it will cost. The missing figure is usually the one that decides the response.
Ask for: A written answer from the supplier to each gap, or the document that fills it.
Red flags
- A usage meter is announced without the allowance per plan
- A new version is described as open without the licence being linked
- The answer is only available on a call
What your contract lets them do, and lets you do
The supplier's notice describes what it intends. Your contract describes what it is allowed to do to you, and when.
Does the contract allow the supplier to change the price, the terms or the product during the term, and on how much notice?
Deal-stopperMany subscription agreements allow changes at renewal only, and some allow them at any time on notice. Which one you signed decides whether the change applies now or at your next renewal.
Ask for: The change, pricing and notice clauses of your signed agreement, and any order form that overrides them.
Red flags
- The agreement incorporates terms on a web page the supplier can edit
- The notice period in the announcement is shorter than the contract allows
- Nobody can find the signed order form
When is your next renewal relative to the effective date, and can a quote or early renewal fix the current price?
Deal-stopperA price rise that takes effect before your renewal can often be avoided by quoting or renewing before the date; one that takes effect after it cannot. The window is usually short and nobody will remind you.
Ask for: Your renewal date, the supplier's or partner's written position on quotes issued before the effective date, and the expiry date on any quote you obtain.
Red flags
- Renewal is automatic and the cancellation window closes before you have the new price
- The quote you are given expires before you can get it approved
Does the change give you a right to terminate, and on what terms — a refund, a pro-rata credit, or nothing?
ImportantSome agreements let a customer leave without penalty if the supplier makes a material change; others say that disagreeing with a change means cancelling at your own cost. Knowing which is the basis of any negotiation.
Ask for: The termination and refund clauses of the agreement, and the supplier's written answer on whether this change triggers them.
Red flags
- The only remedy offered is to stop using the service
- Annual fees are stated to be non-refundable in all cases
Your data and everything that depends on it
A retirement makes data unreachable on a date. A price or terms change can make staying unaffordable. Either way, the export comes first.
Can you export everything you would need to rebuild elsewhere — history, attachments, settings and audit trails, not only the current records — and have you tested it?
Deal-stopperAn export that has only been read about is a hope. The records that are hardest to rebuild, such as history, timesheets, approvals and audit logs, are the ones most often missing from a default export.
Ask for: A completed test export, opened in the tool you would move to, with a list of what was and was not in it.
Red flags
- The export omits history, comments or attachments
- Export is only available on request, or only through a paid service
- Access becomes read-only or ends on the effective date with no grace period stated
What reads from or writes to this product — reports, dashboards, integrations, scheduled jobs, other people's workflows — and what happens to each on the date?
Deal-stopperThe product is rarely the only thing that stops. Reports and integrations built on it fail silently on the first run after the change, and the people who depend on them are often not the people who received the notice.
Ask for: An inventory of integrations and reports from the product's admin console and from your own systems, each with an owner.
Red flags
- Nobody knows which reports read from the product
- An integration was built by someone who has since left
If the supplier is being acquired or has changed its data terms, what changes about who can access your data, where it is held and what it may be used for?
Deal-stopperA change of owner or a terms rewrite can introduce new processors, new locations or new uses such as model training. Those are data protection decisions you have to make, not background.
Ask for: The revised data processing agreement, the sub-processor list with its change date, and any opt-out the supplier offers, with the setting you chose.
Red flags
- Training on customer content is on by default and the opt-out is per workspace
- The sub-processor list changed without the notice your agreement requires
What it will actually cost
A percentage in an announcement is not a number on an invoice. Work out the invoice.
What will your invoice be after the change, calculated from your own seats and usage rather than from the headline percentage?
ImportantPrice changes are often tiered by plan, seat count or currency, so the headline figure may not be the one that applies to you. The only reliable number is the one worked out from your own account.
Ask for: A quote or calculation from the supplier, in writing, for your actual configuration.
Red flags
- Different sources give different percentages for your plan
- The supplier will only give the new price at renewal
If something that was included becomes metered, how much of it do you use today, and can you set limits and alerts before billing starts?
Deal-stopperWhen a capability moves from a plan limit to a meter, usage that used to stop at a cap can become a charge. Automations that loop and agents left on busy queues are the usual surprise.
Ask for: Your current usage report for each meter, the allowance on your plan in writing, and a screenshot of the limits you have configured.
Red flags
- Usage cannot be seen until the first metered invoice
- There is no way to cap spend, only to be alerted
When the licence is the product
For open-source libraries and open-weight models, there is often no contract at all — the licence file is the whole deal, and it can change between versions.
Does the licence of the new version match the licence of the version you use today, and is that checked on every upgrade rather than only on first adoption?
Deal-stopperA project or model family can move from a permissive licence to a non-commercial or source-available one between point releases. An upgrade is often a one-line change made by an engineer for technical reasons, and that is exactly when the licence goes unread.
Ask for: The licence file of the exact version in use and of the proposed one, recorded in your dependency or model register.
Red flags
- The announcement calls the release open but does not link the licence
- The licence restricts commercial use, or adds a field-of-use or user-count limit
- The licence is governed by a law and a court you have never contracted under
Are the versions you rely on pinned, and can you keep running them if the supplier stops distributing them?
ImportantA permissive licence that has already been granted is only useful if you still have the artefact. Weights and packages can be withdrawn from a host, and a build that fetches the latest version will pick up the new licence without anyone deciding to.
Ask for: Pinned version identifiers in your configuration and a copy of each artefact you depend on, stored where you control it.
Red flags
- Builds pull the latest version by default
- The only copy of the weights is on a third-party host
Who decides, and by when
A change with a date needs an owner with a date. Without one, the default decision is made by the calendar.
Who owns the response, and what is the date by which a decision must be made to leave enough time to act on it?
Deal-stopperThe effective date is not the decision date. An export, a migration or a procurement all take time, so the real deadline is the effective date minus the time the chosen response needs.
Ask for: A named owner, a decision date and an action date in a shared calendar, with the notice attached.
Red flags
- The notice went to a billing mailbox nobody reads
- The decision date is the effective date
Is the change, your decision and its evidence recorded where the next person to review this supplier will find it?
Worth askingSuppliers change terms repeatedly. A record of what changed, what you decided and why is what lets the next review start from facts rather than from memory.
Ask for: An entry in your supplier register with the notice, the version of the terms or licence in force, and the decision.
Red flags
- The only record is an email thread
- Nobody can say which version of the terms the organisation is currently on
This checklist is general guidance, not legal, security or financial advice, and it does not replace your own advisers on anything contentious. It was last reviewed on 21 September 2026. Tell us if something here is wrong or missing.