Which procurement system does your buyer use?

SAP Ariba cXML

Ariba buyers reach you through SAP Business Network. Punchout needs an Enterprise supplier account there; a Standard account cannot run punchout or cXML.

Buyer identity

The buyer's Ariba Network ID (ANID), for example AN01234567890. It is the From identity in the buyer's cXML.

Timeline

Plan in weeks. One buyer's published supplier guide quotes 8 to 12 weeks for an Ariba punchout.

Supplier fees

SAP Business Network may charge suppliers fees once a buyer relationship passes SAP's thresholds; PunchRelay does not charge or collect them.

What you send the buyer's team

1. Accept the buyer's trading relationship on SAP Business Network.
2. Send the buyer the cXML setup URL, the cXML order URL and the shared secret of this connection.
3. Upload a punchout index catalog (CIF or cXML) for this buyer. Ariba validates the file, and the buyer approves it and every later version.
4. The buyer tests in their Ariba test realm, sends a test purchase order, then publishes the catalog.

Ariba punchout for your Shopify store

Coupa cXML

Coupa buyers set up punchout in their own Coupa instance; there is no central validation step.

Buyer identity

The From identity the buyer's Coupa admin will send, usually a DUNS number or a NetworkID.

Timeline

Plan for about a week, plus the buyer's own testing.

Supplier fees

The Coupa Supplier Portal charges suppliers no network or transaction fee.

What you send the buyer's team

1. Send the buyer's Coupa admin the cXML setup URL, the cXML order URL, the buyer identity and the shared secret of this connection.
2. Send your list of units of measure before the first test. Coupa can refuse to import a cart with a unit it does not know.
3. Have a 150 × 50 px logo and UNSPSC codes for your items ready; Coupa buyers ask for them.

Coupa punchout for Shopify, no supplier fee

JAGGAER cXML

JAGGAER's punchout follows the cXML standard published at cxml.org.

Buyer identity

The From identity the buyer's JAGGAER team gives you for cXML.

Supplier fees

JAGGAER charges suppliers no fee.

What you send the buyer's team

1. Send the buyer's team the cXML setup URL, the cXML order URL, the buyer identity and the shared secret of this connection.
2. Ask which cart transfer field their setup reads: cxml-urlencoded or cxml-base64.

Punchout for Jaggaer

Oracle Procurement cXML

Oracle Procurement punches out straight from the buyer's Oracle instance to your catalog. Oracle offers native XML or cXML; PunchRelay uses cXML.

Buyer identity

The From identity the buyer's Oracle administrator sets for the cXML punchout.

Supplier fees

No network fee: the punchout runs from the buyer's Oracle instance.

What you send the buyer's team

1. Ask the buyer's Oracle administrator to set up the punchout with cXML, not Oracle native XML.
2. Send them the cXML setup URL, the cXML order URL, the buyer identity and the shared secret of this connection.

Punchout for Oracle

Workday cXML

Workday supports cXML punchout and purchase orders. Public detail on Workday's supplier setup is thinner than for Ariba or Coupa, so confirm each step with the buyer's Workday team.

Buyer identity

The From identity the buyer's Workday team sets for cXML.

What you send the buyer's team

1. Send the buyer's team the cXML setup URL, the cXML order URL, the buyer identity and the shared secret of this connection.
2. Ask which cart transfer field their setup reads: cxml-urlencoded or cxml-base64.

Punchout for Workday

SAP (OCI) OCI

SAP systems punch out with OCI: the buyer's system signs in with a username and password, and the cart goes back to the buyer's HOOK_URL. OCI returns a cart only; purchase orders do not come back through OCI.

Buyer identity

A unique name for this buyer, such as their company or SAP system. SAP buyers sign in with the OCI username and password, not with this identity.

Supplier fees

OCI connections include a one-time $499 setup by PunchRelay.

What you send the buyer's team

1. Send the buyer the OCI URL, the OCI username and the OCI password of this connection.
2. Ask the buyer to send the setup as a POST. A GET puts the password in the URL, where logs and browser history keep it.
3. Agree how purchase orders will reach you. If the buyer's system can send cXML purchase orders, give them the cXML order URL.

OCI punchout for Shopify (SAP, DACH)

Ivalua cXML

PunchRelay has no Ivalua-specific steps yet; it is set up like any other cXML system.

Buyer identity

The buyer's cXML From identity, from their Ivalua administrator.

What you send the buyer's team

1. Send the buyer's team the cXML setup URL, the cXML order URL, the buyer identity and the shared secret of this connection.
2. Ask which cart transfer field their setup reads: cxml-urlencoded or cxml-base64.

Unimarket cXML or OCI

We have no checked setup steps for Unimarket yet. Ask the buyer's Unimarket administrator whether their punchout uses cXML or OCI and what they need from you.

Buyer identity

The buyer's cXML From identity, from their Unimarket administrator. For an OCI-only buyer, a unique name for the buyer.

What you send the buyer's team

1. Ask the buyer's Unimarket administrator whether their punchout uses cXML or OCI, and choose the protocol to match.
2. Send them the URLs and credentials of this connection for that protocol.
3. For cXML, ask which cart transfer field their setup reads: cxml-urlencoded or cxml-base64.

Another system cXML or OCI

PunchRelay works with procurement systems that punch out with cXML or OCI. Ask the buyer's IT team which one their system uses.

Buyer identity

The buyer's cXML From identity. For an OCI-only buyer, a unique name for the buyer.

What you send the buyer's team

1. Ask the buyer's IT team whether their system uses cXML or OCI, and choose the protocol to match.
2. Send them the URLs and credentials of this connection for that protocol.
3. For cXML, ask which cart transfer field their system reads: cxml-urlencoded or cxml-base64.