This FAQ is designed for suppliers, sales teams, and IT teams who receive a PunchOut requirement from an enterprise customer and need a quick explanation before technical setup starts.
Quick Answers
Do we need a new website?
Usually not. If the supplier already uses PrestaShop as a B2B catalog, PunchOut can often be added as a module and configured per buyer.
Does PunchOut place the order?
No. PunchOut returns the selected cart to the buyer's procurement system. The buyer then creates a requisition or purchase order in their own system.
Is cXML the same as OCI?
No. cXML is XML over HTTPS and is common with Oracle, Coupa, and Jaggaer. OCI is an SAP-style browser form protocol used in SAP Ariba and SAP environments.
Does every buyer use the same mapping?
No. Even when buyers use the same protocol, they may require different UOM, UNSPSC, currency, tax, or extrinsic fields.
What should we test first?
Test setup request authentication, catalog launch, add to cart, return cart, and whether the buyer's system accepts every line item correctly.
Implementation Scope Checklist
- One buyer or many buyers?
- Oracle cXML only or SAP Ariba OCI too?
- Create flow only or edit/cancel also?
- Static prices or buyer-specific pricing?
- Basic logs or full support bundle?
Frequently Asked Questions
What is cXML PunchOut?
cXML PunchOut is a protocol that lets a buyer open a supplier's live catalog from inside a procurement system, select items, and return the cart as structured cXML.
Is product import the hardest part?
No. Importing products is usually straightforward if the spreadsheet is clean. The harder part is session handling, buyer authentication, field mapping, and return-cart compatibility.
Can one PunchOut implementation support multiple buyers?
Yes, but the system needs buyer management, credential separation, product visibility rules, and support for buyer-specific mapping differences.