JAGGAER

JAGGAER PunchOut, from the supplier’s side

JAGGAER is strongest in higher education, healthcare and public-sector research buying — sectors with unusually strict contract-compliance expectations. That shapes what it asks of a supplier catalogue.

How JAGGAER PunchOut works

  1. The buyer selects your catalogue from their JAGGAER marketplace. JAGGAER sends a cXML PunchOutSetupRequest to your endpoint.
  2. You authenticate against the configured credentials and return a session URL.
  3. The buyer shops your site, which must present the contract pricing agreed with that institution.
  4. Checkout posts a PunchOutOrderMessage back to JAGGAER as requisition lines.
  5. The requisition follows the institution’s approval workflow and issues as a purchase order.

What JAGGAER requires from you

Contract pricing that matches the agreement exactlyJAGGAER buyers frequently reconcile catalogue prices against the contract on file. Discrepancies are treated as a compliance issue, not a data issue.
Thorough product classificationUNSPSC coding is typically expected across the catalogue, and institutions often have their own additional category requirements on top.
Clean, complete product dataDescriptions, manufacturer part numbers, packaging and units all get scrutinised. Sparse catalogue data causes more rework here than on the other platforms.
Hazard and compliance attributes where relevantResearch and healthcare buying frequently requires handling, hazard or regulatory attributes on relevant lines.

Where suppliers lose time on JAGGAER

Compliance review is a real gate, not a formalityExpect catalogue content to be reviewed against the contract before go-live. Budget time for a revision round; it is normal rather than a sign something went wrong.
Institutions customise heavilyTwo JAGGAER buyers can have materially different requirements. What one institution accepted is a starting point for the next, not a template.
Consortium pricing complicates the catalogueHigher-education buyers often purchase under consortium agreements, so the correct price depends on which agreement the shopper is buying under — not simply which institution they belong to.
Academic calendars affect the queueInstitutional procurement teams are measurably harder to reach at term boundaries and during fiscal year-end. This is a scheduling reality worth planning around.

Timeline and price

Two to four weeks of supplier-side work, plus a catalogue compliance review that is more substantial than on other platforms. Plan for at least one revision round on catalogue content.

A JAGGAER 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.

JAGGAER questions

Why is JAGGAER stricter about catalogue data?

Its core customer base — universities, hospitals and research institutions — operates under procurement rules that require demonstrable contract compliance, often with public accountability attached. The platform reflects the obligations of the buyers using it.

Do we need UNSPSC codes for every product?

Assume yes unless the buyer tells you otherwise. If your product data has no classification at all, that is a data preparation task that runs alongside the integration rather than after it, and it is work we handle.

Can the same catalogue serve a JAGGAER buyer and a Coupa buyer?

Yes. The underlying catalogue and pricing logic are shared; the platform-specific handshake and classification requirements differ per buyer. Adding a second platform is an additional connection, not a second build.

Working out what your JAGGAER buyer needs?

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

Start a conversation See pricing