PunchOutHub Business 1:5 is designed for suppliers who need Oracle / SAP Ariba PunchOut without rebuilding their PrestaShop store or starting a large middleware project.
Business Edition—1:5
One supplier store can support up to five independent buyer profiles. Each buyer can have its own credentials, return URL, catalog scope, pricing group, and procurement setup.
Business 1:5 is for suppliers selling to multiple companies, divisions, factories, or procurement portals from one PrestaShop store.
Separate buyer credentials
Each buyer profile can use its own Sender ID, Shared Secret, environment, protocol, and return configuration.
- Safer buyer separation
- Duplicate Sender ID protection
- Active / disabled buyer control
Buyer-specific catalog scope
Show all products, selected categories, excluded categories, selected products, or excluded products per buyer.
- Buyer A sees catalog A
- Buyer B sees catalog B
- No SQL editing needed
Buyer-specific pricing
Use PrestaShop customer groups and native pricing rules to show different prices to different buyers.
- Default shop pricing
- Customer group pricing
- Works with PrestaShop price engine
Oracle / Ariba-ready flow
Supports standard cXML PunchOut flow for buyers who need procurement-to-store catalog browsing and cart return.
- PunchOutSetupRequest
- PunchOutSetupResponse
- PunchOutOrderMessage return
Admin visibility
Dashboard and buyer pages show capacity, status, license health, logs, and support-ready information.
- Buyer usage 2 / 5
- License health card
- Support bundle export
Ready to sell safely
The commercial ZIP keeps the advanced mapping engine out of the core package to reduce source exposure.
- Core runtime stays lightweight
- Mapping Engine sold separately
- Enterprise scope stays protected
1) Business 1:5 Core Module
- Dashboard and license health
- Buyer management up to 5 profiles
- Catalog scope per buyer
- Customer group pricing per buyer
- cXML PunchOut create, catalog, cart return
- Logs, compliance view, support bundle
- No Buyer Mapping Engine UI / controller / templates in the sellable ZIP
2) Enterprise Mapping Engine
- Available for larger buyer onboarding projects
- Supports 10, 20, 50+ buyer connection planning by quote
- Auto-detect cXML / OCI fields from real buyer payloads
- Buyer-specific mapping profiles and field overrides
- Dry-run / preview before production changes
- Import / export mapping JSON for staging and support
- Designed for Oracle, SAP Ariba / OCI, and complex procurement payloads
Core module only
The Business 1:5 package focuses on the parts customers need to go live: buyers, catalog scope, pricing, cXML flow, logs, and support bundle.
Enterprise-ready mapping
Buyer Mapping Engine can be added for larger rollouts that require buyer-specific payloads, mapping profiles, and onboarding for 10, 20, 50+ buyer connections.
Lower source exposure
The sellable ZIP avoids shipping advanced mapping UI, controller, templates, and transformation tools in the standard package.
Buyer initiates PunchOut
Oracle / SAP Ariba sends a PunchOut setup request to the supplier store.
Authenticate buyer
PunchOutHub validates the buyer profile, Sender ID, Shared Secret, and session context.
Shop in PrestaShop
The buyer browses the supplier catalog with buyer-specific catalog and pricing rules.
Return cart
PunchOutHub returns the selected items to the procurement system as a PunchOut order message.
Install / upgrade module, clear cache, open dashboard, verify no fatal or Smarty error.
Create buyers, verify 1:5 capacity, block duplicate Sender ID, and confirm limit behavior.
Verify selected catalog scope and PrestaShop customer group pricing per buyer.
Run setup, add item, return cart, empty cart, and confirm logs / support bundle.
| Decision point | PunchOutHub | Typical middleware project |
|---|---|---|
| Built specifically for PrestaShop suppliers | ✓ | Depends |
| Transparent package and starting price | ✓ | ✗ |
| Business 1:5 buyer profiles | ✓ | Project scope |
| Buyer-specific catalog and customer group pricing | ✓ | Project scope |
| Support-ready dashboard, logs, and bundle | ✓ | Depends |
| Advanced mapping kept as optional add-on | ✓ | Usually custom |
Show buyers the two points that matter: the PunchOut session is active inside the supplier catalog, and the selected cart can be returned to Oracle as a PunchOutOrderMessage with item lines, total, and XML payload preview.
Connection example
Oracle • PunchOutPunchOut session active, buyer connected, catalog browsing, add-to-cart workflow, and cart summary visible in the supplier catalog.
Return to Oracle example
Returned to OracleReturned PunchOutOrderMessage summary with item lines, total amount, and cXML payload preview for buyer-side validation.
PunchOutHub includes native PrestaShop admin visibility for license status, buyer usage, quick connection tests, return-to-Oracle tests, log reports, support bundle export, and compatibility readiness.
Admin Dashboard, License Health & Quick Validation
- System Status and Last Test Result
- Buyer Usage 1:1 / 1:5 visibility
- License Health and edition comparison
- Quick Connection Test and Purchase Return Test
- Masked log reports and Support Bundle export
Compatibility Matrix
- PrestaShop 1.7.8.8 / 8.x / 9.x readiness
- PHP baseline visibility
- cXML create / edit / cancel status
- OCI add-on readiness status
- Theme return fallback support
For suppliers that need to onboard many buying organizations, divisions, or procurement portals, PunchOutHub can be scoped with Buyer Mapping Engine, assisted onboarding, and buyer-specific validation.
10 buyer connections
For growing B2B suppliers with several departments, sites, or buyer portals that need separate catalog, pricing, and routing profiles.
20 buyer connections
For enterprise suppliers serving multiple divisions, companies, Oracle environments, or SAP Ariba / OCI buyer setups.
50+ buyer connections
For large rollouts that require onboarding planning, mapping review, priority support, and buyer-specific payload validation.
Start with Business 1:5 for standard PunchOut. For 10, 20, 50+ buyer connections or complex buyer-specific payloads, request Enterprise Mapping Engine scope and pricing.