How to Draft a SaaS Pricing Change Clause That Keeps You Compliant and Out of Court

Raising prices is a normal part of running a SaaS business. Inflation, increased infrastructure costs, added features, and shifts in market positioning all create legitimate reasons to adjust subscription fees. The legal problem is not the price increase itself — it is how the price increase is communicated and implemented under the terms of your subscription agreement.

In 2026, that legal problem has become significantly more serious. New York, Connecticut, Massachusetts, Maryland, and Arkansas each enacted or amended subscription and auto-renewal laws in 2025. The FTC’s enforcement of unfair or deceptive pricing practices has accelerated. And the standard 30-day notice window that was adequate five years ago is now the minimum — not the standard — in well-drafted enterprise SaaS agreements.

If your subscription agreement’s pricing change clause was written before 2024, or adapted from a template without legal review, there is a meaningful chance it creates legal exposure every time you raise your prices. This guide explains what a compliant pricing change clause must include, what enforcement trends to watch in 2026, and how to structure your renewal and notification process to avoid the disputes that pricing changes routinely trigger.

Why Pricing Change Clauses Are a Legal Issue — Not Just a Business One

Many SaaS founders treat pricing changes as a business communication question: how do we tell customers we are raising prices in a way that minimizes churn? That framing misses a more urgent question: how do we implement pricing changes in a way that is contractually and legally valid?

A price increase that is not supported by your contract is not a business decision — it is a breach of contract. If your subscription agreement locks customers into a fixed price for a defined term, raising prices before the end of that term, without the contractual right to do so, exposes you to breach of contract claims from every affected customer. In a class action scenario, that exposure can be material.

Even outside fixed-term contracts, a price increase that is not communicated with the notice required by your Terms — or that violates state subscription law notice requirements — can be reversed by payment processors at the customer’s request, result in chargebacks, and trigger regulatory investigations in jurisdictions with active subscription law enforcement.

The solution is a properly drafted pricing change clause that gives you the right to adjust pricing, defines the procedure you must follow, and ensures your implementation of that procedure satisfies both contractual and regulatory requirements.

The Core Elements of a Compliant Pricing Change Clause

1. The Right to Change Pricing: Grant Yourself the Authority Explicitly

Your subscription agreement must explicitly grant you the right to change pricing. A surprising number of SaaS agreements — particularly those adapted from older templates — are silent on this point, which means that any price change arguably requires customer consent rather than simple notice.

The clause should state clearly that the vendor reserves the right to modify subscription fees, and that modified fees will apply at the next renewal of the subscription term following the required notice period. This language does two things: it establishes the legal basis for the change, and it ties the implementation to the renewal date — which is both commercially appropriate and legally defensible.

2. Notice Period: What the Law Requires vs. What Best Practice Demands

The minimum notice period required by most state subscription laws is 30 days. But 30 days is increasingly inadequate for enterprise SaaS agreements, where customers have budget cycles, board approvals, and procurement processes that require longer planning horizons.

For SMB SaaS products with monthly subscriptions, 30-day notice is generally sufficient. For annual subscriptions or enterprise agreements, 60 to 90 days is the current commercial standard. For agreements with auto-renewal provisions, the notice period for pricing changes should align with — or exceed — the notice period required to prevent auto-renewal, so that customers who receive a pricing change notice have enough time to evaluate and decide whether to renew at the new price or terminate.

The notice period should run from the date the customer receives the notice, not the date the vendor sends it. If you email notice to a billing address and the customer does not check that inbox for two weeks, you do not want to argue later that notice was received on the day of sending. Use delivery confirmation mechanisms or account-level in-app notices to ensure receipt can be documented.

3. Notice Format: Conspicuous, Specific, and Documented

How you deliver a pricing change notice matters as much as when you deliver it. Multiple state laws and the FTC’s 2024 negative option rule (which applies to subscription products) require that material changes — including price increases — be disclosed in a “clear and conspicuous” manner.

“Clear and conspicuous” means that the notice cannot be buried in a routine marketing email, embedded in a footer update to your privacy policy, or sent in a mass communication where the pricing change might be overlooked. Best practices in 2026 include: a dedicated email with the price change as the subject line, an in-app notification requiring acknowledgment, or a physical notice for paper-billed customers. For enterprise accounts, a direct communication from the account manager is advisable in addition to formal written notice.

The notice must specify: the current price, the new price, the date the new price takes effect, and the options available to the customer (renew at the new price, or terminate before the new price takes effect). Vague language like “pricing may be subject to adjustment” is not adequate notice and will not protect you from a customer who disputes the charge after the fact.

4. Automatic Application at Renewal: No Deemed Acceptance Traps

Some SaaS agreements include language stating that continued use of the service after receipt of a pricing change notice constitutes acceptance of the new price. This “deemed acceptance” approach is increasingly problematic under state subscription laws, which require affirmative consent to material price changes in some jurisdictions.

The safer approach is to state that the new pricing applies at the next renewal date following the notice period, and that the customer’s renewal of the subscription constitutes their agreement to the new pricing. This is commercially equivalent — you still implement the price change at renewal — but it is legally cleaner because the acceptance event is the affirmative act of renewing, not the passive act of not canceling.

