How to Set Up a PunchOut Integration with Precoro (for Suppliers)

TABLE OF CONTENTS

• Supported Types of PunchOut Integration 

• Request Documentation

• Integration Credentials

Supported Types of PunchOut Integration 

To simplify ordering from as many suppliers as possible, we offer clients the ability to connect PunchOut integrations not preconfigured by Precoro. This article explains how to configure the integration and what information your clients will need to establish the connection.

Please consider that Precoro only supports the following:

• cXML connection
• Punchout + PO
  For the integration to work correctly, your client's flow will be as follows:
  • A purchase order or requisition document creation is initiated in Precoro.
  • The client is redirected from Precoro to your website to select items for purchasing.
  • Once ready, the client presses the checkout button on your website. It redirects them back to Precoro and transfers information about the selected items.
  • When the order is approved, Precoro sends it to you.
• Level 1 PunchOut catalogs
  The client will be redirected to your website for item selection. Items will not be saved to their catalog in Precoro.

Request Documentation

To help you set up the integration, we've prepared request templates to exchange data between you and Pecoro. Please configure the PunchOut according to the files provided below:

1. PunchOut Setup Request 
   POSR request will be sent when a client wants to connect to PunchOut: download.

2. PunchOut Order Message
   Use the POOM request when redirecting your client back to Precoro when they've filled their shopping cart to transfer information about the items they're ordering: download.
3. PO Pushout
   Precoro will send this request to you once the order is approved: download.

Integration Credentials

To connect the integration from Precoro's side, your client will need to enter the credentials shown in the screenshot below. Please send the necessary information to the client. If negotiated with the customer, you can send two sets of credentials: for testing and for real orders.

Here is a description of each field:

Connection Identity Fields

Sender Domain
Specifies the type of identifier used for the client in the cXML header.
Available options: NetworkID or DUNS

• Use NetworkID for an Ariba Network ID (ANID)
• Use DUNS for a Dun & Bradstreet number

Supplier Domain
Specifies the type of identifier used for your organization in the cXML header.
Available options: NetworkID or DUNS

• Use NetworkID if you are identified on the Ariba Network
• Use DUNS if you use a DUNS number

From Identity
The client’s actual identifier value, based on the selected Sender Domain (ANID or DUNS).

For example: AN01234567890 (if Sender Domain = NetworkID)

To Identity
Your organization’s actual identifier value, based on the selected Supplier Domain (ANID or DUNS).

For example: AN09876543210 (if Supplier Domain = NetworkID)

Sender Identity
The credential used to authenticate the cXML request, typically your system login or integration username. It often matches the From Identity, but may differ depending on your setup.

Security

Shared Secret
A password or token used to authenticate cXML messages between your system and the client’s system. Both sides must use the same value.

Endpoint URLs

Punchout URL
The entry point on your side used to launch the PunchOut catalog session. This URL receives the PunchOutSetupRequest when a customer clicks Request from [PunchOut_Name] 
in Precoro.

Purchase Order Request URL
The URL on your side that receives the OrderRequest when the customer submits a purchase order from Precoro.

Use this table to quickly check the meaning of each field during setup.