What Happens If A SaaS Customer Exceeds Usage Limits

If a SaaS customer exceeds their usage limits, what happens next depends on what your contract says. You may be able to charge overage fees, move them to a higher plan, restrict the extra usage, suspend access or ask them to reduce their usage - but only if your terms clearly allow it.

That sounds simple, but SaaS usage can get messy quickly. A customer might add extra users without telling you, send far more API calls than expected, store large files, share one login across a team, or put a heavy load on your platform in a way your pricing never covered.

The good news is that this is very manageable if your SaaS usage limits are clear in your customer contract from the start. The key is to make your limits measurable, your fees transparent and your enforcement process fair enough that customers understand what will happen before it happens.

Can You Charge A SaaS Customer For Exceeding Usage Limits?

Yes, you can usually charge a SaaS customer for exceeding usage limits if your SaaS terms clearly give you that right and explain how the extra charges are calculated.

For example, your subscription terms might say that a plan includes:

• up to 20 user seats
• 100,000 API calls per month
• 500GB of storage
• 10,000 emails or messages sent each month
• access for one company or one workspace only

If the customer goes over those limits, your contract can set out what happens next. You might charge a fixed overage fee, charge on a usage based model, upgrade the customer to the next plan, or contact them first to agree a change.

What you want to avoid is surprising the customer with a bill they couldn't reasonably have predicted. In England and Wales, a SaaS contract is still governed by ordinary contract law principles. If your charging mechanism is unclear, you may struggle to recover unpaid invoices if the customer disputes them.

If you sell to consumers as well as businesses, you also need to think about the Consumer Rights Act 2015 and transparency around pricing. Consumer terms that are unclear, hidden or unfair can be challenged. Many SaaS providers sell business to business, but if freelancers, sole traders or consumers can sign up online, it's worth checking your terms carefully.

What Should Your Overage Fees Clause Say?

Your overage fees clause should say when extra fees apply, how they're calculated, when they're invoiced and whether the customer gets any warning before charges start.

A strong clause usually covers:

• The usage metric: for example, seats, API calls, storage, transactions, active users, projects, integrations or data processed.
• The included allowance: for example, 50 seats or 1 million API calls per calendar month.
• The overage rate: for example, GBP 0.01 per extra API call block, GBP 10 per additional seat per month, or a published usage rate.
• The billing period: for example, monthly in arrears, at the next renewal, or immediately once a threshold is crossed.
• Whether charges are automatic: or whether you'll notify the customer and ask them to approve an upgrade.
• Taxes: for example, whether prices are exclusive of VAT where applicable.

Say Maya runs a project management SaaS. Her standard plan includes 30 seats and 200GB of storage. One customer adds 12 extra team members and uploads large video files, taking them to 600GB of storage. If Maya's terms say extra seats are billed at GBP 8 per seat per month and extra storage is billed at GBP 20 per 100GB per month, she has a clear basis to invoice the customer.

If her terms only say reasonable extra charges may apply, the customer has more room to argue. That wording might help in some situations, but it's much weaker than a clear pricing mechanism.

Can You Suspend Access If A Customer Goes Over Their Limits?

Yes, you can suspend or restrict access for excessive usage if your contract gives you that right and you use it reasonably.

Suspension is a useful tool, but it can also be disruptive for your customer. If their team relies on your software every day, cutting off access without warning could damage the relationship and may lead to a dispute.

A balanced SaaS suspension clause might let you suspend, throttle or restrict access where:

• the customer's usage materially exceeds their plan limits
• the usage creates security, performance or availability risks
• the customer hasn't paid overage fees after being invoiced
• the customer is sharing accounts or allowing unauthorised users
• the customer refuses to move to a suitable plan after notice

It's usually sensible to build in a notice process unless there's an urgent risk. For example, you might give 5 business days' notice to fix ordinary overuse, but reserve the right to act immediately if the usage threatens your systems, other customers or data security.

For business customers, the Unfair Contract Terms Act 1977 can be relevant where you're limiting liability or relying on standard terms. Your suspension wording should be reasonable, clear and tied to a genuine business need, not a broad right to switch off access whenever you like.

How Do Usage Based Pricing Terms Work?

Usage based pricing terms work by linking the customer's fees to how much they use the software, rather than charging only a flat subscription fee.

This can be a good model for SaaS products where customer usage varies widely. For example, a small customer might only need 5 seats and modest storage, while an enterprise customer might need hundreds of users, millions of API calls and priority infrastructure.

Common Usage Based Models

You might structure your pricing as:

• Tiered plans: each plan includes a fixed allowance, with overage fees above that allowance.
• Pay as you go: the customer pays for each unit used, such as each transaction or API call.
• Committed spend: the customer commits to a minimum monthly or annual amount, with extra usage charged separately.
• Volume pricing: unit prices reduce when the customer reaches higher usage bands.
• Hybrid pricing: a base subscription fee plus usage charges.

Your contract should match how your billing system actually works. If your platform measures usage daily but invoices monthly, say that. If usage is rounded up to the nearest block, say that too. If unused allowance doesn't roll over, make that clear.

You should also think about what happens when you change your pricing. Many SaaS contracts allow pricing changes at renewal, with advance notice. If customers are on annual plans, changing usage rates mid-term without a clear contractual right can cause pushback.

Do You Need A SaaS Fair Use Policy?

It depends, but a SaaS fair use policy is a good idea if your product offers unlimited or generous usage in a way that could be abused.

