No. With Shopspray Punchout you are using your existing commerce solution and product catalog. You are simply punchout-enabling your existing commerce solution and getting a direct, safe and real-time order data transfer channel for purchase requisitions/orders between your customers ERP/eprocurement system and your commerce platform. Get a demo
EDI: is the electronic transmission of structured data by agreed message standards from one computer system to another without any human intervention. Hence, EDI is simply the transfer of information from server to server, ideal for automating recurring standardized transactions and is not to compare with modern ecommerce experiences.
Punchout or punchout catalog: Based on the standard protocols OCI (from SAP) and latest cXML (commerce XML) a punchout session gives buyer and seller the ability to transfer order data between an ERP or eprocurement system and a digitized product catalog on a server (punching out of one system and into another). Earlier versions of punchout are utilizing distributed or intermediate product catalogs, placed on a 3rd party server environment, in order to provide the needed order data and make the connections between buyer and seller.
Commerce punchout: A more modern version of punchout, based on the same punchout protocols (OCI and cXML) but where the intermediate catalog is replaced by a direct connection between buyers ERP/eprocurement system and sellers commerce platform and hence provides a true modern, real-time, commerce ordering experience that utilizes all the business logic and rules (with regards to users, assortment, product information, prices, campaigns, etc.) in the sellers commerce platform for personalized ordering. Shopspray is a commerce punchout add-on, since we are punchout enabling commerce platforms with no need for intermediate punchout catalogs. Get a demo
The Shopspray Punchout Add-on is – when installed – a native part of your commerce stack. Our product gives you punchout capabilities within the commerce editor framework/dashboard and is leveraging on all your commerce-, personalization- and visitor group rules. As such you are able to utilize all the great features of your commerce stack in a punchout context and punchout-enable your customers directly using the existing commerce editor interface. Get a demo
Since we are committed to the cXML and OCI standards, the Shopspray Punchout add-on supports a wide array of procurement solutions. Your purchasers procurement solution is never a problem with Shopspray Punchout. We support: SAP, SAP Ariba, Coupa, Dynamics 365, Dynamics NAV 365, Business Central, Oracle/Peoplesoft, Exact, Unimarket, Jaggaer (SciQuest), Birchstreet and many more. Get a demo
Shopspray Punchout currently supports XML, cXML, OCI (OCI4 and 5 with backwards compatibility to OCI3), OBI & Peppol. Get a demo
Getting punchout enabled with the Shopspray add-on is straight forward. Install the add-on and customize your templates as you wish. Usually you are up and running within a few days to a few weeks. Shopspray can help you with the installation process or you can get assistance from one of our partners. Get a demo
Installation is easy. Our add-on is installed as a nuget-packet and with a few installation steps you have punchout capability natively in your commerce solution and you can start onboarding your customers directly from your commerce editor interface/dashboard. Get a demo
Installation is simple but you might want to let your implementation partner assist you installing or making changes in order templates. We can always provide you with just the right partner for installing and setting up your Shopspray Punchout add-on on your commerce solution. Get a demo
Absolutely! Just contact us using our contact form and we will set up a demo session for you. Get a demo
Shopspray Nordics (HQ):
Hyllie Boulevard 53
215 37 Malmö, Sweden
Shopspray Central Europe:
Marzellenstraße 23,
50668 Köln, Germany
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |