A supplier we know of had the better product. Lower price, too. They still lost the contract.

SAP Ariba, Coupa, Oracle Procurement Cloud and E-Business Suite, and JAGGAER, plus other systems that speak standard cXML or OCI. If your buyer uses something less common, send us what they have given you and we will tell you whether it is supported before you commit to anything.

The build is two to four weeks for a PunchOut catalogue against an existing site, three to six weeks when purchase orders and invoicing are included, and four to eight weeks when the catalogue itself needs building. What follows is the buyer’s own testing queue, which is usually the longer half and which no supplier or vendor controls.

Yes, directly with the buyer’s technical team — connectivity setup, cXML validation, test order cycles and go-live approval. This is the part suppliers most often underestimate, and handing it back to you would defeat the purpose of outsourcing the integration.

Additional buyer connections are $450 once, not a recurring fee. Your monthly cost is set by the tier you are on, not by how many buyers are connected to it — a supplier with four buyers pays the same monthly figure as one with a single buyer.

That is the Full Enablement tier. We consolidate whatever product data you have, structure and classify it, build a catalogue site designed for procurement buyers, and connect it. Most of the work is the data rather than the site.

Orders arrive as structured data instead of emailed PDFs, so nobody rekeys them and rekeying errors stop reaching your invoices. Your catalogue becomes the default path inside the buyer’s system rather than something they have to raise a manual requisition against. We are a new company and will not quote you efficiency statistics we have not measured — but that is the mechanism, and it is why buyers mandate it.