1382 results found
-
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 -
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 -
Use Thumbnails for Property Images in Filter
Please adjust the default template
Resources/views/storefront/component/listing/filter/filter-property-select.html.twig
so that when images are assigned to properties, the appropriate thumbnail images are used instead of the full original images.Currently, the original image is loaded, which can negatively impact page load performance.
In our instance, I’ve already implemented a manual fix by replacing:
{% set media = element.media.url %}
with:
{% set media = element.media.thumbnails | filter(t => t.width == 100 and t.height == 100) | first.url %}This ensures that a 100x100 thumbnail is used when available.
3 votes -
Add newsletter subscription checkbox on account registration
Add the ability to activate newsletter subscribe checkbox on the account registration (/account/login and /checkout/register). So a switch in the admin settings (probably Log-in & sign-up or Newsletter), when it's turned on, a checkbox in the registration pages appear to subscribe for the newsletter, just above the CTA.
6 votes -
Add a "budget functionality" to the B2B Components
The permission management of the B2B Components does not properly fill out the function of managing budgets for each B2B Components user.
Someone needs to keep track on how much a customer has bought and if his/her budget is spent.
They also need to know how high the budget is with no indication of that being given via our B2B Components.I good way to solve this would be to build a budget functionality as in the B2B Suite.
That would make it easier to keep track of the budget and it would reduce the amount of controlling.12 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…
2 votes -
Add hreflang support across multiple sales channels
Currently hreflang only applies to different domains within one sales channel. It would be useful to be able to define other languages for hreflang tags across multiple sales channels (i.e. separate sales channels for EU and US, linking to each other)
6 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 -
Make first- and last name optional for company accounts
First- and last name should be optional if setting up a new customer entry through the administration or by using the register form IF it is a company account.
24 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,…2 votes -
Language inheritance for Custom Fields
Just like other fields in the products (title, description, etc.) the custom fields should inherit the values from a parent language unless overwritten. Currently, they just remain empty.
5 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 -
Produktvergleich
EXPORT TOO SLOW!!!
The export from the product comparison is much too slow at >170k products. In SW5, it took me less than a minute for the PriceAndStock feed. Now it takes at least an hour. We need at least a half-hourly export.
Please fix this. Thank you.
1 vote -
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?