Skip to content
Gatebold

Gatebold E-Procurement Gateway

From PunchOut cart to Magento order: your catalog in SAP Ariba, Coupa, Jaggaer, etc.

Gatebold handles both steps of the purchase: the cart returned to the procurement system (cXML / OCI PunchOut), then the approved order created in Magento (OrderRequest). No protocol logic in your store, everything traced.

Gatebold·Products·E-Procurement Gateway

What Gatebold solves

Three frictions that make e-procurement integrations painful.

Operational friction

Every new buyer brings its own cXML or OCI format, technical identifiers, mapping rules. Without a shared framework, teams start over every time.

Implementation friction

PunchOut logic ends up in a custom Magento module that is not tested like product code and survives upgrades poorly.

Visibility friction

When an order goes wrong, no one sees what was actually exchanged. Support becomes binary: retry or escalate to developers.

Product model

Platform + connector - two components, one clear responsibility each.

The Gatebold platform owns the protocol and observability. The Magento / Adobe Commerce connector owns the storefront integration. Neither steps on the other.

Gatebold platform

The platform

  • · PunchOut session orchestration
  • · Structured, versioned cXML and OCI mapping
  • · OrderRequest order reception and mapping
  • · Sandbox and production environments
  • · Transaction logs and detailed inspection
  • · Per-buyer and per-catalog configuration

Connector

Magento 2 / Adobe Commerce

  • · Lightweight module, maintained as a real product
  • · PunchOut storefront pages and journeys
  • · Consumes the Gatebold API, re-implements nothing
  • · Compatible with existing B2B architectures
  • · Clear upgrade path between versions

Cart and order

PunchOut and OrderRequest: the cart, then the order in Magento.

Gatebold handles both steps of an e-procurement purchase. PunchOut returns the cart to your customer's procurement system; OrderRequest creates the approved order in your Magento.

1. PunchOut cart

From the procurement system to your catalog, and back

  • · The buyer starts a PunchOut session from SAP Ariba, Coupa, etc. (cXML PunchOutSetupRequest or OCI call)
  • · Gatebold opens a secure session on your Magento, with this buyer's catalog and prices
  • · The cart goes back to the procurement system as a cXML PunchOutOrderMessage or an OCI cart return, mapped to the buyer's rules

2. OrderRequest order

From the purchase order approved on the buyer side to the Magento order

  • · Once the cart is approved on the buyer side, the procurement system sends the cXML OrderRequest to Gatebold
  • · Gatebold validates it, maps it (part numbers, quantities, units, addresses) and pushes it to your connector
  • · The order is created in Magento, ready for fulfilment and invoicing, with every exchange traced in the platform

Per-buyer configuration

Each buyer has its own configuration. Nothing global.

A typical Magento module applies a global config to all buyers. Gatebold lets you configure each connection independently.

Connection mode

Auto-login or classic login, configurable per buyer. Buyers access the catalog directly without unnecessary steps.

Automatic account creation

Each connection decides whether the buyer is automatically created in Magento or must already exist.

Magento customer group

Each buyer can be assigned to a specific customer group (prices, catalog, rules). No global compromise.

Restricted web access

Block direct access to the Magento storefront outside PunchOut, per connection. Buyers must go through their procurement system.

Dedicated mapping

Each buyer has its own cXML and OCI mapping: product codes, units of measure, classifications, custom fields.

Isolated credentials

Technical credentials (shared secret, identities) specific to each connection. No sharing between buyers.

Why this model

What changes for the team, the project, the operations.

  • Faster integration

    A new buyer plugs in based on existing mappings. First exchanges can be tested in sandbox in hours.

  • Cleaner storefront code

    Your Magento does not accumulate cXML or OCI logic. Upgrades stay predictable.

  • Truly effective support

    Every transaction is browsable. Support gives factual answers to end users without paging developers.

  • Explicit governance

    Sandbox / production split, per-buyer permissions, audit traces. Fewer grey areas.

  • Hand-off with integrators

    Technical partners get a shared framework. Less time wasted rediscovering each context.

  • Controlled technical debt

    Protocol logic evolves inside the Gatebold product, not in custom code that decays over time.

Who it's for

The teams that get the most value.

B2B merchants

E-commerce teams that need to connect several e-procurement buyers without slowing the product roadmap.

IT / integration teams

Architecture leads looking for a clean separation between storefront and protocol.

Magento integrators

Agencies and technical partners shipping PunchOut projects without starting from scratch.

Support teams

Customer support that needs to see transactions in order to answer end users.

Pricing

A monthly subscription, starting at 149 EUR/month.

Starter at 149 EUR/month, Professional at 299 EUR/month, Enterprise on request, plus a per-production-connection price for each buyer. Sandbox and test connections are free. Magento connector and onboarding included.

Frequently asked questions

PunchOut, protocols, go-live and pricing.

What is Gatebold E-Procurement Gateway?
It is a native Magento 2 / Adobe Commerce connector paired with a SaaS platform. Together they make your Magento catalog accessible via PunchOut from your enterprise clients' procurement systems, through the cXML and OCI protocols.
Which procurement systems is Gatebold compatible with?
Gatebold supports the cXML PunchOut and OCI protocols, used by the vast majority of e-procurement platforms (SAP Ariba, Coupa, Oracle Procurement, Jaggaer, SAP SRM, etc.). Compatibility is protocol-level: go-live includes a joint validation phase with each final buyer.
What is the difference between PunchOut, cXML and OCI?
PunchOut is the mechanism that lets a buyer browse your catalog from their own procurement system. cXML and OCI are the two protocols that carry these exchanges: cXML is used by Ariba, Coupa, Oracle, etc., while OCI is the historical SAP standard. Gatebold supports both.
Does Gatebold handle the purchase order (cXML OrderRequest) after PunchOut?
Yes. Once the PunchOut cart is approved in your customer's procurement system, it sends a cXML OrderRequest to Gatebold, which validates it, maps it and creates the matching order in your Magento 2 / Adobe Commerce, with no custom code. The cart and the order are two distinct flows, configured per buyer.
Do I need to develop anything in Magento?
No. The Gatebold connector installs like a standard Magento module, and all the protocol logic (cXML, OCI, mapping, sessions) is handled by the SaaS platform. Your store stays focused on e-commerce.
How much does Gatebold E-Procurement Gateway cost?
The subscription starts at €149/month, plus a per-production-connection price for each buyer. Full details of the Starter, Professional and Enterprise plans are on the E-Procurement pricing page.See E-Procurement pricing
What does a go-live with a buyer look like?
Each connection follows the same path: credentials exchange with the buyer's e-procurement team, PunchOut flow configuration, cross-testing in a qualification environment, then production switch. You can follow every cXML or OCI exchange through the platform's observability.

The other Gatebold product

Do you also sell in France from Magento?

Gatebold E-Invoice Gateway connects your Magento to your chosen Approved Platform for the French 2026/2027 e-invoicing reform. DGFiP-compatible solution.

Gatebold E-Invoice Gateway

Discover E-Invoice Gateway

Let's look at your context.

30 minutes to look at your Magento / Adobe Commerce stack, your target buyers, and tell you whether Gatebold fits.