Skip to main content
Talk to an expert
PunchOut logo

PunchOut integration for B2B and procurement commerce

B2B buyers order from their procurement system, not yours. iWeb connects your catalogue, pricing contracts and order workflow to procurement systems like SAP Ariba, Coupa and Jaggr so buyers place purchase orders without leaving their native tools. Orders land in your ERP validated and mapped. Shipments and invoices flow back automatically. Works with Adobe Commerce, Magento Open Source, Shopify Plus, BigCommerce and other storefronts.

Also searched as: B2B integration, procurement, PunchOut, cXML, OCI, EDI, PEPPOL, account-based commerce.

PunchOutiWeb integration layeryour storefront
Talk to an expertSee the estate map ↓
Works with - Adobe Commerce · Magento Open Source · Custom B2B storefronts · SAP Commerce Cloud · Other storefronts
On this pageGet a brief reviewed
01 · What you get

What a PunchOut integration gives you.

Buyers order from their procurement system

No portal switching, no manual PO entry, no email or phone order placement. Buyers browse your catalogue, place orders and see status within their own procurement workflow.

Orders land in ERP or OMS without rework

Purchase orders arrive with all required fields (cost centre, approval signatures, buyer contact, ship-to address) validated and mapped. Finance and operations teams do not have to chase missing data.

Procurement teams see shipments and invoices on-time

ASNs and tracking data flow back automatically. Buyers do not phone your warehouse asking for tracking; their procurement system shows delivery status as it updates.

Contract pricing and approvals are enforced

Each buyer sees only their approved SKUs at their contracted prices. Your sales and finance teams do not have to police off-contract orders; the system enforces the rules.

02 · When it's worth it

Where a PunchOut integration earns its place.

If two or more of these are true, the integration usually pays for itself quickly.

Allow large enterprise buyers to launch your catalogue within their procurement system without leaving their workflow
Publish buyer-specific pricing, contracts and product availability through PunchOut sessions
Capture purchase orders from procurement systems and route them into ERP, OMS or order queues with validation
Support multiple authentication methods (OAuth, SAML, basic auth) for buyer account linking
Handle order acknowledgements, shipment notifications and invoice exchange through structured messages
03 · The limits

Where off-the-shelf connectors fall short.

Vendor connectors are fine for simple cases. Here's where the real ones need more.

Generic catalogue may not respect buyer contracts

PunchOut platforms often deliver a static product feed to all buyers. Your buyer contracts, tiered pricing, approved-SKU lists and regional availability rules may not be enforced in the PunchOut session without custom integration work.

Order mapping and format gaps

Buyers may send purchase orders with fields, cost-centre codes or approval workflows that your ERP does not understand. Off-the-shelf connectors often drop unmapped fields or fail silently, leaving gaps in order data or requiring manual rework.

ASN and tracking acknowledgement delays

Most PunchOut solutions do not automatically send shipment confirmations and tracking data back to the buyer's system. Buyers see order status in your portal but not in their procurement system, creating double-checking and manual follow-up.

EDI and PEPPOL format variance

Different buyers expect different EDI dialects, segment orders or PEPPOL profiles. A single generic connector rarely handles the variation needed for multinational or multi-sector accounts without repeated configuration or custom coding.

Credential and session expiry handling

PunchOut sessions time out or credentials drift without clear visibility. Orders may queue up silently if authentication fails, or buyers may be locked out without notification to your operations team.

04 · The real work

Buyer procurement systems speak different languages and enforce different approval workflows; the real work is enforcing your contracts and keeping status synchronized without breaking the buyer's month-end or payment timeline.

05 · Where it sits

Where this integration sits in your estate.

PunchOut holds the commercial record. The iWeb integration layer manages the rules, mappings, monitoring and exceptions. The commerce platform presents the customer-facing experience. The estate map helps agree ownership before anything is built.

Commerce platform agnostic. Connect PunchOut across your entire technology stack.

System of record
Source / owner
PunchOut
PunchOut procurement integration layer between buyer systems and your ERP
  • Buyer procurement session and catalogue launch
  • cXML, OCI and EDI message exchange
  • Buyer contract pricing and approval rules enforcement
  • Purchase order intake and validation
  • Order acknowledgement and shipment tracking relay
  • Invoice and credit note exchange with buyer systems
iWeb integration layer
Customer-facing commerce
Commerce platform
Adobe CommerceMagento Open SourceCustom B2B storefrontsSAP Commerce CloudOther storefronts
  • Storefront product catalogue and inventory
  • Cart and checkout for non-PunchOut buyers
  • Customer account and session management for direct orders