Fair use policies are common where it's hard to predict every limit in advance. For example, you might offer unlimited projects, unlimited messages or unlimited AI summaries, but still need protection if one customer uses the product in a way that affects performance or costs far more than expected.

A fair use policy shouldn't be a hidden trap. If you advertise something as unlimited, then use a vague policy to impose strict limits later, customers may feel misled. For consumer-facing products, the unfair commercial practices rules in the Digital Markets, Competition and Consumers Act 2024 and the Consumer Rights Act 2015 can be relevant to how pricing and key limits are presented. The Consumer Protection from Unfair Trading Regulations 2008 may still be relevant to conduct before 6 April 2025 under transitional and saving provisions.

What To Include In A Fair Use Policy

Your policy can cover:

• what normal and acceptable use looks like
• examples of excessive, automated or abusive use
• whether account sharing is allowed
• technical actions you can take, such as throttling or rate limiting
• when you can require the customer to upgrade
• how much notice you'll give before restricting access, where possible

For example, if your SaaS tool includes AI document generation, you might say that unlimited generations are subject to fair use, and that automated bulk generation, resale of outputs or unusually high requests may be restricted or moved to an enterprise plan.

Templates often miss these product-specific details. Fair use wording works best when it reflects how your software actually operates and where your costs or system risks sit.

Can You Audit A Customer's SaaS Usage?

Yes, you can audit a customer's SaaS usage if your contract gives you audit rights and you handle the process carefully.

For many SaaS providers, an audit doesn't mean turning up at a customer's office. It often means reviewing usage logs, account data and billing records to check whether the customer is staying within their plan.

Your audit wording might let you check:

• the number of active users or seats
• whether logins are being shared
• API call volumes and automated use
• storage, bandwidth or processing usage
• whether the software is being used by unauthorised group companies, clients or contractors
• whether usage matches the licence scope in your agreement

If your audit involves personal data, UK GDPR and the Data Protection Act 2018 matter. Usage logs can include names, email addresses, IP addresses, device data and activity records. You should only collect and use what you need, explain this in your privacy notice, apply appropriate security and make sure your customer contract has the right data protection terms.

If you process personal data on behalf of your customer, you may also need data processing terms that meet Article 28 of the UK GDPR. This is especially relevant if your SaaS product stores customer records, employee data, health information, financial information or other personal data uploaded by the customer.

Your audit clause should avoid being heavy-handed. A practical approach is to let you review system records at reasonable intervals, request supporting information if needed, and invoice any underpaid fees if overuse is found.

What If The Customer Says The Usage Limit Was Not Clear?

If the customer says the limit wasn't clear, the outcome will usually turn on what your contract, order form, pricing page and onboarding materials actually said.

This is where SaaS providers often get caught out. The sales page says one thing, the order form says another, and the terms say something broader. If those documents don't line up, the customer may argue they didn't agree to the limit or fee you're trying to enforce.

To reduce that risk, keep your usage rules consistent across:

• your website pricing page
• the checkout flow or sign-up screen
• your order form or proposal
• your SaaS terms and conditions
• your acceptable use policy or fair use policy
• renewal notices and upgrade communications

For online sign-ups, make sure customers actively accept your terms before they subscribe. This is often done through a checkbox or clear button wording. Simply placing terms in a footer can make it harder to prove they were accepted.

You should also keep records. If a customer later disputes an overage invoice, it helps to have:

• the version of the terms they accepted
• the date and time of acceptance
• the plan or package they selected
• usage reports showing how the limit was exceeded
• copies of notices you sent about overuse

If you sell to larger customers, your order form or heads of terms can do a lot of the heavy lifting. It can set out the customer's exact usage allowances, fees, support level, renewal date and any negotiated exceptions.

How Should You Deal With Overuse In Practice?

You should deal with overuse in a way that follows your contract, protects your platform and keeps the customer relationship as constructive as possible.

A practical process might look like this:

1. Detect the overuse: use your system reporting to identify when a customer is close to or over their limit.
2. Check the contract: confirm what their plan includes and what your terms allow you to do.
3. Notify the customer: explain the usage issue, the relevant limit and the likely fee or required upgrade.
4. Offer options: for example, reduce usage, buy extra capacity, upgrade the plan or discuss a custom plan.
5. Invoice clearly: show the usage period, metric, allowance, overage amount and fee calculation.
6. Escalate only if needed: if the customer doesn't respond or the usage creates risk, use your suspension or restriction rights.

For lower value accounts, you may want automatic overage billing. For larger accounts, you may prefer account manager approval or written notice before extra charges apply. There's no single right answer. It depends on your product, customer base, risk level and commercial style.

You can also design your product to make disputes less likely. Usage dashboards, automated alerts at 80 percent and 100 percent, and clear in-app upgrade prompts can make your legal terms feel fair and easy to follow.

Key Takeaways

• Your SaaS contract should clearly state each usage limit, such as seats, API calls, storage, users or fair use restrictions.
• Overage fees are easier to enforce when the pricing formula, billing period and notice process are clear.
• Suspension rights can protect your platform, but they should be used carefully and tied to genuine overuse, unpaid fees or system risk.
• A fair use policy helps with unlimited or high-volume features, but it shouldn't contradict your marketing or pricing pages.
• Audit wording, usage logs and data protection terms are especially important if you monitor customer activity or process personal data.
• Your pricing page, order form and SaaS terms should tell the same story so customers know exactly what they're agreeing to.

If you'd like help with your SaaS terms, overage fees, fair use policy or data protection wording, you can reach us at 08081347754 or team@sprintlaw.co.uk for a free, no-obligations chat.