In a recent Business Bloomer Club Slack thread, a concerning situation was shared involving the unexpected and immediate closure of a plugin on the WordPress.org repository due to trademark violations related to WooCommerce.
The author of the affected plugin explained that the plugin was removed without prior warning, a surprising move given that past violations typically resulted in a remediation email with time to address the issue.
This raised questions among community members about consistency in the enforcement of WordPress plugin guidelines and the fairness of immediate takedown actions.
What Triggered the Takedown
The immediate closure was attributed to the use of the “WooCommerce” trademark in the plugin name and description, which is a clear violation of longstanding guidelines.
The plugin in question had “WooCommerce Checkout” in its listing, which likely flagged the issue. There were also other smaller concerns, including a deactivation survey that made an API call — something that must be disclosed in the plugin readme.
While these are all technically valid points, the abruptness of the closure was a departure from the typical plugin review process, where developers are given time to resolve the issues.
A Growing List of Remediation Tasks
Initially, the plugin author received a short list of action items but was later sent a much longer list — around 30 in total. The author acknowledged the validity of many of these requests and expressed a willingness to comply.
However, the frustration came from the lack of opportunity to fix the initial concerns before the plugin was unpublished, especially considering that some of the flagged behaviors are common among popular plugins.
Community Reactions and Plugin Team Dynamics
Community members in the Slack thread expressed surprise and disappointment, noting that such a drastic measure seemed out of character.
One member pointed out that the plugin review team has grown recently, and with new volunteers involved, inconsistency in enforcement has become more frequent.
Another noted that “WooCommerce Checkout” is undoubtedly a trademark violation, but the immediate closure still felt like an overreaction.
What You Can Do as a Plugin Author
If you’re publishing plugins on the WordPress.org repository, this incident serves as a reminder to proactively review trademark policies and ensure your plugin name, description, and code do not infringe on any terms. In particular:
- Avoid using “Woo” or “WooCommerce” at the start of your plugin name.
- Clearly disclose any API calls or data collection mechanisms in your readme.
- Be prepared for varying levels of enforcement depending on who reviews your plugin.
Also, keep your WordPress.org email up to date. As shared later in the Slack thread, many plugins are temporarily closed simply because an automated email from WordPress.org bounced — accounting for over 90% of closures according to the plugin review team.
Conclusion
The takeaway here is twofold: first, ensure compliance with trademark and disclosure policies before submitting or updating a plugin on the repository.
Second, understand that the review process may not always be consistent, especially with new team members joining the ranks.
While immediate closures are rare, they are possible — and the best defense is proactive compliance and open communication with the plugin team when issues arise.
