ProductPlatform OverviewPunchOutPurchase OrdersInvoicesMulti-Store ControlTransactionsHow It Works
IntegrationsShopify ReadyCoupaSAP AribaJAGGAEROracle ProcurementIvaluaGEP SMARTcXMLOCI
SolutionsB2B SuppliersMulti-Store CommerceBuyer OnboardingEcommerce Agencies
Catalog comparison

PunchOut vs hosted catalog: choose the right buying model.

Understand the difference between a supplier-hosted PunchOut experience and catalog content maintained inside the buyer procurement system.

Resource guidePunchOut Central
01UnderstandDefine the buyer question
02MapConnect store and protocol
03ValidateTest the full transaction
At a glanceCompare the two models
QuestionPunchOutHosted catalog
Where content livesPunchOut: the supplier maintains the shopping experience and catalog on its site.Hosted catalog: the buyer or its catalog process stores and maintains item content in procurement.
Shopping experienceThe buyer opens the supplier store, searches and builds the cart there.The buyer searches and selects from catalog content available inside procurement.
Best fitRich, configurable, frequently changing or buyer-specific products and pricing.Stable item data that the buyer wants to search and manage locally.
Supplier responsibilityMaintain the store, access rules, connection and returned cart behavior.Provide accurate catalog data in the buyer's required format and update it when the buyer process requires.

Why a buyer may ask for PunchOut

PunchOut lets the buyer shop on the supplier site while keeping the requisition and approval process in procurement. It is useful when the supplier has a broad, configurable or frequently changing catalog that is better maintained in the supplier's ecommerce operation.

The supplier can keep the Shopify or Shopify Plus catalog and return the selected cart to procurement rather than building a separate static catalog for every buyer.

When a hosted catalog may be a better fit

A hosted or buyer-maintained catalog can be useful when the buyer needs local search, internal classification or tightly controlled item content. It also creates a content-maintenance responsibility inside the buyer's procurement process.

The right answer is often buyer-specific. Ask where the buyer needs product data, pricing and search to live before choosing the catalog model.

Questions for the buyer conversation

  • Does the buyer need to open the supplier store from procurement?
  • How often do product, price, availability or configuration details change?
  • Does the buyer need local search before opening the supplier site?
  • Who owns catalog updates and approval of item changes?
  • What must be returned in the requisition and purchase order?

Reference material

These primary-source references explain the general protocol or catalog concepts. Buyer-specific implementation requirements still take precedence.

Put the guide into practice

Not sure which catalog model the buyer means?

Share the buyer requirement and the current Shopify catalog so the options can be compared accurately.