Connected neighbours
Integration layer
ERP
Source of buyer master data, contracts, pricing, inventory, orders, acknowledgements, invoices and credit notes.
Integration layer
Contract management system
Holds buyer-specific pricing, approved SKU lists, payment terms and volume tiers that iWeb enforces at PunchOut session time.
Integration layer
WMS or logistics
Provides shipment confirmations, ASNs and tracking data that iWeb sends back to buyer procurement systems.
Integration layer
Buyer procurement systems
SAP Ariba, Coupa, Jaggr, BravoSolution and others; iWeb handles protocol translation and session lifecycle.
Integration layer
Identity and access control
Manages buyer account credentials, OAuth / SAML tokens and SSO so procurement system logins sync with your user directory.
Two-way sync where relevant
06 · Surrounding systems

Systems this integration usually sits next to.

Examples, not a closed list. iWeb is platform-agnostic on both sides: we wire this integration into whatever ecommerce platform and surrounding systems your estate already runs.

Ecommerce platforms (examples)
  • Adobe Commerce
  • Magento Open Source
  • Custom B2B storefronts
  • SAP Commerce Cloud
  • Other storefronts
Surrounding systems (examples)
  • SAP Ariba
  • Coupa
  • Jaggr
  • BravoSolution
  • ERP (SAP, Oracle, NetSuite, Sage)
  • Order management system (OMS)
  • Warehouse management system (WMS)
  • Contract management platform
Not sure?

Not sure if this works with your stack?

Tell us what you’re using and what needs to connect. We’ll give you a straight view on what’s possible, what might be awkward, and the safest way to approach it.

07 · Data flows

The data flows we wire.

Each flow has a direction and an owner. We agree both before a line of code is written.

→Into BUYER SYSTEM
←From BUYER SYSTEM & ERP
↔BOTH WAYS
PunchOut catalogue launch: When a buyer logs in to their procurement system, iWeb retrieves the session request (cXML or OCI), looks up buyer-specific catalogue, pricing and contracts, and delivers a browsable product catalogue within the buyer's portal
The buyer sees only approved products and their negotiated prices.
Purchase order intake: When a buyer confirms an order in their procurement system, PunchOut sends the purchase order message back through cXML, OCI or EDI
iWeb validates the order against buyer contracts, inventory and credit rules, then hands it to your ERP or OMS for processing.
Order acknowledgement and shipping data: After the order is confirmed in your ERP or OMS, iWeb sends order acknowledgements, ASNs (advance shipment notices) and tracking information back to the buyer's procurement system so they see fulfillment status without checking a separate portal.
Invoice and credit note exchange: Once goods ship, iWeb extracts invoice and credit note data from your ERP and sends them to the buyer's procurement system in the format they expect (cXML, EDI, PEPPOL), aligned to their PO numbers and accounting codes.
Contract pricing and buyer master data: Buyer-specific pricing, contract terms, approved product lists and payment terms flow from your ERP or pricing system into the PunchOut catalogue, and buyer account changes (credit limits, contact updates) sync back to both systems.
08 · How we build it

How iWeb configures the integration around your business.

Same method on every integration. The decisions come before the code.

  1. 01
    Design buyer-specific catalogue logic

    iWeb defines which products, pricing tiers, lead times and inventory thresholds each buyer sees based on their contract, account status and regional rules. Catalogue filtering happens at session start, not after order capture.

  2. 02
    Map and validate purchase order data

    iWeb captures cXML, OCI or EDI purchase orders, maps buyer-specific fields (cost centre, approval workflow, custom attributes) to your ERP schemas, validates against contracts and credit limits, and routes to the right queue (drop-ship, standard, special order).

  3. 03
    Orchestrate order acknowledgement and shipment flow

    iWeb extracts order status, ASNs and tracking from your ERP or WMS and sends them back to the buyer's procurement system in their preferred format (cXML, EDI, PEPPOL) so buyers stay in sync without manual updates.

  4. 04
    Manage authentication and session lifecycle

    iWeb handles OAuth / SAML login, session token generation, buyer account linking and credential refresh so buyers log in once and stay authenticated throughout the PunchOut session without security compromises.

  5. 05
    Monitor order flow and flag exceptions

    iWeb maintains a queue of inbound purchase orders, tracks acknowledgements back to the buyer system, flags orders stuck in validation or payment holds, and alerts your operations team to contract mismatches or mapping errors.

09 · Ownership

Who owns what.

The single most important table in any integration. One system owns each field; everything else reads it.

