Core event sequence
01 Launch
Buyer clicks supplier catalog from procurement.
02 Setup request
Procurement sends PunchOutSetupRequest to supplier endpoint.
03 Setup response
Supplier validates and returns StartPage URL.
04 Catalog session
Buyer browses, searches, and adds products.
05 Return cart
Supplier posts PunchOutOrderMessage or compatible cart back to buyer.
06 Approval / PO
Buyer completes internal approval and sends purchase order if configured.
Common supplier-side endpoints
Names can vary by deployment. A PrestaShop implementation commonly uses these logical endpoints:
/module/punchout/entry
/module/punchout/catalog
/module/punchout/returncart
/module/punchout/order_receiver
Main documents
| Document | Direction | Purpose |
|---|---|---|
| PunchOutSetupRequest | Buyer → Supplier | Starts the session and carries buyer identity. |
| PunchOutSetupResponse | Supplier → Buyer | Returns StartPage URL for shopping. |
| PunchOutOrderMessage | Supplier → Buyer | Returns selected cart lines to procurement. |
| OrderRequest | Buyer → Supplier | Purchase order flow after buyer approval, when in scope. |
Simple explanation for customers
A helpful way to explain this to customers: PunchOutHub does not force the buyer to manually copy products from the supplier store. Instead, the buyer enters the supplier catalog from procurement, selects items, and sends the cart back to procurement in a structured format.