Hosted catalogues and punchout connections look operationally innocuous. The category manager publishes a catalogue, the requester searches it, the procurement engine generates a purchase order, and the supplier fulfils. The customer's perception of the cost of running catalogues is usually limited to the buyer's-side enablement effort and the supplier's catalogue maintenance. In commercial reality, the Ariba contract treats hosted catalogues, punchout sites, and CIF imports as separately licensable artefacts with their own document-volume and connection-count meters.
The licensing footprint of a typical mid-sized Ariba catalogue programme — fifty to two hundred suppliers across hosted and punchout patterns — is rarely below six figures annually, and is frequently in the high six figures. The cost is mostly invisible to the procurement team because it lands in document subscriptions and network fees rather than in a line item labelled "catalogues." This article walks the structure.
The four catalogue patterns in Ariba
1. Hosted catalogues (CIF, BMEcat)
The supplier provides a catalogue file (CIF for legacy Ariba, BMEcat for some industries) which the buyer imports into the Ariba catalogue. The catalogue items become searchable to requesters. The supplier maintains the catalogue centrally and pushes updates on a defined cadence.
2. Punchout catalogues
The supplier hosts the catalogue on its own e-commerce platform. The buyer's requester clicks a punchout link in Ariba, is transported into the supplier's site, builds a shopping cart, and returns the cart to Ariba for purchase order generation. The supplier maintains the catalogue on its side; Ariba carries the punchout configuration and the cart-return integration.
3. Smart Order Routing / catalogue aggregators
An intermediate pattern where multiple suppliers' catalogues are aggregated by a third-party catalogue aggregator (an Ariba partner). The buyer maintains one integration with the aggregator and receives content from multiple suppliers.
4. Free-text / non-catalogue items
Requisitions for items that do not exist in any catalogue, raised as free-text requests. Operationally less efficient, but licensing-wise often cheaper because the document does not carry the catalogue overhead.
How each pattern is licensed
The licensing rules differ across the four patterns. Hosted catalogues are typically licensed at a per-item or per-catalogue basis, depending on the order form. Punchout catalogues are licensed at a per-connection basis — each active punchout site is a countable connection. Aggregators are licensed at the aggregator's per-connection rate, which is often cheaper per supplier than direct punchouts at scale. Free-text items consume a different meter, typically the buyer platform fee.
The implication is that the same operational shape — one supplier, one catalogue, one PO — can have materially different licence costs depending on which pattern the customer has chosen. Customers who have grown organically without an explicit catalogue strategy frequently end up with a mix of all four patterns and a licence cost that is higher than any single-pattern deployment would have been.
The document-volume meter and catalogue patterns
Separately from the connection-count meters, the buyer platform fee is calculated on the volume of documents processed. Catalogues drive document volume in two ways: directly, through the requisitions and POs generated against catalogue items, and indirectly, through change orders, invoice mismatches, and contract amendments that catalogue items disproportionately produce.
The indirect volume is the more underestimated cost. A catalogue with poorly maintained price data produces invoice mismatches at scale; each mismatch is a separate document against the buyer platform fee meter. Customers who clean up their catalogue price discipline frequently see a step-change reduction in their buyer platform fee tier at renewal. See our analysis of buyer platform fee renewals for the tier mechanics.
The supplier-side dimension
The supplier-side cost of Ariba catalogues is often passed back to the buyer through pricing. Suppliers who maintain hosted catalogues incur the catalogue maintenance fee on the Ariba Network, plus the document-volume fees on the supplier side. Major suppliers typically absorb the cost as part of doing business; smaller suppliers occasionally surface it in pricing negotiations or in catalogue-maintenance carve-outs in supplier contracts.
The customer's licensing position interacts with the supplier-side dynamics in one specific way: a customer that pushes too many small suppliers onto hosted catalogues sometimes finds those suppliers requesting price increases at contract renewal that offset the operational savings of catalogue automation. See the Ariba Network fees analysis for the supplier-side detail.
The CIF import treatment
CIF (Commerce eXtensible Markup Language file) imports are the legacy hosted-catalogue mechanism. The CIF import volume is occasionally separately metered in older Ariba contracts. Customers on older order forms should specifically review whether CIF imports count against a separate meter — the clause is often in a schedule rather than the main contract body, and is frequently missed by procurement teams reviewing the main contract.
The CIF treatment is also a particular pressure point in S/4HANA conversion scenarios, where the customer is shifting from legacy ECC-integrated Ariba to S/4HANA-integrated Ariba. The CIF import behaviour can change in the conversion, and customers should confirm the conversion-side treatment as part of the licensing analysis. See our analysis of S/4HANA migration compliance for the broader conversion framework.
The renewal-time playbook
Three negotiating moves materially reduce catalogue-related cost at renewal. First, push for a unified "catalogue access" licence that covers hosted, punchout, and aggregator patterns at a single rate, with a defined volume band. Second, request a six-month "punchout cleanup" window in which dormant punchout connections can be deactivated without contractual cost. Third, negotiate explicit anti-double-counting language for items that may appear in multiple catalogue patterns (e.g., the same SKU available via punchout and via free-text fallback).
These moves typically reduce catalogue-related licence cost by twenty to thirty per cent versus the SAP default. On a mid-sized programme, the saving is in the high six figures annually. See the contract negotiation service for the engagement model.
The operational disciplines that contain catalogue licensing cost
Four operational disciplines materially contain the licence cost of an Ariba catalogue programme. First, an annual punchout-connection audit that identifies dormant connections for deactivation. Second, a quarterly catalogue price-discipline review that reduces invoice mismatches and the resulting document-volume inflation. Third, a category-strategy view that consolidates suppliers onto fewer, larger catalogue connections rather than many small ones. Fourth, an explicit policy on free-text versus catalogue requisitions that prevents proliferation of low-value punchouts.
These disciplines are operationally inexpensive and they consistently outperform reactive cleanup at renewal time. See the broader operational context in our Ariba topic page, the closely related discussion in Ariba mobile app licensing, and the SAP Ariba Licensing Audit Guide for the full framework.
What good looks like
A well-managed Ariba catalogue licensing position has unified contract language across catalogue patterns, an annual punchout cleanup discipline, a quarterly catalogue price-discipline review, and an explicit category strategy that limits punchout proliferation. Customers who hit this standard typically pay twenty-five to thirty-five per cent less for their catalogue programme than customers on default SAP terms, with no material reduction in operational throughput.