5 results found
-
Shopware Analytics - Beta Phase
Following the launch of the first iteration of Shopware Analytics, we are continuing to develop the next iterations, which will further enhance functionalities. Additionally, we will steadily introduce a series of new dashboards featuring more metric visualizations. These updates will be rolled out independently of Shopware minor releases, leveraging the flexibility of our App-based service.
We invite you to explore the new features of Shopware Analytics and share your feedback. Your insights and feedback will be considered during development to ensure continuous improvement.
Here you can find the original feedback, which was the base of the first iteration: https://feedback.shopware.com/forums/942607/suggestions/45651289
70 votesWe already started the further development and already added new statistics:
Added a new KPI “Promotion codes”
Added a new KPI “Sales by manufacturer”
Added a new KPI Sales by country
Added a new KPI Best selling products
UI enhancements and technical improvements
-
Compliance with the EU standard on eInvoicing till 2025
Please research about whether or not we should implement ZUGFeRD or x-invoice into Shopware and if yes, on how to implement it. Maybe this could be a good starting point (German only): https://stachowitz-medien.de/e-rechnungen/.
Please also think about communication if we will not implement this into Shopware.
48 votesWe are currently developing a solution to create e-invoices with Shopware 6.
-
B2B Components - Allow default permissions for new accounts or customer groups
There should be an option to set default permissions for new user accounts, perhaps based on customer group assignment. Currently the only way to automatically enable B2B Components features is through a custom registration form.
4 votes -
Specify what field-values are missing when saving a product having empty mandatory fields
Currently, if mandatory fields are empty while saving, the following message is shown:
"1x "This field must not be empty.""
This often times will lead to uncertainty since the exact field is not mentioned within the error message itself.
Therefore, it would be nice to have some kind of message that looks like:
[fieldname]: "This field must not be empty."
81 votesHello,
Thank you for your feedback and your patience with this topic!
In a first iteration, we already improved the error handling for the product module by highlighting the specific tab in which the error occurred and displaying a list of missing fields at the top of the module. In further iterations, we like to specify these messages.
In general, this topic is relevant not only for the product module but also for all kinds of user situations within the administration. We would like to work on this more generally and would love your feedback on it as well: https://feedback.shopware.com/forums/942607/suggestions/48892556.
We’ll keep you updated as things progress, and we appreciate your understanding and input!
Best,
Marie Reckendrees
-
Product visibility per debtor
Target user: B2B customers, mainly EnterpriseCurrent problem: you cannot limit catalogue views for customers. So you cannot limitate, what products customers do see, find and buy in the end.current workaround: with dynamic access we can limit product visibility to certain tags or customer groups. There is no bulk edit function so you have to do it individually for every product & customerpossible approach: should be done in combination with dynamic accesspossible scenarios:Show most of all products to all customers, plus a handful of products which are only visible to one specific customer, e.g., custom-made products.Each customer has his own hand-picked…
5 votes
- Don't see your idea?