Three testers. One timeline.
Each run is saved to Session History with the full request, response and returned cart.
01
cXML PunchOut
PunchOutSetupRequest → StartPage → PunchOutOrderMessage.
- ◆create / edit / inspect
- ◆BrowserFormPost Captured Automatically
- ◆Cart Items Parsed
- ◆Basic & Raw XML Modes
OCI RoundTrip
Launch an OCI catalog and catch the NEW_ITEM-* fields posted to HOOK_URL.
- ◆~TARGET, ~OkCode, ~CALLER
- ◆Custom Parameters
- ◆GET or POST Launch
- ◆Auto-generated HOOK_URL
cXML Order
Build an OrderRequest, send it, and read the supplier’s status.
- ◆Visual OrderRequest Builder
- ◆Line Items + Classification
- ◆Ship-to / bill-to
- ◆Test vs Production
Built-in Mock Supplier
No supplier handy? Point any tester at these endpoints, or use the Use Mock button on each form.
cXML PunchOut
https://punchout-tool-suite.vercel.app/mock/cxml/punchoutOCI RoundTrip
https://punchout-tool-suite.vercel.app/mock/ocicXML Order
https://punchout-tool-suite.vercel.app/mock/cxml/orderA shared secret of invalid makes the mock PunchOut endpoint return a 401 status, so you can see error handling.
cXML document types
PunchOutSetupRequest— starts a punchout sessionPunchOutSetupResponse— supplier returns the catalog StartPage URLPunchOutOrderMessage— cart returned via BrowserFormPostOrderRequest— purchase order sent to the supplier
OCI Parameters
HOOK_URL— where the catalog posts the cart~OkCode / ~TARGET / ~CALLER— session controlNEW_ITEM-DESCRIPTION[n],NEW_ITEM-QUANTITY[n], …NEW_ITEM-LONGTEXT_n:132[]— long text