A punchout catalog is a supplier's online catalog that a business buyer opens from inside their own procurement system, such as SAP Ariba, Coupa or SAP SRM. The buyer clicks the supplier, lands on the supplier's site with their contract range and prices, fills a cart, and the cart goes back to the procurement system as a purchase requisition instead of an order. Approval and the purchase order then follow the buyer's own rules.
The opposite is a hosted catalog: the supplier uploads a file (CIF, BMEcat or a buyer's spreadsheet template) and the products live inside the buyer's system. Punchout keeps the product data on the supplier's side, which suits large or configurable ranges and frequent price changes. Both routes depend on the same thing: article numbers, units, prices and classification codes that a procurement system can read without someone retyping them.
Punchout or hosted catalog: where the product data lives
The choice is mostly about who maintains the catalog and how often it changes. With punchout, the buyer's system stores only a link and credentials; everything the buyer sees comes from the supplier's site at the moment they shop. With a hosted catalog, the buyer's system stores a copy that is only as current as the last upload.
Punchout and hosted catalog formats compared
| cXML punchout | Live session | Supplier's website | Contract prices at the moment of shopping | SAP Ariba, Coupa and other cXML procurement systems |
|---|---|---|---|---|
| OCI punchout | Live session | Supplier's website | Same, returned as NEW_ITEM fields | SAP-based purchasing (SRM) |
| CIF file | Hosted catalog | Buyer's procurement system | Fixed until the next upload | Static catalogs in cXML-based systems |
| BMEcat file | Hosted catalog or data exchange | Buyer's system or a wholesaler's PIM | In the file, per article | Manufacturer to wholesaler exchange, often with ETIM features |
| Buyer's spreadsheet template | Hosted catalog | Buyer's system | Fixed until the next upload | Smaller buyers without punchout |
Many suppliers run both. A distributor of electrical parts might offer punchout to its largest accounts, send BMEcat files to wholesalers, and fill a spreadsheet template for a municipality that buys twice a year. Each output reads from the same product record, which is why the data model matters more than the protocol.
A punchout session, message by message
The cXML Getting Started guide describes procurement punchout as live, interactive catalogs on a website: the procurement application shows a button instead of product details, and the user's browser opens the supplier's pages. The supplier's site needs three things: a URL that accepts the setup request, a way to recognize the buyer, and a checkout button that sends the cart back instead of taking payment.
One cXML punchout session from click to purchase order
- Setup request. The procurement system posts a PunchOutSetupRequest with the buyer's credentials and a shared secret, plus a BuyerCookie and a BrowserFormPost URL to return the cart to.
- Setup response. The supplier checks the credentials and answers with a StartPage URL, usually a session-specific login link to its catalog.
- Shopping. The buyer browses the contract range, configures products and fills a cart on the supplier's site.
- Cart return. At checkout the site posts a PunchOutOrderMessage as a hidden form field to the BrowserFormPost URL. Each line is an ItemIn with part number, price, description, unit of measure and classification.
- Approval. The cart becomes a requisition and goes through the buyer's approval workflow. Nothing is ordered yet.
- Purchase order. Once approved, the procurement system sends an OrderRequest to the supplier, which is the actual order to fulfil.
The cXML Reference Guide defines three session types in the operation attribute: create, edit and inspect. Edit lets a buyer reopen a cart they returned earlier, and inspect shows it read-only. The supplier can store its own reference, such as a quote number, in SupplierPartAuxiliaryID, and the procurement system passes it back in later sessions and in the purchase order.
cXML or OCI: two protocols for the same round trip
cXML (commerce XML) is the protocol behind SAP Ariba and Coupa punchout. The setup request and the returned cart are XML documents, and the same family of documents covers purchase orders, order confirmations, ship notices and invoices. That is why buyers on cXML systems often ask a punchout supplier to accept cXML purchase orders too.
OCI (SAP's Open Catalog Interface) is simpler. The buyer's system opens the supplier's URL with login parameters and a HOOK_URL, the return address for the cart. The cart comes back as an HTML form of numbered fields. The Unite OCI technical information lists the fields it sends automatically: NEW_ITEM-EXT_PRODUCT_ID, NEW_ITEM-PRICE, NEW_ITEM-PRICEUNIT, NEW_ITEM-QUANTITY, NEW_ITEM-UNIT, NEW_ITEM-DESCRIPTION, NEW_ITEM-LONGTEXT, NEW_ITEM-CURRENCY and NEW_ITEM-LEADTIME in days. It notes that OCI fields are generally cut off at 255 characters.
The receiving SAP system can be stricter. In 2BA's OCI field mapping for SAP SRM, NEW_ITEM-DESCRIPTION holds 40 characters, NEW_ITEM-UNIT 3 and NEW_ITEM-MATGROUP, the buyer's material group, 10. A webshop title of 90 characters arrives in the requisition as its first 40, so a supplier needs a short name written for that field.
Level 1 and level 2 punchout
In a level 1 punchout the buyer's catalog shows one entry for the supplier. The buyer clicks it, lands on the supplier's home page and searches there as they would in any webshop. SAP's training on punchout catalogs notes that even level 1 needs a small static index file, typically a single comma-separated line, uploaded to the SAP Business Network. It is the easiest level to set up, but the buyer has to know which supplier sells the item before they start.
In a level 2 punchout the supplier uploads a CIF-like index with a line for each SKU. The buyer's catalog search then shows those items like a hosted catalog, and a click punches out straight to that item or category on the supplier's site. If the index carries prices, SAP points out that the current price on the supplier's site may differ, so the live session stays the price that counts. The index is one more file to keep in sync with the live site, so ask each buyer which level their setup expects.
The product data a punchout cart carries back
The buyer's procurement team never sees the supplier's product page again after checkout. What lands in the requisition, the approval mail and the purchase order is a handful of fields, and each has to make sense on its own. The example below follows one illustrative product, a black cable tie sold in bags of 100, through both protocols.
One cable tie in a punchout cart
| Supplier article number | ART-88401 | SupplierPartID | NEW_ITEM-VENDORMAT or EXT_PRODUCT_ID |
|---|---|---|---|
| Short name | Cable tie 4.8 x 300 mm black | Description / ShortName | NEW_ITEM-DESCRIPTION |
| Long description | UV-resistant polyamide 6.6 cable tie for outdoor bundling | Description text | NEW_ITEM-LONGTEXT |
| Unit of measure | Piece (EA or PCE, from the buyer's list) | UnitOfMeasure | NEW_ITEM-UNIT |
| Price and price basis | EUR 12.40 per 100 pieces | UnitPrice + PriceBasisQuantity | NEW_ITEM-PRICE + NEW_ITEM-PRICEUNIT |
| Classification | UNSPSC or ECLASS code | Classification domain | NEW_ITEM-MATGROUP (buyer's group) |
| Manufacturer and part number | Brand name, manufacturer article number | ManufacturerName, ManufacturerPartID | Custom NEW_ITEM field |
| Lead time | 3 days | LeadTime (days) | NEW_ITEM-LEADTIME (days) |
Three fields cause most failed or confusing carts:
- Units of measure. Coupa's cXML supplier enablement steps tell buyers to request the supplier's units of measure up front, because a cart with a unit that does not exist in Coupa fails to come in. Map every sales unit on your site (piece, bag, box, meter, roll) to the codes each buyer uses before go-live.
- Price basis. A price per 100 or per meter has to travel with its quantity. cXML has PriceBasisQuantity for this and OCI has NEW_ITEM-PRICEUNIT. Without it, the requisition shows a price 100 times too high or a quantity 100 times too low.
- Classification. Buyers report spend by category, so the cart carries a code such as a UNSPSC commodity code in cXML, or the buyer's own material group in OCI. Some industrial buyers use ECLASS instead. Ask each buyer which system and version they expect.
Pack sizes, minimum order quantities and lead times also show up later when a buyer compares your cart with another supplier's quote. The request for quote guide lists the fields buyers need to compare offers on equal terms.
Hosted catalog files: CIF and BMEcat
When a buyer does not support punchout for your account, or wants every item searchable in its own system, you send a file instead. The cXML Getting Started guide shows a CIF 3.0 example: a header with CIF_I_V3.0, CODEFORMAT: UNSPSC, the currency and an item count, then one comma-separated line per item with supplier ID, part number, description, classification code, price and unit (EA). The classification column is not optional; the header declares which code system it uses.
BMEcat is an XML standard for exchanging catalog data in B2B, maintained by the German purchasing association BME; its BMEcat page names 2005.2 as the current version. A BMEcat article carries the order unit, content unit, price details and images, and its feature block can describe the product against a classification such as ETIM, with ETIM codes for every feature, value and unit. A wholesaler that works with ETIM can take those features into its own system as structured attributes, without mapping each one.
Hosted files and punchout are not either/or. A level 2 punchout index is itself a small hosted catalog, and many buyers who punch out for ordering still want a full catalog file for their category managers. If you also sell through B2B marketplaces, the same article data travels there too; the B2B marketplace guide covers what those channels ask for.
Does your business need punchout?
Punchout is a sales channel to procurement departments, so the question is whether your buyers ask for it. A short test:
- You likely need it when large customers buy through SAP Ariba, Coupa or SAP and tell you that suppliers without a catalog connection lose preferred status, or when your range is large, configurable or changes price often.
- A hosted file is enough when a buyer orders a stable range of a few hundred items a few times a year, or asks only for a CIF, BMEcat or spreadsheet upload.
- Neither yet when customers order by email or through your B2B webshop and nobody has asked. Clean article data first; the protocol can follow.
Most webshop platforms do not speak cXML or OCI out of the box. Suppliers usually add punchout through an app, extension or a punchout integration service that sits between the procurement systems and the shop. On Shopify, several apps in the Shopify App Store add cXML or OCI punchout, and some of them work from the B2B company catalogs described in the Shopify B2B guide. Whichever route you choose, the service reads products, prices and units from your shop, so gaps in the shop's data become gaps in every buyer's requisition.
Onboarding one buyer: credentials, test and production
Each punchout customer is a small project of its own. Coupa's enablement steps give a typical order: the buyer confirms you support punchout and cXML, holds a scoping call, sends a supplier questionnaire, collects your cXML credentials, and sets up punchout only after your supplier record and contract exist in their system. Testing runs against test credentials first; production uses a separate set you provide.
On your side, that means three things per buyer:
- Identity and secret. The domain and identity the buyer sends in the setup request, and the shared secret you agree on, so your site knows which account, assortment and price list to show.
- Assortment and prices. Which products this buyer may see and at which contract prices. List prices in a contract session defeat the point of punchout.
- Code lists. The buyer's units of measure, classification system and any extra fields they want returned, such as a cost center or a contract number.
Plan the first test order as a full round trip: setup, cart, approval and the purchase order arriving in your order system. Most problems only show at the last step, when the order line has to match an article you can ship.
Seven punchout data checks before the first buyer connects
Punchout catalog readiness checks
Keeping punchout and catalog files on one product record
WISEPIM is not a punchout platform: it has no cXML or OCI endpoint and does not receive carts or purchase orders. What it does is keep the article data that punchout and hosted catalogs read from complete and consistent. Feed Hub exports BMEcat 2005 files with ETIM feature blocks, order units and one price per article, for products whose family is linked to an ETIM class, and its XML import reads a supplier's BMEcat with the ETIM features already attached. Product classification maps product families to ETIM classes and GS1 GPC bricks; a UNSPSC or ECLASS code can live in an ordinary attribute and travel to any channel that maps it.
The punchout service on your webshop then reads short names, units, prices and codes that were checked once, in one place, instead of being fixed per buyer during each onboarding.

