Hosted Catalog (Static Catalog)
⚠️ Source Note: Extracted from TradeCentric vendor blog. TradeCentric’s analysis favors PunchOut, but the hosted catalog definitions are accurate industry usage. Do not attribute to Justin King or B2BEA.
A hosted catalog (also called a static catalog or CIF catalog) is a product file — typically in CSV, XML, or CIF (Catalog Interchange Format) format — that a supplier provides to a buyer for upload into their eProcurement system. Once uploaded, buyers can search for and order items directly within the eProcurement platform without leaving it.
The key distinction from PunchOut: a hosted catalog is a point-in-time snapshot. It does not pull live data from the supplier’s eCommerce site. Pricing, availability, and product data reflect what was in the file at the time of upload.
How It Works
- Supplier exports a product file (CSV, XML, or CIF format) containing SKUs, descriptions, pricing, UNSPSC codes, and other attributes
- Supplier submits the file to the buyer’s eProcurement team
- Buyer’s procurement team reviews, approves, and publishes the catalog to their users
- Buyers search and order from within the eProcurement platform — no redirect to supplier site
- When product data changes, supplier must generate and submit an updated file; buyer must re-approve and republish
CIF Format
CIF (Catalog Interchange Format) was developed by Ariba in 1996 as a standardized format for exchanging product data between procurement systems. It is the most common format for hosted catalogs in SAP Ariba environments. Other platforms accept CSV or XML variants.
Hosted Catalog vs. PunchOut
Feature
Hosted Catalog
PunchOut Catalog
Data source
Static file in buyer’s system
Live from supplier eCommerce
Pricing
Pre-set, manually updated
Real-time, buyer-specific
Inventory
Only when file refreshed
Instant, live feed
User experience
Buyer’s procurement portal UI
Supplier’s branded eCommerce site
Maintenance
Supplier pushes updated files to each buyer
Supplier updates their own eCommerce site once
Setup time
Quick (file upload)
Moderate (requires integration)
Best for
Small, stable catalogs
Large, complex, or frequently updated catalogs
Buyer admin burden
Higher — buyer team must re-approve updates
Lower — live data, no buyer re-approval needed
When Hosted Catalogs Make Sense
Hosted catalogs are not obsolete — they are the right tool in specific situations:
- Small, stable product set: A supplier with 50 SKUs that rarely change doesn’t need the integration overhead of PunchOut
- Buyer system limitations: Some smaller or older eProcurement systems don’t support PunchOut; hosted catalog is the only option
- Limited IT resources: Suppliers without development resources to build a PunchOut integration can still participate in eProcurement via a catalog file
- Transitional step: A hosted catalog is often the first step a supplier takes toward eProcurement integration, before investing in PunchOut
Many organizations use both: hosted catalogs for stable, frequently reordered commodity items, and PunchOut for larger or more complex categories.
Limitations at Scale
The practical challenge with hosted catalogs at scale: a supplier with 500 active customers each running their own eProcurement system would need to maintain and push updated catalog files to 500 separate systems. Every pricing change, new product, or discontinued SKU requires a new file submission and a buyer re-approval cycle. PunchOut eliminates this by making the supplier’s eCommerce site the single source of truth.