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.
Jaggaer Integration Profile
- Strict cxml.org Standard: Jaggaer demands textbook cXML without vendor dialect drift. Clean schema validation is mandatory.
- $0 Supplier Fees: Unlike Ariba, Jaggaer charges suppliers no network fees, no transaction percentage, and no subscription tiers.
- Dedicated Enablement Queue: Connections run through a specialized Jaggaer enablement engineer with a 1.5–2 week testing window.
- Mandatory Commodity Codes: Universities and research labs enforce strict UNSPSC classifications and ISO units of measure.
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.
| Dimension | Jaggaer Punchout Specification | Supplier Operational Requirement |
|---|---|---|
| Protocol & Schema | cXML 1.2.014+ (strict cxml.org compliance) | Clean DTD/XSD validation, no proprietary dialect extensions |
| Target Buyer Profiles | Higher education, life sciences, research labs (SciQuest); European enterprise (BravoSolution) | Strict compliance reporting, research grant accounting |
| Network & Transaction Fees | $0 (Zero network fees, $0 per-order cut) | Supplier retains 100% of order margin |
| Enablement Pipeline | Dedicated Jaggaer enablement coordinator | 1.5–2 week testing slot; requires prepared test credentials and catalog |
| Cart Transfer Mechanism | cXML PunchOutOrderMessage via HTTP POST | Contract pricing, UNSPSC codes, valid ISO UOM per line item |
| PO Return Leg | Direct cXML OrderRequest to connector endpoint | Durable ingestion, matched against the transferred cart, held for your review |
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.
Commodity codes and raw wire logs decide your queue slot
Universities and life-science institutions rely heavily on UNSPSC codes for grant reporting and indirect spend categorization. If your transferred cart contains missing or generic commodity codes, Jaggaer's validation will reject the line items during enablement testing.
Because Jaggaer's enablement team handles dozens of supplier queues concurrently, delays in resolving test cart errors will forfeit your testing slot. Keeping raw, credential-redacted XML wire logs for every session allows your team to pinpoint payload discrepancies and respond to the Jaggaer coordinator in minutes.
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 credential-redacted 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.
6-step Jaggaer enablement workflow
Following a structured deployment sequence ensures your integration passes Jaggaer's technical enablement on the first attempt without losing pipeline priority.
Endpoint Readiness
Deploy live cXML endpoint with valid TLS 1.3 certificate and durable payload logging.
Identity Exchange
Exchange From/To domain credentials, punchout URL, and shared secrets with the Jaggaer team.
Catalog & UNSPSC Prep
Audit Shopify B2B catalog items to ensure valid UNSPSC classifications and standard ISO UOMs.
Test Slot Execution
Execute PunchOutSetupRequest, session auth, and cart transfer in Jaggaer's testing realm.
PO Return Verification
Verify that the test cXML OrderRequest arrives and lands in your Purchase orders inbox.
Production Sign-Off
Promote credentials to live buyer instance and confirm first live requisition dispatch.
What PunchRelay does for a Jaggaer connection
cXML purchase orders are accepted durably, checked against the transferred cart and placed in the Purchase orders inbox in the PunchRelay app. Nothing is created in Shopify until someone on your team reviews the PO and clicks Create Shopify order. The order is then created unpaid, with payment pending, ready to fulfill. OCI returns a cart only; the purchase-order leg is agreed and tested separately for each buyer.
Every message in both directions is logged with credentials redacted. 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.