Buy Side vs. Sell Side: The Two Sides of PunchOut Explained | PunchCommerce                       ![](//analytics.punchcommerce.de/matomo.php?idsite=1&rec=1)

  [Skip to content](#main-content)

   Know-how · Basics  Buy side vs. sell side. Two worlds, one word: PunchOut.
=========================================================

 Your customer says “PunchOut” and means their procurement system’s ability to open external catalogs. You are asked to “deliver PunchOut” and mean an interface on your catalog. Both are right, because PunchOut has a buying side (buy side) and a supplier side (sell side). This page shows what each side does, which terms it uses and what you as a supplier actually have to deliver.

 [ Start free trial ](https://www.punchcommerce.de/register) [ Compare both sides ](#vergleich)

30 days free · no credit card · cancel anytime

  sides that both say “PunchOut” 2

 protocols the buy side dictates: OCI and cXML 2

 setup of the sell side per customer &lt; 1 h

 In short

 The buy side is procurement, the sell side is the supplier
------------------------------------------------------------

The answer

 The buy side is your customer’s procurement system: it opens your catalog, takes over the cart and runs approval and ordering. The sell side is your catalog: it accepts the call, logs the buyer in, shows their prices and returns the cart in the customer’s protocol. Together, the two make a PunchOut.

 The terms come from e-procurement: buy-side solutions are the systems companies buy with, sell-side solutions the systems suppliers sell with. A PunchOut connects one of each. The buyer punches out from their system into your catalog, puts items into the cart and brings it back; the whole cycle is explained on the page “[What is PunchOut?](https://www.punchcommerce.de/en/punchout)”.

 Misunderstandings arise because both sides use the same word for their half. When your customer writes that they have PunchOut “in use” and want to “connect” you, their half is done. What is missing is yours. Their system does not come with it, because a PunchOut catalog has to know your items, your prices and your credentials. The technical standards for this, OCI and cXML, are dictated by the buy side; the sell side delivers them.

### Buy side

 Your customer

- runs the procurement system, such as SAP Ariba, Coupa or SAP S/4HANA
- sets up your catalog as a supplier catalog and approves it for buyers
- dictates the protocol and controls approvals, cost centers and budget

### Sell side

 You as the supplier

- provides the catalog, as an online shop or as a Hosted Catalog without a shop
- speaks the customer’s protocol, OCI or cXML, and returns the cart
- issues credentials and maintains range and prices per customer

 Comparison

Buy side and sell side compared directly
----------------------------------------

The overview shows who does what in a PunchOut, who dictates what and where the line between the two sides runs. Everything left of the line is handled by your customer in their system; everything right of it is delivered by you.

  Comparison of buy side and sell side by criteria   Criterion Buy side (your customer) Sell side (you)     Who  Buy side (your customer) your customer’s procurement   Sell side (you) you as the supplier, manufacturer or dealer    System  Buy side (your customer) procurement system, such as SAP Ariba, Coupa, Jaggaer, Onventis or SAP S/4HANA   Sell side (you) your online shop with plugin or the Hosted Catalog, connected via PunchCommerce    Role in the PunchOut  Buy side (your customer) opens the catalog, takes over the cart, runs approval and ordering   Sell side (you) accepts the call, logs the buyer in, shows range and prices, returns the cart    Means by “PunchOut”  Buy side (your customer) the system’s function to integrate external catalogs   Sell side (you) the interface on the catalog that accepts the call and sends the cart back    Protocol  Buy side (your customer) dictates it: OCI (SAP standard) or cXML (Ariba standard), see [OCI vs. cXML](https://www.punchcommerce.de/en/oci-vs-cxml)   Sell side (you) delivers it: PunchCommerce speaks both in the same plan    Credentials  Buy side (your customer) enters them in the procurement system   Sell side (you) issues them per customer: username and password with OCI, identities and SharedSecret with cXML    Prices  Buy side (your customer) expects the terms agreed for their company   Sell side (you) stores range and prices per customer in the catalog    Approval and budget  Buy side (your customer) run in the procurement system: approval levels, cost centers, budget check   Sell side (you) not involved; the catalog only sees the cart    Purchase order  Buy side (your customer) creates it after approval and sends it as a cXML OrderRequest, email or EDI   Sell side (you) receives it, confirms and delivers; see [After the PunchOut](https://www.punchcommerce.de/en/punchout-order-flow)    Typical terms  Buy side (your customer) supplier catalog, catalog approval, supplier enablement, Level 1 and Level 2   Sell side (you) gateway, plugin, entry URL, field mapping, Hosted Catalog    Costs  Buy side (your customer) license of the procurement system; the terms for supplier catalogs are set by your customer’s contract with the vendor   Sell side (you) PunchCommerce Business: €49 per customer per month; without a shop plus the Hosted Catalog add-on, €50 per customer per month; both plus VAT    What PunchCommerce provides  Sell side the sell side: login, protocol, field mapping and cart return for your shop or the Hosted Catalog; the buy side stays with the customer

 Terms

 Who uses which terms and where misunderstandings arise
--------------------------------------------------------

 Your customer’s request comes in the language of their procurement system. Six phrases suppliers regularly misread, and what the buy side means by them.

### “We already have PunchOut.”

This means the buy side: the procurement system can open catalogs. Your sell side is still missing, because the system does not come with a catalog that knows your items and prices.

### “Send us your catalog.”

Can mean a catalog file, such as BMEcat or CIF, Ariba’s catalog file format, or a PunchOut catalog. Ask before you export; the difference is shown on the page [PunchOut vs. content catalog](https://www.punchcommerce.de/en/punchout-vs-content-catalog).

### “We need OCI.” / “We need cXML.”

The buy side names the protocol of its system. You do not have to decide, you deliver what is named. If the customer names none, the page [OCI vs. cXML](https://www.punchcommerce.de/en/oci-vs-cxml) helps.

### “Level 2 PunchOut”

A buy-side term from Ariba: the buyer searches in the procurement system and jumps directly to an item. For the sell side, this means an item index and a direct entry; see [Level 1 vs. Level 2](https://www.punchcommerce.de/en/punchout-level-1-vs-level-2).

### “Catalog approval” and “supplier enablement”

Steps on the buy side: procurement checks your catalog and releases it for its buyers. Until then, their buyers do not see your catalog, even if your sell side is ready. Allow time for this.

### “Supplier account” and “Ariba Network”

With SAP Ariba, the buy side runs a network in which you also need a supplier account; a free Standard Account is sufficient. With most other systems, the customer enters your data themselves.

 Which procurement system your customer uses and which protocol it speaks is shown in the overview of [procurement systems](https://www.punchcommerce.de/en/procurement-systems).

 Scope of delivery

 What you as a supplier actually have to deliver
-------------------------------------------------

 The sell side consists of six things. None of them is an IT project if a gateway handles login, protocol and cart return. What your customer contributes is listed alongside.

### What you deliver

 Sell side

- a catalog: your online shop with plugin or the Hosted Catalog without a shop
- per customer, the PunchOut URL and credentials for their procurement system
- the protocol their system expects: OCI or cXML
- range and prices per customer, as agreed
- the cart with part number, quantity, unit and price in the right format
- on request, commodity groups by ECLASS or UNSPSC and additional fields

### What your customer contributes

 Buy side

- the name of their procurement system and the protocol
- with cXML their identities, with Ariba the invitation to the SAP Business Network
- the entry of URL and credentials in their system
- the catalog approval for their buyers
- a test order with which both sides check the cart

### How PunchCommerce provides the sell side

 PunchCommerce accepts the call from your customer’s system, logs the buyer into your shop or the Hosted Catalog and returns the cart via [OCI PunchOut](https://www.punchcommerce.de/en/oci-punchout) or [cXML PunchOut](https://www.punchcommerce.de/en/cxml-punchout). You set up customers, credentials and range, usually in under an hour.

 Why your customer requires the sell side from you and what it does for you is shown on the page [PunchOut benefits for suppliers](https://www.punchcommerce.de/en/punchout-benefits-for-suppliers). If you switch shop systems later, the sell side stays unchanged for your customers; how that works is shown on the page [Replatforming with the gateway](https://www.punchcommerce.de/en/punchout-gateway-replatforming).

 FAQ

Frequently asked questions about buy side and sell side
-------------------------------------------------------

What suppliers ask when their customer talks about PunchOut and means something different from what they do.

 ###   Am I buy side or sell side? +

 If you sell items to companies that order through a procurement system, you are the sell side: you provide the PunchOut catalog. The buy side is your customer with their procurement system, such as SAP Ariba, Coupa or SAP S/4HANA. If you buy through such a system yourself, you are the buy side towards your suppliers; that changes nothing about the PunchOut connection to your customers.

###   My customer says they already have PunchOut. Why do I still have to do something? +

 Because they mean the buy side: their procurement system can open external catalogs and take over carts. The sell side, a catalog that accepts the call, logs the buyer in and returns the cart in the right format, does not come with their system. It runs on your side, because only you know your items, prices and credentials. What the connection does for you is shown on the page [PunchOut benefits for suppliers](https://www.punchcommerce.de/en/punchout-benefits-for-suppliers).

###   Who decides whether OCI or cXML is used? +

 The buy side. Your customer’s procurement system dictates the protocol: SAP SRM speaks OCI, SAP Ariba cXML, SAP S/4HANA, Coupa and Jaggaer both. You deliver what their system expects. The page [OCI vs. cXML](https://www.punchcommerce.de/en/oci-vs-cxml) shows which one it is; PunchCommerce provides both protocols in the same plan.

###   Do I need access to my customer’s procurement system? +

 As a rule, no. Your customer enters the PunchOut URL and credentials in their system and approves the catalog for their buyers; you never see their system from the inside. One exception is SAP Ariba: there you set up the PunchOut in your own supplier account in the SAP Business Network; a free Standard Account is sufficient. The details are shown on the page [PunchOut for SAP Ariba](https://www.punchcommerce.de/en/punchout-sap-ariba).

###   Can I use the same sell side for several customers? +

 Yes. One PunchOut catalog serves any number of buy sides. For each customer, you define credentials, protocol, range and prices in PunchCommerce; the catalog recognizes from the login which customer is buying. Your shop or your Hosted Catalog stays the same.

###   What does the sell side cost with PunchCommerce? +

 PunchCommerce Business costs €49 per connected customer per month, plus VAT, and can be tested free of charge for 30 days. Without your own shop, the Hosted Catalog add-on is added at €50 per customer per month, also plus VAT. If your customer requires guaranteed availability with an SLA, [PunchCommerce Enterprise](https://www.punchcommerce.de/en/enterprise) is the right plan. All features at a glance: [Compare plans and pricing](https://www.punchcommerce.de/en/features-and-pricing).

  Get started

 The buy side is at your customer. You deliver the sell side.
--------------------------------------------------------------

 €49 per customer per month, plus VAT; without your own shop plus the Hosted Catalog add-on, €50 per customer per month. Setup in under an hour, GDPR-compliant hosting in Germany.

 [ Start free trial ](https://www.punchcommerce.de/register)30 days free · no credit card · cancel anytime

 ![Patrick Dornbusch, founder of PunchCommerce](https://www.punchcommerce.de/static/patrick-dornbusch.webp)Patrick Dornbusch

Founder of PunchCommerce

Prefer to talk first? In 30 minutes we’ll work out which option suits your shop, your ERP and your customers’ procurement systems.

 [ Schedule a consultation  (opens in a new window) ](https://account.netzdirektion.de/appointments/punchcommerce)30 min · remote · with the founder

 PunchCommerce® is a product of [ ![netzdirektion | Gesellschaft für digitale Wertarbeit mbH](https://www.punchcommerce.de/static/netzdirektion-logo.png) (opens in a new window) ](https://netzdirektion.de) ![DEKRA seal: quality management according to ISO 9001](https://www.punchcommerce.de/static/dekra-netzdirektion-iso-9001.png) **ISO 9001:2015**
certified quality management

 netzdirektion | Gesellschaft für digitale Wertarbeit mbH · © 2020 - 2026
