A catalogue your people will actually use

A connection that takes your buyer from your procurement system out to the supplier's own website, lets them build a basket there, then returns that basket into your system for approval. The item data lives with the supplier rather than in your catalogue.

A hosted catalogue keeps the supplier's items and prices inside your system, which gives you control and means somebody has to maintain them. Punchout leaves that with the supplier, which stays current automatically but gives you less control and needs testing whenever either side changes.

cXML is the message format most punchout connections use to pass the session and the returned basket between your procurement system and the supplier's site. OCI is the equivalent used widely in SAP environments. Both are established protocols, and a punchout setup is largely configuring and testing one of them correctly.

A Catalog Interchange Format file, a flat file of items and prices a supplier sends you to load into your system as a hosted catalogue. It is simple and widely supported, and it goes out of date the moment prices change unless someone refreshes it.

Because a catalogue nobody uses does not control anything. Procurify's 2026 benchmark found adoption ranging from 18.6 percent to 76.2 percent by sector and treats below 40 percent as a signal of off-policy buying. Low adoption usually means the content is stale, not that people are being difficult.

It depends on the category, but the useful question is how many of your items carry a price older than ninety days. Not one competitor page we reviewed proposes any hygiene measure at all, which is why catalogues decay quietly.

Chase supplier content, load and enrich items, apply your classification, reconcile prices against contracts, set up and test punchout connections, retire dead items, and report on what is going stale.

Either a fixed fee for a build or cleanup, a price per block of items maintained, or a monthly dedicated seat. We quote after the free audit, because it depends on item counts, how many suppliers need chasing and how much enrichment your content needs.

Yes. Coupa, SAP Ariba, Oracle, Jaggaer, Zip, Ivalua, Precoro and Procurify among others. We are platform agnostic because we sell the work, not a tool, so we have no reason to move you.

We do the chasing. Punchout needs both ends configured and tested, and suppliers vary enormously in how responsive their technical teams are. Coordinating that is most of the effort, and it is the part your own team usually cannot get to.

Some will not, and we tell you which rather than quietly loading poor data. Where content is thin we enrich it ourselves from specifications and prior purchase history, and where a supplier is genuinely unworkable that is useful sourcing information in itself.

Punchout covers suppliers big enough to run their own commerce site. Hosted catalogues cover everyone else, plus anything you have negotiated a specific price on. Most mid-market buyers need both, which is part of why maintenance gets messy.

Access is scoped by you, granted to named people, and revoked through your own leaver process. We contract on standard clauses, name every sub-processor, and work to GDPR, UK GDPR, PIPEDA, the Australian Privacy Principles and Saudi PDPL. ISO 27001 alignment is in progress and SOC 2 Type II is on the roadmap. We state status honestly rather than showing badges we do not hold.

Content fixes land quickly, but behaviour follows behind. People who have been raising free-text requests for a year need to discover the catalogue works again. Expect the numbers to move over a quarter, not a fortnight.

Yes, and it is the sensible way in. Pick the supplier your people order from most, fix that catalogue properly, measure adoption against the audit baseline, then widen.