Spartacus

Divante is a core contributor to Spartacus — the official Angular-based headless storefront for SAP Commerce Cloud. We build, customise, and upgrade production storefronts for B2C retailers and B2B manufacturers.

Core
SAP open-source contributor
Angular
TypeScript · NgRx · RxJS
B2B & B2C
Full SAP CC feature coverage
18 yrs
SAP Commerce expertise
Trusted by

We helped build Spartacus. We know it end to end.

Spartacus is the official headless Angular storefront for SAP Commerce Cloud — also marketed by SAP as SAP Composable Storefront. Divante engineers contributed directly to its architecture, component library, and B2B feature set. That depth of knowledge is not available from a typical systems integrator.

We implement Spartacus for B2C retail, B2B distribution, and manufacturing brands — delivering fully customised storefronts that run on the current Angular LTS version, use Clean Core OCC extensions, and survive SAP Commerce version upgrades without conflict. We also provide structured migration paths from JSP Accelerator and legacy Spartacus versions.

Capabilities

What we build.

B2C Storefront Implementation

Full B2C Spartacus builds — PLP, PDP, cart, checkout, and account pages — with your design system applied as a custom Angular component library. Optimised for Core Web Vitals and SEO.

B2B Procurement Storefront

Complex B2B features on Spartacus: quote management, approval workflows, cost centre billing, punchout (OCI/cXML), contract pricing, and multi-buyer account hierarchies.

Accelerator Migration

Structured migration from JSP Accelerator to Spartacus with full feature parity validation. We run both storefronts in parallel during transition to eliminate risk and allow traffic-split testing.

OCC API Extensions

Custom SAP Commerce OCC API endpoints and facades — Clean Core, upgrade-safe, fully tested. We extend the OCC layer for custom catalogue attributes, B2B logic, and third-party integrations.

Custom Component Development

Bespoke Angular components that extend or replace Spartacus defaults — following the platform's CMS-driven architecture so your customisations survive version upgrades cleanly.

Version Upgrade & Support

Proactive Spartacus and SAP Commerce Cloud version upgrades, patch management, and L2/L3 support retainers. We document all customisations against the upgrade path before each release.

Our process.

01

Architecture review

Assess SAP Commerce version, customisation depth, OCC API extension inventory, and integration landscape. For Accelerator migrations, we catalogue every custom JSP template and extension to build a complete feature parity matrix.

02

Storefront build

Implement Spartacus with your design system applied as a custom Angular library. B2B and B2C feature sets configured per your commerce model — quote workflows, account hierarchies, or standard checkout.

03

OCC extension & integration

Extend OCC APIs for custom catalogue data, third-party integrations, and B2B procurement logic — all using Clean Core patterns that survive SAP Commerce platform upgrades without conflict or patch dependencies.

04

Go-live & upgrade path

Deliver with full regression test coverage, documented customisation inventory, and a clear upgrade path aligned to SAP Commerce Cloud release cycles. Post-launch support retainer or managed upgrade service available.

Technology

Technology foundation

The tools and frameworks powering production deployments.

Angular 17+Current LTS version
TypeScriptStrict mode, full type coverage
NgRxState management
RxJSReactive streams
OCC APISAP Commerce REST layer
SAP BTPIntegration & extension platform
Jest · CypressUnit & E2E testing
Docker · KubernetesContainer deployment
Case Studies

Selected client work.

AI-powered eCommerce platform transforming recruitment advertising

Custom AI-driven product matching, dynamic storefronts and checkout optimisation for Germany's largest local portal - rebuilt from the ground up in 14 months.

↑ 3x conversion rate uplift
Read case study →

Yelmo: digital order picking saves 4.7 million print-outs a year

Mobile-first SAP integration that replaced paper-based warehouse workflows across 3 distribution centres.

4.7M print-outs eliminated annually
Read case study →

myAPP reaches 12,000 employees across a global steel empire

Unified employee self-service portal deployed across 50 countries for one of Europe's largest steelmakers.

12,000+ daily active users
Read case study →
All case studies →

Frequently asked questions

Everything you need to know before we talk.

What is Spartacus, and how does it relate to SAP Composable Storefront?
Spartacus is the open-source Angular storefront for SAP Commerce Cloud. SAP rebranded it to "SAP Composable Storefront" in 2022, but the project, codebase, and Angular foundation are the same. Most teams and the wider SAP community still refer to it as Spartacus. Existing implementations continue on the same upgrade path and repository regardless of which name you use.
Should we migrate from JSP Accelerator to Spartacus?
If you are on JSP Accelerator with a significant amount of custom JSP extensions, a migration to Spartacus is a substantial project — not a like-for-like swap. SAP has deprecated the Accelerator and it will not receive new feature investment. The migration pays off in significantly better Core Web Vitals performance, easier frontend development, and access to future SAP feature releases. We recommend a structured discovery to quantify the effort before committing.
What is Clean Core and why does it matter?
Clean Core is SAP's architectural principle for extending SAP Commerce Cloud without modifying the platform's core source code. Extensions and customisations are built via defined extension points — OCC API facades, hooks, and event-driven integrations — rather than directly patching SAP code. This means platform upgrades do not conflict with your customisations. We apply Clean Core patterns to all OCC extension work, which dramatically reduces upgrade risk and time.
How long does an Spartacus implementation take?
A new B2C Spartacus build (design system + core pages + checkout) typically takes 16–24 weeks. B2B builds with procurement workflows are 24–36 weeks depending on feature complexity. Accelerator migrations range from 20–40+ weeks depending on the volume of custom JSP extensions and integrations. We provide a detailed effort estimate after the architecture review phase.
Can Spartacus work with non-SAP Commerce backends?
Spartacus is designed specifically for SAP Commerce Cloud and depends on the OCC API contract. It is not a general-purpose Angular storefront framework. If you need a headless Angular frontend for a non-SAP backend, we would recommend a purpose-built Angular application or a different headless frontend framework rather than adapting Spartacus.

Still have questions?

Talk to our team - we reply within one business day.

The Controller of your personal data is Cloudflight Poland Sp. z o.o. with its registered office at Wroclaw, Poland, who processes your personal data for marketing purposes, including delivering our offer, in accordance with our Website Terms of Use. You have the right to data access, rectification, erasure, restriction and portability, object to processing and to lodge a complaint with a supervisory authority. For detailed information, please refer to the Privacy Policy.

We reply within 1 business day