Ariba Discovery and the Ariba Network sit adjacent to each other in the SAP procurement portfolio and are routinely confused. The confusion costs money. Customers who treat them as interchangeable end up with the wrong subscription, the wrong supplier-onboarding posture, and the wrong cost profile. The two products are commercially distinct, operationally distinct, and aimed at different stages of the procurement lifecycle. The first part of any Ariba portfolio review is to clarify which of the two the customer actually needs, which they currently subscribe to, and whether the current state matches the operational use case.
This article explains the difference between the two products, the use cases each supports, the licence structures they carry, and the consolidation move that frequently produces a cleaner portfolio.
Ariba Discovery: the sourcing-event side
Ariba Discovery is a supplier-discovery service. The buyer posts a sourcing event or supplier-search request, and Discovery surfaces suppliers from its network that match the requirements. Discovery is positioned for spot sourcing, new-supplier onboarding, and category-expansion projects rather than for steady-state procurement transactions. The buyer side is typically licensed on a per-event or per-posting basis, with annual commitments that bundle a fixed number of postings at a discounted rate. The supplier side is licensed on a subscription basis, with suppliers paying for the right to be discoverable in the relevant category.
Discovery is most valuable in categories where supplier turnover is high or where the buyer's existing supplier base does not cover the category adequately. It is less valuable in mature categories with established preferred-supplier lists, where the buyer's procurement effort is in managing existing suppliers rather than discovering new ones.
Ariba Network: the transactional side
The Ariba Network is a transactional platform. Once a buyer-supplier relationship exists, the Network is the channel through which purchase orders, advance ship notices, invoices, service entry sheets, and remittance documents travel. The Network is positioned for steady-state procurement transactions across the buyer's full supplier base, not for spot sourcing or supplier discovery. The buyer side is licensed against transaction-volume thresholds, supplier counts, and the bundled buyer-platform fee. The supplier side is licensed on a supplier-pays model with tiered annual fees indexed against transaction volume.
The Network is most valuable when the buyer has high transaction volumes across many suppliers and wants the standardisation and automation the Network provides. It is less valuable when the buyer's transaction volume is concentrated among a small number of suppliers who can be managed directly through EDI or supplier portals. See our companion article on buyer commerce thresholds for the threshold structure.
The commercial line between them
The commercial line between Discovery and Network is the transition from supplier discovery to steady-state transaction. A new supplier identified through Discovery may subsequently be enabled on the Network for transactional exchange. The two stages can be licensed separately or bundled into an integrated arrangement, depending on the customer's procurement footprint and the SAP packaging in force at deal time.
The most common configuration error is to subscribe to both products without operationalising the link — using Discovery to identify suppliers but not enabling them on the Network, or operating the Network without using Discovery to expand the supplier base. The misalignment produces a paying-for-both-but-using-one pattern that surfaces clearly only on a portfolio review.
The Discovery-only use case
Customers with a defined supplier base who use Discovery only for periodic category expansion can typically operate on a small Discovery subscription, posting a defined number of events per year, without needing the Network. Their transactional commerce runs through ERP, EDI, supplier portals, or other means. The Discovery line is small but discrete.
The Network-only use case
Customers with a mature supplier base and high transactional volume can typically operate on the Network without Discovery. The supplier-onboarding work is managed through the Network's own onboarding workflow, the supplier-search capability of the Network, or direct procurement-team engagement with suppliers. The Network line is the dominant Ariba cost.
The integrated use case
Customers with rapidly expanding supplier bases — growth-stage companies, M&A-active enterprises, customers expanding into new geographies — benefit from the integrated configuration where Discovery feeds the Network. The two subscriptions complement each other operationally, and the integrated configuration justifies the combined cost.
The portfolio review workflow
A portfolio review of the Discovery and Network subscriptions has four steps. The first is to extract the subscription line items from the order forms and reconcile them against the current Ariba modules in operational use. The second is to extract the operational metrics — postings per period from Discovery, document counts and supplier counts from the Network — to validate whether the operational use justifies the subscriptions. The third is to identify the misalignments: subscriptions running below operational need, subscriptions running above operational need, or subscriptions paid for but not used. The fourth is to model the consolidation options and the renewal repositioning that would correct the misalignments.
The portfolio review is best timed for the year before the renewal cycle, with the corrective action incorporated into the renewal negotiation. Customers who run the review on cadence consistently produce cleaner Ariba portfolios than customers who let the SAP commercial team propose the renewal from the existing subscription footprint.
The negotiation posture
The defensive negotiation posture for the Discovery and Network combination has three elements. The customer should negotiate the two subscriptions separately, not as a bundled package, so that each can be sized independently. The customer should attach use-based metrics to each subscription so that the renewal can be revisited if the operational use does not match the subscription size. The customer should reserve the right to convert between subscription tiers or to consolidate to a single subscription if the operational pattern changes. See our contract negotiation service for the framework we use.
For the methodology behind Ariba portfolio reviews, see our cloud licensing economics white paper. For the broader Ariba context, see our Ariba topic page. For a worked example of a portfolio consolidation that combined Discovery and Network into a single integrated arrangement, see our retail group case study.