Shopware Roadmap

Currently, only the complete order list can be added to the shopping cart. With the adjustment, individual products can be added to the shopping cart conveniently. In addition, the administration of order lists is significantly simplified. This further accelerates the ordering and the managing process of orderlists.

The facelift of the B2B Suite makes it easier and faster for merchants, debitors, and sales representatives to find their way around, since it uses design components that are already familiar from the Storefront in Shopware.

Several different products can be quickly added to an order list. This saves the debtor valuable time in maintaining orderlists.

We want to make it possible for our Merchants to migrate from Shopware 5 to transfer custom products into Shopware 6.

The admin search is an important tool for merchant in his daily doing. He should easily find what he is looking for and shouldn't be bothered with unnecessary information. Therefor he should be able define what he wants to search for. Also his settings and behaviour should be saved to the database, so that every admin user has his own preferences.

Every shop owner has to deal with returns. Currently one needs to return the whole order and partial returns are not possible. With this epic we want to introduce a basis on how to create return and have status per item in shopware.

The order module is one of the most important modules for the merchants. By reworking the user interface and the usability, we want to ensure that the whole process of handling orders will get more convenient and a lot easier.  We will achieve this by restructuring tabs & cards and simplify working with the order states.

The import and export was closely tied to shopware's internal data structure. In this step we will remove the dependency on internal identifies like UUIDs and lay the base to enable merchants to import their data into shopware according to their needs and use cases.  

Shopware provides templates for many essential business documents, such as invoices, delivery notes or credit notes. These are updated and undergo some detail improvements.

When a shipping or payment method isn’t avaliable anymore, the shop will change to the next available one without any user interaction.

A store customer is already informed during registration or other touch points that a possible delivery to his desired address is not possible. 

The Import-Export profiles help merchants to handle regular data transfers. We will add additional functions to enable merchants to create and use profiles more safely and efficiently.

The available conditions in the Rule Builder will continuously grow in the next iterations. With this step we will provide a more straightforward interface, which will help merchants to build the right rule

Currently Shopware is not offering a regularly maintained, up-to-date icon library for our devs and community. With this epic we want to introduce and release a new icon kit package which will be published and closely connected to our internal tools like Figma. With changes and additions in Figma, we want to introduce an automated package release of the new icon pack to our community. We not only want to release the package but also refactor the administration to make also use of this new package. The icon kit should be updated, unified and optimized for general usage at Shopware by our community

With a new API-first approach, we are adding another asynchronous option to the already existing payment flows. With this, we enable client applications to initialise and execute payments themselves and to synchronise them with Shopware at a later point in the ordering process.

Currently shopware offers a flexible tag engine. With this feature, we will enable merchants to be able to remove and edit tags by providing a basic administration interface.

The current Rule Builder List-Item-Dropdowns only provided one level of information, which makes it difficult for merchants to identify the correct elements. We add more informations to help merchants find the correct data to use in the Rule Builder.

One of the key features of Shopware are the Shopping Experiences. As we already have a lot of great plugins, we also want to enable app developers to extend the CMS. Therefore it will be possible for apps to bring their own custom elements to the Shopping Experiences.

The overview in the Rule assignment tabs provide a basic functionality right now. With this feature we will extend the functionality here to enable merchants to better organize and manage their rule assignments.

Merchants have the possibility to generate order documents via a bulk change, download them and send them directly with a status mail to the customer, if desired. It is also possible to configure whether any additional Flow Builder actions should be executed or not.

This will enable merchants to organize their Sales Channels by sorting and marking them as favourites.

With AppScripting we want to enable developers to create more powerful apps. We will define certain extension points, where you can manipulate Shopware entities with a limited scripting syntax. This will allow for apps that synchronously change the cart in order to e.g. implement some sorts of special discounts.

With Shopware, you should be able to sell all kind of products. We will provide a solution to handle downloadable products as a first step. Your customers will be able to download the digital goods right after checkout or get the download link afterwards, depending on the payment status.

Variants in Shopware 6 work completely differently than in Shopware 5. In Shopware 6 everything is a variant and there is no longer a master product. In listings, however, it can be useful to display information such as a description or a generic image that cannot be assigned to a specific variant. Through this, we want to allow the merchant to display other information in the listing that describes the generic product in its entirely without referring to specific variants.

