- or
No existing idea results
- ~ No ideas found ~
1396 results found
-
Add selection field in user profile settings for measurement preferences
When a user changes the unit in a product, this change is applied at the user level and stored in the database in the
user_configtable with the keymeasurement.preferenceUnit. If there is already a dedicated entry for this in the database, it would be nice if the selection could be changed directly in the user profile.1 vote -
JSON LD
JSON LD ist seit über einem Jahrzehnt das Standardformat, um Produktdaten in Online Shops strukturiert vorzuhalten.
Es ist deutlich einfacher zu warten, separiert die Daten klar von der Markup ... und ist von Shopware zu erwarten ;)
–
JSON LD has been the standard format for storing product data in online shops in a structured manner for over a decade.
It is much easier to maintain, clearly separates the data from the markup ... and is to be expected from Shopware ;)
1 vote -
Shopware Publisher: Creates a possibility to restore old versions
Creates a way to restore old versions within Shopware Publisher
5 votes -
AI-powered product recommendations for B2B reorders
Instead of classic recommendations like “You might also like,” B2B shop customers should proactively receive notifications about which products they are likely to run out of soon, based on their individual order history.
Example: “You will probably run out of this product in about 3 months.”:
- Configurable forecast periods (weeks/months).Especially useful for shops with high order volumes (several hundred orders per customer).
Benefit: Simplifies reordering, increases customer satisfaction, and can boost sales.
2 votes -
Optimizing the Guest Session: Seamless Transition to Registration During Checkout
If a guest visitor is in a guest session and goes through the checkout process up to the order confirmation page (/checkout/confirm), but then decides to create an account, they currently have to return to the shop (i.e., leave the checkout). However, there is no direct option to register there, as the guest session is still active and would need to be ended first.
An inexperienced user might not immediately realize this and, in the worst case, abandon the purchase.
Additionally, if a visitor in a guest session manually accesses the login page (/account/login), the registration form is displayed and can be submitted, but it is simply cleared because the guest session is still active.
It would be beneficial if visitors/customers were more prominently offered a way to reach the login page within the guest session, possibly combined with a notice that the guest session must be ended or by automatically terminating the guest session.
If a guest visitor is in a guest session and goes through the checkout process up to the order confirmation page (/checkout/confirm), but then decides to create an account, they currently have to return to the shop (i.e., leave the checkout). However, there is no direct option to register there, as the guest session is still active and would need to be ended first.
An inexperienced user might not immediately realize this and, in the worst case, abandon the purchase.
Additionally, if a visitor in a guest session manually accesses the login page (/account/login), the registration form is displayed and…
7 votes -
Export orders with redeemed voucher codes
I would like to be able to use the export tool to export all voucher codes redeemed for an order as part of the order export.
3 votes -
Export SEO route by product main category
Several times it had been asked to send a TWIG variable for exporting the path of the main category, that is defined via catalogues > products > SEO and can be found if a special sales channel was selected in section seo-urls.
Currently the sales channels for product comparision (product export) or Social Shopping have no working variable to read the main category's seo-route.
Please check if it can be added to provide an easier export.
3 votes -
Integration of background videos in worlds of experience
It is currently not possible to integrate a background video - comparable to the display on https://scd.shopware.com/ - natively into a CMS page with the standard experience world elements in Shopware 6. Although video and HTML elements exist, these do not allow a combination of background video and overlaying content (e.g. text, buttons, HTML block).
The integration of a video as a background is a common design element in modern web design and is used in particular for landing pages, campaigns or emotional brand appearances. The current CMS structure only allows this with considerable technical effort (e.g. through individual CMS components, theme customizations or third-party plugins). This significantly restricts the creative and design freedom of editors.
Proposal for implementation:
- Expansion of the worlds of experience to include a new standard element with the following features:
- Option to integrate a video (MP4 or external source) as a background video
- Option to activate autoplay, mute, loop and poster image
- Overlaying content layer with configurable slots for:
- Text (WYSIWYG)
- HTML editor
- buttons
- Full responsiveness (mobile optimization, optional fallback image)
- Optional transparency or color overlay settings for better readabilityBenefits:
- Greater visual design options without technical hurdles
- Enables conversion-oriented landing pages directly in the Shopware backend
- Improves usability and reduces dependency on third-party developers or plugins
- Contributes to branding through modern visualsIt is currently not possible to integrate a background video - comparable to the display on https://scd.shopware.com/ - natively into a CMS page with the standard experience world elements in Shopware 6. Although video and HTML elements exist, these do not allow a combination of background video and overlaying content (e.g. text, buttons, HTML block).
The integration of a video as a background is a common design element in modern web design and is used in particular for landing pages, campaigns or emotional brand appearances. The current CMS structure only allows this with considerable technical effort (e.g. through individual CMS…
3 votes -
organisation unit should be defined in new emplyee
As the organisation units are available with version 6.7, it should be possible to map the unit for new employees.
Currently only the role can be set.
Employees can only be mapped within the organisation unit when the employee is active (invitation link is clicked within the 2 hours reaction time).
If organisation units are active in the customer and units are defined, it should be possible to map it within the employee mask. For existing and new employees.
1 vote -
Add empty alt tags to untagged thumbnails in image galleries
Untagged images in the gallery get an empty alt tag when not tagged, which is a good default behaviour. The thumbnails in the gallery also need this. Currently, untagged images don't get any alt tag at all. This is an accessibility problem!
1 vote -
Treat quote management like a normal checkout.
Quotes should be treated in the same way as normal orders. Availability rules such as items in the shopping cart do not work in Quote Management, because the items are not in the shopping cart when placing an quote order.
Third-party extensions that extend the checkout process often also not work, either partially or completely.
1 vote -
CAPTCHAs: Different keys per sales channel
You can currently only store one key pair per CAPTCHA in the Basic information. If you change the sales channel in the
Basic information and enter another key, the previous one will be overwritten.9 votes -
Convert digital <> physical products
It should be possible to convert a physical product to digital or the other way around in the product module
1 vote -
Contact Form: Remove salutation Requirement
In most places, the salutation is no longer a requirement, but for some reason, in the contact form, it still is.
If you want to override this via an extension, you have to override not only the template but also the validation as well as the ContactFormRoute since it builds criteria with the salutationId and assumes it to be set.
There doesn't seem to be a good reason to force this requirement. At the very least, there should be a config to make the field optional.1 vote -
Check plugin compatibility before updates in Shopware Native PaaS
Unlike self-hosted Shopware, Shopware Native PaaS doesn’t show whether installed plugins are compatible with the next Shopware version before updating. This forces manual checks — and internal plugins can’t be checked at all. A compatibility check tool in sw-paas or a dashboard would save time and reduce update risks.
2 votes -
Support cron jobs per application in Shopware Native PaaS
Some business processes (like product imports) need automated scripts to run on a schedule. Shopware Native PaaS should support cron jobs per application, ideally managed through sw-paas.
2 votes -
Allow application updates without logging all Admin users out
Updating an application in Shopware Native PaaS currently forces all Admin users to log out, interrupting work. Updates should be possible without logging everyone out.
2 votes -
Show only compatible updates in composer outdated
The composer outdated command lists updates even if they aren’t compatible with the current Shopware version. It would be more useful if it only showed updates that can actually be applied.
1 vote -
Show which plugins have updates in the Admin
When the “Extension updates are available” popup appears in the Admin, it’s unclear which plugins need updating. The affected plugins should be listed directly in the Admin.
2 votes -
Allow SSH or SFTP access to applications
Debugging plugins and themes in Shopware Native PaaS would be much easier if developers could connect directly to files and the database via SSH or SFTP.
2 votes
- Don't see your idea?