Documentation Center

PunchOutHub Docs

This documentation explains PunchOutHub from business overview to technical setup. It is written for B2B suppliers, IT teams, procurement consultants, and buyers who need to understand the supplier-side PunchOut workflow before implementation.

OverviewUnderstand supplier-side PunchOut positioning.InstallationPrestaShop setup and readiness checklist.TroubleshootingDiagnose session, return, and buyer setup issues.
Platform support
PunchOutHub is built for supplier-side PunchOut integration on B2B eCommerce platforms. This website currently focuses on PrestaShop readiness, the free upgrade checker, PunchOut documentation, and comparison resources. Shopware native support is part of the multi-platform expansion roadmap.

Platform support

PunchOutHub currently presents a PrestaShop-focused supplier-side PunchOut path for B2B eCommerce teams, with Shopware kept as part of the future native plugin roadmap.

Current focus

PrestaShop

Supplier-side PunchOut support for PrestaShop stores, including buyer session, catalog access, cart return, configuration, and troubleshooting workflows.

Free tool

Readiness checker

The free PunchOut Readiness Checker & Audit Report helps merchants review platform readiness before a PunchOut or upgrade project.

Roadmap

Shopware

Shopware native plugin support is planned as part of the multi-platform expansion roadmap.

Enterprise options

Licensing and protection

Domain-locked signed licensing and integrity checks are available, with server-side monitoring planned as a future enterprise protection option.

Quick start checklist

This checklist is written for a practical first implementation review.

  • Confirm store platform and version: PrestaShop 1.7.8.8, 8, or 9.
  • Confirm buyer system: Oracle Fusion / Oracle iProcurement / SAP Ariba / compatible cXML buyer.
  • Install the PunchOutHub module package in the store.
  • Enable HTTPS for the store and all PunchOut endpoints.
  • Create or verify buyer profile in PunchOutHub admin.
  • Enter Sender ID / buyer identity values supplied by the buyer.
  • Configure Shared Secret securely.
  • Confirm BrowserFormPost / return URL from the buyer side.
  • Run PunchOut setup request test.
  • Add item to cart and test Return to Oracle / Return to buyer flow.
  • Review masked logs and support bundle if troubleshooting is needed.

PrestaShop installation notes

PunchOutHub is positioned as a native PrestaShop module rather than a separate external catalog system. This helps suppliers keep their product data, pricing, and catalog experience close to the existing store.

VersionStatusGuidance
PrestaShop 9Recommended optionRecommended for new builds and future-facing deployments.
PrestaShop 8SupportedStrong option for stable production stores.
PrestaShop 1.7.8.8Supported on requestUseful for suppliers that cannot upgrade immediately.
Deployment note
Always test on staging first, especially when upgrading an existing production store or changing buyer credentials.

Buyer setup

A buyer profile represents the procurement-side identity that will PunchOut into the supplier store. Keep buyer-specific values separate so each buyer can be tested, supported, and logged clearly.

Identity

Sender ID, buyer identity, domain, and other values used to match incoming cXML requests.

Shared Secret

Used to authenticate the buyer request. Store and show it carefully; do not expose it in public logs.

Return URL

The buyer-side URL that receives the returned PunchOut cart. Often referred to as BrowserFormPost URL.

Status and edition

Buyer availability may depend on license edition such as Single Buyer or Business 1:5.

PunchOut flow explained

From a business point of view, PunchOut lets a buyer enter the supplier catalog from procurement, select products, and send the cart back to procurement for internal approval and purchase order processing.

01
LaunchBuyer clicks supplier catalog in procurement.
02
Setup requestBuyer system posts setup data to supplier.
03
ResponseSupplier returns StartPage URL.
04
CatalogBuyer browses and adds products.
05
Return cartSupplier returns selected items.
06
ProcurementBuyer continues approval / PO flow.

Common endpoint names

/module/punchout/entry /module/punchout/catalog /module/punchout/returncart /module/punchout/order_receiver

Testing checklist

Use these tests before a customer demonstration or buyer-side UAT.

  • Module installs without fatal error.
  • Admin dashboard opens correctly.
  • License status and integrity status display correctly.
  • Buyer profile saves successfully.
  • PunchOutSetupRequest returns success response.
  • Catalog opens with PunchOut session context.
  • Add-to-cart works inside PunchOut session.
  • Cart return posts back to buyer URL.
  • Empty / cancel cart return behaves correctly.
  • Logs show setup, restore, add, and return events without exposing secrets.

Troubleshooting

No Return to Oracle button

Check whether the buyer entered through a real PunchOut session, whether the session restored, and whether the cart template renders the PunchOut return action.

400 / invalid request

Review incoming cXML body, content type, endpoint URL, buyer identity, and Shared Secret.

Return URL issue

Confirm BrowserFormPost URL is present, valid, and uses HTTPS when required by the buyer.

PrestaShop cache issue

Clear dev/prod cache after module updates, especially on PS9 or after admin UI changes.

Support bundle
When asking for support, prepare masked logs, platform version, buyer profile screenshot, endpoint URL, and a sample request if available.

Licensing and editions

Keep public wording accurate. The current sellable line uses local/offline-first licensing with domain lock and integrity checks. Do not describe future server-side monitoring as already active production functionality.

EditionTypical useNotes
Single BuyerOne company / one buyer portalGood first deployment package.
Business 1:5Up to five buyer profilesBetter for growing supplier-side PunchOut programs.
OCI / Mapping / EnterpriseAdditional buyer requirementsScope separately based on buyer platform and field mapping needs.
Safe wording
Use: “Domain-locked signed local license included. Server-side license monitoring is planned for future enterprise protection.”

Security notes

  • Use HTTPS for all PunchOut endpoints.
  • Mask Shared Secret, license keys, tokens, and raw payloads in exported support bundles.
  • Use buyer profile separation for clearer troubleshooting and access control.
  • Keep production debug output off.
  • Use staging before upgrading a live buyer setup.

For security contact: security@getpunchouthub.com

Shopware roadmap

Shopware native plugin support is part of the PunchOutHub multi-platform expansion roadmap for future supplier-side PunchOut implementations.

Roadmap message
Shopware is listed as a future native plugin expansion path for merchants planning beyond PrestaShop.

Support request checklist

Before sending a support request, prepare the following:

  • Store domain and platform version.
  • PunchOutHub version.
  • Buyer platform and buyer requirement.
  • Screenshot of buyer setup page with sensitive values masked.
  • Latest masked logs or support bundle.
  • Whether the issue happens during setup request, catalog session, add-to-cart, return cart, or PO/order receiver stage.

Need implementation help?

Send the buyer requirement and store version. We can review compatibility before implementation.

Contact support
Free readiness tool

Not sure if your store is ready for PunchOut or a platform upgrade?

Use the free PunchOut Readiness Checker & Audit Report v1.4 to review your PrestaShop version, PHP baseline, SSL status, theme/module risk, PunchOut readiness, and optional buyer requirement status before starting a B2B integration project.

Download Free ToolView compatibility guide