Punchout for every buyer. One published price.
Connect your catalog to Coupa, SAP Ariba, Jaggaer, Prendio and SAP SRM — cXML 1.2 and OCI 5.0 from one endpoint. From $199/month, unlimited punchout sessions, no per-buyer fees.
Both go straight to the information. No form in the way.
StackProcure is punchout catalog software for B2B suppliers. It connects your ecommerce catalog to enterprise procurement systems using cXML 1.2 and OCI 5.0, so buyers can shop your products from inside Coupa, SAP Ariba, Jaggaer, Prendio or SAP SRM and send the cart back as a requisition. Pricing is published and flat: $199 to $499 per month with unlimited punchout sessions.
A buyer asked you for punchout. Now what?
It usually arrives the same way. A hospital system, a university or a state contract tells you that to keep selling to them, your catalog needs to be available inside their procurement system. They send a document mentioning cXML, PunchOutSetupRequest and a shared secret, and give you a date.
Your options are to build it — a multi-month protocol project — or to buy it, at which point you discover that many punchout providers charge per buyer connection and won’t tell you what that costs until you’ve had a call.
One integration. Every buyer, either protocol.
Connect your catalog once. Every buyer that speaks cXML — Coupa, SAP Ariba, Jaggaer, Prendio — and every buyer on SAP’s OCI can punch out to it. Add your fourth buyer, your tenth, your thirtieth: the price doesn’t move.
Both protocols, one endpoint.
cXML 1.2 for Coupa, Ariba, Jaggaer and Prendio. OCI 5.0 for SAP SRM. You don’t have to know which one your buyer runs before you start — and you don’t pay more for either.
Published, flat pricing.
$199 to $499 per month. Unlimited punchout sessions on every plan. No per-buyer fee, no per-transaction fee. The number is on the pricing page.
Your data stays yours.
We run it, so there’s nothing for you to operate. Session and order history export to CSV whenever you ask — including on the way out.
How a punchout session actually works
Five legs, one round trip. This is the protocol as it really runs — the same lifecycle StackProcure implements and logs.
-
1 SetupSetup
The buyer’s procurement system sends a PunchOutSetupRequest and authenticates with a shared secret. StackProcure verifies it and opens a session.
PunchOutSetupRequest buyer ⇄ StackProcure -
2 ShopShop
The buyer’s browser lands in your storefront, signed in and price-correct for that buyer.
session redirect StackProcure ⇄ storefront -
3 TransferTransfer
They click Transfer Cart. The cart comes back to StackProcure with a signed token.
signed cart token StackProcure ⇄ storefront -
4 ReturnReturn
StackProcure packages the cart as a PunchOutOrderMessage and hands it back. It appears in their procurement system as a draft requisition.
PunchOutOrderMessage buyer ⇄ StackProcure -
5 OrderOrder
Once approved, their system sends the purchase order as a cXML OrderRequest. You have the order, with no line item re-keyed by anyone.
OrderRequest buyer ⇄ StackProcure
Which DTD version applies is set by your buyer, and often differs per document type. When a buyer says “we need cXML,” the useful question back is: which DTD version, for which documents?
Who runs on it
A medical supply distributor running punchout to hospital procurement since 2025 — live sessions, real purchase orders, cXML end to end.
We’d rather name one customer than show you six grey logos. That page is coming when they’re ready to go on record.
How we compare
Half the punchout market won’t publish a price at all. Of the ones that do, Punchout Cloud lists $399/month for a plan including one buyer connection. StackProcure is $199/month for three, and $499/month for unlimited.
Tell us who’s asking
Tell us which buyer asked you for punchout and which platform your catalog runs on. We’ll tell you what it takes, what it costs, and how long it’ll actually take — including if the answer is that we’re not the right fit.