![\"open](\"https:\/\/windmuehlenbauer.com\/wp-content\/uploads\/2024\/04\/OCI-begriff_230px.png\")
<\/figure>\n<\/div>\n\n\n\n![\"cxml](\"https:\/\/windmuehlenbauer.com\/wp-content\/uploads\/2024\/04\/cxml-begriff_230px.png\")
<\/figure>\n<\/div>\n<\/div>\n\nWhat does the punch-out process look like in concrete terms?<\/h2>\n\n
Your customer’s employee logs into their purchasing system. There he selects the relevant Punchout catalog. This automatically redirects the employee and logs them in. In this “catalog”, the employee searches for the desired items and places them in the shopping cart. The interface is usually similar to the supplier’s online store. <\/p>\n\n
Once the shopping basket has been sent, it is forwarded back to the purchasing system. There, the employee can adjust the order or add accounting information (e.g. the cost center). Once the order information has been confirmed in the purchasing system, the process of approval by the cost center manager or supervisor begins. After approval, the supplier receives the final purchase order. This workflow is shown in the following image. <\/p>\n\n There are two standards on the market. The cXML standard is mainly found in systems originating from American regions. The OCI standard is widely used in European systems. All relevant purchasing systems such as e-marketplaces<\/a>, e-procurement systems<\/a> or ERP systems<\/a> can process punchout catalogs. You can find a brief overview here: <\/p>\n\n Systems that use the cXML punchout catalog:<\/p>\n\n Systems that use the OCI punchout catalog:<\/p>\n\n As a rule, your customer has two catalog types that they can integrate into their purchasing system. Static catalogs can be integrated. There are formats such as BMEcat<\/a>, Datanorm<\/a> or Excel templates. I like to compare these with stone tablets. Because every time a change is made, a new sheet has to be created and sent to the customer. <\/p>\n\n Dynamic catalogs, on the other hand, update the data in a matter of seconds and reduce the maintenance effort through automation. These include the punchout catalogs presented above. The following table shows the advantages and disadvantages of this type of catalog. There are other functions that reduce the disadvantages. These must be technically mastered and strategically desired by both the supplier and the customer system. <\/p>\n\n To integrate external catalogs into the purchasing system, you need an online store or website or an external solution (e.g. Primus Shop) with the appropriate interface. Depending on the purchasing system, a cXML or OCI interface must be implemented. <\/p>\n\n As a first step, I recommend clarifying the commercial details with your customer, such as prices, product range, leading purchasing system and locations or departments authorized to place orders.<\/p>\n\n On this basis, the punchout catalog can be configured on the supplier side in the second step. Important information such as URL, user or password or shared secret is shared with the contact person of the customer system. This can be a service provider, the customer themselves or the provider of the purchasing system. <\/p>\n\n In the third step, the integration of the Punchout catalog is implemented and tested. After the successful test, live operation begins. In the optional fourth step, the ordering process for the order and subsequent processes such as goods receipt and invoicing are discussed. This step offers great potential for automation using EDI. You can find details on this process automation in the article “What is EDI?”.<\/a> <\/p>\n\n Punchout catalogs have many advantages. Manual updating of data and prices is no longer necessary, as this has already been done in your ERP system (merchandise management system). The customer can view stock levels and order configurable items. As a supplier, this type of catalog is particularly useful for regular changes to Product Data, prices or stock levels. No team is required to create catalogs and upload them to the customer. Unlike static catalogs, no customer approval is required. This saves you time as a supplier, as all order-relevant information is identical in the customer system and your ERP system. This eliminates the need for price differences, ordering “old” items or last-minute appointment requests from your customer. <\/p>\n\n In addition to the many advantages, dynamic catalogs also have a few disadvantages for the customer. Therefore, it depends on the strategic position and your goal as a supplier. In my experience, it is possible to convince the customer of Punchout catalogs in the medium term. At the latest when the lack of comparability in the purchasing system is restored with OCI Backgroundsearch or Punchout Level 2. <\/p>\n\n Punchout catalogs qualify you for customers who require Punchout-capable suppliers and increase your reputation with your customers!<\/strong><\/p>\n\n Peter Pr\u00fctting is an expert in value-oriented and digital business development. With over 15 years of sales experience from the perspectives of wholesale, manufacturing, and e-marketplaces, he takes a holistic view. His colleagues value him as a customer-centric and focused leader who guides teams through digital transformation. Away from his daily work, he recharges his batteries by mountain biking. <\/p>\n<\/div>\n<\/div>\n\n Looking for a punchout catalog?<\/p>\n\n\n\n We help you find the right solution and implement it quickly.<\/p>\n\n\n\n![\"\"](\"https:\/\/windmuehlenbauer.com\/wp-content\/uploads\/2024\/04\/punchout-catalog-process_495px.jpg\")
Which systems can interact with Punchout catalogs?<\/h2>\n\n
\n
\n
Advantages and disadvantages of Punchout catalogs <\/h2>\n\n
![\"electronic](\"https:\/\/windmuehlenbauer.com\/wp-content\/uploads\/2024\/04\/statische-kataloge-bmecat-excel-template_495px.jpg\")
<\/figure>\n\nFeature<\/th> Static catalog (e.g. BMEcat)<\/th> Dynamic catalog (e.g. OCI, cXML)<\/th><\/tr><\/thead> Data sovereignty<\/td> Customer<\/td> Supplier<\/td><\/tr> Narrow down the range<\/td> ✅<\/td> ✅<\/td><\/tr> Comparability and searchability in the purchasing system<\/td> ✅<\/td> ❌ (with the exception of the background search of OCI or level 2 for cXML)<\/td><\/tr> Article configuration<\/td> ❌ Only possible with effort<\/td> ✅<\/td><\/tr> Controlled price approval by the customer<\/td> ✅<\/td> ❌<\/td><\/tr> Indication of stock levels<\/td> ❌<\/td> ✅<\/td><\/tr> Up-to-dateness of prices, descriptions etc.<\/td> After upload and approval by the customer<\/td> Always up to date<\/td><\/tr> User interface<\/td> In the customer’s design<\/td> In the supplier’s design<\/td><\/tr> Menu and article structure<\/td> In customer logic<\/td> In supplier logic<\/td><\/tr> Order is sent via the customer system<\/td> ✅<\/td> ✅<\/td><\/tr> Goods receipt and invoice are posted in the customer system<\/td> ✅<\/td> ✅<\/td><\/tr><\/tbody><\/table><\/figure>\n\n How does onboarding work?<\/h2>\n\n
My conclusion<\/h2>\n\n
![\"Expert](\"https:\/\/windmuehlenbauer.com\/wp-content\/uploads\/2025\/09\/peter-pruetting-experte-procurement-ecommerce_blau_600px.png\")
<\/figure>\n<\/div>\n\n\n\n