- or
1410 results found
-
Settings > Log-in & sign-up: Add company name field required
Use Case: We have two sales channels (B2B and B2C) and could set this up in the B2B sales channel.
2 votes -
Native support of IndexNow
Whats this?
"IndexNow is an easy way for websites owners to instantly inform search engines and web crawlers used for information retrieval (“search engines”) about latest content changes on their website. In its simplest form, IndexNow is a simple ping so that search engines know that a URL and its content has been added, updated, or deleted, allowing search engines to quickly reflect this change in their search results."
Currently supports: Microsoft Bing, Naver, Seznam.cz, Yandex, YepWebsite: https://www.indexnow.org/index
4 votes -
Returns-Management: Dealing with multiple returns / partial cancellation per order
I can currently only create one return per order via the returns management. However, this means that if I have two partial returns per order (for which I create two separate partial cancellations), both returns are visible on the second partial cancellation. However, only the specified returned item should be visible for each partial cancellation.
3 votes -
Revision of list prices
The implementation of strikethrough prices has been poorly and even incompletely implemented. In the ITA shop, we don't have a proper way to display a sale category, as the default function here also goes to the first tab.
And independently, the in-house solution/rule for discounted items in the dynamic product groups is incredibly slow.
The host once sent me the Slow Query. If printed out, I could wallpaper at least half the room (high ceilings in an old Berlin building).
So please take a look at the topic. Anyone who has multiple sales channels and different prices within them will wish they were back in Shopware 5. It was all easy peasy and performant.
The implementation of strikethrough prices has been poorly and even incompletely implemented. In the ITA shop, we don't have a proper way to display a sale category, as the default function here also goes to the first tab.
And independently, the in-house solution/rule for discounted items in the dynamic product groups is incredibly slow.
The host once sent me the Slow Query. If printed out, I could wallpaper at least half the room (high ceilings in an old Berlin building).
So please take a look at the topic. Anyone who has multiple sales channels and different prices within them will…
2 votes -
Color recognition - Image Keyword Assistant
The Image Keyword Assistant should be able to recognize colors. This is particularly important for variant articles, where the same images are often used in a different color.
3 votes -
Add informal (Du) text snippets for German language
It would be useful to have an offical "Du"-Version of the de-DE snippets, either natively or through the language pack.
6 votes -
Absolute discount should be possible per item
Currently it is not possible to give an absolute discount of e.g. 5€ on every item in the shopping cart but only a percentage discount or an absolute discount on the entire shopping cart.
It should be possible to give an absolute discount per item in the shopping cart.
3 votes -
Backend: Product Filtering and Customization - Filter Value
The product filters section needs more customization and can be optimized.
Here is an example of the main shortcomings:
1 - Allow the addition of custom fields and properties.
2 - Allow the use of operators such as: "Like," "=", "And," "Or," "Starts with," etc.
3 - Allow filtering by entering multiple values in a search field.8 votes -
Output the favicon of the sales channel for Google as well
Although other favicons are stored in the theme, Google seems to favour the favicon.ico in the public folder that displays your logo.
In fact, I have noticed this in several Shopware 6 shops in Google search results.
If you only have one public sales channel, you can simply replace the favicon.png with your own, but we have four sales channels with different favicons.
In this case, you have to set up redirects.
It would be better if the corresponding favicons of the respective shops were actually used and displayed.
1 vote -
Dynamic pricing or promotions based on affiliate code
Currently, Shopware does not allow evaluating the affiliate code via the rule builder prior to ordering or registering a new customer account, making it impossible to have affiliate-specific pricing or discounts based on those affiliate codes. This functionality should be added to the rule builder.
3 votes -
Quotes: Shipping and payment
For offers, the shipping method and payment method used cannot be changed or edited. A shipping method and a payment method are still specified. It should be possible to change this data when editing.
Bei Angeboten kann die verwendete Versandart und die Zahlungsart nicht geändert oder bearbeitet werden. Deonnoch wid eine Versandart und eine Zahlungsmethode angegeben. Bei der Bearbeitung sollte die Möglichkeit bestehen diese Daten zu ändern.
4 votes -
Filters for Flow Builder
For bigger lists of any entity, it is super important to have filters in order to find efficiently what you are looking for. We have filters for the Products, Customers, Rule Builder overviews and probably in many other menus as well.
There for we should most definitely also have this kind of filtering also for the Flow Builder overview.
Finding the flow you are looking for only with the search is a pain. Try to search for the flow "Order placed". Since the string "order" is part in 90% of all flows out of the box, you will not be able to find it but will need to filter manually through the list of flows again.
For bigger lists of any entity, it is super important to have filters in order to find efficiently what you are looking for. We have filters for the Products, Customers, Rule Builder overviews and probably in many other menus as well.
There for we should most definitely also have this kind of filtering also for the Flow Builder overview.
Finding the flow you are looking for only with the search is a pain. Try to search for the flow "Order placed". Since the string "order" is part in 90% of all flows out of the box, you will not be…
1 vote -
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 -
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
- Don't see your idea?