- or
No existing idea results
- ~ No ideas found ~
1434 results found
-
Delivery time as Rule Builder condition
The Rule Builder is missing the option to use the delivery time of a product as a condition. This would be a useful improvement, for example to use this as an availability rule for shipping methods.
7 votes -
Logging of running flows
For monitoring the system and testing flows, it is extremely important that there is logging in the admin area.
The following information is important for logging:
- When did the flow run?
- Which trigger was activated?
- Which data was fed into the flow?
- Which data was decisive for the conditions?Zapier provides excellent logging for such systems.
2 votes -
Show detailed error message why a voucher could not be redeemed.
Regardless of whether a promotion is no longer valid (end date reached) or the maximum number of redemptions has already been reached, the error message in the offCanvas is always the same and therefore confusing for the customer.
Currently, the content from snippet ‘checkout.promotion-not-found’ is displayed per se.
It would be desirable if the exact reason why the voucher code cannot be used was given in relation to the above examples, i.e.
- ‘Promotion is no longer valid / expired’
- ‘Maximum number of redemptions already reached....’
5 votes -
"not specified" salutation handling
This is handled rather inconsistently in Shopware. In some but not all places, if you leave out the salutation, Shopware searches the database for the "not_specified" entry that comes with the installation and inserts it if found. If also sometimes inserts it just for display in the Administration if the real salutation reference is null, so you wouldn't even know the real value without looking directly into the database, but again, not always.
Crucially, that "not_specified" entry can be changed and deleted at will, so there's no guaranteed meaning behind it.
Also, sometimes like in the contact form the salutation is randomly required. You can delete it for addresses and the database has a default value of null, but then there is a non-configurable validator that won't let you through the checkout process if no salutation is given. And again, "given" can just mean that you set the "not_specified" salutation, which can have any meaning you assign to it.
This is an intransparent mess and should be changed. The very legality of requiring a salutation is now even in question. Just allow null values for all salutations in the application, it's already allowed in the DB structure, stop enforcing it in random places without a way to turn it off, and make the display name of a "null" salutation translatable via config.
This is handled rather inconsistently in Shopware. In some but not all places, if you leave out the salutation, Shopware searches the database for the "not_specified" entry that comes with the installation and inserts it if found. If also sometimes inserts it just for display in the Administration if the real salutation reference is null, so you wouldn't even know the real value without looking directly into the database, but again, not always.
Crucially, that "not_specified" entry can be changed and deleted at will, so there's no guaranteed meaning behind it.
Also, sometimes like in the contact form the salutation…
1 vote -
Keep admin menu open
Please stop auto collapsing the menu sidebar, when clicking on the page editor (Erlebniswelten). Its so annoying and completely unnecessary on large screens.
5 votes -
Hide empty entities in search results
Add an option that allows to hide empty entities in search results.
One example here would be manufacturers that are not being assigned to any products in the given sales channel.
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.
6 votes -
Net margin of sold products
Hello,
We are missing the net margin of products sold that day. It would be cool if this could be added e.g. an average margin for all sales and a margin per supplier and/or product.
(price.net-purchaseprice.net)/price.net
Thanks in advance!
Kind regards,
4 votes -
maintenance mode without own path
Make active Maintenance-Mode not redirect to another path. Render the maintenance page with the status code if the maintenance mode is active, keeping the current URL.
This makes the customers happy. while they don't need to find out where they were before.
1 vote -
Display order details clearly on one page instead of using tabs (similar to Shopware 6.4)
The details of an order should be clearly displayed on one page. Unfortunately, the details are currently spread across several tabs.
Clicking around, loading the various tabs and changing details takes longer than if everything could be done on one page.
Shopware 6.4 is clearer than Shopware 6.7.
Please change this.
1 vote -
Image keyword assistant multi-language support
It should be possible to generate the alt texts for multi-language shops in the respective language.
5 votes -
Avoiding errors with PayPal partial refunds
The PayPal API built into Shopware enables refunds with a single click. Unfortunately, in the hustle and bustle of everyday customer service, mistakes often occur with partial refunds—for example, instead of a $20 discount, the entire amount ($100) is accidentally refunded. This happens to every employee at least once a month because the entire amount is preset in the “Amount” field by default and it is easy to forget to adjust it.
Possible solutions:
1) The “Amount” field is empty and the amount must be actively entered.
2) The amount is highlighted in red.
2) A warning message appears: “Do you really want to refund the full amount?”
4) A second button with a less saturated color, “Partial refund,” is placed next to the blue “Refund” button.
Can Shopware or PayPal do anything about this, or is there already a solution?
The PayPal API built into Shopware enables refunds with a single click. Unfortunately, in the hustle and bustle of everyday customer service, mistakes often occur with partial refunds—for example, instead of a $20 discount, the entire amount ($100) is accidentally refunded. This happens to every employee at least once a month because the entire amount is preset in the “Amount” field by default and it is easy to forget to adjust it.
Possible solutions:
1) The “Amount” field is empty and the amount must be actively entered.
2) The amount is highlighted in red.
2) A warning message appears: “Do…
6 votes -
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 -
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 -
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.
26 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
- Don't see your idea?