Release notes 202307.0

Edit on GitHub

The Spryker Commerce OS is an end-to-end solution for digital commerce. This document contains a business-level description of new features and enhancements.

For information about installing the Spryker Commerce OS, see Getting started guide.

Spryker Commerce OS

This section describes the new features released for Spryker Commerce OS.

[Spryker SDK] Performance Tracing Toolbar feature

Trace your request execution flow to find bottlenecks and optimize your code. The developer toolbar has a new section now, allowing engineers to easily activate the request tracing and examine the whole request flow to find bottlenecks and build performant and optimal code.


Business benefit: Lower response time, faster end-user experience resulting in higher conversion rates.


Integrate profiler module

[Spryker Code Upgrader] Upgrader Compliance Evaluator improvement

Make sure your code is compliant and simple to upgrade with Spryker Code Upgrader. This tool allows your team to evaluate your project code and highlight potential issues. Fixing these issues simplifies your upgrading experience.

  • Detecting dead code: Reducing dead code is important for maintenance and upgrade because otherwise, your teams invest time in maintaining the code that is not used.
  • Security checker: We let you know about known vulnerabilities in third-party packages so that your team keeps them up-to-date.
  • Minimal version check: Spryker Code Upgrader is available for customers from SCOS version 2022.04.
  • PHP versions check: We verify that you use the same version of PHP in composer.json, deploy*.yml, and your runtime to maintain consistency and prevent possible incompatibilities when installing dependencies. For instance, if you are using PHP 8.1 during development or upgrades, but your production system is running on PHP 7.4. Additionally, we check for the minimal PHP version, which is PHP 7.4. Keep in mind that the minimal version will be upgraded to 8.0 in the future, as 7.4 has reached its end of life.

These are the structural code validator of dependency providers:

Example of the violation report:


Message: The class "Pyz/Zed/Single/Communication/Plugin/SinglePlugin" is not used in the project.
Target:  Pyz/Zed/Single/Communication/Plugin/SinglePlugin

Business benefit: Easier upgrades, fewer security risks, and higher awareness of known vulnerabilities in your dependencies.


[ACP App] Algolia App feature

With Algolia Search, you can create an efficient path to purchase for your customers using our innovative search and navigation solution. It empowers your buyers to quickly discover the products they desire. Currently designed for headless storefronts, the ACP Algolia App is not directly compatible with Yves storefronts out of the box. However, it offers a powerful and flexible implementation that allows you to integrate robust search capabilities into your Storefront, streamlining the customer journey and effectively increasing conversions.

Business benefit: More accurate search results without any additional maintenance.


[ACP App] Bazaarvoice App improvement

Spryker has updated how purchase data is synchronized with Bazaarvoice by embedding the process in our Order Management System (OMS). Spryker customers now have maximum control over when requests are sent to buyers to review purchased products.

Business benefit: Send optimally timed reminders to customers for reviews, increasing the possibility of gaining social proof for your products.


Usercentrics, a consent management platform, helps with privacy regulations and data quality. Enabling organizations to collect, manage, and document website visitors’ consent, Usercentrics helps mitigate legal risks, secure data capture, and increase revenues. Usercentrics is now available on Spryker App Composition Platform.

The Usercentrics app helps you as follows:

  • Address your consent management needs globally in one click.
  • Obtain, manage, and document the consent of your website visitors frictionlessly.
  • Ensure you are compliant with privacy laws (GDPR, CCPA, LPGD) out of the box.
  • Provide a great user experience for your visitors to manage their cookie preferences.

Business benefit: Empower companies to take control of their data and to easily comply with privacy regulations with minimal investment.



[ACP App] Payments with PAYONE feature

Revolutionize the way you accept payments with the PAYONE app, which is now available on Spryker’s App Composition Platform. As the leading payment service provider in Germany and Austria, PAYONE has over 1,200 experts who deliver the latest payment services from a single source–for all company sizes and industries.

With the PAYONE app, you can do the following:

  • Enable your customers to make payments with credit cards and via PayPal.
  • Seamlessly integrate PAYONE payments with just one click.
  • Secure payments according to international standards through fraud prevention and integrated risk management.
  • Rest assured that all PCI compliance concerns are taken care of for you.

Business benefit: Securely process payments with ease using a leading payment provider, with a quick and easy setup.


Payone integration in the Back Office

[ACP Foundation] Monitoring and Logging for SCCOS improvement

ACP tenant monitoring and logging are required to oversee all ACP-related transactions within Spryker Cloud Commerce OS (SCCOS) properly.

Spryker is providing this feature as an integral part of having an end-to-end monitoring and logging system in place for all ACP app-related actions within SCOS.

This feature works out of the box; no additional configuration is required.

Business benefit: Ensure the stability and monitoring of your transactions when using ACP apps.

[Framework] GlueApplication as API enabler infrastructure feature

Glue as an API stays the same, but the main module carrying the infrastructure for our API development layer gets a complete rework as the GlueApplication module transforms from a Storefront-specific JSON:API complying API provider to an infrastructure that allows the development of different API applications. The applications now follow two separate types: Storefront and backend, which have access to different storage engines that allow for different use cases and get deployed in two different types of containers. The Storefront type has access to Redis & Search storages which allow for quick horizontal scalability to support bursts of traffic. The backend type has direct access to Zed application layer facades, which allow APIs to be built on top of the core business logic.

Business benefit: The separation of API applications by type and functionality allows for more diversity in how we design APIs and the exposure of business logic to consumers.


[Framework] Configure OAuth 2.0 clients on install improvement

Previously, OAuth 2.0 clients were not able to be updated other than having one client per installation. To begin, our client was our own Storefront, but when opening the consuming of APIs, we had to allow more API consumer clients to be installed in the system. This feature allows for creating as many OAuth 2.0 clients as needed for consumers.

Business benefit:

Allows for the creation of multiple OAuth 2.0 clients, so the business can allow for secure connection of multiple API consumers with different access rights.


Install the Customer Account Management feature

[Framework] Catalog Back Office Performance Improvements improvement

Searching our tables in the back office can cause serious pain for business users that are trying to search any large tables due to how our querying works on the database in the back office. We allowed now for the possibility for our customers to decide on specific tables to allow a more strict yet performant search on specific columns in tables.

Business benefit: If a business user has a specific need for faster search on product SKUs or prices or something that contains a large amount of data, a quick configuration in code can help allow for strict yet more performant search


Create and configure Zed tables

[Framework] Replace Swift Mailer / Swift Mailer library improvement

We have been dependant on a deprecated library, Swift Mailer, in our email-sending library. This has been reworked to allow the usage of the more up-to-date Symfony Mailer component.

Business benefit: Jumping to a more widely used and supported component allows customers higher maintainability and feature richness.


[Cloud Self-Service] Management of Spryker CI variables feature

Access to the variables in Spryker CI lets you change pipelines’ behavior without having to wait for our support. You can now manage the following variables:


Business benefit: Gives you more control over your projects and enables you to resolve issues faster.

Documentation for this feature is coming soon.

[Cloud Self-Service] Maintenance Mode feature

Turn on and off the maintenance mode of an application using a dedicated pipeline without having to create a support ticket. This lets you deploy new versions of applications without disrupting the user experience with unexpected errors.

Business benefit: Easier management of maintenance. You can turn on maintenance mode more quickly, reducing downtime and minimizing disruption.


[Cloud Self-Service] Environment variables management feature

Manage environment variables and secrets of applications using a UI without having to create a support ticket. This lets you make changes autonomously, controlling the scope of the application and scheduler variables. You decide if changes should be applied immediately or during the next deployment.

Business benefit: Flexibility. You can change environment variables according to a needed schedule, which lets you adapt more easily to changing needs and requirements.


Add variables in the Parameter Store

[Cloud Observability] Infrastructure Health Check Monitoring Dashboard feature

Empowers your team with built-in dashboards to observe the status of the whole platform.

At a glance, your team can monitor the health status and uptime of their environment as a whole, the applications running, the average response time, and the availability of single services and components.


Infrastructure Health Check Monitoring Dashboard feature is not part of Spryker’s base offering and is an optional additional feature.

Business benefit: Access to actionable insights to improve operational efficiency.

Documentation for this feature is coming soon.

Infrastructure Health Check Monitoring Dashboard: Birds eye overview example:


Infrastructure Health Check Monitoring Dashboard: ELB/ALB example:


Infrastructure Health Check Monitoring Dashboard: ElastiCache example:


Infrastructure Health Check Monitoring Dashboard: RDS example:


Infrastructure Health Check Monitoring Dashboard: Elasticsearch example:


[Cloud Observability] Pipeline Success Dashboard feature

Provides your team with a real-time view of the deployment pipeline performance, enabling them to track the success and failure rates of pipeline runs, allowing them to:

Easily monitor their pipeline metrics, including the number of overall succeeded pipeline runs and the overall number of failed runs, and quickly identify and troubleshoot any issues,

Have visibility into pipeline performance to drive continuous improvement of deployment processes,

Optimize release cycles and ultimately deliver applications faster and more reliably.


Pipeline Success Dashboard is not part of Spryker’s base offering and is an optional additional feature.

Business benefit: Access to actionable insights to improve operational efficiency.

Documentation for this feature is coming soon.

Pipeline Success Dashboard example:


[Core Commerce] Upgraded Angular to v15 and Node.js to v18 improvement

To maintain the stability and longevity of our platform, we have migrated to Angular v15 and Node.js v18, which are actively supported by their respective communities. This ensures continued support and leveraging of these versions’ latest features and improvements. No infrastructure changes are required on your end before performing the upgrade.


[Composable Storefront] Early Access release

Spryker is launching an Early Access program for customers who want to be among the first to utilize the new Spryker Composable Storefront.

Composable Storefront is currently running under an Early Access Release. Early Access Releases are subject to specific legal terms, they are unsupported and do not provide production-ready SLAs. They can also be deprecated without a General Availability Release. Nevertheless, we welcome feedback from early adopters on these cutting-edge, exploratory features.

Spryker Composable Storefront provides an efficient solution for developers to implement and customize stores on Spryker’s commerce platform. It offers pre-packaged, decoupled, composable components for common features found on digital commerce sites. Customers can also create their own custom components to be used in the Storefront.

If you are interested in being part of Spryker’s Composable Storefront Early Access program, contanct your Spryker representative.

Business benefit: Spryker Composable Storefront allows Spryker customers to implement and customize a decoupled storefront quickly. It offers Spryker customers a future-proof, agile, and scalable solution.



[Dynamic Multistore] Early Access release

Spryker is launching an Early Release Access program for customers who want to be among the first to utilize the new Dynamic Multistore.

Dynamic Multistore is currently running under an Early Access Release. Early Access Releases are subject to specific legal terms, they are unsupported and do not provide production-ready SLAs. They can also be deprecated without a General Availability Release. Nevertheless, we welcome feedback from early adopters on these cutting-edge, exploratory features.

Dynamic Multistore lets business users create stores in your platform’s back-end without the help from the development team.

For further information about accessing this Early Release feature, contact your Spryker representative.

Business benefit: Boosts productivity and agility whilst empowering business users.


Dynamic Multistore