Replatforming: Switch Shops, Keep Your PunchOut Connections | PunchCommerce                       ![](//analytics.punchcommerce.de/matomo.php?idsite=1&rec=1)

  [Skip to content](#main-content)

   Know-how · Gateway  Replatforming: PunchOut during a shop switch. The gateway keeps your customer connections stable.
===================================================================================================

 A new shop system is on the way, and ten corporate customers order via PunchOut from the old one. With PunchCommerce as the gateway, nothing changes for these customers: credentials, protocol, field mapping and the address their procurement system calls live in the gateway, not in the shop. You only reconnect the shop side, via plugin or API, and move customers one by one.

 [ Start free trial ](https://www.punchcommerce.de/register) [ Steps of the switch ](#wechsel)

30 days free · no credit card · cancel anytime

  changes in your customers’ procurement systems 0

 active PunchOut connections 500+

 shop systems with a ready-made plugin 9

 The problem

 Without a gateway, every customer connection is tied to the shop
------------------------------------------------------------------

In short

 When you switch shops, nothing changes for PunchOut customers if the connection runs through a gateway: PunchOut URL, credentials, protocol and field mapping live in PunchCommerce. Only the shop is reconnected, via plugin or REST API, customer by customer.

 For dealers and manufacturers, switching shops is routine: Shopware 5 is no longer maintained, the Magento installation is due for replacement, the custom build is to give way to a standard. It only gets difficult because of the PunchOut customers. Each of them has stored an address and credentials in their procurement system, and the connection was coordinated, tested and approved with each of them once.

 If the PunchOut logic sits in the shop, as a custom build or as a module that handles protocol and login itself, it moves with the switch. Then the address their system calls changes for your customers, often the credentials too, and the field mapping in the cart has to be re-checked against the new shop. With ten customers, that means ten rounds of coordination with ten procurement departments that have to schedule their IT for it.

 The result: shop projects get postponed because nobody wants to touch the connections, or the old shop keeps running for the PunchOut customers long after the new one is live. How a PunchOut works and what the customer stores in their system is explained on the page “[What is PunchOut?](https://www.punchcommerce.de/en/punchout)”.

### What has to be redone per customer when the connection lives in the shop

- a new PunchOut URL your customer has to enter in their procurement system
- new credentials, because login and validation lived in the old shop
- field mapping and additional fields that were tested against the old shop
- a test run with your customer’s IT, a separate appointment per customer
- with SAP Ariba, a new catalog version to be approved by procurement

### A worked example

 Ten PunchOut customers, each with a coordination call with the customer’s IT, a test run and an approval: that is ten procedures whose timing is set not by you but by your customer’s procurement. With a gateway, it is zero.

 The gateway principle

 The gateway sits between the procurement system and the shop
--------------------------------------------------------------

 PunchCommerce accepts the call from your customer’s procurement system, validates the credentials, logs the buyer into the shop and returns the cart via OCI (SAP standard) or cXML (Ariba standard). Everything your customer knows therefore lives in the gateway. The shop behind it is interchangeable.

Before and after the switch

  Your customers’ procurement systems

Call the PunchOut URL of PunchCommerce with the credentials you issued.

 SAP Ariba Coupa SAP S/4HANA Jaggaer Onventis

  stays unchanged

 ![PunchCommerce](https://www.punchcommerce.de/static/logo_punchcommerce.svg)Gateway: login, protocol, field mapping, cart return.

 OCI cXML IDS Connect

  stays unchanged

  Your shop: old one out, new one in

Connected to the gateway via plugin or REST API. The entry URL per customer points to the new shop.

 Shopware 5  Shopware 6 Magento JTL-Shop Spryker Vendure Medusa Custom build

  is reconnected

### What stays

 Your customer’s side

- the PunchOut URL your customer’s procurement system calls
- the credentials per customer: username and password with OCI, identities and SharedSecret with cXML
- the protocol per customer and the field mapping for the cart
- the catalog approval and the settings in your customer’s system
- the customer ID (uID) by which PunchCommerce recognizes the customer

### What changes

 Your side

- the plugin: installed in the new shop instead of the old one
- the entry URL per customer in PunchCommerce: points to the new shop
- the customer ID on the customer in the new shop: stored once
- a test run with the simulator in PunchCommerce, without your customer

 Which protocol your customer speaks also stays as it is when you switch. The details on login and cart are shown on the pages [OCI PunchOut](https://www.punchcommerce.de/en/oci-punchout) and [cXML PunchOut](https://www.punchcommerce.de/en/cxml-punchout).

 Steps of the switch

How to switch shops without touching a single customer
------------------------------------------------------

Six steps, all on your side. Because the entry URL is stored per customer in PunchCommerce, you move customers one by one and run the old and the new shop in parallel for as long as you like.

1. 1 You · new shop### Install the plugin

    Install the PunchCommerce plugin in the new shop system, for example from the Shopware Store, as a Magento extension or as an npm package for Vendure. For custom-built shops, use the REST API.
2. 2 You · new shop### Carry over the customer ID

    Create your PunchOut customers in the new shop and store the same customer ID (uID) per customer as in PunchCommerce. Range and prices per customer are maintained in the shop as before.
3. 3 You · PunchCommerce### Change the entry URL

    Enter the address of the new shop with the plugin’s path as the customer’s entry URL. Leave the customer’s mode, protocol and credentials unchanged.
4. 4 You · PunchCommerce### Check the field mapping

    The field mapping to your customer’s protocol stays in place. Check whether the new plugin delivers the same additional fields and the same classification your customer receives today.
5. 5 You · PunchCommerce### Test with the simulator

    Run the purchase and the cart return with the simulator in PunchCommerce before the first buyer sees the new shop. The cart must carry the same fields as before.
6. 6 Your customer### Nothing to do

    Your customer changes nothing in their procurement system: PunchOut URL, credentials and catalog approval remain valid. Tell them the date and ask for a test order.

 Who it is for

 For dealers and manufacturers with several PunchOut customers
---------------------------------------------------------------

 With a single PunchOut customer, the switch is a manageable appointment even without a gateway. The effort grows with every additional customer, because each brings their own procurement system, their own IT and their own approval process.

- ### Dealers with many corporate customers

    Ten or more PunchOut customers, each with their own range and their own prices. Every customer you do not have to touch during the switch saves a coordination call with their procurement and IT.
- ### Manufacturers with a framework agreement

    The corporate customer demanded the PunchOut catalog in a tender and approved it once. A new address or new credentials mean a new approval there. With the gateway, the existing one remains.
- ### Shop project in planning

    If you run Shopware 5, a custom build or a shop reaching end of life today and will switch in the next few years, connect your PunchOut customers through the gateway now rather than through the shop.

### Which shops have ready-made plugins

 Ready-made plugins exist for nine shop systems, including [PunchOut for Spryker](https://www.punchcommerce.de/en/spryker), [PunchOut for Shopware](https://www.punchcommerce.de/en/punchout-shopware), [PunchOut for Magento](https://www.punchcommerce.de/en/punchout-magento), [PunchOut for Vendure](https://www.punchcommerce.de/en/punchout-vendure), [PunchOut for JTL-Shop](https://www.punchcommerce.de/en/punchout-jtl) and [PunchOut for Medusa](https://www.punchcommerce.de/en/punchout-medusa). Other systems and custom builds are connected via the documented REST API. All options are shown in the overview [Integrations](https://www.punchcommerce.de/en/integrations).

 If a corporate customer requires guaranteed availability for the switch and someone who takes responsibility for operations, [PunchCommerce Enterprise](https://www.punchcommerce.de/en/enterprise) with an SLA is the right plan. What a PunchOut connection in your own shop would cost you is calculated on the page [Make or Buy](https://www.punchcommerce.de/en/punchout-make-or-buy).

 FAQ

Frequently asked questions about replatforming with PunchOut customers
----------------------------------------------------------------------

What dealers and manufacturers want to know before switching shops.

 ###   Does my customer have to change anything in their procurement system when I switch shops? +

 No. Their procurement system calls the PunchOut URL of PunchCommerce and logs in with the credentials you issued in PunchCommerce. Both stay the same when you switch shops, as do the protocol and the catalog approval in their system. Which shop PunchCommerce opens behind it is defined solely by the entry URL on your side.

###   Can I run the old and the new shop in parallel during the migration? +

 Yes. The entry URL is stored per customer. You move one customer to the new shop, test with them and leave the other customers in the old shop until you are confident. There is no need for a cut-over date for all customers.

###   I am moving from the Hosted Catalog to my own shop. Does this apply as well? +

 Yes. You switch the customer’s mode in PunchCommerce from Hosted Catalog to gateway and enter your shop’s entry URL. The customer’s credentials, protocol and field mapping stay in place. The reverse route, from the shop into the [Hosted Catalog](https://www.punchcommerce.de/en/hosted-catalog), works the same way.

###   My new shop is custom-built or a system without a plugin. What then? +

 Then you connect the shop to the gateway via the documented REST API. PunchCommerce continues to handle the protocols OCI, cXML and IDS Connect, the interface between trade software and wholesale shops; your shop exchanges only the buyer’s login and the cart with the gateway. All plugins, extensions and connection options are listed under [Integrations](https://www.punchcommerce.de/en/integrations).

###   Does the switch change the field mapping for my customers? +

 The field mapping to the protocol lives in PunchCommerce and stays. What may change are the fields the new shop delivers: additional fields, classification, units of measure. Check in the simulator whether the cart from the new shop carries the same values as before and remap fields where necessary.

###   What does the shop switch cost with PunchCommerce? +

 Nothing extra. PunchCommerce Business costs €49 per connected customer per month, plus VAT, regardless of which shop runs behind it or how often you switch. The plugins are free of charge. If you move from the Hosted Catalog to your own shop, the Hosted Catalog add-on (€50 per customer per month, plus VAT) no longer applies; in the other direction, it is added. 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

 Your next shop is coming. Your PunchOut customers will not notice.
--------------------------------------------------------------------

 €49 per customer per month, plus VAT, for OCI, cXML and IDS Connect. Setup in under an hour, shop switch without any change on the customer’s side, 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
