Known Bugs in the Native PrestaShop Dashboard
The PrestaShop Dashboard is one of the platform's most criticized features, and has been for years. The issues are documented on the official forum, GitHub, and PrestaShop developer communities.
The first recurring bug involves visitor and session counting. The native statsdata module records visits in the database, but it counts bots, crawlers, and monitoring tools as real visitors. Result: your visitor count is systematically inflated, sometimes by 50% or more. The displayed conversion rate is therefore mechanically underestimated, because the numerator (orders) is correct but the denominator (visits) is wrong.
The second problem concerns discrepancies with Google Analytics. Merchants who compare PrestaShop dashboard data with GA find significant gaps: differences in session counts, revenue figures, traffic sources. These discrepancies are explained by different counting methodologies, but they undermine trust in PrestaShop data.
The third bug affects trend charts. The dashboard displays revenue and order curves that don't always match the actual data in the order tables. Timezone issues, unfiltered order statuses, and stale cache create visual inconsistencies that mislead merchants.
Why PrestaShop Statistics Are Unreliable
The fundamental problem comes from the architecture of PrestaShop's statistics system. Data is stored in dedicated tables (ps_statssearch, ps_connections, ps_page_viewed, etc.) that are populated by native modules: statsdata, statssearch, statsregistrations. These modules work as hooks, executing on every page load to record the visit.
This architecture creates several problems. First, the statistics tables grow very quickly and end up slowing down the back office. An active store can accumulate millions of rows in just a few months. Second, these tables aren't always properly cleaned by CRON tasks, leading to obsolete or corrupted data.
Second cause: the native statistics modules haven't been maintained at the same pace as the PrestaShop core. Some modules date back to PrestaShop 1.6 and were ported to 1.7 and 8.x without a major overhaul. Incompatibilities with new PHP versions, custom themes, and third-party modules create unpredictable behavior.
Third cause: the lack of intelligent filtering. PrestaShop doesn't distinguish a real visitor from a bot, doesn't properly handle multi-device sessions, and doesn't account for cookie consent in its counting. In a GDPR context, these statistics are not only inaccurate but potentially non-compliant.
Common Fixes for the PrestaShop Dashboard
The first fix recommended by PrestaShop developers is to regularly purge the statistics tables. Via phpMyAdmin or a maintenance module, you can empty the ps_connections, ps_connections_page, ps_connections_source, ps_guest, and ps_page_viewed tables. This lightens the database and can fix some inconsistencies, but you lose all your history.
The second fix involves configuring a CRON task for automatic cleanup. PrestaShop has a maintenance script (cron_currency_rates, for example), but statistics cleanup tasks aren't always enabled by default. Adding a CRON that runs daily stats cleanup can stabilize the data.
The third approach is to disable native statistics modules and rely solely on Google Analytics or a third-party tool for visitor tracking. This solves the bot problem but deprives you of metrics directly in the back office.
These fixes are band-aids. They improve the situation temporarily but don't solve the root problem: PrestaShop wasn't designed as an analytics tool. Its dashboard is a bonus, not a core feature. And with each update or module change, the problems can resurface.
Why Back Office Modules Don't Solve the Problem
Faced with the limits of the native dashboard, many merchants turn to third-party statistics modules available on PrestaShop Addons. These modules promise advanced reports, more complete charts, and more reliable data. In practice, they're limited by the PrestaShop ecosystem itself.
The first problem is the data source. Most back office modules use the same order and customer tables as the native dashboard. They present the data differently but don't correct it. If your ps_orders table contains orders with inconsistent statuses, the third-party module will display them too.
The second problem is performance. A module executing complex SQL queries in the PrestaShop back office impacts your admin panel's load times. Heavy reports (cohorts, LTV, margin by product) require intensive calculations that aren't meant to run in the PHP context of an e-commerce back office.
The third problem is maintenance. Each PrestaShop update risks breaking third-party modules. Merchants regularly find themselves with incompatible statistics modules after an update, temporarily losing access to their data.
Finally, no back office module can integrate external data like advertising costs, real transaction fees, or cross-channel tracking data. They remain confined to PrestaShop's data perimeter.
The Alternative: A Dedicated External SaaS Solution
The most reliable approach is to externalize analytics into a dedicated SaaS platform that connects to PrestaShop to sync raw data and processes it in an environment optimized for analysis.
An external solution has several structural advantages. First, it doesn't impact your store's performance. Analytics calculations run on dedicated servers, not in your back office's PHP context. Your PrestaShop stays fast.
Second, a SaaS platform can cross-reference data from multiple sources. PrestaShop orders, certainly, but also visitor tracking data, advertising costs from your ad platforms, transaction fees from your PSP, and delivery data. This consolidated view is impossible to achieve in a back office module.
Additionally, an external solution isn't affected by PrestaShop updates. The sync module is the only piece in your back office, and it simply transmits data. All analytics logic is on the SaaS side, maintained and updated independently.
Finally, a dedicated solution can offer advanced analyses that PrestaShop will never natively support: cohorts, LTV, RFM segmentation, multi-cost net margin, and audience syncing to advertising platforms.
How Fullmetrix Fixes PrestaShop Dashboard Issues
Fullmetrix takes this external SaaS approach. The PrestaShop module (compatible with 1.7 through 8.x) only handles syncing your orders, products, and customers to the platform. It runs no calculations in your back office and doesn't impact your store's performance.
On the tracking side, Fullmetrix uses a first-party script and server-side tracking that replaces PrestaShop's native statistics modules. This tracking distinguishes real visitors from bots, respects GDPR consent, and produces reliable traffic data. You no longer need to compare three data sources to know how many visitors you actually have.
The Fullmetrix dashboard displays verified metrics: revenue, order count, average order value, conversion rate, acquisition cost, net margin. Each figure is calculated from PrestaShop's actual transactional data, not from potentially corrupted statistics tables.
For advanced analyses, Fullmetrix automatically generates cohort reports, RFM segmentation and lifecycle stages, LTV calculation per cohort, and net margin integrating all 5 cost types (COGS, shipping, transaction, operational, ad spend). Data is hosted in the European Union and the platform is designed to be GDPR-compliant, unlike native modules that don't handle consent.