- or
81 results found
-
I am trying to customize SEO URL slugs and encountered an issue
When I use variable meta-title in the url template, it works only for main products, not for variants, even if there is meta title inheritance enabled. But even when I check html of the variant page, meta title is not there. I don't know if you made it on purpose or it is a bug, but it means: I cannot use meta title variable for variants when creating a url.
This lead to my other thought: let's turn Use single canonical URL for all variants - because of course we do not want google to mark it as duplicates when we are using inheritance for all the descriptions and stuff. But when I turn it on, you force me to pick one of the variants. But I don't logically want it to be one of the variants, i want it to be main product. That leads me to another problem that I tried to solve with you: main product cant have the same product number as variant. So I cannot create variant as main product - so I cannot use it as main product for canonical URL. BUT! I think you would tell me: change storefront presentation, lets go to Product-Variants-Storefront presentation-Product lsitings and instead of Main product you could pick one variant and go with it. But I don't want to do it, because if I choose it as "Main product" in the storefront it is more beneficial since it shows, that there are more variants and price starts at.... You know what I mean? I don't want the specific size of the product be as main variant, you actually told me not to, since you require variant and main product to have different product number.
This is actually really frustrating. Because I want it (as it should be):
- main product - main URL - it is main product page that I want to be crawled by search engines
- variants - url with whatever slug added to the main product URL, but I don't want Google to crawl it.
Sounds pretty easy, right? And it even works like that, just not in case if I want to use MetaTitle as a slug.You give me these:
- main product - main URL (i want to use meta title for that and you allow it since it is in the list of supported variants)
- variant - can't use meta title - it makes it different url, which is ugly and not practical
- seo canonical - can use only variant, not meta title, so basically I have many duplicate pages and it takes us down from Google.When I use variable meta-title in the url template, it works only for main products, not for variants, even if there is meta title inheritance enabled. But even when I check html of the variant page, meta title is not there. I don't know if you made it on purpose or it is a bug, but it means: I cannot use meta title variable for variants when creating a url.
This lead to my other thought: let's turn Use single canonical URL for all variants - because of course we do not want google to mark it as duplicates when…
1 vote
1267 results found
-
Analytics: Add user permission to see statistics
Currently, when the Shopware Analytics extension is installed and active, any user has access to those statistics. Since these statistics show partly sensitive organisation data, there should be a user permission, in order to define which user can access the statistics.
Example:
We access our Admin in our local store, when customers ask for certain products. Now we access the dashboard and the customer will see exactly how much revenue we made.3 votes -
Easier process to apply changes from Staging to Live and from Live to staging
Usually, the right way to apply changes is to first test it in your staging system. After the testing is successful, you need to apply the same changes once again in your Live system.
It would be great, if those changes could be synced easily between the two environments, allowing to apply changes from the staging easy and fast also in the live environment.
2 votes -
User permissions: Selective access to elements (Shopping Experience Layouts, products, etc)
It would be great, if the user permissions would also allow to give users only access to specific elements of a menu.
For example, if a user is only supposed to have access to one specific Shopping Experiences layout to work on, it currently requires the user to get access to all layouts.
Especially when you are working with external partners, which should only have access to designated elements, a more detailed permission level would be useful.
2 votes -
Connect multiple databases to a Shop
Customer data is often a very sensitiv topic. In our case, the desired set up for storing the data would be to have one database for the Shop relevant and a complete separate database for all customer related data.
2 votes -
Product sets configurator
Many Shopware users are lacking the function "product sets", which allows the buyers to pick a selection of products from a list of products on product detail pages. This function is available via extensions, but this is considered a standard functionality, that a Shopsystem should provide out of the box.
Simular extension:
https://store.shopware.com/de/dvsn895115432267m/produkt-konfigurator-fuer-sets-bundle-konfigurator.html3 votes -
Configuration of the display of cross-selling (Shopping Experiences)
Within the cross-selling configuration or the ‘Shopping Experiences’, it should be possible to select different positions for the different cross-sellings.
This would allow the product detail page to be quickly customised even without individual programming.
4 votes -
Improve Admin search customer module
When creating a new order (Orders > Create order), the first step is for colleagues to search for a customer, usually using the e-mail address.
The customer they are looking for often only appears on page 4-5 of the search results - if they are found at all.
If no matching customer is found, colleagues use the “Create customer” button and enter the relevant customer data.
However, when saving, it is often found that the email address entered already exists, which leads to an abort.
Suggestions for improvement:
Optimization of customer search:
Improve search algorithms to find customers faster and more accurately based on their email address (or other unique criteria).
Implementation of a “live search” that displays possible hits as they are entered.
Check during customer creation:
Introduction of real-time validation of the e-mail address during entry in the “Create customer” form.
Immediate display of a message if the e-mail address already exists in the system to avoid the abandonment process.
When creating a new order (Orders > Create order), the first step is for colleagues to search for a customer, usually using the e-mail address.
The customer they are looking for often only appears on page 4-5 of the search results - if they are found at all.
If no matching customer is found, colleagues use the “Create customer” button and enter the relevant customer data.
However, when saving, it is often found that the email address entered already exists, which leads to an abort.
Suggestions for improvement:
Optimization of customer search:
Improve search algorithms to find customers faster…
3 votes -
Resend order confirmation
Implement a function / Add button to resend order confirmations
11 votes -
Manufacturer pages in the same tab
It would be useful if the shop owner could decide/set whether the link to the manufacturer's website (click on the logo/manufacturer on the product detail page) is opened externally in the new tag or in the same tab.
If a store page for the manufacturer is to be displayed instead of the manufacturer's website, this is less useful in a new tab.
Here it would be better if the owner had the option of opening the page in a new tab or in the same one
2 votes -
Rulebuiler condition which detects the change of payment method
Condition in the rulebuiler which determines the (non-balanced) change of payment method.
Something like: Used payment method was > Incoice > is now > prepayment
For example, in the flow builder you could influence the mails that are sent when the status changes, so that a distinction is made between manual switching (by the admin) or automated switching (by payment integrations) and the payment method change by the customer in the frontend.
Since the order also reaches the status “canceled” when the customer changes the payment method in the frontend, these mails could be prevented here, as they can be confusing.
Condition in the rulebuiler which determines the (non-balanced) change of payment method.
Something like: Used payment method was > Incoice > is now > prepayment
For example, in the flow builder you could influence the mails that are sent when the status changes, so that a distinction is made between manual switching (by the admin) or automated switching (by payment integrations) and the payment method change by the customer in the frontend.
Since the order also reaches the status “canceled” when the customer changes the payment method in the frontend, these mails could be prevented here, as they can be…
2 votes -
Bulk edit variants: enable change of cover image
If you filtered some variants by a property i.e. color, the bulk edit has no setting to select another Coverimage for products with selected properties. This would be helpful to avoid unnecessary work.
3 votes -
Storage stock alert / warning via Email
Storage stock alert / warning via Email:
- Minimum stock per item can be defined
- daily notification of affected items
In Shopware 5 there was a function to define a minimum stock per article. If this was undercut, the system sent an email message to the admin so that the stocks could be replenished.
37 votes -
Drafting: Create a draft state of your changes
Problem:
Users cannot currently create and manage a comprehensive draft state for changes across their storefronts. This makes it difficult to plan, test, or iterate on updates without affecting the live environment. As a result, merchants may delay changes, work in risky live environments, or rely on inefficient workarounds — increasing the likelihood of errors and reducing agility in campaign or content management.Solution:
Create and manage a draft state for all kinds of changes in Shopware before publishing them live. This allows you to bundle multiple updates, such as content, design, and promotions, into a draft, enabling safe workflows and reviews without affecting your live store. By facilitating collaboration and approval workflows, this feature improves control, reduces errors, and streamlines shop updates.Problem:
Users cannot currently create and manage a comprehensive draft state for changes across their storefronts. This makes it difficult to plan, test, or iterate on updates without affecting the live environment. As a result, merchants may delay changes, work in risky live environments, or rely on inefficient workarounds — increasing the likelihood of errors and reducing agility in campaign or content management.Solution:
Create and manage a draft state for all kinds of changes in Shopware before publishing them live. This allows you to bundle multiple updates, such as content, design, and promotions, into a draft, enabling safe workflows…2 votes -
Add field validation on storefront
Add field validation for fields like email/name/phone etc that can be configured in the setting.
Now someone can type anything, write text in the phone field or even just type "A" in the name field.
2 votes -
Better filter options within e.g. customer and order overview
If you work with the customer and order overview on a daily basis, this quickly leads to frustration.
For example, the number per page cannot be set and is far too low. This should be 100 or 200. Otherwise the unnecessary effort is too high and the work quickly becomes frustrating.
Also, the filter or listing is often reset when changing pages. This also takes an incredible amount of time.
We would like to see better handling here.
2 votes -
Further evaluation of the customer search
There should be an evaluation of customer search queries within the Shopware search.
This means that the search can be adapted to customers in ever greater detail. This is requested time and again by large customers.
2 votes -
B2B: Add option to product detail page like cost center, project, etc.
It would be great, if B2B store would have the option to add selection or comment fields on product detail pages.
This could be used, so that buyers can directly select the cost center or the project, which the product is bought for. This information could then be automatically integrated into the invoices, saving a lot of manually effort for the finance department.
2 votes -
Migration: Automatic placeholders for missing values
Customer migrations are tedious and involve a lot of work, as data records are often not transferred to Shopware 6 because they are missing from Shopware 5.
For example, if the salutation of a customer is not filled in Shopware 5, but the field has become a mandatory field in Shopware 6. Or the first name.
To make migrations much easier, the migration wizard should store a meaningful placeholder in such cases so that the data is transferred correctly.
Within Shopware 6, you can then search for these placeholders and adjust the entries. This takes away the frustration that many customers experience during a migration.
Customer migrations are tedious and involve a lot of work, as data records are often not transferred to Shopware 6 because they are missing from Shopware 5.
For example, if the salutation of a customer is not filled in Shopware 5, but the field has become a mandatory field in Shopware 6. Or the first name.
To make migrations much easier, the migration wizard should store a meaningful placeholder in such cases so that the data is transferred correctly.
Within Shopware 6, you can then search for these placeholders and adjust the entries. This takes away the frustration that many…
2 votes -
New Trigger for the Flow Builder: Customer Login
Currently, the Flow Builder does not offer a dedicated trigger for logging into a customer account, only in connection with the checkout process. This significantly limits automation possibilities.
Proposed Enhancement:
A new "Login" trigger that activates whenever a customer logs into their account – independently of the checkout process.Possible Use Cases:
Automatic tag assignment based on login frequency.
Customer group changes for logged-in users, e.g., granting access to exclusive content or discounts.
Automated email dispatch, e.g., a welcome back message after a long period of inactivity or targeted marketing campaigns.
2 votes -
Improve UI and Logic for Postal Code Validation and Advanced Validation Rules
he current UI for the Postal Code settings is not intuitive and may confuse users. The "Advanced Validation Rules" option can only be enabled after enabling "Postal Code Validation," but there is no clear indication that these options are linked. Additionally, there is no visibility into which validation rules apply when enabling "Postal Code Validation."
Problems Identified:
Lack of clear dependency between "Postal Code Validation" and "Advanced Validation Rules."
No information on which postal code validation rules are applied by default.
Unclear if "Postal Code Required" influences the validation settings.
2 votes
- Don't see your idea?