Finance Index
What is a procurement catalog, and do mid-market companies need punchout?
Reference guide to catalogs and punchout, including request intake, purchasing controls, approval routing, vendor coordination, and finance visibility.
A procurement catalog is a curated list of pre-approved items with set prices that requesters select from instead of free-typing what they need. An internal catalog is hosted in your system; a punchout catalog connects out to a supplier's web store (via standards like cXML or OCI) and returns the cart as a request. Catalogs reduce off-contract buying - but full punchout is largely an enterprise, high-volume convenience, not a mid-market necessity.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| A procurement catalog | A procurement catalog is a curated list of pre-approved items with set prices that requesters select from instead of free-typing what they need. | Keeps spend controlled before the commitment is made. |
| ERP alignment | Mostly the latter. | Keeps accounting records aligned with the ERP. |
| Related terms | An internal catalog lives in your procurement system with items and prices you maintain; a punchout catalog hands the requester off to the supplier's own web store and pulls the cart back as a request. | Keeps vendor records and payment decisions reliable. |
| What is punchout and how | The requester "punches out" from the procurement system into the supplier's site, shops, and the cart returns as a structured request using protocols like cXML or OCI - preserving negotiated pricing and approval routing. | Keeps vendor records and payment decisions reliable. |
| Set up an internal catalog | Maintain a list of approved items with their agreed prices and vendors, surface it in the request form so buyers select rather than free-type, and keep it current. | Keeps vendor records and payment decisions reliable. |
Do mid-market companies actually need punchout catalogs, or is that an enterprise feature?
Mostly the latter. Punchout earns its integration cost when you have very high transaction volume with a few big suppliers and want requesters shopping live catalogs at negotiated prices. Most mid-market teams get the substance of catalog benefit - steering buyers to approved items and prices, cutting maverick spend - from a far simpler mechanism: a maintained list of preferred items and vendors surfaced inside the request form. That delivers guided buying without standing up and maintaining cXML connections. Reserve true punchout for the handful of suppliers where the volume genuinely justifies it.
What is the difference between an internal catalog and a punchout catalog?
An internal catalog lives in your procurement system with items and prices you maintain; a punchout catalog hands the requester off to the supplier's own web store and pulls the cart back as a request. Internal is simpler to control; punchout keeps supplier pricing live but needs integration.
What is punchout and how does a punchout catalog work (cxml, oci)?
The requester "punches out" from the procurement system into the supplier's site, shops, and the cart returns as a structured request using protocols like cXML or OCI - preserving negotiated pricing and approval routing. It's a live-catalog integration, valuable mainly at high volume.
How do I set up an internal catalog of pre-approved items and negotiated prices?
Maintain a list of approved items with their agreed prices and vendors, surface it in the request form so buyers select rather than free-type, and keep it current. This is the high-value, low-effort version of catalog buying for most mid-market teams.
How do I connect amazon business or staples-type suppliers via punchout?
Through the supplier's punchout/cXML setup into a procurement system that supports it - worth it only if your volume with that supplier is high enough to justify the integration and maintenance. Otherwise a preferred-vendor entry and approval guidance covers it.
Which spend categories benefit most from catalogs - office supplies, it hardware, mro?
High-frequency, standardized, repeatedly-ordered categories: office supplies, IT peripherals, MRO consumables. These are where a catalog (or preferred-item list) prevents both maverick buying and re-keying.
Catalog prices drift out of date and POs go out at wrong prices - how do I maintain catalog accuracy?
Assign an owner and a refresh cadence tied to contract updates, and reconcile catalog prices against invoiced prices to catch drift. Stale catalogs cause match exceptions; treat price maintenance as the cost of running a catalog.
How do I handle non-catalog (free-text) requests alongside catalog requests?
Allow free-text requests for the long tail while steering common buys to the catalog/preferred items - and review free-text requests for items that should become catalog entries. The catalog covers the predictable; free-text handles the rest without blocking it.
Catalog-first purchasing vs request-first purchasing - which model fits a finance-led team?
Request-first with preferred items embedded fits most finance-led teams: the request is the control, and the catalog/preferred list guides the choice within it. Catalog-first models suit high-volume operational buying; finance-led indirect spend is better served by guided request-first.
How do catalog items map to GL accounts and item masters in the ERP?
Tie each catalog/preferred item to its GL coding and (where relevant) ERP item master so a catalog selection carries correct coding downstream. The mapping is what makes catalog buying clean in accounting, not just convenient at request.
Stampli perspective
Stampli's position is that spend control should start before the invoice arrives. When requests, approvals, purchase orders, invoices, and payments stay connected, finance can manage policy, coding, and evidence as one workflow instead of reconstructing the story after the fact.