What is Punchout Tester?

Punchout Tester is a free online tool for testing and debugging procurement integration workflows. It supports cXML PunchOut, OCI RoundTrip, and cXML Order protocols, allowing you to simulate buyer-side requests, capture supplier responses, and validate your integration setup without needing a full procurement system.

Do I need to create an account to use Punchout Tester?

No, you can use all testing tools without creating an account. However, creating a free account allows you to save your test session history, reuse credentials with saved presets, and track your testing over time.

Is Punchout Tester really free?

Yes! Punchout Tester is completely free to use with no credit card required. We built this tool to help developers and businesses test their procurement integrations more easily.

Is my data secure?

Yes. All communication is encrypted via HTTPS. We store only the test session data you create (requests, responses, timestamps). We never store sensitive credentials like shared secrets in plain text, and you can delete your session history at any time.

What is cXML PunchOut?

cXML PunchOut is a protocol that allows procurement systems (buyers) to "punch out" to supplier catalogs. Users browse and shop on the supplier's website, then the selected items are returned to the buyer's procurement system as a cart for approval and ordering.

What are the three PunchOut operation types?

The three operation types are:

• create - Start a new shopping session
• edit - Modify an existing cart/order
• inspect - View an existing cart/order without editing

What credentials do I need for testing?

You'll need the supplier's PunchOut endpoint URL and the following credentials:

• From credentials (buyer identity)
• To credentials (supplier identity)
• Sender credentials (usually matches From)
• Shared Secret (password for authentication)

What's the difference between Basic and Advanced mode?

Basic Mode provides a user-friendly form where you fill in fields like credentials, operation type, and user details. The tool generates the cXML request for you.

Advanced Mode lets you write and edit the raw XML directly, giving you full control over the request structure. This is useful for testing edge cases or custom XML structures.

How do I test a PunchOut integration?

1. Go to the cXML PunchOut Tester
2. Enter your supplier's endpoint URL
3. Configure your credentials (From, To, Sender, Shared Secret)
4. Click "Send PunchOut Request"
5. If successful, you'll be redirected to the supplier's catalog
6. Add items to your cart and complete the checkout process
7. The supplier will POST the cart back to our callback URL
8. View the complete request/response and parsed cart items in your session history

What is OCI?

OCI (Open Catalog Interface) is SAP's standard for catalog-based procurement. In an OCI RoundTrip, the ERP system sends parameters via HTTP GET/POST to an external supplier catalog. After shopping, the supplier returns cart data using form fields like NEW_ITEM-DESCRIPTION[1], NEW_ITEM-QUANTITY[1], etc.

What are the key OCI parameters?

Essential OCI parameters include:

• HOOK_URL - The callback URL where cart data is posted
• ~TARGET - Target frame or window
• ~OkCode - Return control code (usually "OK")
• ~CALLER - Identifier for the calling system

What procurement systems support SAP OCI?

Punchout Tester supports OCI integration with over 100 eProcurement systems, primarily SAP-based platforms and OCI-compatible systems:

Note: OCI is primarily used in European markets, especially Germany, while cXML is more common in North American markets.

How do I test an OCI integration?

1. Go to the OCI RoundTrip Tester
2. Enter your supplier's catalog URL
3. Add any custom OCI parameters your supplier requires
4. Our tool automatically generates a HOOK_URL callback
5. Click "Send OCI Request"
6. Shop in the supplier catalog and complete checkout
7. The supplier posts cart data (NEW_ITEM-* fields) to our HOOK_URL
8. View the parsed cart items in your session results

What are NEW_ITEM fields?

NEW_ITEM fields are the format OCI uses to return cart data. Each item in the cart has an index number, and data is sent as NEW_ITEM-DESCRIPTION[1], NEW_ITEM-QUANTITY[1], NEW_ITEM-PRICE[1], etc. Our tester automatically parses these into a readable cart format.

What is a cXML OrderRequest?

A cXML OrderRequest is an XML message that sends a purchase order from a buyer to a supplier. It includes order details like line items, quantities, prices, shipping addresses, and billing information.

When should I use the Order Tester?

Use the Order Tester to validate that your supplier can receive and process purchase orders via cXML. This is separate from PunchOut - PunchOut is for catalog browsing, while OrderRequest is for transmitting actual purchase orders.

What's the difference between test and production deployment mode?

Test mode indicates the order is for testing purposes and should not be fulfilled. Production mode indicates a real order. Always use test mode when validating your integration to avoid creating real orders accidentally.

I'm getting authentication errors. What should I check?

Authentication errors are usually caused by:

• Incorrect shared secret
• Wrong From/To/Sender identity values
• Mismatched domain values (e.g., "NetworkId" vs "networkid")
• Supplier endpoint not configured to accept your credentials

Double-check all credentials with your supplier and ensure they match exactly (credentials are case-sensitive).

The supplier's response shows an error. What do I do?

Check the response XML in your session details. Look for error messages or status codes. Common issues include:

• Invalid endpoint URL
• Supplier system is down or unreachable
• Missing required fields in the request
• Supplier-specific validation errors

I sent a PunchOut request but didn't get redirected to the catalog. Why?

This usually means the PunchOutSetupResponse didn't include a valid StartPage URL, or the request failed. Check your session details to see the full response from the supplier and look for error messages.

How do I report a bug or request a feature?

Use our Contact Form to reach out. We're always looking to improve Punchout Tester and welcome your feedback!

Can I use Punchout Tester for production integrations?

Punchout Tester is designed for testing and validation. While you can test production endpoints, we recommend using it primarily during development and QA phases. For production monitoring, consider implementing your own logging and error handling.

Do you offer integration development services?

Yes! Punchout Tester is built by Takeoff Digital. We offer custom procurement integration development, particularly for Magento/Adobe Commerce. Check out our Magento PunchOut Plugin or contact us for custom solutions.

What e-commerce platforms support PunchOut?

Most major e-commerce platforms can support PunchOut through extensions or custom development:

• Magento / Adobe Commerce (via extensions or custom development)
• Shopify (via apps or custom integration)
• WooCommerce (via plugins)
• BigCommerce (via apps)
• Custom platforms (via API integration)

What procurement systems support cXML PunchOut?

Punchout Tester supports integration with over 100 popular eProcurement systems that use cXML, including: