- or
1269 results found
-
Extend ScheduledTask "delete_newsletter_recipient_task"
It seems that the deletenewsletterrecipient_task only removes unconfirmed newsletter subscribers that remain in that particular state for longer than x-days. It would be good, if we could automatically remove all newsletter recipents that already unsubscribed and remain in status "Awaiting deletion". Those currently have to be deleted manually.
9 votes -
Promotion label
Used promotions have a position in the cart, given the promotion's name. That name therefore normally should be something "understandable for the customer".
However when having a larger number of promotions, it can get quite confusion to work internally with all the promotions in a shop, having nothing but these "customer friendly names".Solution: The "name" of promotions is their internal identifier. Above that every promotion gets a field for a public "label" which its position in the cart gets labeled when cashed in.
Example:
Shop has three different promotions named "10 % new customer promotion", "10 % newsletter voucher" and "10 % easter campaign" for unique identification internally.
When used, each of these promotions positions uses its "labals" instead of their "names", which could even be the same label in all three cases (for example simply "your 10 % discount")Used promotions have a position in the cart, given the promotion's name. That name therefore normally should be something "understandable for the customer".
However when having a larger number of promotions, it can get quite confusion to work internally with all the promotions in a shop, having nothing but these "customer friendly names".Solution: The "name" of promotions is their internal identifier. Above that every promotion gets a field for a public "label" which its position in the cart gets labeled when cashed in.
Example:
Shop has three different promotions named "10 % new customer promotion", "10 % newsletter voucher"…7 votes -
Custom Product- Amount in Off Canvas
The quantity of a configuration can currently only be specified on the product detail page. If a customer tries to increase it in the off-canvas menu, it won't work.
2 votes -
GPSR EU Rule 2023-988
GPSR EU Rule 2023-988 - valid from December 13th, 2024
In order to display this correctly in the shop, the manufacturer needs the following additional fields, which are also displayed in the Manufacturer tab:
Address
Email address
When importing from third countries - responsible person in the EU (for this manufacturer)
Name, address, email addressFurthermore, warnings are required for many products.
In order to display these correctly, an additional field for these warnings would be very helpful.You can of course put it all together yourself. But since it is an EU standard, we think it would make sense to add it as a standard in Shopware.
GPSR EU Rule 2023-988 - valid from December 13th, 2024
In order to display this correctly in the shop, the manufacturer needs the following additional fields, which are also displayed in the Manufacturer tab:
Address
Email address
When importing from third countries - responsible person in the EU (for this manufacturer)
Name, address, email addressFurthermore, warnings are required for many products.
In order to display these correctly, an additional field for these warnings would be very helpful.You can of course put it all together yourself. But since it is an EU standard, we think it would make sense…
4 votes -
deactivate emails to customers after status change globally
After manual status change in the orders, even if I delete all the flows in the shop, Shopware6 always asks me to send emails to the actual customers. I need settings the skip this step.
13 votes -
Add function for assigning cross-selling articles category-wide.
At the moment, you have to assign the cross-selling articles manually for each article. Here it would be good to add the function of being able to specify cross-selling articles directly for the category, so that you have the option of automatically assigning these cross-selling articles to all articles in this category.
1 vote -
There should be a bulk edit function for categories to set one lyout for several categories.
It is currently not possible to assign one layout to several categories at the same time.
There should be a bulk edit function or a similar function for categories, so this will be possible.2 votes -
The product cards of the search results from AI should be exactly the same as the regular product cards
Hi,
It makes no sense why the product cards on the search results from AI are different from the standard product cards used at listings and the regular search results, or cross-selling sliders.
Now you can only click on the product to open the product detail page, while you would rather have a customer inform about the prices and provide the ability to add the products to the cart.
1 vote -
Add column country in customer overview
More address data for information is often asked for the customer and order overview. Please add acountry for a durable selection.
7 votes -
Rendering Mailtemplate
When an email template is customized, it's possible that certain objects cannot have a "null" value. If this occurs, the email template will not be sent, and no error message will be logged. This leads to additional analysis effort.
3 votes -
API: Status of E-Mail
Setzen der Status der einer E-Mail versand/nicht versandt nach Dokumentart an der Bestellung per API
Set the status of an email sent/not sent by document type on the order via API
2 votes -
Automated Birthday Greetings with Discounts
I would like to suggest an enhancement to Shopware 6 that brings back a popular and valuable feature from Shopware 5: automatically sending birthday emails with discount codes or greetings to customers.
The Issue:
Currently, Shopware 6 lacks the functionality to automate birthday-related actions through the Rule Builder and Flow Builder. This prevents shop owners from creating personalized birthday campaigns, which are an effective tool for customer engagement and loyalty.Proposed Solution:
Enhance the Rule Builder and Flow Builder with the ability to:Identify Birthdays:
Add a rule condition that checks the "Date of Birth" field in customer profiles.
Allow dynamic filtering, such as "is today," "is in the next X days," or "has already occurred this year."
Automated Email Trigger:Enable automated email workflows based on the customer's birthday, either on the exact date or as part of a pre-scheduled campaign.
Custom Discount Code Generation:Integrate the ability to generate unique, single-use discount codes as part of the workflow.
Include these codes dynamically in the email template.
Personalized Messaging:Allow email templates to include dynamic fields, such as the customer's name or age (optional), to make the greetings feel personal.
Benefits for Shop Owners:Strengthened Customer Loyalty: Birthday emails are a great way to engage customers on a personal level and show appreciation.
Increased Sales Opportunities: Discounts incentivize customers to make a purchase, driving revenue.
Time Efficiency: Automating this process saves time for shop owners, especially for shops with a large customer base.
Customer Delight: A thoughtful gesture like a birthday greeting can leave a lasting positive impression.I would like to suggest an enhancement to Shopware 6 that brings back a popular and valuable feature from Shopware 5: automatically sending birthday emails with discount codes or greetings to customers.
The Issue:
Currently, Shopware 6 lacks the functionality to automate birthday-related actions through the Rule Builder and Flow Builder. This prevents shop owners from creating personalized birthday campaigns, which are an effective tool for customer engagement and loyalty.Proposed Solution:
Enhance the Rule Builder and Flow Builder with the ability to:Identify Birthdays:
Add a rule condition that checks the "Date of Birth" field in customer profiles.
Allow…1 vote -
Add Function Customer Streams in Shopware 6
In Shopware 5, it was possible to sort customers into the following customer streams:
The following Dynamic segmentation: customers are automatically sorted into streams as soon as they fulfill the criteria.
Parallel groups: Customers can be in multiple streams, allowing flexible segmentation.
Possible applications: Streams can be used for personalized marketing campaigns, specific discounts or targeted newsletters.
Please add the customer stream again in Shopware 6:
Customers can be assigned to one or more dynamic groups.
The dynamic customer groups should be definable via the Rule Builder and the standard customer group (e.g. B2B, standard customer) should not be changed.
The dynamic groups should exist in parallel and not affect the basic configuration. The whole process should take place without the use of tags.
The goal is to use the customer streams to adapt the frontend output to articles with the help of the dynamic product groups. This based on the sales history of already purchased products, categories, brands, etc.
In Shopware 5, it was possible to sort customers into the following customer streams:
The following Dynamic segmentation: customers are automatically sorted into streams as soon as they fulfill the criteria.
Parallel groups: Customers can be in multiple streams, allowing flexible segmentation.
Possible applications: Streams can be used for personalized marketing campaigns, specific discounts or targeted newsletters.
Please add the customer stream again in Shopware 6:
Customers can be assigned to one or more dynamic groups.
The dynamic customer groups should be definable via the Rule Builder and the standard customer group (e.g. B2B, standard customer) should not be changed.
…
1 vote -
Allow data mapping of custom fields in CMS Elements
Currently it is only possible to use shopware standard fields via data mapping in CMS elements. It would be great if we could also use custom fields here.
7 votes -
Show variants in admin product list
EN
Display variants permanently in the product overview via option. It is repeatedly pointed out that it is inconvenient for editing that information on variants can only be viewed after opening the main product, for example, prices or stock.DE
Varianten per Option dauerhaft in der Produktübersicht anzeigen. Es wird immer wieder darauf hingewiesen, dass für die Bearbeitung unpraktisch ist, dass Informationen zu Varianten erst nach dem Öffnen des Hauptprodukts einsehbar sind, zum Beispiel Preise oder Bestand.25 votes -
Enable CSV upload for shopping lists directly in the shopping lists menu
Currently it is only possible to upload CSV files via the quick order function.
These orders can then be made into a shopping list.
The upload of CSV files however is not possible via the feature "shopping lists" directly, which you would expect.
It would be beneficial to add this functionality directly in the shopping lists feature in the frontend/admin.1 vote -
Add the option to create a subscription out of the quick order
As a merchant/customer it would increase the ease of use if I would have the option to create a subscription out of a submitted quick order.
1 vote -
It should be possible to migratate customers without firstname and family names.
Currently you need a first name and family name to migrate customers from SW5 to SW6. Sometimes Customers are not real persons but companies.
There should be an option for that.1 vote -
Query data from Shopware Analytics
It would be good if the data from Shopware Analytics could be accessed via the API in order to integrate it into Grafana, for example.
1 vote -
Customer Repository and Context:SKIP_TRIGGER_FLOW by default
The idea is to modify the injected context to the customer repository by SKIPTRIGGERFLOW.
During the creation of the integration plugin with any system in the customer synchronization process, we always have to remember to add Context:SKIPTRIGGERFLOW otherwise a lot of emails are sent to the imported customers.1 vote
- Don't see your idea?