Skip to main content
CCI
SAP Commerce Cloud specialists

SAP Commerce, connected.

We keep ERP, PIM, CRM, payment, marketplace, and analytics contracts intact while SAP Commerce modernization moves through cutover.

Book a strategy callBook a strategy callReview servicesReview services

SAP Commerce Cloud

ERP

PIM

CRM

Payments

Focused practice

SAP Commerce only. No platform sprawl.

The work sits in extension layers, OCC contracts, ImpEx cutovers, Solr indices, Backoffice workflows, and Composable Storefront delivery.

OCC / Commerce REST API

OCC v2

Custom OCC v2 controllers, DTOs, and facades for headless storefronts, mobile apps, and ERP integrations.

Spartacus / Composable Storefront

SSR

Angular SSR storefront delivery with CMS component mapping, libs, theming, and CCv2 deploy pipelines.

ImpEx & data migration

ImpEx

Catalog imports, staged versioning, cronjob automation, and cutover validation for go-live and ongoing sync.

FlexibleSearch & Solr performance

Solr

Query rewrites, index strategy, region-cache tuning, and autoscaling for sub-200ms PLPs at production scale.

News

Releases and announcements from the CCI open source work on SAP Commerce.

Open source

SAP Commerce Stripe Connector released as open source

A Stripe integration for SAP Commerce Cloud, published under the MIT license: hosted Stripe Checkout, inline Payment Elements with PaymentIntent confirmation, signature-verified webhook processing, payment lifecycle handling mapped to Commerce transaction states, and OCC endpoints for Composable Storefront checkout.

View the repository

Connected SAP Commerce, without brittle edges.

CCI designs the integration layer around SAP Commerce ownership boundaries: OCC contracts, CPI flows, OPF payment adapters, ERP pricing, PIM catalog data, and CRM customer state.

OCC / CPI / OPF

Integration review starts at the contract.

We inspect payload shape, retry semantics, idempotency keys, timeout budgets, and failure queues before changing code. The result is a connection map your platform team can operate.

Transport
CPI iFlows, OCC v2, webhooks, hot folders
Payments
SAP OPF adapters, PSP captures, refunds, 3DS flows
Data
ERP pricing, PIM catalog deltas, CRM account updates
Middleware

SAP CPI

Payments

SAP Open Payment Framework

ERPEnterprise systems

ERP connectors

PIMCatalog data

PIM connectors

PSP, tax, CRM, and order flows live in the full service scope.

The home page shows the core integration families. The service page breaks down payment gateways, retries, security, and delivery artifacts.

Review integration services

Open source for the SAP Commerce workbench.

Reusable connector, analysis, MCP, and agent tooling maintained in public for teams working in SAP Commerce Cloud.

SAP Commerce Stripe Connector

A MIT-licensed SAP Commerce connector for Stripe Checkout, Payment Elements, webhooks, OCC, and Composable Storefront checkout.

  • Hosted Checkout and inline Payment Elements flows.
  • Signature-verified webhook processing and transaction-state mapping.
  • OCC endpoints for sessions, PaymentIntents, finalization, and refunds.

SAP Commerce Stripe Connector

hybris/bin/modules/stripe/stripebackoffice/src/com/cci/hybris/stripe/backoffice/constants/StripebackofficeConstants.java

View repository
/*
 * SPDX-License-Identifier: MIT
 * Copyright (c) 2026 Commerce Cloud Integrations
 */

package com.cci.hybris.stripe.backoffice.constants;

import java.util.List;

/**
 * Constants used by the Stripe backoffice extension.
 */
public final class StripebackofficeConstants extends GeneratedStripebackofficeConstants
{
	public static final String EXTENSIONNAME = "stripebackoffice";
	public static final String STRIPE_SECRET_KEY = "stripe.secret.key";
	public static final String STRIPE_PUBLISHABLE_KEY = "stripe.publishable.key";
	public static final String STRIPE_WEBHOOK_SECRET = "stripe.webhook.secret";
	public static final String STRIPE_CHECKOUT_SUCCESS_URL = "stripe.checkout.success.url";
	public static final String STRIPE_CHECKOUT_CANCEL_URL = "stripe.checkout.cancel.url";

Stripe is a trademark of Stripe, Inc.

The work we take on.

Three engagement shapes cover most SAP Commerce estates: platform upgrades, storefront replacement, and performance recovery. Client-named outcomes will be published only with their approval.

Platform upgrade

A rehearsed, reversible cutover

Challenge
Legacy Hybris landscapes with fragile ERP pricing and unowned accelerator customizations.
Delivered
A 2211 upgrade path with pricing isolated behind retry-safe facades, and catalog/customer migration rehearsed before cutover.
Diagram of SAP Commerce storefront, OCC, platform, data, and runtime control surfaces
A typical SAP Commerce engagement starts by mapping ownership across storefront, OCC, platform core, data, and runtime.

Storefront replacement

Route-by-route parity, no big bang

OCC DTO population refactored, storefront calls batched, and parity components delivered for SmartEdit-managed content.

Performance recovery

Budgets enforced at release time

Query plans rewritten, cache regions tuned, indexing jobs split, and load-test gates added to the release process.

Technical notes for teams already in the migration.

Dense guides, not blog filler. Each article is written for architects and senior engineers operating SAP Commerce in production.

Explore all guides
Architecture12 min read

SAP Commerce Cloud architecture overview

How CCv2, extension boundaries, Backoffice, Solr, OCC and storefront layers fit together in a maintainable production landscape.

Read article
MigrationsDraft guide

2211 upgrade readiness checklist

What to inspect before committing to an upgrade branch: deprecated APIs, build hooks, data volume, Solr schema drift and storefront contracts.

Read article
StorefrontDraft guide

Composable Storefront performance gates

Practical budgets for OCC call volume, CMS component rendering, SSR cache behavior and LCP before a Spartacus rollout.

Read article