Advanced Coupons plugin review and common issues

BOGO deals in Advanced Coupons require: (1) the trigger product (the “buy one” part) is in the cart before the coupon is applied — verify the trigger product matches exactly (right variation, minimum quantity); (2) the reward product (the “get one free” part) is an in-stock, purchasable product; (3) the coupon’s “BOGO Type” is configured correctly (same product, alternative product, category-based); (4) the coupon type is set to “BOGO Deal” not “Percentage Off.” Test with a simple 1-for-1 BOGO first to verify basic functionality, then add complexity.

URL coupons use a URL parameter (e.g., yourdomain.com/?coupon_code=SUMMER20) to trigger automatic coupon application. If the coupon is not applying: (1) verify the URL parameter format matches the Advanced Coupons URL Coupon settings — the parameter name must match exactly; (2) the URL coupon must redirect to a page that goes through WooCommerce’s session (typically the shop or cart page); (3) check if a security plugin or Cloudflare is stripping URL parameters; (4) the coupon must be active and meet all its conditions at the time of application.

Advanced Coupons shows a reason when a cart condition is not met. If the rejection reason is not visible to the customer, check the coupon settings in WordPress → Coupons → [coupon] → Cart Conditions. Review each condition and verify the current cart actually meets it: check product quantities, categories, totals, and user role match. Enable Advanced Coupons’ debug mode (if available) or add WP_DEBUG to wp-config.php to see condition evaluation in the PHP error log. Temporarily remove conditions one at a time to identify which is failing.

In WordPress → Coupons → Add New, set the Discount Type to “BOGO Deal.” In the BOGO settings: set Trigger Products to the specific product with a quantity of 2; set Reward Products to the same product with a quantity of 1 and a price adjustment of “100% off.” Customers who add 2 or more of the specified product to cart and apply the coupon receive the third at no charge. Configure whether the coupon applies once per order or multiple times (buy 4 get 2 free) in the BOGO multiplier settings.

Advanced Coupons’ store credit system allows manual credit assignment or purchase-triggered credit via the Premium loyalty program feature. For basic manual store credit: go to WordPress → Users → [customer] → Store Credit section and add credits. The customer can apply store credit at checkout. For automatic credit earning (e.g., earn $1 credit per $10 spent), the Premium loyalty program automates the earn-and-redeem cycle. Configure earn rates and redeem conditions in Advanced Coupons → Loyalty Program.

Yes, substantially. WooCommerce’s native coupons handle simple percentage and fixed discounts with basic usage limits. Advanced Coupons free adds cart conditions (coupon only works when cart contains specific products), BOGO deals, URL auto-apply coupons, and store credit — capabilities that are genuinely useful for running effective promotions. For most WooCommerce stores, the free version of Advanced Coupons is a straightforward upgrade to the coupon system that costs nothing.

Scheduled coupon activation and expiration (setting a specific start and end time, not just a date) requires Advanced Coupons Premium. WooCommerce’s native coupons have a basic expiry date but no start date and no time-of-day scheduling. For Black Friday campaigns that activate at midnight and expire 24 hours later, the Premium scheduling feature is necessary.

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.