- or
No existing idea results
- ~ No ideas found ~
1484 results found
-
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 -
Optionally, the net prices should remain the same, even if there are other taxes in other countries.
Currently, the net price changes if you offer products in other countries with different taxes. The gross price remains the same.
There should be an option to decide for yourself whether the net price remains the same with a variable gross price, or whether the gross price remains the same with a variable net price.
79 votes -
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 -
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 -
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 -
Provide a GUI for non-technical tasks in Shopware Native PaaS
Not everyone is comfortable using sw-paas commands for everyday tasks. A simple dashboard for creating apps, cloning environments, etc would make Shopware Native PaaS easier to use for less technical users.
2 votes -
Shorten and simplify the sw-paas build history display
The build history in sw-paas grows very long, making it hard to find the latest entry. By default, show only the most recent few builds with an option to expand the full history. Clear formatting and a summary line like “Latest build: SUCCESS at 14:35” would make it much easier to read.
2 votes -
Command to fully clone an environment in sw-paas
Setting up a new staging or testing environment in Shopware Native PaaS is slow because everything has to be reinstalled and reconfigured manually. A single sw-paas command could copy the database, settings, and plugins from an existing environment in one step, saving significant time.
2 votes -
Make it easy to hide deleted apps in sw-paas
Right now, the sw-paas list shows apps that have already been deleted. This clutters the view and makes it harder to find what’s actually active. It would be great if deleted apps were either hidden or clearly marked so they’re easy to ignore.
2 votes -
B2B Components: Multi-level approval
Multi-stage approvals are always required, agreed and requested by large customers. This is required in large and complex environments.
3 votes -
Improve the inheritance of properties in variants
Currently, the properties are all inherited from the main article to the variants. This can be helpful for the property “heavy”, for example, but it is a hindrance if, for example, the main product is in the color “red” and this is also transferred to the variants.
5 votes -
Image keyword assistant for logos
The image keyword assistant should be able to recognize well-known logos, not just objects.
For example, when you upload the Shopware logo, only “Logo” appears as the alt text. When you upload Facebook logo, “Symbol, sign, cross” appears, which isn't really accurate, and nothing appears at all for Instagram logo.
1 vote -
Mail Templates - Show Order Employee Details
It should be possible to show the first and last name of the order employee in mail templates - just like order confirmation.
4 votes -
Unstable Behavior of the Rich Text Editor in Content Modules
Background:
As a team that works extensively with Shopware’s CMS and builds sophisticated pages via Shopping Experiences, we’ve repeatedly encountered critical usability issues with the built-in rich text editor used in content modules and custom fields.Problem:
The current text editor behaves inconsistently and creates significant friction in content workflows:It frequently injects arbitrary CSS classes into the HTML output without user input.
There is no easy way to reset text color back to the default.
When applying formatting such as bold, it sometimes adds font color tags even though no color change is intended or visible.
Bullet points are difficult to handle correctly — indentation from the left margin is often broken, and formatting differs inconsistently between modules or contexts.
These bugs and inconsistencies make it unnecessarily difficult to edit and style text, especially for more complex layouts.
Wish / Recommendation:
We would like to see a more robust and predictable editor with the following improvements:Clean and controlled HTML output without injected inline styles or classes.
A reset function for colors and formatting.
Standardized and reliable bullet point behavior across modules.
Generally more stability and polish, especially for professional users managing large-scale CMS layouts.
Background:
As a team that works extensively with Shopware’s CMS and builds sophisticated pages via Shopping Experiences, we’ve repeatedly encountered critical usability issues with the built-in rich text editor used in content modules and custom fields.Problem:
The current text editor behaves inconsistently and creates significant friction in content workflows:It frequently injects arbitrary CSS classes into the HTML output without user input.
There is no easy way to reset text color back to the default.
When applying formatting such as bold, it sometimes adds font color tags even though no color change is intended or visible.
Bullet points are…
2 votes -
CMS Extension: Allow custom form to be used for newsletter sign-up
Currently, a custom form provided by the CMS extension can only be used to have a customer send a request to a predefined e-mail address. The ability to also use a custom form for newsletter registration would allow the shop owner to customize the layout or add some basic things, i.e. their own mandatory terms & conditions checkboxes.
3 votes
- Don't see your idea?