Common symptoms
No Return to Oracle button
Most likely normal web session, lost PunchOut session, or cart template not rendering the return action.
400 / invalid setup
Check incoming cXML body, endpoint URL, buyer identity, content type, and Shared Secret.
Catalog opens but cart fails
Check product add-to-cart flow, session restore, and PrestaShop cart behavior.
Return fails
Check BrowserFormPost URL, HTTPS, buyer acceptance, and posted payload format.
If Return to Oracle is missing
- Confirm the buyer launched from procurement, not a normal store URL.
- Check logs for setup success and session restore success.
- Add an item and check whether add-to-cart is logged.
- Go to cart and verify PunchOut return action renders.
- If session context is missing, test restore from buyer cookie and URL/session handoff.
Fast customer question
Ask: “After launching from Oracle and adding an item, do you see a Return to Oracle button on the cart page?”Useful log checkpoints
| Checkpoint | Meaning |
|---|---|
| SETUP / IN-SETUP | Incoming request reached the supplier endpoint. |
| SETUP_OUT_OK | Supplier returned a successful setup response. |
| SESSION_SAVE_OK | PunchOut session was stored. |
| RESTORE_SUCCESS | Catalog or cart page restored PunchOut context. |
| ADD_OK | Item was added inside the session. |
| OUT_RETURN_POST | System attempted to post the cart back to buyer. |
Support bundle checklist
- Platform version and PunchOutHub version.
- Screenshot of buyer profile with secrets masked.
- Masked logs around the failed test.
- Exact step where it fails: setup, catalog, add cart, return cart, or PO.
- Sample cXML request if available.