Punchout Setup Guide: How to Connect Your ERP to an External Marketplace
Punchout integration lets your procurement users browse supplier catalogues without leaving their ERP. This guide explains what punchout is, whether you need it, and how to set it up step by step.
What Is Punchout?
Punchout is a standard protocol connecting an enterprise procurement or ERP system to an external supplier catalogue. A user clicks a link inside their procurement system, browses the external catalogue, selects products, and returns with the items already populated in a purchase requisition. No manual entry, no switching between systems.
There are two main punchout protocols in use. cXML (Commerce eXtensible Markup Language) is the most widely adopted, used by SAP Ariba, Coupa, Oracle, and most enterprise procurement platforms. OCI (Open Catalog Interface) is SAP's native integration standard, used within the SAP ecosystem. Both protocols do the same thing: they allow external catalogue browsing from within an internal procurement workflow and return selected items as structured line items.
Do You Need Punchout?
Punchout is the right method if you already run an ERP or eProcurement platform with an active purchasing workflow and want users reaching an external marketplace from inside it. Without it, they visit the marketplace separately and rekey the order.
It pays off most with many users ordering through an ERP, where all activity must run through a governed workflow and purchase order data has to populate the finance system automatically. Without an ERP or eProcurement platform, you do not need punchout: a standalone procurement platform with its own ordering interface is the simpler start.
What You Need Before You Start
- A procurement or ERP system that supports cXML or OCI punchout. Systems with native punchout support include SAP, SAP Ariba, SAP S/4HANA, Oracle, Coupa, NetSuite, and Microsoft Dynamics 365.
- Administrative access to your procurement system to configure external catalog connections.
- IT or ERP administrator availability for initial setup and testing.
- An active account on the external marketplace, with punchout access activated.
For punchout with Borong, punchout access is enabled by your account manager. Contact the Borong team for assistance.
cXML Punchout Setup: Step by Step
Step 1: Request Your Punchout Credentials
The external platform provides a supplier URL, a shared secret or authentication token, and configuration documentation specific to your procurement system. For Borong, contact your account manager or integrations@borong.com. Have these ready before opening your procurement system's configuration.
Step 2: Configure the External Catalog in Your Procurement System
Navigate to the external catalog or punchout configuration section in your ERP or procurement platform. The exact menu path varies by system. Add the external platform as a new supplier catalog. Enter the supplier URL, authentication credentials, and set the catalog type as cXML punchout.
Step 3: Map the Return Basket Fields
When a user selects items and returns to their internal system, the product data must map to the correct requisition fields. Key fields to configure: item description, supplier item number, unit price, currency, unit of measure, and quantity. Also verify that cost centre and tax code fields are mapped correctly for your organisation's chart of accounts setup.
Step 4: Run a Test
Initiate a test punchout session from your procurement system. Confirm the external catalogue loads correctly, that product selections return as structured line items, and that all field mappings are accurate. Test across multiple product categories to confirm consistent behaviour across the catalogue before going live.
Step 5: Go Live and Brief Your Users
Once testing passes, activate the catalog. Send users a short guide on reaching it from the existing workflow, with screenshots of the launch entry point and what to expect on return. Clear communication at launch drives adoption.
OCI Setup
On SAP using OCI, the sequence is the same but runs through SAP's Manage External Catalogs configuration in the materials management or SRM module. OCI authenticates differently from cXML, so request OCI-specific documentation for your SAP version from your external platform's integration team.
Troubleshooting
- Catalog fails to load: Verify the supplier URL and authentication credentials are entered correctly. Confirm your network or firewall is not blocking the external endpoint.
- Return basket fields not mapping correctly: Review the field mapping configuration in your system. Provide a sample return basket XML to the external platform's integration team for diagnosis.
- Currency mismatch: Check that the currency settings in your external platform account match the currency configuration in your procurement system.
- Authentication failures: Credentials may have expired. Contact your account manager to refresh.
Frequently Asked Questions
Can't find the answer you're looking for? Reach out to our customer support team.
Which ERP systems support punchout?
SAP, SAP Ariba, SAP S/4HANA, SAP Business One, Oracle, Oracle NetSuite, Microsoft Dynamics 365, Coupa, and most modern enterprise procurement platforms support cXML punchout. SQL Account and AutoCount, widely used by Malaysian SMEs, do not natively support punchout. For these platforms, direct API integration or a standalone procurement platform workflow is the recommended approach.
How long does punchout setup take?
For a straightforward cXML setup with a procurement system that has native punchout support, configuration and testing typically takes one to three days of IT effort. More complex environments with custom field mappings or non-standard ERP configurations may take longer. Borong's integration team provides support throughout.
Can multiple users share one punchout catalog configuration?
Yes. A single punchout catalog configuration can be made available to all relevant users within your procurement system. User-level catalog access is typically managed through your procurement system's user administration settings, not within the punchout configuration itself.
Is punchout the same as an API integration?
No. Punchout handles the browsing and cart-return workflow: a user selects products from an external catalogue and those selections populate a requisition. API integration handles back-end data flows: purchase order synchronisation, invoice matching, and spend reporting between systems. Most enterprise deployments use both, punchout for the user-facing ordering experience and API integration for the back-end data synchronisation.
Ready to Set Up
Punchout?
Our integration team can walk you through credentials, configuration, and testing for your specific ERP environment.