8 Questions When a Supplier Changes What You Bought

1. What exactly did the accepted purchase promise?

The first question is the original purchase. Capture the service, version where specified, included features, location, capacity, support and permitted use. A vendor’s current page may describe a different offer from the one the business accepted. Retain the dated order form, incorporated terms and relevant description of the purchased service.

For an agent product, write down the customer job the supplier enables. “Uses model X” is less informative than “extracts the agreed fields within this workflow under these access rights.” A supplier can change an implementation without changing a contractual promise; it can also preserve a product name while changing a material condition. The record needs both the contract and the operational dependency.

Do not treat an internal preference as a negotiated entitlement. The buying team may strongly prefer a feature that was labelled experimental. Conversely, a feature that appears small in release notes may be essential to a promised customer outcome. A useful review identifies the difference before choosing a response.

2. Which document and agreement control the decision?

The second question is document priority. An order form, service-specific policy, negotiated amendment and general agreement can address different parts of the promise. The source that is easiest for an agent to retrieve may not control the disputed condition. Record the applicable hierarchy from the actual agreement rather than guessing that the newest webpage always wins.

Google Cloud’s public terms identify circumstances in which an offline agreement governs instead. This is a reason to resolve applicability before taking a notice period from a search result. Keep the relevant entity, service and document version in the register.

3. What changed in the capability or commercial condition?

The third question is the change itself. Separate reduced functionality, discontinuation, price changes, altered access rights and revised legal terms. They may have different notices and remedies. Combining them under one “vendor update” label makes the response harder to assess.

Use a before-and-after record with exact clauses or source links, the observed change and the purchasing implication. Where the supplier’s description is ambiguous, list competing interpretations. A confident agent paraphrase should not replace a condition that determines the customer’s rights.

A technical regression test can establish that a workflow behaves differently. It does not alone establish breach, materiality or a contractual remedy. Keep those evidence tracks linked but separate so that the engineering result does not silently become a legal conclusion.

4. Which open commitments does the change affect?

The fourth question is the affected obligation. Trace the change to a specific customer promise, supplier commitment or operating control. If a capability becomes unavailable, which open work can no longer finish? If a use restriction changes, which planned activity needs a fresh entitlement review? If the price changes, which fixed-price commitments remain exposed?

Record cash implications separately: overlapping subscriptions, dedicated commitments, export costs and any claimed recovery. A future service credit should not be treated as money available to pay a replacement supplier. The fallback must work within both the operating and funding calendar.

5. When was notice received, and which deadlines apply?

The fifth question is timing. Preserve the notice’s publication date, receipt date, effective date and any action deadline. They can be different. A change discovered through a public changelog may already have been sent to an account address; an email received today may describe a later effective date.

The OpenAI example requires the customer to make the specified termination choice within five business days of receiving the relevant notice, followed by thirty days’ written notice. Those two intervals do different jobs. The DN tool therefore asks the operator to enter an established response deadline rather than deriving business days from an unspecified calendar.

The current AWS Customer Agreement illustrates another structure: notice for discontinuing material generally available functionality that the customer uses, with stated exceptions, and a separate notice provision for adverse SLA changes. The distinction demonstrates why one generic vendor-notice period is inadequate.

Assign an owner who can read the notice and take the relevant action. A shared inbox is not an operating process unless someone monitors it and the business can act within the applicable interval. Record whether notice was acknowledged and whether the interpretation was escalated before the deadline.

Use actual dates in the decision. A statement that there is “a month to migrate” can hide time already spent reviewing, weekends in a business-day deadline and prerequisites controlled by another party. The remaining window should be compared with the work still required, not the original duration printed in the notice.

6. What remedy is actually available?

The sixth question is the remedy. Possible contract outcomes include continued access, a termination choice, a refund, a credit or no special right for the specific change. Establish the actual terms and applicable law rather than substituting a standard customer expectation.

OpenAI’s Services Agreement provides a particular example: a materially functionality-reducing update triggers notice and a time-limited termination choice, with beta or evaluation features excluded from that right. This is not a universal right to freeze a model or reject every service change. The account’s applicable agreement and order form remain necessary evidence.

7. Can a replacement workflow finish in time?

The seventh question is practical continuity. A termination right can be commercially weak if a replacement cannot complete the job before the change takes effect. Conversely, remaining with the supplier may be viable if a permitted adjustment preserves the required outcome at an acceptable cost.

Estimate the remaining migration work as a sequence: alternative entitlement, configuration, data movement, validation, operator handover and customer transition. Dependencies matter more than a single optimistic duration. The calculator uses an entered calendar-day duration and does not claim that the migration has been tested.

In a hypothetical case, the review date is11 November, the change takes effect on1 December and the remaining migration is25 calendar days. There are20 days until the change, so the plan has a five-day gap. A later response deadline would not fix the operational mismatch. The business needs a different schedule, transitional arrangement or customer decision.

8. What survives exit, and what closes the record?

The eighth question concerns the obligations after the choice. Termination may leave accrued fees, confidentiality, data handling, dispute and other provisions in effect under the applicable agreement. It should not be reduced to pressing a cancellation button.

The AWS agreement contains conditional post-termination content-retrieval provisions. This illustrates why an export plan should be read alongside the termination route and account obligations. It does not establish a guaranteed export window for every termination or every supplier.

The DN Service-Change Procurement Register reports the entered deadlines and the difference between available calendar time and remaining migration work. It keeps an unknown date unknown. A completed entry does not prove that a notice is valid, a remedy enforceable or the alternative operational.

Close the review with one explicit decision: continue under the changed terms, request a documented accommodation, invoke a supported remedy, migrate or hold the affected commitment for further review. Retain the evidence and the person authorised to decide. The goal is a defensible purchasing record that can be updated when facts change.

This method is most valuable before a customer promise becomes difficult to fulfil. Link supplier changes to the obligations that depend on them. A weekly list of release notes is much less useful than a dated record showing which open commitment needs a decision and when.

Frequently asked questions

Primary sources

1. OpenAI Services Agreement. Business fees, fourteen-day published price-change timing, order forms and modification rights. Reviewed 2026-11-11.
2. AWS Customer Agreement. Current service-change, discontinuation, notice and post-termination conditions; account and contracting-party scope matters. Reviewed 2026-11-11.
3. Google Cloud Terms of Service. Applicability provisions explain that certain offline agreements govern instead of the public online terms. Scope checked 11 November2026. Reviewed 2026-11-11.

Related DN research

• AI Agent Evidence Expiry
• Agent Runtime Portability Index