A supplier to test your punchout against
Free, hosted, and running right now. Point your buyer system at it and find out what your documents actually look like to the other side.
The problem this solves
Every free punchout tool runs the wrong way round. They simulate a buyer, so a supplier can check their catalogue works. If you are building the buyer side, there is nothing to point at — so you end up testing your integration against itself.
Round-tripping your own build and parse proves the two halves agree with each other. It does not prove either one conforms. If both share a misreading, every test passes and the first real supplier rejects every document.
What is missing is an independent judge. This is one.
What you can do with it
| Punch out | POST a real PunchOutSetupRequest, get a
StartPage, shop a catalogue of 96 products with
genuine UNSPSC codes, and receive a conformant
PunchOutOrderMessage back. |
|---|---|
| Send an order | POST an OrderRequest and be told what is wrong
with it — including whether your header
Total reconciles with the sum of its lines. |
| Receive documents | Have order confirmations, ship notices and invoices POSTed to your own cXML inbox, so you can test the half of the flow nobody can normally test. |
| See what survives | Apply a buyer platform's ingestion rules to your cart and find out what it would actually store. A valid document can still arrive with the wrong price. |
| Validate anything | Paste any cXML document into the validator and get a verdict against the real DTDs. No account needed. |
| Use SAP OCI | Full call-up support including DETAIL,
VALIDATE and BACKGROUND_SEARCH. |
Reference: what actually breaks a punchout
cXML imposes almost no length limits. Every limit that truncates your data is imposed by the buyer platform, and none of them publish it. These pages write down what we have been able to establish.
cXML field limits by platform — what actually breaks a punchout
Why your Description arrives truncated at 254 characters, why leading zeros vanish from part numbers, and why the schema said it was fine.
cXML InvoiceDetailRequest — the rules that fail validation
The four things everyone gets wrong in an invoice, and multi-country VAT, GST and sales tax with the reasoning shown.
ConfirmationRequest and ShipNoticeRequest — cXML fulfilment
Order confirmation and dispatch, including the rules the DTD cannot express and the buyer enforces anyway.
SAP OCI field limits — NEW_ITEM lengths and HOOK_URL failures
SAP SRM's Open Catalog Interface: field lengths, the FUNCTION values, and the charset trap.
The honest limits
| It is a sandbox | Synthetic catalogue, invented companies, no SLA, no support contract. Nothing you send is stored beyond a week and none of it is looked at. |
|---|---|
| It stays free | There is no paid tier and no upgrade prompt. If it saves you a day, there is a coffee link. |
| It is open source | github.com/njp970/punchoutsandbox — including every conformance rule it enforces. |