When creating new products, some fields currently have to be filled in that are not always necessary. The creation of new products via the administration should be made easier for new merchants through a reduction of mandatory fields and the expansion of standard values.

Different countries require address entry and validation in different formats. The format of the address and the validation of the postal code can therefore be defined for each country.

As a merchant who has customers with multiple individual price conditions, you can pull those defined prices from your system of choice in Shopware via API. These individual prices can then be displayed at several steps within the customer journey if a customer is logged in. This enables you to offer prices specifically calculated for each customer.

Small improvements for the statistic module on the dashboard. We will show only paid orders and provide the possibility to select the date range for the dashboard Statistics.

Merchants will be able to save layouts with placeholder elements and get visual feedback on why a layout cannot be saved. Missing entries will get marked in the layout as well as in the element settings so that they can be easily corrected.

Our content management system makes it easy for merchants to create, structure, and deliver all sorts of content to tell their stories to customers. To further enrich the capabilities of individual content creation, we will offer app developers the possibility to use custom entities within our CMS.

This will enable merchants to choose either to link to a category page, an external URL or to a landing page. With the help of a more visual selection, it will be more accessible to link to internal pages.

The Flow Builder is able to delay flow sequences for later execution, so that you are able to define follow-up actions after an event has been triggered.

Currently the extension system of the Shopware Administration is based on Vue.js and Twig.js in combination. 3rd party developer can use twig.js block system to hook into every part of the administration. This technology offers a lot of downsides for Shopware as we are not able update and optimize our admin as fast as we would like to. Nearly every change of our ui components can break 3rd party extensions. With this epic we want to introduce a new way of extending Shopware Administration via declarative javascript, easy to learn and use and working the same way for self-hosted or cloud extensions: the extension api. Developers should rely on our extension api methods to extend the administration and do not need to take care of templating, block overriding and further things. They just can trust the methods to extend the administration as Shopware can maintain the components, make changes to templates, add features and so on without breaking the code. Our long term goal is to offer a complete extension api which offers all devs the freedom to extend the admin to their needs without the downsides of template and block overrides.

Flow Templates enables merchants to define reusable templates for flows, which can be shared between different systems and allows merchants to use predefined example flows.

Building a Rule is a complex and difficult task. So is checking if a Rule is working as intended. We will add a tool, which helps merchants to test a Rule before actually applying it.

Not every Condition can be used in every context. With this feature, the Rule Builder will help merchants to identify which Conditions are available in which context.

As a merchant, you need to ensure an overall sufficient customer experience on every device. Therefore it's necessary to customize your layout device-specific. As a first step, we will provide the possibility to hide & show blocks and sections for certain devices.

Variants of a product can be edited via bulk edit. New filters in the variant overview also allow that only defined variant groups can be marked for a bulk edit. This can save a lot of time when editing a large number of variants.

A unified interface in transactions that allows our partners to implement a consistent experience for refunds in payment methods.

The Rule Builder allows Merchants to check for discounts and goods more precisely

Currently the Rules to check for customer values are missing some information. With this feature we will add the missing checks for all values availabe in the admin

As a further development of the initial integration of bulk edit, merchants will have the option of using bulk edit for the customer module. In addition, simple and advanced product prices can be changed with a Bulk Edit as well. This is again a significant time saver for merchants who perform price updates via the administration.

This will enable merchants to set a custom layout as the default layout for category and product pages. The layout assignment for shops with many products and categories is therefore more efficient and changes can be applied quickly on all pages.

The merchant gets the possibility to maintain the lowest price in the administration. The information is always displayed if necessary in the storefront to fullfill the Amendment of Directive 98/6/EC Therefore, in the case of price reductions, in addition to the price reduction on the current price, the merchant must also indicate the lowest price of the goods in the last 30 days before the price reduction.

Currently, Rules are only display by name in a (searchable) list when selecting a Rule or listed in the Rule Administration Listing. This leads to problems on behalf of the merchants, since it is difficult for them to identify the Rule they want to use.

With this epic we want to optimize the loading behaviour of scripts in the administration. In the current situation all javascript gets loaded directly which causes a slow startup and overall low performance and impression when using the administration. With this epic we want to realize lazy loading mechanisms which optimize the loading of scripts to just load necessary javascript instead of everything at one time. The final release will be with 6.5 major release as this contains breaking changes. Last 2 tasks will be implemented in fall 2022.

