Reference

PunchOut Level 1 vs Level 2

A buyer has asked for “Level 2 PunchOut” and not explained what that means. It is not a different protocol — it is a different place for the search box, and it commits you to something Level 1 does not.

The distinction in one paragraph

In Level 1, the buyer clicks your name inside their procurement system and lands on your catalogue home page. They search on your site. In Level 2, the buyer searches inside their own system, your products appear in those results, and clicking one takes them straight to that product’s page on your site.

The protocol underneath is identical. What changes is that Level 2 requires you to hand the buyer an index of your products for their search engine, and to supply a deep link for every product in it.

Side by side

 Level 1Level 2
Where the buyer searchesOn your siteInside their procurement system
What they click firstYour company nameA specific product
Where they landYour catalogue home pageThat product’s page
Index file requiredNoYes
Deep links per productNoYes, and they must stay valid
Ongoing maintenanceYour catalogue onlyYour catalogue and the index, kept in step
Visibility in buyer searchNone — they must know to look for youYour products compete on the results page

Why a buyer asks for Level 2

Their users don’t know your name An employee needing a part searches for the part. If your products only exist behind a click on your company name, you are invisible to everyone who does not already buy from you.
They want comparable results Procurement teams like a single results page across suppliers. Level 2 is what makes that possible, which is why buyers with several suppliers in one category push for it.
It shortens the path to a requisition Fewer clicks between "I need this" and a line on a requisition means fewer abandoned purchases and less off-contract buying.

What Level 2 actually costs you

The upside is real: your products appear where the buyer is already looking. But be clear about what you are taking on, because this is the part that gets skipped in the sales conversation.

  • Two representations of one catalogue. Your live site and the index the buyer holds. Both have to agree.
  • Deep links that must not rot. Every indexed product needs a stable URL. Restructuring your site later breaks every one of them at once.
  • A refresh cycle. Price changes, discontinuations and new lines all have to reach the index on the buyer’s schedule, not yours.
  • A stale-index failure mode. When the two drift apart, the buyer sees a price that is not real. That is a contract-compliance conversation, not a bug report.

None of this is a reason to refuse Level 2. It is a reason to price and schedule it as its own piece of work rather than as a variation on Level 1, and to agree the refresh cycle in writing before you start.

Level 2, CIF, and hosted catalogues

These three get used interchangeably and they are not the same thing. The difference that matters is where the authoritative price lives.

  • Hosted or CIF catalogue. You send a file. The buyer loads it and orders from it. They never visit your site, and your price is only as current as the last file you sent.
  • Level 1 PunchOut. No file. The buyer comes to you for everything, and your site is authoritative.
  • Level 2 PunchOut. A file for search, your site for selection and price. A hybrid, with the maintenance burden of both.

If a buyer says "just send us a catalogue file", they are describing CIF, not PunchOut — and it is a materially different piece of work. Worth confirming before anyone agrees to a date.

A caution about the terms themselves

"Level 1" and "Level 2" are not defined in the cXML specification. They are industry shorthand, and platforms apply them loosely — some buyers use "Level 2" to mean any deep-linked punchout, others reserve it for a specific index-file arrangement their system supports. Ask what the buyer’s system actually requires rather than accepting the label, because the label is not load-bearing.

Common questions

Is Level 2 PunchOut a different protocol?

No. Both levels use the same cXML or OCI handshake and the same cart return. The difference is where the buyer starts searching — inside their own procurement system, or on your site — and whether you have supplied an index of your products for their system to search.

Do we have to offer Level 2?

Only if your buyer asks for it, and many never do. Level 1 satisfies most requirements. Level 2 is worth wanting when you are one of several suppliers in a category, because it puts your products in the buyer’s native search results alongside everyone else’s rather than behind a click on your name.

What is the index file?

A structured extract of your catalogue — commonly a CIF file, sometimes a supplier-specific format the buyer specifies — loaded into the buyer’s procurement system so their search can find your products. It carries enough to display a result and a deep link back to that product on your site. It is not your whole catalogue and it is not where the order comes from.

What happens when the index goes stale?

The buyer searches, finds a product, punches out, and lands on something discontinued or differently priced. This is the real cost of Level 2 and the reason to think before agreeing to it: you now maintain two representations of your catalogue and they have to agree with each other.

Is a CIF catalogue the same as Level 2 PunchOut?

No, though they are related and the terms get mixed up constantly. A pure CIF catalogue is static — the buyer loads your price file and orders from it without ever visiting your site. Level 2 PunchOut uses an index for search but sends the shopper to your live site for the actual selection, so your pricing and availability stay authoritative.

Has a buyer asked you for Level 2?

Send us what they specified. We will tell you whether they mean an index file, a deep-linked punchout, or a CIF catalogue — and what each would take.

Start a conversation See pricing