Data
Source / owner
Maintained by
Notes
DataBuyer catalogue and product list
Source / ownerERP or master product data system
Maintained byProduct and procurement team
NotesiWeb filters the master list by buyer contract and approval rules at PunchOut session time.
DataBuyer-specific pricing and contract terms
Source / ownerERP pricing module or contract management system
Maintained bySales and procurement leadership
NotesiWeb retrieves contract pricing at catalogue build time and enforces it at order validation.
DataPurchase orders and order capture
Source / ownerERP or OMS
Maintained byOperations and order management team
NotesiWeb receives cXML / OCI / EDI purchase orders, validates and maps them, then hands off to ERP or OMS.
DataOrder acknowledgements, ASNs and shipment tracking
Source / ownerERP, WMS or OMS
Maintained byFulfilment and logistics team
NotesiWeb extracts acknowledgement and dispatch events from ERP / WMS / OMS and sends them back to buyer procurement system.
DataInvoices, credit notes and payment terms
Source / ownerERP finance module
Maintained byFinance and accounting team
NotesiWeb retrieves invoices and credits from ERP and exchanges them with buyer procurement system in agreed EDI or PEPPOL format.
DataBuyer account, credit limit and approval workflow
Source / ownerERP or CRM
Maintained byCustomer service and credit control
NotesiWeb enforces credit and approval rules at order validation and syncs account changes with PunchOut session logic.
10 · Experienced integrator

Built this before

iWeb has built PunchOut integrations for B2B sellers across trade, manufacturing, foodservice and industrial sectors. We understand how procurement systems work, how to enforce buyer contracts, how to handle EDI and PEPPOL variants, and how to keep orders, acknowledgements and invoices in sync without breaking month-end or audit timelines.

iWeb has handled cXML, OCI, EDI and PEPPOL protocols for different buyer procurement systems (SAP Ariba, Coupa, Jaggr, BravoSolution) in parallel against a single ERP.
iWeb designs buyer catalogue filtering and contract-pricing enforcement at session start so pricing mismatches and unapproved orders are caught before they land in ERP.
iWeb orchestrates order acknowledgements, ASNs and tracking back to buyer procurement systems so buyers see fulfilment status without leaving their native tool.
iWeb manages PunchOut session lifecycle, token refresh and authentication drift so buyer credentials stay in sync with your identity and account systems.
iWeb maintains exception queues and monitoring for orders that fail validation, missing ASNs, invoice format errors and silent delivery failures so your operations team is alerted before buyers call.
11 · Before launch

What we test before launch.

Every one of these is rehearsed before a customer ever sees the integration.

Verify buyer catalogue is filtered correctly: each test buyer sees only their approved SKUs at their contracted prices.
Validate purchase order parsing: capture a real buyer PO (cXML, OCI or EDI), confirm all fields map to ERP, and confirm validation rules (credit limit, approval workflow) execute as expected.
Check order acknowledgement round-trip: confirm order is accepted in ERP and acknowledgement message is sent back to buyer procurement system within SLA.
Test ASN and tracking relay: ship a test order, confirm shipment event flows from WMS to buyer procurement system with correct tracking and delivery estimate.
Confirm invoice exchange: generate a test invoice in ERP, confirm it is sent to buyer procurement system in correct EDI or PEPPOL format, and linked to original PO.
Verify session timeout and re-authentication: let a buyer session expire, confirm re-authentication prompt is clear and new session re-establishes without losing cart or order state.
Load test during peak: simulate multiple concurrent buyer sessions and concurrent purchase order inbound traffic; confirm response time and queue depth stay within acceptable limits.
12 · Failure points

Common risks and where they bite.

We name these on day one. A risk written down is a risk you can plan around.

Purchase orders queue silently when validation fails

If a buyer PO fails contract validation (unapproved SKU, credit hold, pricing mismatch), the order may sit in a queue without notification to the buyer or your operations team. Days pass before anyone discovers the hold.

Buyer accounts drift between PunchOut and ERP

A buyer's credit limit, approval workflow or contract terms change in your ERP but the PunchOut session still enforces the old rules. Or a new buyer is added to ERP but is not yet set up in PunchOut, causing order rejections.

ASNs and tracking do not reach the buyer system

Your WMS or ERP sends shipment confirmations but they never make it back to the buyer's procurement system. Buyers phone your warehouse asking for tracking status, creating unnecessary support load.

EDI or PEPPOL format errors cause invoice rejection

Your ERP generates invoices in one EDI format but the buyer expects a different segment order or PEPPOL profile. The invoice fails procurement validation and your accounts team has to reissue or manually correct the data.

PunchOut session expires mid-order

Buyer credentials time out, OAuth tokens expire, or session state is lost. The buyer is logged out mid-checkout without clear feedback. They re-authenticate and place a duplicate order, or give up.