Please make sure that every plugin is supporting the new Bootstrap version. At the same time the old version should work and should be the default value. After this Epic is done every new feature or fix needs to be done for the old and the new Bootstrap version so we can simply switch before the release to the new version.

With this epic we want to solve some issues when loading the administration initially. There is potential in optimizing the boot process by evaluating current requests and possibilities to load data directly to the template.

With this epic we want to change the administration fonts from source sans to inter. We need to define a font scale in Figma throughout all components. Afterwards the changes have to be implemented to the admin.

If you as a merchant offer your customers the choice between several shipping methods, you can manually control the display order in the checkout by specifying a position for each method. This way, recommended shipping methods can be prominently displayed.

With this epic we want to address all known tasks which are non epic related but lead to a major break.

With an interface for tax services, our merchants have the option of having tax calculations - e.g. in the USA - conveniently carried out by third-party providers.

Users can decide if they want AND / OR Search in the Admin. Due to performance, this feature is only available for shops that have Elastic Search installed. This is possible with On-Premise systems. Our goal is also to make it possible on cloud systems in the future.

We have updated the Storefront to Bootstrap v5 (currently behind the major feature flag V6_5_0_0). The update affects pretty much every area of the Storefront, and there are still some issues like styling bugs. Those issues will be addressed with this epic to keep the Storefront appearance and behavior as close as possible to the previous Bootstrap version 4. This Epic also includes removing the Major Flag for the BS5 implementation.

Merchants have the capability to offer subscriptions that automatically re-news the order after a certain period. These offers can be easily configured by the merchant in the Shopware Admin. Customers can purchase their subscriptions in the storefront easily through the regular checkout and manage them in their customer account. This is a great and compelling opportunity to increase customer lifetime value.

As a merchant who has different inventories, you need to manage the stocks of products and the respective availability of them for your shop. The Multi-Inventory functionality ensures, that products can be purchased independent of the inventory location, as long as they are available in one of them. Depending on the scenario, availability can be managed via warehouse groups and with priorities, in addition to being configured using the Rule Builder.

With a new optional way to quickly add items to the shopping cart by entering product numbers, we're improving a popular B2B functionality that allows merchants to take customer orders in a particularly efficient way.

With the possibility to place orders by uploading a file of items, we improve a popular B2B feature that allows merchants to take large customer orders without them having to go through the whole online shop journey.

In this epic we are adding visual quick wins into the Roadmap for the 6.5 major update. This includes visually concepting the rework, but also implementing it.

After the Trunk branch becomes the new 6.5 branch, the deprecations and feature flags will be removed. Therefore, this Epic includes all tasks and issues referring to the Storefront deprecation removals.

Based on our deprecations and implementations for Shopware 6.5.0.0, we must remove outdated/not-wanted dependencies from our Component. There is already a document in the Handbook which provides further details for the dependencies. Some dependencies will also be removed due to the BS5 update (e.g. jQuery).

With the next major version 6.5 we want to improve the UI of the storefront. In this epic we want to implement Quickwins (like e.g. changing colors, borders, sizes) which do not involve bigger template changes like moving/removing twig blocks/html.

To Make the Advanced Search compatible with the 6.5 and also make it available in cloud we need a POC for the new advanced search

Customers can manage, cancel or pause their subscriptions independently in their customer account. This provides greater flexibility and control for the customer while promoting customer satisfaction. This feature improves the customer experience and can help strengthen customer loyalty and increase customer lifetime value.

With Apps from the Shopware Store, you can already bring new functionalities and integrations to your cloud shop. Private Apps will additionally allow you to upload apps directly to your shop. This will not only allow for e.g. template modifications by the merchant but also for more complex customizations by e.g. shopware partners

Enterprise customers should have the possibility to define keywords for the Enterprise Search leading directly to a landing page. This especially make sense for brand names etc.

Merchants will be able to edit the templates of different social shopping platforms in order to add their custom content (e.g. legal texts).

Merchants are able to track orders that come from Social Shopping so that they better understand which channels are driving sales.

Merchants will be able to work with a new premium theme for the Professional Edition to have a quick start in their online business. The Cinema theme design has a unique character and concept.