Settings and activity
1 result found
-
101 votes
We 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
An error occurred while saving the comment An error occurred while saving the comment 
Mona Maisack
commented
Hello everyone,
I am testing the new Shopware Analytics feature on Shopware 6.7.11.1, and I noticed that the charts strictly use UTC±0 instead of the timezone configured in the Shopware Admin profile (e.g., Europe/Berlin).
For example: An order placed at 07:00 AM local time is displayed as 05:00 AM in Shopware Analytics.
Since Shopware Analytics is an independent app-based cloud service, it seems it doesn't read the context.timezone from the browser profile yet. This shifting makes it difficult to correctly evaluate hourly sales peaks and day-to-day transitions (orders around midnight get pushed to the previous day).
It would be great if the dashboard charts could automatically adjust to the local timezone set in the user profile, just like the core order overview does.
Thanks for the great work on this tool so far!
Mona Maisack
supported this idea
·
Hello Shopware Support Team,
We are currently facing an issue with the Shopware Analytics (Beta) extension and would like to report a bug.
Our Environment:
Shopware Version: 6.7.11.1
Note: We are aware that version 6.7.12.1 is available, but due to internal deployment schedules, we cannot perform the update for another few weeks. Therefore, we need to address this on our current version.
Problem Description:
We are receiving the following error message in the Analytics dashboard:
code: 376, Cannot parse uuid : while converting '' to UUID
Initially, we suspected a conflict with a third-party plugin (Acris EU Cookie Richtlinie Pro). However, the plugin vendor investigated the issue directly in our system and clearly ruled out their extension. The tracking itself works perfectly. The issue lies within the Shopware Analytics query logic.
Detailed Findings & How to Reproduce:
The trigger: The error occurs only when filtering the Analytics dashboard by our specific sales channel: "WEIN-MOMENT".
Affected reports: The error exclusively breaks session-based evaluations (such as Conversion Rate, Unique Visitors, and Most Popular Search Terms).
What works:
If no sales channel filter is applied, the data displays flawlessly (e.g., showing the correct number of unique visitors).
Order- and revenue-based evaluations work perfectly fine, even when the "WEIN-MOMENT" filter is active.
Conclusion:
The tracking data is being captured correctly in the database. However, as soon as the sales channel filter for "WEIN-MOMENT" is applied, the Shopware Analytics query seems to pass an empty string ('') instead of a valid UUID, causing the database/application to throw the conversion error.
Since this is an Analytics Beta feature, could you please check if this is a known bug and if there is a known hotfix or workaround we can apply before we upgrade to 6.7.12.1?
Thank you for your support!