Coupa

Coupa PunchOut catalogue setup, from the supplier’s side

Your buyer runs Coupa and wants a PunchOut catalogue. Coupa is generally the most straightforward of the major platforms to integrate with — here is what it actually involves and where it still catches suppliers out.

How Coupa PunchOut works

  1. Coupa sends a cXML PunchOutSetupRequest to your endpoint when a buyer selects your catalogue from their Coupa marketplace view.
  2. You authenticate it against the shared secret configured on both sides and return a PunchOutSetupResponse with a session URL.
  3. The buyer shops your site under their own contract pricing.
  4. On checkout, your site posts a PunchOutOrderMessage back to Coupa, which lands as lines on a Coupa requisition.
  5. After approval, Coupa issues a purchase order — over cXML to your endpoint if you have order integration, or via the Coupa Supplier Portal or email if not.

What Coupa requires from you

A shared secret and endpoint URLExchanged with the buyer’s Coupa administrator. Coupa configures your catalogue as a supplier-hosted punchout site against these.
Commodity mappingCoupa organises spend by commodity. Your catalogue lines need to map onto the buyer’s commodity structure or the requisition will not route correctly for approval.
Consistent supplier part numbersCoupa matches returned cart lines against what it knows about you. Part numbers that change between the catalogue and the cart return cause line-level failures.
A test instance connectionCoupa buyers almost always have a sandbox. Expect to be configured and tested there before anything touches production.
Valid UNSPSC on every returned lineCoupa validates classification on the cart it receives. A line with a missing or invalid UNSPSC code causes Coupa to reject the cart outright — not to warn, and not to accept it unclassified.
ISO-standard units of measureUnits must be valid codes such as EA for each or BOX for box. This is the single most common cause of a cart that returns but prices incorrectly.
HTTPS with a valid certificateCoupa requires the punchout endpoint to be served over HTTPS with a valid SSL certificate. An expired certificate takes a live catalogue down silently.
A session that loads cleanlyDepending on the buyer’s configuration your store opens in an iframe or a new tab. Frame-busting scripts, redirect loops or headers that block framing will break the session in one of those modes and not the other.

Where suppliers lose time on Coupa

The Supplier Portal is not the integrationCoupa Supplier Portal is a web interface where you can see and acknowledge orders manually. It is free and useful, but being on the CSP does not mean you are integrated — PunchOut and document automation are separate work.
Buyer-specific pricing is the hard partThe protocol work is routine. Showing buyer A their negotiated price and buyer B theirs, on the same storefront, is what most existing ecommerce platforms cannot do out of the box.
Cart returns fail on unit-of-measure mismatchesA UOM your catalogue calls "EA" and the buyer’s system calls "each" will silently reject or misprice lines. This surfaces during testing and is tedious rather than difficult.
Coupa versions differ between customersCoupa releases frequently and buyers sit on different releases with different configuration options. What one Coupa buyer asks for is not automatically what the next one will.

Timeline and price

Coupa PunchOut is often the fastest of the four to stand up — commonly two to three weeks of supplier-side work. Buyer testing tends to move quicker than Ariba because sandbox access is usually easier to arrange.

A Coupa PunchOut catalogue is our Connect tier at $199/month for year one, stepping down to $129 from year two. If the buyer also wants purchase orders and invoices exchanged electronically, that is Order Loop at $349. You do not start paying until the connection is live in production.

The buyer's test queue, not the integration work, is what usually sets the date — see what actually controls the clock.

Coupa questions

Is the Coupa Supplier Portal enough on its own?

It depends entirely on what your buyer asked for. The CSP lets you receive and acknowledge orders manually through a browser. If your buyer specifically asked for a PunchOut catalogue, the CSP does not provide that — they want to shop your catalogue from inside Coupa, which requires an integrated punchout site.

Can one catalogue serve several Coupa buyers?

Yes. The same punchout site can serve multiple buyers, each authenticated separately and each seeing their own pricing. That is why additional buyer connections are a one-off cost rather than a repeat build.

What if we also need invoices to go back electronically?

That is cXML invoicing and it is separate from PunchOut, though it uses the same protocol family. It is the difference between our Connect and Order Loop tiers — see pricing for what each covers.

Further reading

Working out what your Coupa buyer needs?

Send us the requirement they gave you. We will tell you what it means in Coupa terms, which tier covers it, and roughly how long it takes.

Start a conversation See pricing