Jaggaer is what you get when two very different procurement companies merge. One root is SciQuest, the American platform that became the default purchasing system of universities, research labs and life-science organizations. The other is BravoSolution, the Italian spend-management vendor that many European enterprises, and most Italian procurement teams, still call by its old name. If your buyer is a university lab in Ohio or a manufacturer in Milan, there is a fair chance the system behind their requisitions is the same one: Jaggaer.
The strictest cXML in the business
Jaggaer's punchout runs on cXML, and their supplier documentation is unusually explicit about it: punchout must follow the cXML standard as published at cxml.org. In practice that strictness is good news for suppliers. Where other networks tolerate dialect drift, Jaggaer expects the textbook document flow, which is exactly the flow described in our punchout guide: PunchOutSetupRequest in, PunchOutSetupResponse with a start URL out, PunchOutOrderMessage on cart transfer, and purchase orders delivered as cXML OrderRequest documents. If your endpoint implements the standard correctly, and logs every document raw so deviations are visible, a Jaggaer connection is one of the more predictable enablements you will do. For how this compares with the SAP-flavored alternative, see cXML vs OCI.
No supplier fees, unlike the network next door
Jaggaer does not charge suppliers network fees, transaction percentages or subscription tiers. That single fact separates it sharply from Ariba, where punchout suppliers budget a Silver-tier subscription and a transaction fee before the first order arrives. The cost of a Jaggaer connection is your side of the integration and your time in their enablement process. Nothing else.
Enablement runs through a dedicated team
Unlike Coupa, where the buyer's admin self-configures your connection, Jaggaer runs supplier enablement through its own team, coordinated with your buyer's project. Their published enablement terms imply a working pipeline of roughly one and a half to two weeks per supplier once your slot comes up, which in practice means your calendar time depends on queue position more than on engineering. What keeps your slot short is arriving prepared: endpoint live, test credentials issued, catalog data clean, and raw XML logs ready to share the moment a test cart misbehaves.
What the Jaggaer side will ask from you is familiar cXML material: your punchout URL, From and To identities, a shared secret, and per-item data their platform cares about, UNSPSC classifications and units of measure above all. Universities and labs are strict about commodity codes because their reporting depends on them; a catalog with sloppy UNSPSC data will surface in testing, not after.
What PunchRelay does for a Jaggaer connection
PunchRelay gives your Shopify store the standards-clean cXML endpoint Jaggaer expects: shared-secret validation, punchout sessions opened against the Shopify B2B company location you assign, contract pricing from your B2B catalogs and price lists, quantity rules enforced before the cart transfers, and incoming OrderRequest documents acknowledged in under 150 ms and created as Shopify orders. The per-buyer configuration layer covers the details that vary per Jaggaer deployment: transfer encoding, UNSPSC and unit-of-measure mapping from your Shopify product data, and correlation fields on the purchase order return.
Every message in both directions is logged raw. In a Jaggaer enablement, where a dedicated team is testing against the published standard, being able to answer “here is exactly what we received and exactly what we sent” is the difference between closing a test loop in one email and losing your pipeline slot to the next supplier in the queue.
If your biggest customer runs Jaggaer, or still says BravoSolution, leave your email below. We will map the shortest path to a live connection, catalog checklist included.