The product list is the most overlooked lever in a ULA renewal, because buyers fix on price while the list quietly sets cost and audit scope for years. Trim dead products in the right order, scrutinise every addition, and shape the list before the number is ever discussed.
By the Meridian advisory team, former Oracle LMS and GLAS licensing analysts. Updated 4 June 2026.
The product list defines what you can deploy unlimited and what you must certify and support afterward. Carrying products you do not use inflates the support base for years, while quietly added products can expand future cost and audit scope. Shaping the list is the lever most buyers miss because they focus on price, yet the list outlives the price. A renewal negotiated only on the headline number, with the same bloated list carried forward, locks in years of support on software no one runs. The list is where the durable money is.
Price is a one time fight. The product list is a multi year liability. Win the list and you shape the support base for the whole next term. Negotiate the list before the price, because once price is agreed the list tends to set hard.
Every product on the list that you do not deploy is dead weight that, if carried forward, can add to the support base for years. The opportunity at renewal is to remove what you genuinely do not use. The discipline is order: where you have already deployed a product under the unlimited right, you generally need to certify and license what is in use before dropping the product, so you keep the entitlement you earned and shed only the dead capacity. Removing first and certifying later loses the deployment. Sequence matters more than ambition here.
The other direction is additions. Oracle often proposes folding in new products, options, or packs as part of a renewal, framed as value. Each addition expands what you can deploy unlimited, which sounds attractive, but it also expands the surface you must certify, support, and defend in an audit later. Treat every proposed addition as a future support and scope commitment, not a free upgrade. The concessions Oracle trades around these additions are covered in the concessions Oracle will trade.
Take an indicative renewal where the existing list carries eight products, three of which are not deployed anywhere. Carried forward unchanged, those three sit in the support base for the next term and beyond. By certifying and licensing what is actually in use across the deployed products, then renewing with the three dead products removed, the organisation renews a leaner list and a lower forward support base. If Oracle proposes adding two new options to sweeten the deal, each is weighed against the certification and support it commits the organisation to later, rather than accepted as a bonus. The figures are indicative and the right moves depend on the contract, but the shape is consistent: trim the dead, scrutinise the new.
| List item | Status | Renewal move |
|---|---|---|
| Deployed and used | Active entitlement | Keep, certify what is in use |
| On list, not deployed | Dead weight | Remove from renewed list |
| Proposed addition | Future commitment | Weigh against later support and scope |
| Deployed, being retired | Transitional | Certify now, plan exit |
Start with an independent deployment baseline, because you cannot shape a list you have not measured. Knowing exactly what runs, and where, tells you which products are real entitlement and which are dead weight. Bring that evidence to the table first and negotiate the list before the price, since a list agreed under deadline pressure tends to set hard. Frame every removal as licensing what you use and shedding what you do not, and frame every proposed addition as a cost you will carry, so the conversation stays anchored to the multi year liability rather than the one time fee. If a capped structure would suit your position better than a fresh unlimited term, that path is set out in negotiating a capped ULA instead.
The product list is where a renewal either quietly bleeds money for years or is shaped into a lean, defensible base. Measure your deployment, trim the dead products in the right order, scrutinise every addition, and settle the list before the price. Do that and the renewal you sign reflects what you actually use, not what the previous list happened to contain. The full negotiation framework lives in our pillar, the certify or renew guide.
The product list sets cost and audit scope for the whole next term, so it is the lever that matters most and the one buyers most often miss. Remove products you do not use, but certify and license what is deployed first so you keep the entitlement. Weigh every proposed addition as a future commitment. Measure your deployment, then negotiate the list before the price. The price is one fight; the list is years of them.
The product list defines what you can deploy unlimited and what you must certify and support afterward. Carrying products you do not use inflates the support base for years, while quietly added products can expand future cost and audit scope. Shaping the list is the lever most buyers miss because they focus on price.
Usually yes, but deliberately. Removing a product you have already deployed means you must license what is in use through certification first, then drop it from the renewed list. Done in the right order, trimming dead products lowers the long run support base without losing entitlement you have earned.
Book a confidential assessment and we will baseline your deployment and build the product list strategy that lowers your forward support base.