What is a Procurement Punchout Catalog?

A procurement punchout catalog connects a supplier's e-commerce site directly to a buyer's procurement system, so employees can shop on the supplier's website and return their cart to the internal platform as a purchase requisition. The catalog stays on the supplier's servers, which means pricing, stock levels, and product data are always current. Punchout connections typically run on the cXML or OCI protocols.

A procurement punchout catalog is a supplier-hosted online store that plugs into a company's purchasing system. Instead of the buyer maintaining a local copy of the supplier's product list, an employee "punches out" from their procurement tool to the supplier's website, fills a shopping cart, and sends that cart back into the procurement system for approval and payment.

The result is a form of guided buying that feels like normal online shopping. The difference is that everything the employee buys flows through the company's approval rules, budgets, and purchasing process rather than a personal credit card and an expense claim.

How does a punchout catalog work?

A punchout transaction follows a fixed sequence, usually built on cXML (commerce eXtensible Markup Language, the standard popularised by Ariba) or OCI (Open Catalog Interface, the SAP equivalent). Here is what happens when someone orders laptops through a punchout connection:

1. The employee starts in the procurement system. They select the supplier, for example Dell or Amazon Business, from a list of approved vendors.
2. The system authenticates with the supplier. It sends a setup request containing the buyer's credentials, so the supplier knows which company is shopping and which contract pricing to display.
3. The supplier's site opens with negotiated pricing. The employee sees the supplier's full storefront, but with their company's contracted prices, approved product ranges, and any category restrictions already applied.
4. The cart returns to the procurement system. When the employee checks out, the supplier sends the cart contents back as structured data rather than charging a card.
5. The requisition follows the normal approval flow. The cart becomes a purchase requisition, routes through the right approvers, and generates a purchase order once approved.

The employee never re-keys product codes or prices. The supplier never receives an order that finance has not approved.

Punchout catalogs vs hosted catalogs

The main alternative to punchout is a hosted catalog: a list of products and prices that lives inside the buyer's procurement system rather than on the supplier's site. The buyer loads it and maintains it.

Hosted catalogs cover two different things, and the distinction matters. The first is supplier-supplied: a file of contracted items and prices the supplier sends over, such as an office supplies agreement covering 200 lines. The second is internal: stock the business holds and issues itself, like the batch of laptops IT keeps for new starters. There is no supplier site to punch out to for internal stock, so a hosted catalog makes items requestable through the same front door as everything else.

Punchout catalogs suit suppliers with large or fast-changing ranges. An IT reseller with 50,000 products and weekly price changes cannot realistically send the buyer a spreadsheet every Monday. Punchout keeps the data on the supplier's side, so buyers always see live stock and current pricing. The downside is less buyer control: if the supplier changes their site or pricing display, the buyer finds out when someone complains.

Most mid-size and enterprise companies run both models: punchout for high-volume suppliers with big ranges, hosted catalogs for fixed-price agreements and for whatever the business stocks itself.

Why do punchout catalogs matter for procurement teams?

Punchout catalogs solve a specific problem: employees will always choose the easiest way to buy. If the sanctioned route means submitting lengthy requests for routine purchases, people go around it. They buy on a personal card, expense it, and procurement loses visibility of the spend, supplier relationships, and negotiated discounts.

Punchout catalogs remove that excuse. The buying experience matches what employees already expect from consumer e-commerce, while procurement keeps three things it cares about:

• Contract pricing applies automatically. Employees cannot accidentally pay list price when the company negotiated X% off.
• Approvals happen before money moves. The cart becomes a requisition, not a completed order, so budget owners approve before the supplier ships anything.
• Spend data stays structured. Every line item arrives with product codes, quantities, and prices, which makes invoice matching and category reporting far more accurate than parsing expense receipts.

Historically, punchout was a project. Each connection needed coordination between the buyer's procurement system, the supplier's e-commerce team, and usually an IT resource on each side, running two to six weeks per supplier depending on how comfortable the supplier was with cXML or OCI. That only paid off for suppliers with serious transaction volume, which is why punchout stayed confined to a handful of the largest contracts.

That calculation has changed. Most hardware and tail spend goes through the same small set of storefronts: Amazon Business, CDW, Staples. Modern platforms, like Omnea, ship those connections natively, so the integration work is already done. Employees shop the supplier's full range at live pricing, the basket flows back into the approval chain automatically, and there is no catalog file for the buyer to maintain. Suppliers outside that set still need a proper integration, but the storefronts covering the bulk of everyday buying no longer do.

Where punchout fits in the wider purchasing process

Punchout catalogs handle one slice of company spend: repeatable, catalog-friendly purchases such as hardware, office supplies, lab consumables, and MRO items (maintenance, repair, and operations goods). They do not help with the purchases that cause procurement teams the most pain, such as new SaaS subscriptions, consulting engagements, or anything requiring a contract negotiation, security review, or legal sign-off.

That distinction matters when designing an intake process. A punchout catalog answers "I need ten more monitors from our approved supplier." It cannot answer "I want to buy a new analytics tool nobody has vetted yet." 

This is why intake platforms like Omnea sit in front of every type of purchase, not just catalog buys. Employees raise one request regardless of what they are buying. Guided buying then steers catalog-eligible purchases to the right channel: a punchout to an approved storefront, or a hosted catalog of contracted items and internal stock. New software or services requests through security, legal, and finance review. Punchout handles the transaction; intake decides whether the transaction should happen at all.