WooCommerce
WooCommerce is an open-source e-commerce plugin for WordPress that enables businesses to build and manage online stores.
About this data
Updated June 29, 2026
Overall Pulse Score
-21 over this period
A 0-100 index summarizing the tone of 1,002 relevant public mentions gathered from public online communities across 21 weeks in the selected period. It measures online sentiment, not a rating of the product's quality.
Weekly Sentiment Trend
Pulse Score by week over the selected period. Each point is one complete week of mentions.
This week in public discussion
Recent discussion around WooCommerce leaned heavily negative, with commenters raising a high volume of bug reports and reliability concerns across the period. Mentions of broken sitemap pagination, PHP version mismatches, and payment display errors were among the specific issues flagged. A smaller share of positive posts highlighted community events and integration strengths, but these were far outnumbered by complaints. Several mentions also pointed to missing features and gaps in third-party integrations.
Read the deeper analysisAI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.
Sentiment mix by week
How the tone of public discussion splits each week.
Most-discussed praise
Most-discussed complaints
Themes across the selected period, with mention counts.
How WooCommerce compares
Pulse Score over the selected period versus the top tracked competitors in E-Commerce.
Where the mentions come from
Share of the 1,002 relevant public mentions in the selected period, by source.
Sample public mentions
Showing 5 of 1,002 analyzed public mentions in this period, with links to the original source. We do not reproduce full threads.
“Select2 multiple field height and padding issues after WooCommerce 10.6.2 (WP 7.0 RC). ### Prerequisites - [x] I have carried out troubleshooting steps and I believe I have found a bug. - [ ] I have searched for similar bugs in both open and closed issues and cannot find a duplic...”
“GA4 transaction_id should use get_order_number() instead of get_id(). ### Describe the bug: The plugin currently sends the internal WooCommerce database order ID to GA4 as the transaction_id using: 'id' => $order->get_id(), inside get_formatted_order(). This causes issues for sto...”
“Hardcoded /wp-content/ paths and incorrect site_url() usage break WooCommerce on non-default WordPress directory layouts. ### Prerequisites - [x] I have carried out troubleshooting steps and I believe I have found a bug. - [x] I have searched for similar bugs in both open and clo...”
“Make WooCommerce recently viewed cookie and tracking-only query strings configurable for FastCGI cache bypass. Hi, I’d like to suggest **two** FastCGI cache-bypass improvements for WooCommerce / high-traffic ecommerce sites using SlickStack. 1. woocommerce_recently_viewed cookie ...”
“Clean up stale feature flags and experimental code. ### Description WooCommerce Core has accumulated feature flags, experimental packages, and conditional code paths over time. Some of them still represent active investments, while others no longer have clear ownership, a realist...”
1,111+ more analyzed mentions, full history, and theme breakdowns are part of Pro.
Get ProDeeper analysis
- Bug reports and reliability complaints dominated discussion by a wide margin, setting a persistently negative baseline tone across the full four-week window.
- Sentiment trended gradually upward from a low point in early May to a relative high in late June, though repeated dips suggested no sustained improvement in community mood.
- Opinion was divided on integrations, with some commenters praising compatibility while others flagged missing or inconsistent support for third-party tools.
- A small but engaged subset of commenters expressed genuine enthusiasm through community events and feature advocacy, indicating loyalty exists alongside frustration.
| Praise theme | Mentions |
|---|---|
| Strong features | 30 |
| Good integrations | 21 |
| New releases | 16 |
| Feature requests | 11 |
| AI quality | 7 |
| Complaint theme | Mentions |
|---|---|
| Bugs | 671 |
| Reliability | 368 |
| UI frustrations | 137 |
| Missing features | 134 |
| Lacking integrations | 108 |
Public discussion around WooCommerce over the past four weeks was dominated overwhelmingly by frustration, with bug reports and reliability concerns accounting for the vast majority of negative mentions. Commenters surfaced a wide range of technical grievances, including sitemap pagination failures causing missing product URLs, decimal-setting mismatches in payment overviews, PHP version requirement conflicts, and plugin dependency states that left stores in broken configurations. The sheer volume of bug-themed mentions relative to praise-themed ones signaled a community that is largely in problem-solving mode rather than celebration mode.
Sentiment trajectory showed a modest but unsteady climb over the window. Discussion opened at its lowest point in early May and edged upward through mid-May before dipping again in late May. A stronger recovery followed into early June, where scores plateaued briefly, then softened slightly before reaching their highest point in the final tracked week. The overall direction was cautiously upward, but the pattern of dips and recoveries suggested that each wave of new mentions brought a fresh round of complaints that kept sentiment from consolidating.
Praise-oriented discussion was present but thin. Several mentions highlighted positive integration experiences, and a smaller cluster celebrated new feature releases and community events such as WordPress meetups where WooCommerce projects were shared enthusiastically. Feature requests also appeared, suggesting some commenters remain invested enough to advocate for improvements rather than simply vent.
Opinion was divided most visibly around integrations and ecosystem compatibility. Some commenters described integrations working well, while others flagged specific plugins and companion tools as unsupported or inconsistently implemented, with one mention pointing out that a consent records feature appeared to cover WooCommerce exclusively despite broader platform promises. Developer-facing technical concerns around monorepo packaging and npm release processes added a layer of internal tooling frustration that sat somewhat apart from end-user sentiment.
AI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.
Member perspectives
Individual opinions from Pro members, posted over time. These are personal member views, not aggregated sentiment data.
Overall Pulse Score
-21 over this period
A 0-100 index summarizing the tone of 1,002 relevant public mentions gathered from public online communities across 21 weeks in the selected period. It measures online sentiment, not a rating of the product's quality.
Data summary
Compare with another tool
WooCommerce
32
Trainual
88
Score-level preview from live weekly tracking.
Are you WooCommerce?
Get a private enterprise dashboard for your product - full history, every source, theme deep-dives, and weekly alerts. You can also respond to the data shown here.
Explore the enterprise dashboardAffiliate disclosure
Some links on this site may be affiliate links. If you click one and make a purchase, we may earn a commission at no extra cost to you. Learn more.
Is WooCommerce your product?
See everything behind this page - full history, every source, theme deep-dives, and weekly alerts - in a private enterprise dashboard.
Request early accessCompare with similar tools
Creative Market
Online marketplace where independent creators sell fonts, graphics, templates, and other digital design assets.
Paid plans available
View DetailsSpocket
Spocket is a dropshipping platform that connects online retailers with suppliers in the US and EU for product sourcing.
Free tier; paid plans available
View Details