13 · Where it applies

Relevant services and sectors.

14 · Questions

Common questions about PunchOut integrations.

What is PunchOut and how does it differ from a standard B2B portal?

PunchOut is a procurement-system integration standard that allows buyers to launch your product catalogue from within their own procurement system (SAP Ariba, Coupa, Jaggr, etc.) using cXML, OCI or other procurement protocols. Unlike a portal, the buyer never leaves their procurement workflow; they browse your catalogue, place orders and see status within their native system. iWeb handles the authentication, catalogue filtering, order capture and status synchronisation.

What procurement protocols does iWeb support?

iWeb supports cXML (most common), OCI (Oracle), EDI (ANSI X12, EDIFACT), PEPPOL and custom protocols depending on your buyer base. Different buyer procurement systems speak different languages. iWeb can connect multiple protocol versions to a single ERP or OMS so you do not have to.

How do we enforce buyer-specific pricing in a PunchOut session?

iWeb retrieves each buyer's contract pricing, approved SKU list and volume tiers from your ERP at session start. When the buyer logs in, their catalogue is pre-filtered and pre-priced before they see it. If a buyer tries to order an unapproved product or at a non-contracted price, the order is rejected at validation time with a clear reason.

What happens when a purchase order arrives from a buyer?

iWeb receives the order message (cXML, OCI, EDI), parses it, maps buyer-specific fields to your ERP schemas (cost centre, approval workflow, custom attributes), validates against their contract and credit limit, then hands off to your ERP or OMS. If validation fails, the order queues for manual review and your operations team is alerted.

How do buyers see order status and tracking after they place an order?

iWeb extracts order acknowledgement, shipment status and tracking data from your ERP or WMS and sends it back to the buyer's procurement system in their preferred protocol (cXML, EDI, PEPPOL). Buyers see delivery status within their own system without logging into a separate portal.

How are invoices and credit notes exchanged with buyer procurement systems?

iWeb retrieves invoice and credit note data from your ERP, maps it to the buyer's expected EDI or PEPPOL format, links it to the correct purchase order, and sends it to the buyer's procurement system. The buyer's account payable team receives the invoice in their native tool, reducing manual reconciliation.

What happens if a PunchOut session times out or authentication fails?

iWeb manages session tokens, OAuth / SAML credentials and timeout policies. If a session expires, the buyer is prompted to re-authenticate. iWeb logs all authentication events so you can monitor for credential drift or repeated failures that might indicate a problem buyer account.

Can we support multiple buyer procurement systems at once?

Yes. iWeb can handle different procurement systems (SAP Ariba, Coupa, Jaggr, BravoSolution, etc.) in parallel, each with their own protocol, pricing rules and order workflows. A single ERP integration layer handles the variation.

How do we handle buyer accounts that require approval workflows?

iWeb enforces approval workflows defined in your ERP or order management system. If a purchase order exceeds a buyer's approval threshold or cost centre limit, iWeb holds the order and routes it to the appropriate approval queue. Once approved, the order proceeds to fulfillment.

What happens to orders that fail validation?

iWeb maintains an exception queue for orders that fail validation (unapproved SKU, contract mismatch, credit hold, incomplete data). Your operations team is alerted, can review the reason, and either approve the order with an override or reject it with a reason sent back to the buyer.

Can PunchOut pricing be different from our online store pricing?

Yes. Your online store and PunchOut catalogue can have different pricing, lead times, inventory thresholds and product lists. iWeb pulls pricing from your contract management or ERP system at session time, so each channel sees the rules you define for it.

How do we know if a PunchOut order has reached the buyer's system?

iWeb tracks acknowledgements. When your ERP confirms an order, iWeb sends an acknowledgement message back to the buyer's procurement system. iWeb logs whether the acknowledgement was received or if it failed, so you can monitor delivery rates and catch silent failures.

What happens during a buyer's month-end or audit deadline?

iWeb ensures orders, acknowledgements and invoices flow on schedule. If your ERP or procurement system has maintenance windows, iWeb queues messages and retries with exponential backoff. Critical dates for payment or delivery visibility are not disrupted by synchronisation delays.

Can iWeb help us migrate existing PunchOut buyers from another platform?

Yes. iWeb can run parallel PunchOut connections during migration, switch buyer sessions from old to new endpoints, and reconcile orders, acknowledgements and invoices to ensure no data is lost during the cutover.

Next step

Have a PunchOut integration brief?

Send the brief, or tell us what is breaking. You will get a written response from a senior expert: the integration boundary, the realistic shape, the risks worth naming, and what it takes to support after launch.
Talk to an expertOr browse all integrations →