Jaggaer integration: catalogue and PunchOut for suppliers
Your customer procures through Jaggaer and asks for an electronic catalogue? With Primus you deliver your range as a hosted catalogue or as a PunchOut via cXML and OCI – in the variant your customer specifies.
- Target system
- Jaggaer (JAGGAER One, JAGGAER Direct)
- Methods
- Hosted catalogue, PunchOut, cXML order
- Formats
- Excel template, BMEcat, cXML, OCI
- Primus solution
- Primus Catalog, Primus PunchOut, Primus Connect
Your customer buys through Jaggaer? This is how your range becomes orderable.
Jaggaer is widely used in industry, in mechanical and plant engineering and by universities and public-sector buyers. For suppliers the integration usually starts with an invitation to the supplier portal of the customer and a request to provide a catalogue.
What exactly is required then varies from customer to customer more than on other platforms: one expects a completed Excel template, the next a BMEcat catalogue, the third a PunchOut. Pro3Con generates all variants from the same product data.
- From your item list: Excel, CSV or an ERP export is enough to start from.
- Matched to the customer: Template, BMEcat or PunchOut – whatever the guideline requires.
- Validated before handover: Mandatory fields, classification and units of measure are checked.
- One catalogue per customer: Range and prices individually for each Jaggaer customer.
- One master catalogue, many platforms: The same data also serves SAP Ariba, Coupa or Onventis.
Three routes into Jaggaer
Catalogue, PunchOut and ordering are separate integration steps. Your customer decides which of them you need.
Hosted catalogue
Your items live on the Jaggaer servers and can be searched there directly. They are delivered as a file that Primus Catalog generates from your item list.
PunchOut via cXML or OCI
The buyer moves from Jaggaer into your catalogue or webshop and brings the cart back. In production today with Primus PunchOut and Primus Connect.
Electronic orders
Orders reach you through the portal, by email or as a cXML message. We assess the transfer into your ERP as part of the project.
Not every Jaggaer is the same
Several product lines that grew out of independent systems run under the Jaggaer name. JAGGAER One goes back to the former SciQuest and works with the Supplier Network Portal; JAGGAER Direct is the former Pool4Tool from Austria and is used in the German-speaking countries mainly in manufacturing.
This has practical consequences for suppliers. In the Supplier Network Portal hosted catalogues are maintained through an Excel template and items are classified by UNSPSC, while PunchOut runs on cXML. Installations in the German-speaking countries, by contrast, frequently require BMEcat catalogues and OCI PunchOuts.
So do not rely on a general statement about formats but on the supplier guideline of your customer. Once it is on the table, a single conversation is enough to clarify which variant is needed.
The hosted catalogue: template, classification, approval
With a hosted catalogue you hand over your item data as a file. In the Supplier Network Portal Jaggaer provides an Excel template for this, in which items and prices are recorded; customers in the German-speaking countries often work with BMEcat or an Excel structure of their own.
The most common hurdle is classification. In the portal Jaggaer requires a valid UNSPSC code or a Jaggaer category for every item; if it is missing or too coarse, the item is not accepted. If your data is classified by ECLASS or in your own product groups, it has to be recoded.
This is what Primus Catalog does: your columns are mapped once, classification and units of measure are converted and the result is validated before handover.
- Catalogue format
- Excel template, BMEcat – depending on the customer
- Classification
- UNSPSC or Jaggaer category, customer rules
- Prices
- Customer-specific per catalogue
- Approval
- Review by the customer before publication
- Authoritative
- Supplier guideline of the customer
- Source
- Excel, CSV, BMEcat, ERP or PIM export
Hosted catalogue or PunchOut: which fits your range?
Both routes make your items orderable in Jaggaer. They differ in where the product data lives.
| Aspect | Hosted catalogue | PunchOut |
|---|---|---|
| Where is the data? | With Jaggaer | With you, retrieved in real time |
| Standard | Excel template, BMEcat | cXML, OCI |
| Product search | Directly in Jaggaer | In your catalogue or shop |
| Price changes | New catalogue version, approval by the customer | Effective immediately |
| Suited to | Manageable, stable ranges | Large ranges, availability, configuration |
| Primus solution | Primus Catalog | Primus PunchOut, Primus Connect |
As both routes build on the same master catalogue in Primus, you maintain your data only once – even if one customer requires a hosted catalogue and another a PunchOut.
Jaggaer PunchOut: cXML, OCI and Level 2
With PunchOut the catalogue stays with you. The buyer starts in Jaggaer, moves into your range and transfers the finished cart back into the requisition.
For this Jaggaer supports cXML and, mainly in SAP-related environments, OCI. Which standard applies depends on the installation of your customer. Primus PunchOut serves both from the same catalogue, so you do not have to commit in advance.
Some customers additionally require a Level 2 PunchOut: an item file is uploaded whose entries appear in the Jaggaer search and point straight to the matching item in your PunchOut. Whether and in what form this is required is something we clarify together with your customer.
Primus: catalogue and PunchOut for Jaggaer from one source
With Primus Catalog your item list becomes a validated catalogue in the required format. Primus PunchOut turns it into a PunchOut shop for cXML and OCI, with no programming of your own.
If you already run a webshop, Primus Connect connects it to Jaggaer as a PunchOut front end – without a second catalogue.
- PunchOut via cXML, OCI 4.0 and OCI 5.0 from the same catalogue
- Catalogues as BMEcat 1.2 and 2005, Excel and CSV
- Classification mapping, for instance from ECLASS or your own product groups to UNSPSC
- Customer-specific ranges and prices for each Jaggaer customer
Four steps to your Jaggaer integration
1Clarify specifications
We record which method, format and classification the guideline of your customer requires.
2Map the data
Your item list is mapped to the fields of the target format; classification and units of measure are converted.
3Validate and test
Primus validates the catalogue. A test in the test environment of the customer follows.
4Approve and maintain
Once the customer has approved it, your range is orderable. Changes go through the same mapping.
They work with Primus
Manufacturers and distributors delivering their product data to their customers’ procurement systems with Primus.
Frequently asked questions about Jaggaer integration
Nothing here that matches? Write to us – you will get a technical answer, not a template.
Which catalogue format does Jaggaer require?
That depends on the product line and on the customer. In the Supplier Network Portal hosted catalogues are maintained through an Excel template; in the German-speaking countries many customers require BMEcat or an Excel structure of their own. The supplier guideline of your customer is authoritative.
Does Jaggaer support PunchOut via OCI or cXML?
Both. Jaggaer supports cXML PunchOut and, mainly in SAP-related environments, OCI. Primus PunchOut serves both standards from the same catalogue.
Which classification does Jaggaer expect?
In the Supplier Network Portal UNSPSC is the standard; items without a valid code are not accepted. Customers in the German-speaking countries often specify ECLASS or product groups of their own. Primus Catalog recodes your classification to the one required.
Can I create a Jaggaer catalogue from Excel?
Yes. You upload your Excel or CSV file to Primus Catalog and map the columns to the catalogue fields. The software converts classification and units of measure, validates the result and provides the catalogue in the required format.
What is a Level 2 PunchOut in Jaggaer?
With a Level 2 PunchOut individual items already appear in the Jaggaer search. It is based on an item file whose entries point to the matching place in your PunchOut catalogue. Whether your customer requires it is clarified in the project.
Can I connect my existing webshop to Jaggaer?
Yes. Primus Connect connects your existing shop as a PunchOut front end: the buyer shops in your shop and the cart goes back to Jaggaer via cXML or OCI.
How many errors does your catalogue have?
Upload a BMEcat file. The validator checks it against the DTD and our quality rules and shows every error with its location. Free, no sign-up.