For customers on auto-renewal, this distinction matters significantly. Our guide on auto-renewal and subscription compliance in 2026 explains the specific requirements that apply to auto-renewing subscriptions, including the notice requirements that must be met before charging a renewed subscription at a higher price.

5. Grandfathered Pricing: When and How to Preserve Commitments

Many SaaS companies have legacy customers on pricing that was offered years ago under promotional or early-adopter terms. When those customers receive a pricing change notice, they often push back hard — and sometimes, their original agreement included commitments that the vendor cannot legally override.

Before implementing any price increase, review your historical contracts for language like “price guaranteed for the life of the subscription,” “locked-in pricing,” or “no price increases.” These commitments — even if made casually in a sales email rather than in the formal agreement — may create enforceable obligations. Raising prices on customers who have these commitments is a breach of contract, regardless of what your current Terms say.

A properly structured pricing change clause includes a savings clause: stating that nothing in the pricing change provision overrides any express pricing guarantee contained in a customer’s Order Form, and that such guarantees govern to the extent they conflict with the general pricing change provision. This protects you from inadvertently breaching commitments made to legacy customers.

State-Specific Requirements to Know in 2026

The patchwork of state subscription laws creates compliance complexity for SaaS companies with customers in multiple states. Key 2026 requirements include:

California: The California Automatic Renewal Law (ARL) requires clear disclosure of material changes to subscription terms, including price changes, before the change takes effect. Failure to comply can result in the automatic renewal being deemed unenforceable, meaning the customer is entitled to a refund.

New York: New York’s 2025 amendments to its subscription law extended ARL-style protections to a broader range of subscription products and increased the required notice period for price increases on annual subscriptions.

Delaware, Virginia, Colorado, Connecticut, Texas: All enacted or strengthened consumer data and subscription protection laws between 2023 and 2025 that have compliance implications for SaaS pricing change procedures.

For B2B SaaS companies that serve businesses rather than consumers, some of these state laws may not apply directly — many subscription laws have consumer-facing scope limitations. But enterprise SaaS vendors that serve SMBs may find themselves serving a mix of consumer-adjacent business customers who receive protection under these frameworks, and the safest approach is to comply with the most protective state standard across your customer base.

The 2026 state privacy and compliance law map provides an overview of the regulatory landscape across all US states, which is relevant context for understanding where your subscription compliance obligations apply.

FTC Enforcement Trends: What They Mean for Your Pricing Clause

The FTC’s increasing scrutiny of subscription practices — documented in our guide on FTC enforcement trends in 2026 — extends specifically to pricing transparency and change notification. The FTC’s “click to cancel” rule and its enforcement actions against companies that make price changes difficult to understand or respond to create additional compliance obligations that sit above and apart from your contractual Terms.

The FTC’s position in recent enforcement actions is that a price increase notification that is technically compliant with your Terms but designed to minimize the customer’s ability to notice, understand, and act on it may still constitute an unfair or deceptive practice. This means your compliance obligation is not just contractual — it is behavioral. The way you implement the process matters, not just the language in the contract.

How to Implement a Price Increase Correctly: A Process Checklist

Having the right clause in your subscription agreement is necessary but not sufficient. You also need to implement each price increase in a way that matches what the clause requires. Here is a process checklist:

• Review all active customer contracts for price guarantees before setting the increase date.
• Calculate the notice period required under your Terms and under applicable state laws for each customer segment, and send notices early enough that the longer window is satisfied.
• Send dedicated, clearly labeled notice communications — not embedded in routine account emails.
• Document delivery of each notice, including timestamps and delivery confirmation.
• Ensure in-app notifications are displayed to active users within the notice period.
• Train your customer success team to answer pricing change questions accurately — inconsistent verbal assurances made after written notice is sent can create implied contract modifications.
• Update your subscription agreement to reflect the new pricing before the first renewal at the new rate.
• Retain documentation of the notice process and any customer responses for at least the statute of limitations period applicable in your primary jurisdictions.

When Pricing Changes Become Contract Amendments

For enterprise customers with individually negotiated contracts — as opposed to standard click-through subscription agreements — a pricing change is often not simply a matter of sending notice. It may require a formal contract amendment signed by both parties.

If your enterprise customer’s Order Form specifies a fixed price for a defined term, you cannot unilaterally change that price by sending a notice under your standard subscription Terms. The price in the Order Form controls for the duration of that term, and a change requires mutual agreement — a signed amendment or a new Order Form executed before the current term expires.

Conflating the treatment of standard subscription customers (who can be notified of price changes) with enterprise customers (who may require formal amendment) is a common and costly mistake. A technology lawyer who regularly advises SaaS companies can help you map your customer base, identify which contracts require amendments versus simple notice, and design a pricing change process that handles both correctly.

If your SaaS subscription agreement lacks a clearly drafted pricing change clause — or if your process for implementing price increases has not been reviewed against the current legal environment — contact TOSLawyer to have your subscription agreement and compliance process evaluated before your next price increase.