SKU Level Price Locks

What is a SKU level price lock?

A SKU level price lock fixes the price of each individual line item, or SKU, for a defined period, rather than locking only the overall contract value. In a SaaS agreement your spend is built from many components: editions, seat types, modules, add ons, support tiers, and consumption units, each with its own price. A SKU level lock holds each of those component prices steady for the term and, ideally, for defined expansions, so the figure on every line is the figure you agreed and not a number the vendor can revise underneath the total.

The distinction sounds technical but it decides real money. Locking the total protects only the basket you bought today. Locking at the SKU level protects the basket you will buy tomorrow, because growth, new modules, and added seats all draw on component prices that the vendor would otherwise be free to reset. In a market where the top 500 SaaS companies made 339 pricing and packaging changes in a single year, the component prices move constantly, and the lock is what holds them where you negotiated.

Why is locking only the total not enough?

Locking only the total is not enough because a vendor can keep the headline flat while repricing the parts you will need next. Picture a renewal where the total is held at this year's number to make the deal look generous. Underneath, the price of the additional seats, the next module, or the higher edition you are likely to add has quietly risen. The total looks protected, but the moment you expand, the repriced SKUs apply, and the increase you avoided on paper arrives in the form of more expensive growth.

This is a quiet version of a broader masking pattern, where a vendor presents a reassuring top line while the mechanics underneath move against you. Name it plainly: a flat total with unlocked SKUs is a price increase deferred to your next purchase. The counter is to refuse to negotiate only the headline and to insist the protection reaches the line items, especially the ones you can already see yourself buying.

How do you draft a SKU level price lock?

Draft it to name the SKUs, fix the prices, and set the term, leaving as little to interpretation as possible. Start by listing every line item in the current order, then add the SKUs you realistically expect to buy during the term: the next edition up, the modules on your roadmap, the additional seat types, the consumption units you may scale into. For each, state the locked unit price and the period over which it holds. The discipline is to lock the future purchase at today's price before you need it, because the price you do not lock is the price you will pay later.

Tie the lock to the other protections so they reinforce each other. A SKU level lock works best beside an uplift cap of 3 to 5 percent CPI indexed on any movement, so even repricing on unlisted items is bounded, and beside an AI carve out so new AI SKUs cannot lift the bill automatically. Specify what happens at renewal, too: whether the locked prices carry forward, and on what terms, so the protection does not expire silently at the moment you most need it.

The price you do not lock is the price you will pay later. List the SKUs you will buy and fix them now.

How do you actually win the lock in negotiation?

Win it by asking explicitly, showing the expansion you expect, and trading for it deliberately. SKU level locks are frequently easier to secure than the headline discount, because they do not reduce the representative's current year bookings, which is the number their compensation usually turns on. A discount costs the rep this year; a price hold on future SKUs costs them nothing now and only constrains a future quote. That asymmetry is your opening, so treat the lock as a distinct ask rather than something folded into the discount conversation.

Bring it early and bring it specific. A buyer who arrives with a named list of SKUs to lock, tied to a credible growth plan, is easy for the vendor to accommodate. A buyer who asks vaguely for price protection at the last minute gets a vague answer. Start the renewal six or more months out, prepare the SKU list as part of the requirements, and let the lock ride alongside the rate negotiation where it belongs.

What mistakes do buyers make with price locks?

The first mistake is accepting a locked total and assuming it covers growth, when it covers only today's mix. The second is locking the discount percentage rather than the price, which leaves you exposed when the list price rises and the percentage applies to a higher base. The third is forgetting the expansion SKUs entirely, so the modules and seats you predictably add are repriced at purchase. Each of these feels protected at signing and turns expensive at the next order.

The disciplined approach is the reverse: lock the price not the percentage, lock at the line item not the total, and lock the SKUs you can already see yourself needing. Documented in the order form rather than promised verbally, these locks are what turn a good headline into a durable one. A protection that is not written is a protection you do not have, and the next person to manage this contract will see only what the paper says.

What does a SKU level lock look like in a real order?

In practice the lock appears as a schedule attached to the order form that lists each SKU, its locked unit price, and the period the lock holds. Picture an enterprise buying a core platform edition today and expecting to add a higher edition, two modules, and several hundred seats over the next two years. A SKU level lock fixes the unit price of each of those items now, at today's negotiated rate, so the expansion draws on prices you agreed rather than prices the vendor sets later. The schedule turns a vague promise of price protection into a list the next buyer can read and the vendor must honour.

The discipline that makes it work is forecasting the expansion honestly. A buyer who lists only today's items locks only today's spend; a buyer who maps the realistic two year roadmap locks the growth as well. You do not have to commit to buying the listed SKUs, only to fix their price if you do, which costs you nothing and removes the vendor's freedom to reprice your growth. That asymmetry, a price hold you may never exercise against an increase you would otherwise certainly pay, is what makes the lock such efficient leverage.

Your next step

SKU level locks are where a good discount becomes a lasting one. For the full clause set, read the SaaS Contract Terms Guide. To pair this with the protections that hold the rest of the deal, see The Uplift Cap: 3 to 5 Percent CPI Indexed and The AI Carve Out Clause. When you want these locks drafted and won on a live deal, our buyer side team can take the table or coach yours through it.

Common questions

Last reviewed March 2026. Market figures cited are published industry data; figures labelled indicative are directional.