What Is a PunchOut Catalog? How It Works in B2B Ecommerce

A PunchOut catalog is a supplier’s online catalog that a buyer reaches from inside their own procurement system. The buyer leaves—“punches out” of—their e-procurement application, lands in the supplier’s store, shops a personalized catalog with their negotiated pricing, and sends the finished cart back to the procurement system for approval. There’s no separate login to manage, no order details to rekey, and no switching between screens.

That one move—shopping the supplier’s live catalog without leaving the system of record—is what separates PunchOut from a static price list. The supplier keeps control of product data and pricing; the buyer keeps control of approvals and spend.

👉 This guide covers what PunchOut is and how it works. If you need the deep cXML and Level 2 integration detail, that lives in our integration guide.

1. HOW DOES A PUNCHOUT CATALOG WORK?
2. PUNCHOUT LEVELS: LEVEL 1 AND LEVEL 2
3. WHY PUNCHOUT MATTERS FOR B2B BUYERS AND SUPPLIERS
4. PUNCHOUT AS PART OF A GOVERNED BUYING EXPERIENCE
5. HOW TO ADD PUNCHOUT WITHOUT REPLATFORMING
6. FAQ

Buyers ask for PunchOut because they want suppliers available where they already work—inside their procurement platforms, where more of their spend now runs. They’re not alone: with the global B2B ecommerce market projected to reach $36 trillion in 2026 and around 80% of B2B sales interactions now happening digitally, the contest has moved to which platforms capture the order inside the buyer’s own purchasing system. PunchOut is how a supplier shows up there.

A single PunchOut order moves through a predictable sequence:

1. The buyer starts in their e-procurement system. An employee opens their procurement application—Coupa, SAP Ariba, Oracle, Jaggaer, or similar—and selects the supplier from an approved vendor list.
2. They punch out to the supplier’s store. The procurement system opens a live session into the supplier’s catalog. The buyer sees the supplier’s full range, their own contract pricing, and real-time availability, all without logging in separately.
3. They build a cart and return it. The buyer adds items as they would on any store, then sends the cart back to the procurement system rather than checking out.
4. The order routes for approval. Inside the procurement system, the cart follows the buyer’s own approval rules. Once approved, a purchase order is issued to the supplier for fulfillment.

The supplier isn’t pulled into the buyer’s internal approvals; the procurement system handles that. The supplier simply receives a clean, approved order.

Not every PunchOut setup offers the same depth, and buyers will often specify which they need.

Level 1 is the simpler form. The buyer punches out, shops the catalog, and returns the cart—the core round trip described above.

Level 2 adds catalog-level integration: the procurement system can search and display the supplier’s items, categories, and pricing within the procurement interface itself, so buyers can find products without always launching a full session. It relies on cXML messaging to pass that data back and forth.

👉 The mechanics of Level 2—cXML setup, request and response handling, field mapping—are an integration topic in their own right. We cover them in full in our cXML and Level 2 PunchOut integration guide.

PunchOut earns its place because it works for both sides of the transaction at once.

For buyers, it keeps purchasing inside the system that already governs it.

• Procurement continuity means no parallel process to police: orders carry the right pricing, follow the right approval chain, and land in the right ledger automatically.
• Manual rekeying disappears, and with it the errors that come from typing part numbers and prices by hand.
• Approved orders move faster because the path from cart to purchase order is built in rather than improvised.

That continuity matters more as buying spreads across more touchpoints—McKinsey’s B2B Pulse survey finds B2B buyers now use an average of 10 interaction channels in a purchase, up from five in 2016, and PunchOut consolidates the supplier relationship into the one channel procurement already trusts.

For suppliers, being available inside the buyer’s procurement system is increasingly the price of entry for institutional and enterprise accounts. With 77% of B2B buyers willing to spend $50,000 or more through remote and self-service channels, the suppliers who are easy to buy from inside procurement workflows are the ones who win the high-value accounts and keep them. That ease drives procurement adoption: when a supplier sits inside the buyer’s everyday workflow with the right catalog and pricing, buyers default to them and reorder without friction, rather than routing around them with manual purchase orders. PunchOut also surfaces a supplier’s live catalog and contract pricing at the moment of purchase, which supports order accuracy, repeat business, and account loyalty.

PunchOut on its own is a connection. What makes it valuable for serious B2B relationships is everything that travels through it.

A genuine procurement-driven experience means the catalog the buyer sees is their catalog: contract pricing specific to their account, the product range agreed in their contract, and the organizational structure that decides who can buy what. Approval workflows enforce spending limits—small orders cleared automatically, larger ones routed to a manager, the largest to finance. Because every order runs through the procurement system against the agreed contract, contract compliance is enforced by the workflow itself rather than checked after the fact, and every purchase stays traceable against the buyer’s policy.

The connector lets the buyer reach the catalog, but contract catalogs, account-specific pricing, role-based purchasing, and approval governance are what make that catalog usable for a large organization. Plenty of solutions can stand up PunchOut connectivity. The harder part—and the one that decides whether a large account actually adopts the channel—is supporting the operating model around the connector. A supplier that offers PunchOut without that operating model has solved the easy half of the problem.

This is why the operating model matters in practice: the buyers who run real volume through PunchOut are the ones with the most procurement complexity to absorb. Virto and OMNIA Partners power cooperative purchasing for more than 11,000 public agencies serving 94% of the U.S. population—a multi-party structure no bare connector could govern. Enterprises such as Bosch run procurement across multiple brands and countries, where account hierarchies, role-based access, and approval rules have to hold together at scale. In both cases, it’s the operating model around the connector doing the work.

👉 Read both case studies here: OMNIA Partners case study & B2B Loyalty Portal for 150K+ Users for Bosch: Case Study.

The most common worry is that PunchOut means another rebuild. It doesn’t have to.

Complexity is the normal condition of B2B procurement, not a sign something has gone wrong—multiple price lists, layered approvals, account-specific catalogs, and several procurement systems across a customer base are simply what enterprise buying looks like. The job of the commerce platform is to structure that complexity, not to push it into custom development or manual workarounds every time a new account comes on.

A well-designed setup preserves what’s already in place. The buyer’s ERP stays the system of record. Their procurement platform stays the purchasing environment. The supplier’s commerce platform supplies the catalog, the pricing logic, and the customer experience layer—and a managed integration gateway carries the messages between them. Nothing is ripped out; the commerce capability is added alongside the existing stack.

For Virto-powered suppliers, that gateway is Greenwing Technology. Virto partnered with Greenwing in 2025 to give sellers production-ready PunchOut, with more than 135 pre-built integrations to e-procurement platforms including Ariba, Coupa, Oracle, and Jaggaer. For enterprises and public-sector organizations with strict procurement requirements, it means connecting to institutional buyers without custom integration work for every account.

👉 If you’re evaluating PunchOut for a procurement-driven B2B business, the PunchOut catalog integration feature page covers how Virto supports the full operating model—contract catalogs, account pricing, approvals, and governance—and lets you book a demo.