Punchout Catalogs for Shopify B2B: cXML, OCI, and When Canadian Suppliers Need One

01. What a Punchout Catalog Actually Is

Most B2B ecommerce assumes the buyer logs into your site, picks products, and checks out. In a punchout, the buyer never starts at your site. They start inside their company's procurement system, click your name in a list of approved suppliers, and get dropped into your store. When they finish, the cart does not check out with you. It goes back to their system as a requisition, which follows their approval chain and becomes a purchase order.

For a supplier, that means you sell through the buyer's front door instead of your own. The buyer's finance and compliance teams like it because every purchase stays inside their controls. You like it because the buyer sees your live catalog, stock, and contract pricing instead of a stale PDF or a spreadsheet upload.

Here is the quick comparison of the ordering channels a Canadian manufacturer or wholesaler usually weighs.

Why it matters: Punchout is a sales channel decision, not an IT project. It matters when your biggest buyers will only buy from suppliers that live inside their procurement platform.

02. How a Punchout Session Works, Step by Step

1. 1. Setup request. The buyer clicks your supplier tile in Coupa, SAP Ariba, Jaggaer, or a similar system, which sends a secure setup request to your store with their credentials.
2. 2. Authentication and session. Your store verifies the request, matches it to a company account, and opens a shopping session with that buyer's catalog and contract pricing.
3. 3. Shopping. The buyer browses and builds a cart, with live availability, units of measure, and their negotiated prices.
4. 4. Return of the cart. Instead of paying, the buyer clicks transfer. The cart goes back to their procurement system as a cXML message or an OCI form post.
5. 5. Approval and purchase order. The requisition moves through the buyer's approvals and becomes a purchase order sent to you, often by EDI, cXML, or email.

Nothing in this flow requires the buyer to create a login on your website or learn a new interface, which is exactly why large buyers prefer it.

Why it matters: Every step after step 3 happens in the buyer's system, so your job is to make the cart that comes back clean: right SKUs, right units, right prices.

03. cXML vs OCI: Which Protocol Do You Need?

There are two protocols in common use. cXML, created by Ariba, is the more widely supported and is used across Coupa, SAP Ariba, Jaggaer, and others. OCI, the Open Catalog Interface from SAP, is simpler on paper, but it is mostly required by buyers running SAP procurement. Industry commentary in 2026 describes the standards themselves as stable, with buyer expectations rather than the protocols changing.

Plan on supporting what your first two or three target buyers actually use, not every protocol in theory.

Why it matters: Choosing a protocol by buyer, not by preference, keeps the project small and avoids paying for connections nobody will use.

04. Where Shopify Fits: Native Features and What Needs an App

Shopify B2B gives you the data a punchout needs: company accounts, catalogs, price lists, quantity rules, and payment terms. We have not found native cXML or OCI punchout in Shopify itself, so you should confirm against Shopify's current documentation. In practice, suppliers add punchout through a third-party Shopify app or a gateway that translates between the procurement system and the store. Several such apps exist, with different protocol coverage, setup fees, and monthly pricing, so compare them against the platforms your buyers use.

• Native: company accounts, customer specific catalogs, price lists, quantity rules, and net payment terms that a punchout session reads from.
• Usually an app or gateway: the cXML or OCI handshake, buyer authentication, and returning the cart to the procurement system.
• Usually custom work: mapping your SKUs, units of measure, and contract prices to the buyer's item codes so the returned cart matches their catalog.

If you are still deciding how far native features take you, start with what Shopify B2B includes and the limits of Shopify B2B without Plus.

Why it matters: The punchout connection is the easy part. The value comes from having clean company, catalog, and pricing data underneath it.

05. Do You Actually Need Punchout? A Readiness Check

Punchout is worth building when it unlocks revenue you cannot get otherwise. Ask these questions first.

1. 1. Has a buyer asked for it? Universities, health authorities, municipalities, and large corporates often require it before they will add you as a supplier.
2. 2. How much volume sits behind the request? One large account can justify the build. Several vague mentions usually cannot.
3. 3. Is your catalog data clean? Consistent SKUs, units of measure, and contract pricing are required. If those are messy, fix them first with a PIM approach.
4. 4. What happens after the purchase order? Plan the order intake, invoicing, and order to cash automation so punchout orders do not require manual re-keying.
5. 5. Is a portal enough? If buyers will log into a self-serve wholesale portal, you may not need punchout at all.

Why it matters: Building punchout for a buyer who would have used your portal is wasted effort. Building it for the buyer who cannot use anything else is a revenue decision.

06. AI Procurement Agents and Why This Is Trending

Punchout is a decades old idea, but it is getting new attention as buying becomes more automated. Buyers are adopting AI assisted procurement that reads supplier data and reorders on its own, and those systems favour suppliers with a machine readable connection over a PDF. We cover that shift in our guide to AI procurement agents and what B2B suppliers need to be ready. A punchout, an API, or EDI feed are the three practical ways to be readable to a buyer's automation.

Why it matters: Structured, connected catalog data is becoming a requirement to be considered, not a nice to have.

07. Key Takeaways

• A punchout catalog lets a buyer shop your live catalog from inside their procurement system, then returns the cart as a requisition for their normal approvals.
• cXML is the most widely supported protocol, and OCI is mostly needed for SAP based buyers. Choose by what your actual buyers use.
• We have not found native cXML or OCI punchout in Shopify B2B, so plan on a third-party app or gateway, built on top of Shopify's native companies, catalogs, price lists, and payment terms.
• Clean SKUs, units of measure, and contract pricing decide whether the returned cart is accepted, so fix catalog data before the connection.
• Build punchout when a specific buyer or group of buyers requires it. If a self-serve portal covers your accounts, you may not need it.

08. Frequently Asked Questions