What Is a PunchOut Catalog? A Simple Guide for Business Central Users

If you work in procurement and use Microsoft Dynamics 365 Business Central, you've probably heard the term “PunchOut catalog” (sometimes written as “Punch-Out” or “Punchout”). It's a technology that has been around since the early 2000s, but it's often misunderstood — especially by teams that are new to procurement automation.

In this guide, we explain what a PunchOut catalog is, how it works, what its limitations are, and how modern AI-based alternatives are changing the game for Business Central users.

PunchOut Catalogs: The Basics

A PunchOut catalog is a protocol that lets a buyer “punch out” from their procurement system (like Business Central) to a supplier's e-commerce website. The buyer browses and shops on the supplier's site, adds items to a cart, and then “checks out” — but instead of completing a purchase on the supplier's site, the cart data is sent back to the procurement system as a purchase requisition.

The idea is elegant: the buyer gets to use the supplier's full product catalog with real-time pricing and availability, while the procurement system captures the order data automatically — no manual re-entry.

How Traditional PunchOut Works: cXML and OCI

PunchOut catalogs use one of two communication protocols:

• cXML (Commerce eXtensible Markup Language): The most common PunchOut standard, developed by Ariba (now SAP Ariba). cXML defines how the buyer's system initiates a PunchOut session, how the buyer browses the supplier's site, and how the cart data is returned as a cXML document.
• OCI (Open Catalog Interface): An alternative standard developed by SAP. OCI works similarly to cXML but uses a different message format. It's more common in SAP environments but is also supported by some Business Central integrations.

The typical PunchOut flow looks like this:

1. The buyer clicks a “PunchOut” button in their procurement system.
2. The system sends a PunchOut Setup Request (cXML) to the supplier's website.
3. The supplier's website opens in the buyer's browser with authenticated pricing.
4. The buyer shops, adds items to cart.
5. The buyer clicks “Return to Requisition” (or similar).
6. The supplier's site sends a PunchOut Order Message (cXML) back to the procurement system with the cart contents.
7. The procurement system creates a requisition from the cart data.

Why PunchOut Catalogs Exist

Before PunchOut, procurement teams had two options for ordering from suppliers: either use a static catalog (uploaded as a CSV or maintained manually in the ERP) or place orders outside the ERP entirely and re-enter the data by hand. Both options had serious problems — static catalogs went stale quickly, and manual entry was slow and error-prone.

PunchOut catalogs solved both problems by giving buyers access to the supplier's live catalog while keeping the data flow inside the procurement system. For large enterprises buying from major suppliers, PunchOut became a standard part of the procurement stack.

The Limitations of Traditional PunchOut

Despite its elegance, traditional PunchOut has significant limitations — especially for mid-market companies using Business Central:

1. Per-supplier integration

Every PunchOut connection requires a technical integration between your procurement system and the supplier's e-commerce platform. The supplier must support cXML or OCI, and both sides must configure endpoints, authentication credentials, and data mappings. This typically costs CHF 1'000-5'000 per supplier and takes weeks to months.

2. Supplier cooperation required

PunchOut only works if the supplier supports it. Many small and medium suppliers don't offer PunchOut — they don't have the technical infrastructure or the business case to build it. This means PunchOut covers only a fraction of your supplier base, usually the largest 5-10 suppliers.

3. Limited Business Central support

PunchOut was designed primarily for SAP Ariba, Coupa, and other enterprise procurement platforms. Business Central has limited native PunchOut support. While third-party connectors exist, they add cost and complexity.

4. Maintenance burden

PunchOut connections break. Suppliers change their cXML endpoints, update their platforms, or modify their catalog structures. Each change requires someone to troubleshoot and update the integration. For companies with 10+ PunchOut connections, this becomes an ongoing maintenance headache.

The AI Alternative: Cart Capture Without Integration

What if you could get the benefits of PunchOut — browsing supplier websites and automatically transferring cart data to BC — without any per-supplier integration?

That's exactly what AI-based cart capture does. Instead of relying on cXML protocols and supplier cooperation, AI reads the supplier's cart page directly — the same way a human procurement officer would — and extracts the product names, SKUs, quantities, prices, and currency.

Zentriq PunchOut is a Chrome extension that implements this approach. Here's how it works:

1. Browse any supplier website and add items to your cart — just like normal shopping.
2. Click the Zentriq PunchOut icon in your Chrome toolbar.
3. AI reads the cart page and extracts all line items with their details.
4. Review the extracted data in the extension popup.
5. Click “Send to BC” — and Requisition Worksheet lines are created in Business Central automatically.

The entire process takes under 30 seconds, works on any supplier website (no integration needed), and requires zero technical setup from the supplier.

PunchOut vs AI Cart Capture: Side-by-Side

• Supplier coverage: Traditional PunchOut works only with integrated suppliers. AI cart capture works on any website.
• Setup time: PunchOut takes weeks per supplier. AI cart capture is ready instantly.
• Cost per supplier: PunchOut costs CHF 1'000-5'000 per supplier. AI cart capture has zero per-supplier cost.
• Maintenance: PunchOut requires ongoing technical maintenance. AI cart capture adapts to website changes automatically.
• Accuracy: Both approaches deliver high accuracy. PunchOut uses structured data (cXML), while AI cart capture uses visual understanding of the page.
• Business Central integration: PunchOut requires a BC connector. AI cart capture integrates via the BC API natively.

When Traditional PunchOut Still Makes Sense

Traditional PunchOut isn't dead. For very large enterprises with a small number of high-volume suppliers, a dedicated cXML PunchOut connection can offer advantages like negotiated pricing tiers, contract compliance enforcement, and deep catalog integration. If you order millions per year from a single supplier, the ROI on a PunchOut connection is clear.

But for mid-market companies that buy from dozens or hundreds of suppliers — most of which don't offer PunchOut — AI cart capture is a far more practical solution. It covers your entire supplier base on day one.

Think of it this way: traditional PunchOut is like building a private highway to each supplier. AI cart capture is like having a car that drives on any road. You don't need a private highway when the AI can navigate any route.

Getting Started

If you're a Business Central user looking to automate procurement without the complexity of traditional PunchOut, AI cart capture is the fastest path to results. Zentriq PunchOut installs in minutes, works on any supplier website, and starts saving time from day one.

Start free with Zentriq or request a demo to see AI cart capture in action.