Spryker's preferred PunchOut Partner within the EU

PunchOut for Spryker. Install the plugin instead of building it.

Your B2B customer demands an OCI or cXML connection to your Spryker Commerce OS — in weeks, not months. With the PunchCommerce module for Spryker you install the integration as a Composer package, configure the gateway through a self-service UI, and go live within days. Compatible with SAP Ariba, Coupa, Jaggaer, Mercateo and every system that speaks OCI, cXML or IDS Connect.

For Spryker Commerce OS · Module as public package · Spryker 202507+ · OCI 4.0/5.0, cXML 1.x & IDS Connect · GDPR-compliant hosting in Germany · ISO 9001:2015 certified

Quick start

Four steps to a PunchOut gateway in Spryker

The PunchCommerce module for Spryker is available as a public Composer package. Installation, theme integration, configuration, and the first test run use the familiar Spryker tooling — no custom development, no agency.

1

Install the module

Pull the Composer package into your Spryker instance via the Spryker Docker SDK. Requirements: Spryker 202507+ and PHP 8.2.

2

Adjust the theme

Drop a few hooks into your Yves theme: a PunchOut login button and cart transfer wiring. Typically done in minutes — we ship the code snippets.

3

Configure the gateway

Set the API endpoint of your PunchCommerce gateway in the Spryker config. You then manage customers, protocols, and field mappings through the self-service UI — without code.

4

Go live

PunchOut sessions, cart transfer, and customer-specific profile data work from day one. Run them in the PunchOut simulator, then roll out to your enterprise customer.

Installation via Spryker Docker SDK
docker/sdk cli "composer require punchcommerce/punchcommerce-spryker-module"
View module on GitLab

Source publicly visible · License: proprietary · Actively maintained by netzdirektion

Value

Why PunchCommerce for Spryker

Four reasons Spryker operators choose the ready-made module over building it themselves.

Plugin instead of custom build

Ready-made Composer package with active maintenance. No custom code, no agency weeks — one Composer command, then configure.

Spryker-native integration

Clean extension of the Customer, Cart, Session, and Persistent Cart bundles. Follows Spryker standards, update-safe, visible in the back office.

Every protocol from day one

OCI 4.0/5.0, cXML 1.x, and IDS Connect 2.5 — cleanly validated, versioned, and tested. SAP Ariba, Coupa, Jaggaer, Mercateo ready to connect.

Fast ROI

Go live in days, not months. Our Spryker customers achieve an average of 150–200 orders per enterprise buyer per year through PunchCommerce.

Maximum compatibility

Spryker to every e‑procurement system — through one gateway

The PunchCommerce module connects your Spryker instance to the central PunchCommerce gateway. From there you speak OCI, cXML and IDS Connect with every major procurement platform — without writing new code per customer.

How your data flows

Every procurement system connects to your Spryker shop through the PunchCommerce gateway. Live, secure, validated.

Data flow between e‑procurement systems, the PunchCommerce gateway, and your Spryker instance Multiple procurement systems send requests via the PunchCommerce gateway to Spryker Commerce OS. Connections are secure and standards‑compliant. Ariba Jaggaer Mercateo Coupa OCI, cXML, IDS 2.5 Spryker Commerce OS

Protocols

OCI 4.0 OCI 5.0 cXML 1.2 IDS-Connect PunchOut Order Request* Order Confirmation*

We speak OCI, cXML and IDS Connect through a unified API — cleanly validated, versioned, and tested.

* Available only with PunchCommerce Enterprise.

Spryker editions & requirements

The module integrates seamlessly with Spryker Commerce OS — compatible with B2B and B2C suites.

Spryker B2B Suite
Spryker B2C Suite
Spryker Cloud Commerce OS
Spryker Marketplace Suite
Spryker 202507+
PHP 8.2+

Fast implementation

  • Module installed via Composer in minutes — no custom build in your project.
  • Visual mapping: Map fields between Spryker and procurement platforms — no code.
  • PunchOut simulator: Testable flows before your enterprise customer goes live.

System names are mentioned for compatibility reference only.

Security & compliance

Trust through quality and transparency

PunchCommerce is operated by netzdirektion | Gesellschaft für digitale Wertarbeit mbH—certified, GDPR‑compliant, and hosted in Germany.

Hosting in Germany

Operation in German data centers with a strict access and authorization model. VPC isolation, encryption at rest & in transit.

Data location: DE

GDPR compliance

Data Processing Agreement (DPA), data minimization, audit logging, and defined retention policies. On request: tenant‑specific data rooms.

Privacy by Design

ISO 9001:2015

netzdirektion is certified to ISO 9001:2015 — ensuring quality, security, and continuous improvement.

ISO 9001 Badge

99.9% uptime guarantee

Proactive monitoring, health checks, and redundant components. Custom SLAs on request.

Monitoring & SLAs

Selected references

Companies that trust us

Phoenix Contact Pharmaserv Logistics Klüh Multiservices

FAQ

Häufige Fragen

Kurz & konkret beantwortet – zu Technik, Datenschutz, Einführung, Kosten, Support und Roadmap.

The module is a Composer package (punchcommerce/punchcommerce-spryker-module) installed via the Spryker Docker SDK: docker/sdk cli "composer require punchcommerce/punchcommerce-spryker-module". Afterwards you set the API endpoint of your PunchCommerce gateway in the Spryker default config.
Yes — a handful of small changes to the Yves theme: a PunchOut login button in the header and hooks for cart transfer. This is typically done in minutes — we ship ready-to-use code snippets you can drop straight into your Twig templates.
The module requires Spryker 202507 or newer and PHP 8.2+. It integrates with the standard Customer, Cart, Persistent Cart, Session, and Kernel bundles — so it is compatible with Spryker B2B Suite, B2C Suite, and Cloud Commerce OS.
Yes. The module follows Spryker standards and does not require infrastructure changes. It can be integrated with any Spryker instance that supports Composer packages — including Spryker Cloud Commerce OS.
Connectivity runs through the central PunchCommerce gateway, which speaks OCI 4.0/5.0, cXML 1.x and IDS Connect 2.5. That covers SAP Ariba, Coupa, Jaggaer, Mercateo, Onventis and every other e-procurement system using one of these standards.
The source code is publicly visible on gitlab.netzdirektion.de; commercial use is covered by a proprietary license under your PunchCommerce contract. Updates, security patches, and Spryker compatibility are actively maintained by netzdirektion.
Yes. The module follows the Spryker extension model with dependency injection and plugin classes. Customizations are done via project modules without modifying the original module — keeping it update-safe.
We test the module against current Spryker releases and ship new versions whenever Spryker introduces breaking changes. The Composer constraints are chosen so that you can apply Spryker patches and minor updates without changing the module.
Module installation and gateway configuration take a few hours. A productive PunchOut connection to an enterprise customer (mapping, tests, go-live) is typically done in 1–2 weeks. Multi-customer scenarios scale through the self-service UI.
A PunchOut simulator is available in the PunchCommerce admin. Use it to test OCI and cXML sessions end-to-end against your Spryker shop without your customer's procurement system being involved.
The module itself is part of your PunchCommerce contract. Pricing (Business at €49/month per customer or Enterprise with SLA and custom pricing) is detailed under PunchCommerce Business and Enterprise. For Spryker setups we recommend a 30-minute consultation to pick the right plan.

Persönlicher Kontakt

Speak directly with the founder

No sales pitch — a technical, honest conversation about your Spryker integration.

Antwort i. d. R. innerhalb von 24h Gründer‑Geführt • Technischer Deep‑Dive möglich
PunchCommerce® ist ein Produkt der Netzdirektion GmbH