Troubleshooting
When the integration doesn’t work
Diagnostic write-ups for the failures that actually stop a go-live. Each one answers in the first paragraph and orders the causes by how often they turn out to be the culprit.
PunchOutSetupRequest returns 401 Unauthorized The buyer clicks your catalogue and their system reports an authentication failure. Your endpoint logs a request but rejects it, or the buyer sees a cXML Response with a 401 status. The cart does not come back to the buyer The shopper reaches your checkout, clicks the button that should send them back, and either nothing happens or they land in their procurement system with an empty requisition. cXML DTD validation failed The buyer rejects your document with a DTD or schema validation error, often quoting an element name that looks perfectly correct in your output. PunchOut opens a blank page The buyer clicks through and gets a white screen, a frame that never loads, or your site loading but immediately logging them out. The buyer rejects your UNSPSC codes A cart or catalogue is rejected citing classification, or lines arrive uncategorised and fail to route for approval. Unit of measure mismatch The cart arrives, the lines look right, and the price is wrong — or the buyer reports that your unit is not one their system accepts. The PunchOut session times out The shopper is dropped mid-session, sent back to a login, or finds their basket empty after browsing for a few minutes.
Check the document before you check anything else
Most rejections are structural and visible without involving the buyer at all. Our free tester runs in your browser — nothing is uploaded.
Open the tester OCI referenceStuck on something not listed here?
Send us the error and the document that produced it. If the answer is quick we will just tell you.
Start a conversation See pricing