Spartacus Roadmap

This document describes what what is planned for Spartacus for Q1 2020 and later.

Last updated February 27, 2020 by Bill Marcotte, Senior Product Manager, Spartacus


Disclaimer - Forward-Looking Statements

This document contains forward-looking statements. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions. Any information is subject to change for any reason without notice. The information in this document is not a commitment, promise or legal obligation to deliver any material, code or functionality. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This document is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP’s intentional or gross negligence.

The various documentation links provided point to SAP Commerce Cloud platform or Accelerator documentation or third-party external links. These links are included for information purposes only and may not reflect exactly what is implemented in Spartacus.

General Release Information

We plan to publish new Spartacus libraries every two weeks. Each release may contain bug fixes, improvements to user experience, and new features.

When new features are available for release, normally we will publish a pre-release “next” version of the libraries with the new features, in order to get feedback. When the final, new, minor version is ready, we usually publish a release candidate (RC), with the final new x.y.0 a weeks later. For example, we will publish a few pre-release 1.5 “next” libraries in January 2020, and then 1.5.0 will be released in February.

Some of the links provided in the following lists point to SAP Commerce Cloud Accelerator documentation, to give an idea of what the feature is about. These links are for context only. While we strive for feature parity, the Spartacus implementation of features may not work exactly as in Accelerator.

B2B features are based on the B2B Accelerator Powertools store. Many B2B features depend on new APIs that are scheduled for release in SAP Commerce during Q2 2020 or later.


For non-technical questions and roadmap feedback, you can reach us on our Slack workspace.

If you have technical questions, you can get in touch with us on Stack Overflow.

Planned for Rest of Q1 2020

Exact dates to be determined

A new major (2.0) is planned for end of Q1 2020 or early Q2, primarily due to planned support for Angular 9 and the new Ivy rendering engine. New Accessibility keyboarding features will also be part of the 2.0 release. The release of a new major version of Spartacus means that the code contains breaking changes.

  • Full Keyboard Support (WCAG 2.0, 2.1.1, Level A, Keyboard; WCAG 2.0, 2.1.2, Level A, No Keyboard Trap)
  • Consistent Navigation (WCAG 2.0, 3.2.3, Level AA, Consistent Navigation)
  • Tabbing/Reading Order (WCAG 2.0, 2.4.3, Level A, Focus Order)
  • Focus Visible (WCAG 2.0, 2.4.7, Level AA, Focus Visible)

Move to Angular 9 / Ivy

  • Move to Angular 9 (aiming for February 2020)
    • Schematics update for supporting migration
    • 3rd party dependencies updates
  • Angular Ivy support (new compilation and rendering pipeline)
    • Smaller, simpler and faster
    • Better performance on mobile devices
    • Less memory used
    • Tree shaking for smaller packages

Other architecture changes that are stretch for 2.0 release (could be added to 2.x release):

  • Session Management (for better handling of authentication)
  • Persistent services
  • Events
  • Library structure for lazy loading
  • Removal of ng Bootstrap
  • Routing improvements
  • Performance improvements

Notes for Upgrading to 2.0

For upgrading to Spartacus 2.0, we’re working on a transition that will easy as possible, using Angular Schematics. Typically we hope the update process will take about a day, if being done by an experienced Angular developer. However, the exception might be if code has been extended or replaced by customers. Not all updates will be taken care of automatically, so we will be looking for feedback as release candidates are published.

Note: One low-level area to avoid at the moment is the Cart, as it is going through a refactor for 2.0 release.

Planned for Q2 2020

B2B Storefront MVP

  • B2B Commerce Org (SAP Commerce Cloud 2005 required)
    (also known as My Company management of units, users, budgets, cost centers, purchase threshholds, user groups, approvals) SAP Commerce Documentation
  • B2B Checkout (check out by account, enter purchase order, select cost center, shipping address restricted by cost center chosen, subject to approval process)
    SAP Commerce Documentation

B2B Stretch for Q2 2020 and into Q3:

Core/B2C Storefront Features

Features planned for the second half of 2020

The items in this section are on our future roadmap - not necessarily for any specific quarter, but order of priority indicates what we’ll tackle first.

Archictecture and Development Features

  • Angular 10 support (Angular release currently scheduled for Q4 2020)
  • Extensibility Improvements (“Sproutlets” - Outlets NG)
  • Performance improvements with CMS
  • Support for SAP Commerce Cloud Cart and Checkout
  • Single-sign on integration with SAP Customer Data Data from GIGYA SAP Documentation

Core/B2C Storefront Features

B2B Storefront Features

Future Outlook

The following features are in our roadmap but currently not planned for a specific quarter.

Some items have notes, for example (1) or (2)

  • (1): The feature requires new OCC REST APIs that are planned for the next SAP Commerce release, scheduled for May 2020. These features may be available sooner to customers using SAP Commerce Cloud hosting services.
  • (2): The feature requires new OCC REST APIs, not yet planned.