- or
No existing idea results
- ~ No ideas found ~
1498 results found
-
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 -
AI-Generated Category Images Based on Product Data
Large online shops or platforms often rely on visually appealing category tiles (e.g., “Summer Dresses,” “Outdoor Furniture”) to help users navigate vast product catalogues. These tiles typically feature manually selected photos or stock imagery, which is time-consuming to curate and often lacks contextual alignment with the actual product assortment in the category.
The idea:
Use AI to automatically generate descriptive images for category tiles by analyzing the product data within each category. The system would ingest product information such as titles, descriptions, dominant colors, materials, common product types, and price ranges — and use this data to create a representative, realistic image via AI.Large online shops or platforms often rely on visually appealing category tiles (e.g., “Summer Dresses,” “Outdoor Furniture”) to help users navigate vast product catalogues. These tiles typically feature manually selected photos or stock imagery, which is time-consuming to curate and often lacks contextual alignment with the actual product assortment in the category.
The idea:
Use AI to automatically generate descriptive images for category tiles by analyzing the product data within each category. The system would ingest product information such as titles, descriptions, dominant colors, materials, common product types, and price ranges — and use this data to create a representative,…2 votes -
Add calculation possibility to rule builder
In some cases, the total height or width of a load is required. This may differ from the height of a single product, so such a rule would be helpful.
2 votes -
Enable Search for Custom Fields in B2B Quick orders search field
The B2B Components Quick Order feature should be extended to support searching by custom fields.
This would allow companies to tailor the search experience to their specific data models—for example, enabling search by internal article numbers, supplier SKUs, or industry-specific identifiers. Enhancing the search logic in this way significantly improves usability and efficiency for B2B customers who rely on custom attributes in their ordering processes.
2 votes -
Show admin user who created an order
Currently there is only a static badge that shows if an order was created by an administrator.
It would be nice if the actual user could be displayed, for example as a tooltip in the order list and directly in the badge in the order details.
5 votes -
AI enable headless shop to use the features
EN
If a headless store wants to use the AI features, there is no API endpoint that can be used for this. At least there is no reference to this in the developer documentation.
So the idea is to make AI features usable via API and document the functionality.DE
Wenn ein headless shop die AI Features nutzen möchte, gibt es keinen API Endpunkt, der dafür genutzt werden kann. Zumindest ist in der Entwicklerdokumentation diesbezüglich kein Hinweis zu finden.
Idee ist also: AI feature über API nutzbar zu machen und die Funktionalität zu dokumentieren.2 votes
- Don't see your idea?