Dev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket

PunchOut connectors

Describes PunchOut functionality in Optimizely Configured Commerce for communicating with procurement systems, acting as an alternate to a static catalog file.

Optimizely Configured Commerce includes PunchOut functionality for communicating with procurement systems, acting as an alternate to a static catalog file. The Configured Commerce website then becomes available through the procurement system with the click of a button, automatically logging the customer into the website to view their catalog and pricing. Insite has developed a partnership with Supplier Solutions and PunchOut2Go as the preferred PunchOut providers who facilitate the communication between the numerous procurement systems and Configured Commerce. These integration partners act as trusted intermediaries who handle the transaction of data between Configured Commerce and the buying parties' procurement system.

More generally stated, PunchOut is an electronic communication between a buyer's procurement or ERP system and the supplier's web website and order management system. With PunchOut, the electronic protocols link the buyer and supplier systems and software applications (typically using cXML documents) to create a collaborative commerce environment.

Benefits of PunchOut

  • Reducing operational costs
  • Eliminating manual PO entry and contract verification
  • Ensuring adherence to negotiated contracts
  • Leveraging the workflow of the buyer's procurement system
  • Delivering accurate and consistent information to the buyers

PunchOut setup

Setting up PunchOut to work with the Configured Commerce website will differ depending on the implementation, typically requiring setup and configuration with an integration partner. More detailed instructions for setup and configuration of PunchOut can be found in the PunchOut/cXML Process and Design article and will be filled through dialogue and communications with your integration partner.

PunchOut process

The following diagram shows the basic PunchOut process flow.

The shopping experience within the PunchOut session works much like a user logged directly into the site, where they can see their specific catalog and pricing. The buyer then adds items to a shopping cart and "checks out". The "check out" process, when using PunchOut, does not follow the typical address and payment steps, instead the cart data is sent to the procurement system which results in a requisition order in the procurement system. Leveraging the procurement system's workflow and approval process, the requisition is then converted to a purchase order and sent electronically to Configured Commerce for processing. Finally, after successful processing, the order is submitted into the client's ERP.

📘

Note

The same purchase order processing interface used by PunchOut can be used to process any electronic orders. Because the interface is based on standard cXML protocol, any outside system could process electronic orders through Configured Commerce- for example, Internet of > Things (IoT), Machine to Machine (M2M), and so on. Insite has another integration partner, Conexiom, that leverages this interface to submit orders sent via email. Conexiom receives emailed orders, parses the message to obtain order header and line data, and submits them to > Configured Commerce for processing and ERP submission.

The following image provides a more detailed visualization of the Configured Commerce PunchOut process flows and interfaces, including the responsibilities of the various systems.