SAP Commerce Cloud Implementation & B2B E-commerce Solutions

The Novarto SAP Commerce Cloud Boost Package is a fixed-scope implementation that delivers a fully functional B2B webshop, integrated with SAP backend systems, configured with product catalog and pricing, and deployed on SAP Commerce Cloud Public Cloud — within a defined timeline and budget.

With Novarto’s Boost Implementation Package, you can start your SAP Commerce Cloud journey with confidence. This package enables you to use the key features of B2B Commerce Cloud, enjoy a satisfying initial experience, and prepare for future growth (e.g., MVP). 

Benefits:

• Novarto leverages proven content and industry best practices to deliver a quick and seamless implementation.
• With a Ready-to-use web shop in the Cloud and selected CI-based flavors, you gain immediate access to a fully functional platform ready to engage customers and drive sales.
• Every essential commerce process step is seamlessly integrated with standard SAP Commerce Backoffice functionalities, empowering you to easily thrive in the digital marketplace.

SAP E-commerce Boost Package Scope:

• B2B-enabled environment
• Individual standard shop setup via script
• Upload of selected master data via ImpEx (e.g. customers, products, prices, stock levels)
• Support of bilingual setup (German and English)
• Product Information Management (PIM) with two catalog versions: Staged and Online
• Search indexing with Apache Solr
• Integration with the customer mail server
• Headless SAP Commerce Cloud, composable storefront (Spartacus)
• Order management via cart and checkout with Account Payment method

Technical Requirements for SAP Commerce Cloud:

• License for SAP Commerce Cloud in the Public Cloud
• Source code repository

Not sure which e-commerce approach fits your situation? Book a 30-minute scoping call with one of our SAP Commerce engineers.

Further Services 

Integrate with S/4HANA

Integrate with Stripe

Integrate with Payment Methods (such as Credit Cards)

Migrating from SAP Hybris to SAP Commerce Cloud

SAP Hybris was rebranded to SAP Commerce Cloud in 2018, but many enterprise organizations are still running on older Hybris versions that are no longer actively maintained by SAP. A migration to SAP Commerce Cloud Public Cloud or Private Cloud brings access to SAP’s latest composable commerce architecture, the Spartacus headless storefront, native SAP BTP integrations, and a supported upgrade path going forward.

Novarto has delivered Hybris-to-Commerce Cloud migrations for enterprise clients across multiple industries. Our migration methodology covers platform assessment, custom extension review, data migration planning, composable storefront adoption, and cutover execution — with embedded engineers managing every phase through to go-live stability.

Migrating from SAP Commerce Accelerator to Composable Storefront

If your organization is currently running an SAP Commerce Accelerator-based storefront, you are operating on a platform that SAP has confirmed will reach end of life. SAP will remove Accelerator UI components from official releases by September 2027, with mainstream support ending in September 2028.

This is not a routine upgrade. The Accelerator architecture tightly couples the frontend presentation layer with backend commerce logic,  meaning business-critical processes such as pricing rules, checkout workflows, and custom integrations are often embedded directly in the storefront. Migrating to SAP Composable Storefront requires identifying, extracting, and properly re-exposing this logic through APIs before a new storefront can be built. Organizations that treat this as a simple frontend replacement consistently encounter operational and SEO risk at go-live.

Novarto manages Composable Storefront migrations through four structured phases: a Readiness Assessment of your current Accelerator customizations and API coverage, API and Backend Preparation to ensure all business logic is properly exposed through SAP Commerce services, Composable Storefront Implementation built to SAP best practices and performance standards, and Performance Optimization covering Core Web Vitals, Server-Side Rendering, and CDN caching. The result is a future-proof SAP Commerce Cloud architecture aligned with SAP’s long-term roadmap — with no technical debt carried over from the Accelerator layer.

The first step is understanding your current system’s actual migration readiness before committing to a timeline or budget.

Find out your migration complexity, risks, and realistic timeline — before the 2027 deadline forces the decision. Request a Composable Storefront Readiness Assessment

FAQ Section

1. What is SAP Commerce Cloud, and how does it differ from SAP Hybris?

SAP Commerce Cloud is SAP’s enterprise e-commerce platform, designed for organizations that require tight integration between their digital storefront and SAP ERP backend systems. It supports B2B, B2C, and B2B2C commerce models, complex product catalog management, omnichannel fulfillment, and personalization at scale.

