Title: Commerce Cloud Integrations | SAP Commerce specialists Source: https://www.commercecloudintegrations.com Publisher: Commerce Cloud Integrations *Animation: Exploded axonometric of a SAP Commerce Cloud estate, lit one layer at a time as the chapters describe the work on it. Six layers stack from the integration layer at the base up through platform services, the SAP Commerce core, OCC v2, the composable storefront and the CDN edge. Six external systems dock into the base: ERP via SAP S/4HANA, PIM via Akeneo, CRM via Salesforce, PAYMENTS via Stripe, MARKETPLACES via Mirakl, ANALYTICS via GA4.* SAP Commerce,\ connected ========= Architecture, integrations, data migration and performance work on SAP Commerce Cloud. [Book a strategy call](https://www.commercecloudintegrations.com/contact) [Review services](https://www.commercecloudintegrations.com/services) [85](https://www.commercecloudintegrations.com/guides) [ technical guides on architecture, integration, migration and performance.Read the work](https://www.commercecloudintegrations.com/guides) - ERPSAP S/4HANA - PIMAkeneo - CRMSalesforce - PAYMENTSStripe - MARKETPLACESMirakl - ANALYTICSGA4 01 / 04 Integration layer ## Integrations with the systems you already run Your ERP owns the prices. Your PIM owns the product data. Payments, marketplaces and analytics each have their own idea of what a product is. We build the connections that keep SAP Commerce in agreement with all of them, while customers are shopping. - ERP prices, stock, orders back - PIM product data and media - CRM customers and service history - Payments authorization and capture - Marketplaces listings and settlement - Analytics what people actually did * What we do Design the contracts and the retry behavior, so a slow ERP does not take the storefront down with it. [Integration work](https://www.commercecloudintegrations.com/services) 02 / 04 Platform services and core ## Customizations and platform improvements Item types, services, Backoffice screens, cronjobs, the Solr index: this is the code that makes SAP Commerce fit your business instead of somebody else's. It is where most of the value sits, and where most of the release time goes. - What we do Build new customizations on the extension points SAP supports, and improve the ones that slow a release down. Same platform, faster to change. [Platform work](https://www.commercecloudintegrations.com/services) [Search and indexing](https://www.commercecloudintegrations.com/performance) 03 / 04 OCC and the storefront ## Composable Storefront builds and OCC work Composable Storefront asks OCC for everything it shows, so the storefront is only ever as fast as the API under it. The two are one job, and we treat them as one job. - What we do Shape the OCC responses around what each page actually reads, then ship one page type at a time. Your current storefront keeps trading until the last one moves. [Composable Storefront](https://www.commercecloudintegrations.com/composable-storefront) 04 / 04 Upgrades and migrations ## Upgrades and platform migrations Everything has to cross: code, configuration, media and the whole commerce database. That is as true of an on-premise SAP estate moving to CCv2 as it is of a storefront coming off Salesforce Commerce Cloud, Magento or Adobe Commerce. The source changes. The data model work does not. - What we do Stand CCv2 up, map the source model onto it, move the data on a rehearsal first, and run both until the cutover. You pick a go-live date after we have done it at least once, not before. [Migrations and upgrades](https://www.commercecloudintegrations.com/migrations) ## News What we have shipped from the open source SAP Commerce work. Open sourceJune 2026 ### SAP Commerce Stripe Connector released as open source A Stripe integration for SAP Commerce Cloud, MIT licensed. Hosted Checkout and inline Payment Elements, both confirming through PaymentIntents. Webhooks arrive signature-verified and map onto Commerce transaction states. OCC endpoints are included for Composable Storefront checkout. [View the repository](https://github.com/commerce-cloud-integrations/sap-commerce-stripe-connector) ## We publish the tools we build Connectors, static analysis, an MCP server, agent skills. Built for our own work on SAP Commerce, kept public so your team can use them too. ### 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](https://github.com/commerce-cloud-integrations/sap-commerce-stripe-connector) ```java /* * 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. ## Technical notes for teams already in the migration Dense guides, not blog filler. Written for the people who have to keep it running. [Explore all guides](https://www.commercecloudintegrations.com/guides) [Architecture12 min read](https://www.commercecloudintegrations.com/guides/sap-commerce-cloud-architecture-overview) ### [SAP Commerce Cloud architecture overview](https://www.commercecloudintegrations.com/guides/sap-commerce-cloud-architecture-overview) [How CCv2, extension boundaries, Backoffice, Solr, OCC and storefront layers fit together in a maintainable production landscape.](https://www.commercecloudintegrations.com/guides/sap-commerce-cloud-architecture-overview) [Read article](https://www.commercecloudintegrations.com/guides/sap-commerce-cloud-architecture-overview) [Migrations4 min read](https://www.commercecloudintegrations.com/guides/sap-commerce-2211-upgrade-readiness) ### [SAP Commerce 2211 upgrade readiness checklist](https://www.commercecloudintegrations.com/guides/sap-commerce-2211-upgrade-readiness) [What to inventory before a 2211-jdk21 upgrade: extensions, addons, removed APIs, storefront path, integrations, and data rehearsals.](https://www.commercecloudintegrations.com/guides/sap-commerce-2211-upgrade-readiness) [Read article](https://www.commercecloudintegrations.com/guides/sap-commerce-2211-upgrade-readiness) [Storefront15 min read](https://www.commercecloudintegrations.com/guides/composable-storefront-production-engineering) ### [Composable Storefront production engineering](https://www.commercecloudintegrations.com/guides/composable-storefront-production-engineering) [CMS boundaries, facades, lifecycle ownership, SSR-safe APIs, rendering policy, and release gates for Composable Storefront code.](https://www.commercecloudintegrations.com/guides/composable-storefront-production-engineering) [Read article](https://www.commercecloudintegrations.com/guides/composable-storefront-production-engineering)