What should procurement check before removing products from an enterprise software agreement?

What should procurement check before removing products from an enterprise software agreement?

What should procurement check before removing products from an enterprise software agreement?
10/21/2026

Before removing products from an enterprise software agreement, procurement should check partial-termination rights and the pricing of the products it plans to retain. Review the support obligations that will continue after the change. A smaller software portfolio can still carry substantial costs if the supplier reprices the remaining products or keeps existing support commitments in place.

At ProcureCon IT Sourcing 2026, Evan Boyd, Vice President of Global Operations at Software Licensing Consultants, described how removing products from an Oracle agreement could affect discounts on the software a customer retained. He explained his team's priorities during contract negotiations: "The fine print's our first focus, but price is always going to follow." Buyers need to understand how cancellation terms affect their remaining obligations before calculating the savings.

In another 2026 session, a presenter urged buyers to establish what happens to their data after termination, particularly when a supplier has used it to train AI. Procurement should confirm data-return and deletion obligations before retiring an AI-enabled service.

Ask the supplier for a written cost breakdown showing what you will pay after removing the proposed products. Work with legal to confirm cancellation provisions and have IT validate which licenses and support services the business still needs. Include any overlapping charges and data-exit requirements in the review before approving the change.

Join ProcureCon IT Sourcing to compare how procurement leaders manage software portfolio changes and negotiate flexibility into enterprise agreements.