SAP Hybris was the original name of the platform before SAP acquired it in 2013. In 2018, SAP rebranded the product as SAP Commerce Cloud and began integrating it more deeply with the SAP ecosystem, including SAP S/4HANA, SAP BTP, and SAP Customer Data Platform. Functionally, SAP Commerce Cloud is the evolved, cloud-native version of the Hybris platform — with a modern composable storefront (Spartacus), cloud-managed infrastructure, and a continuous release cycle replacing the legacy on-premise deployment model.

Organizations still running on older SAP Hybris versions are operating on a platform that is no longer actively developed by SAP. Migration to SAP Commerce Cloud is the supported path forward.

2. What does a B2B SAP Commerce Cloud implementation typically include?

A full B2B SAP Commerce Cloud implementation covers the configuration and deployment of a web storefront tailored to B2B buyer journeys, including account and user management, organization hierarchies, contract pricing and price lists, quote management, order approval workflows, and reorder functionality. It also includes product catalog setup with PIM integration, search configuration (typically using Apache Solr or SAP Search and Merchandising), and integration with backend SAP ERP systems for inventory, order management, and invoicing.

On the technical side, implementation involves environment setup on SAP Commerce Cloud Public or Private Cloud, storefront development (either accelerator-based or composable using SAP Spartacus), CI/CD pipeline configuration, and performance testing. Data migration — including customer master data, product data, and historical orders — is a significant workstream in most B2B implementations.

Novarto implements SAP Commerce Cloud for B2B organizations using an embedded engineering model, with certified SAP Commerce Cloud developers working directly within your project team from design through go-live.

Want to see what a B2B Commerce Cloud implementation looks like end to-end — timeline, scope, and what typically goes wrong? Lets walk you through it. Talk to an SAP Commerce Cloud engineer

3. How long does an SAP Commerce Cloud implementation take?

A standard SAP Commerce Cloud B2B implementation typically takes between 4 and 9 months from project kickoff to go-live, depending on the scope of customizations, the number of backend integrations, catalog complexity, and organizational readiness. The Novarto Boost Package — a fixed-scope B2B starter implementation — is designed to compress this timeline significantly for organizations that want a production-ready foundation quickly, before extending the platform over time.

More complex implementations involving multiple storefronts, multi-language and multi-currency requirements, custom pricing engines, or migration from an existing Hybris or third-party platform typically require 9 to 18 months. Hybris-to-Commerce Cloud migrations add an assessment and refactoring phase that standard greenfield implementations do not require.

The most reliable way to scope an accurate timeline is through a structured discovery engagement that reviews your current system landscape, integration requirements, and catalog structure before committing to a delivery plan.

4. What is a composable storefront, and should we use SAP Spartacus?

A composable storefront — in the SAP Commerce Cloud context, built on the SAP Spartacus framework — is a headless, JavaScript-based frontend that communicates with the SAP Commerce Cloud backend through APIs, rather than using SAP’s traditional accelerator-based storefront, which is tightly coupled to the backend. Spartacus is now SAP’s strategic storefront framework and is the recommended approach for new implementations and migrations.

The composable approach offers significant advantages: faster frontend performance, greater flexibility for UI customization, independent frontend and backend deployment cycles, and better compatibility with modern web development practices. It also enables progressive web app (PWA) capabilities, which improve mobile commerce performance.

Whether Spartacus is the right choice for your project depends on your team’s frontend development capabilities, your timeline, and the extent of UI customization required. Novarto implements both accelerator-based and Spartacus composable storefronts and will recommend the appropriate approach based on your specific situation.

5. How long does a Composable Storefront migration take?

Composable Storefront migration timelines typically range from 6 to 18 months, depending on the volume of Accelerator customisations, number of integrations, state of the API layer, and internal capacity. Storefronts with limited customisation and clean API coverage can complete migration in 6 to 9 months. Heavily customised Accelerator implementations typically require 12 to 18 months. Starting migration in 2025 or 2026 provides sufficient runway for a controlled, low-risk transition ahead of the September 2027 deadline

6. What happens if we do not migrate from SAP Commerce Accelerator before September 2027?

By September 2027, SAP will remove Accelerator UI components from official SAP Commerce Cloud releases. After September 2028, SAP will not provide fixes, patches, or support for Accelerator storefront issues. Organisations that have not migrated face growing security exposure, loss of access to new SAP Commerce Cloud features, and an increasingly difficult migration as internal knowledge of the legacy system fades. The practical consequence: delaying does not avoid the migration cost — it increases it, while reducing the quality of options available.