Customer Reviews for WooCommerce plugin review and common issues

Check: (1) in Customer Reviews → Settings, verify the review request email is enabled and configured with a valid delay and trigger (e.g., “X days after order status changes to Completed”); (2) verify WordPress email is functioning — use WP Mail SMTP test email to confirm; (3) check if orders are reaching “Completed” status — the review request trigger depends on the order status matching the configured trigger; (4) clear all email caches; (5) review WordPress scheduled tasks (crons) — review request sending may be scheduled via WordPress cron, which requires site traffic to trigger. On low-traffic sites, use a true server cron to ensure scheduled tasks run.

Review request emails (especially with coupon offers) are frequently flagged by spam filters. To improve deliverability: (1) configure WP Mail SMTP with a reputable SMTP provider (Postmark, SendGrid, AWS SES) — review emails sent via your hosting’s default mail server often have poor deliverability; (2) ensure the sending domain has properly configured SPF, DKIM, and DMARC records; (3) avoid spam trigger words (“free,” “discount,” “act now”) in subject lines; (4) keep review request emails concise and transactional in nature — avoid heavy promotional language; (5) provide a clear unsubscribe link (the plugin includes this for GDPR compliance).

WooCommerce reviews follow WordPress comment moderation settings. Check: (1) in Settings → Discussion, verify whether all reviews go to moderation or are published immediately; (2) check the Comments moderation queue in WordPress → Comments for pending review approvals; (3) Customer Reviews sends request emails, but the actual review submission and moderation happen through WooCommerce’s native review system — review the WooCommerce discussion settings; (4) if the reviewer’s email is in the WordPress comment blocklist, their review is automatically held for moderation.

Coupon incentives require Customer Reviews Pro. In Pro settings, enable coupon generation for reviews. Configure the coupon type (percentage discount, fixed amount), value, usage restrictions (single use, minimum order), and expiry period. When a customer leaves a review after receiving a review request email, the plugin automatically generates a unique coupon code and sends it to the customer via email. Each customer receives a unique coupon to prevent sharing and abuse.

In Customer Reviews → Settings → Review Requests, configure the conditions for sending review requests. The settings allow filtering by product category — enable review requests only for products in specific categories (e.g., only physical products, not digital downloads). Additionally, configure order-level filters: minimum order amount, customer registration status (skip guest orders), or order status. This prevents sending review requests for categories where reviews are less meaningful or where the post-purchase review cycle does not apply.

Customer Reviews for WooCommerce increases the volume of reviews collected through WooCommerce’s native review system. WooCommerce outputs Schema.org Product markup including aggregate ratings from its native reviews. More reviews collected means more review data in the schema markup. Google may display star ratings in search results when sufficient reviews are present and the schema markup is correctly implemented. Customer Reviews accelerates reaching the review threshold Google typically requires for rich snippet display.

Incentivizing reviews with coupons (offering discounts for verified purchase reviews) is common practice on self-hosted WooCommerce stores and is not prohibited by WooCommerce or WordPress terms. It differs from Amazon’s policies (which prohibit incentivized reviews on their marketplace). For Google Product Reviews, the program guidelines require that incentivized reviews be disclosed. If your store participates in Google reviews programs or a third-party trustmark program (Trustpilot, etc.), check those programs’ specific guidelines on incentivized review practices.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.