Advanced Coupons Premium - WordPress Plugin

A Practical Guide to Configuring Advanced Coupons Premium for WooCommerce Promotions

Advanced Coupons Premium is not just for adding one more discount field to WooCommerce. It is built for creating controlled promotion flows: BOGO deals, automatic coupons, coupon links, free gifts, cart restrictions, customer role rules, order history conditions, and store credit. This guide focuses on the plugin's working logic rather than a marketing overview: what to enable after installation, how to build your first scenario, how to test the result on the storefront, and how to understand why a discount is not being applied.

This guide is written for WooCommerce store owners, site administrators, and marketers who already understand basic WooCommerce coupons but want more precise control over promotions. We will look at Advanced Coupons Premium as a rules system: cart input conditions, coupon action, customer-facing result, order verification, and a safe rollback path if the promotion behaves differently than expected.

We will also cover the scenarios that most often break on real stores: automatic coupon application, free gifts in the cart, condition-based discounts, store credit at checkout, custom checkout pages, and conflicts between multiple discounts. Where the exact behavior depends on the version, enabled modules, or neighboring extensions, the wording will stay cautious: before launching any promotion on a live storefront, test it with a sample product and a sample order.

What Problem the Plugin Solves and Where It Is Actually Useful

Standard WooCommerce coupons cover basic use cases: percentage discounts, fixed cart discounts, product discounts, minimum spend rules, product and category restrictions, email restrictions, and usage limits. That is enough for a simple promotion like "10% off all products through the end of the week." But as soon as a store wants to offer a discount only to a specific segment, automatically add a gift, trigger a coupon from an email link, apply a promotion without manual code entry, or use store credit, the standard toolkit usually falls short.

Advanced Coupons Premium expands the familiar WooCommerce coupon screen and adds modules that turn a discount into a conditional scenario. A coupon is no longer just a discount amount. It can check the cart, user role, order history, shipping region, product presence, item quantity, date and time, payment method, or other parameters, provided the relevant module is enabled and supported by your configuration.

The plugin's practical value becomes especially clear in three types of stores. The first is a repeat-purchase catalog: cosmetics, consumables, groceries, hobby supplies, apparel. These stores benefit from BOGO deals, free gifts, second-order discounts, and perks for returning buyers. The second is a store with customer segments: retail, wholesale, club members, subscribers, VIP buyers, regional groups. In that case, roles, order history, and Cart Conditions matter most. The third is a store with active marketing channels: email, affiliate links, promo landing pages, FunnelKit funnels, or a custom checkout. That is where URL Coupons, Auto Apply, One Click Apply, and integrations become especially valuable.

The plugin may be unnecessary if the store runs one simple coupon per month, has no condition-based WooCommerce scenarios, and already covers all discount logic through another dynamic pricing extension. It can also be excessive if discounts need to be calculated not as coupons, but as a complex pricing matrix based on roles, wholesale tiers, and price lists. In that case, it makes sense to compare Advanced Coupons Premium with dedicated dynamic pricing or wholesale pricing solutions.

Key principle: Advanced Coupons Premium is best treated as a WooCommerce promotion rule builder. Before configuring any campaign, do not ask "what discount should I give?" Ask "to whom, under what condition, through what action, and where will the customer see the result?"

Who This Approach Fits Best

The plugin is especially convenient for teams that want to keep coupons inside the standard WooCommerce workflow while extending them without deploying a separate heavyweight discount rules system. The store manager continues working through Marketing > Coupons or the WooCommerce coupon screen, while the additional Advanced Coupons tabs provide targeted controls: BOGO, Add Products, URL Coupons, Cart Conditions, Auto Apply, store credit, and other options.

This matters for stores where promotions are managed by an administrator rather than a developer. Instead of writing custom code, the team can assemble a clear scenario: create a coupon, define the restriction, enable automatic application, test the cart, and verify the order. A developer is still useful for diagnosing conflicts with checkout, caching, a custom theme, or an unusual sales funnel, but not for every promotion.

When Another Tool Is a Better Fit

If the main requirement is tiered catalog-wide discounts without coupon logic, for example "3 items - 5%, 5 items - 10%, 10 items - 15%" across dozens of categories, a dedicated dynamic pricing plugin may be simpler. If you need a full gift certificate experience with a storefront for gift cards, it is better to look at a specialized gift card solution or a combination of Advanced Coupons with the developer's separate product. If you need a full loyalty system, Advanced Coupons Premium covers part of that through store credit and coupons, but full loyalty points and loyalty tiers usually require a separate module.

What to Check Before Installing It on a Live Store

Before installing the plugin, do more than just make a backup. Coupon logic affects the cart, checkout, order totals, taxes, shipping, emails, and analytics. A discount error can give customers an unintended bonus, while a checkout error can prevent orders from being completed. It is best to think of preparation as a short store audit.

Start with core WooCommerce. Are coupons enabled under WooCommerce > Settings > General? Do you have a sample product, a test customer, and a payment method that lets you complete an order without a real charge? Are you using the default cart and checkout pages, WooCommerce blocks, Elementor checkout, FunnelKit, or another builder? The answer affects how you test store credit, coupon fields, Auto Apply, and user-facing notices.

Also review any neighboring extensions that interfere with pricing or checkout: dynamic pricing, multi-currency, subscriptions, gift cards, cart caching, JavaScript optimizers, custom checkout fields, payment gateways, funnels, and localization plugins. The Advanced Coupons changelog shows that the developer regularly fixes issues around BOGO, Auto Apply, store credit, FunnelKit, WooPayments Multicurrency, WPML, cart/checkout blocks, and other integrations. That is a good sign of active support, but also a reminder that these are the areas that require test scenarios.

• Back up the database and files before installing the plugin on a live site.
• Verify that WooCommerce is active, coupons are enabled, and a basic WooCommerce coupon works without Advanced Coupons.
• Prepare a test product with a normal price, a test category, and a test user with the Customer role.
• Disable aggressive caching for cart, checkout, and account pages if your cache plugin allows exclusions.
• Record which plugins modify product prices, shipping, currency, checkout, or subscription logic.
• If the store already uses a custom checkout, review the Advanced Coupons documentation for that specific integration before launching store credit or Force Apply.

Why Testing Only in the Admin Area Is Not Enough

Coupon settings may look correct in the admin area, but the final behavior is determined in the cart. For example, a category-based condition only works if a product from that category is actually in the cart. Auto Apply will only trigger after the cart recalculates. Add Products will add a gift only after the coupon is applied and only if WooCommerce allows that product to be added. Store credit at checkout depends on whether the customer is logged in and has a positive balance.

That is why even a minimal verification flow should go through the storefront: add a product to the cart, proceed to checkout, apply or auto-apply the coupon, verify the final order total, create a test order, review the coupon in the order, and then remove the test data. If even one step is skipped, you may miss a conflict with the theme, checkout blocks, or another plugin.

Installation and Initial Validation Without Putting Promotions at Risk

Advanced Coupons Premium works on top of the free Advanced Coupons for WooCommerce plugin. In the documentation for certain features, the developer explicitly notes that Premium either enables or requires the free base plugin. For a regular store owner, the logic is simple: first make sure the base plugin is active, then activate the Premium extension, and only after that verify the tabs and modules.

This guide does not cover purchasing, licensing, or downloading the archive file. That is not the point here. What matters is that you should not enable every module on a live store immediately after activation. The more modules are active, the more places a coupon can affect the cart. It is better to enable features as needed: start with Cart Conditions and BOGO for coupon logic, then enable Add Products, Auto Apply, Store Credits, or URL Coupons only if a specific campaign requires them.

Basic Setup Sequence

1. Open the WordPress admin area and make sure WooCommerce is active.
2. Verify that a standard WooCommerce coupon can be created under Marketing > Coupons.
3. Activate both the base Advanced Coupons for WooCommerce plugin and the Premium extension under Plugins > Installed Plugins.
4. Open Coupons > Settings or the settings screen available in your version and review the modules tab.
5. Enable only the modules you need for the first test, such as Add Products or Store Credits.
6. Create a test coupon with a simple condition, apply it to a test cart, and confirm that the order total changes as expected.

If you do not see new tabs on the coupon screen in the admin area, first check whether the base plugin is active, whether the required module is enabled, and whether an optimization plugin is caching the admin interface. Do not jump straight to code changes or reinstalling the plugin. In most cases, the issue is a disabled module, the wrong coupon screen, or a conflict with another extension.

Quick takeaway: the first goal after installation is not to build a complex promotion. It is to prove that the store can create a coupon correctly, apply it in the cart, and record the result in the order.

Your Post-Install Settings Map: Which Modules to Enable First

Advanced Coupons Premium has a lot of capabilities, but in practice it helps to split them into a few groups. The first group controls coupon eligibility: Cart Conditions, role restrictions, order history restrictions, product restrictions, category restrictions, cart amount rules, and similar conditions. The second group controls the action: BOGO, Add Products, shipping overrides, store credit, cashback, automatic application. The third group controls how the coupon reaches the customer: URL Coupons, One Click Apply, Send Coupon, coupon blocks, and account display.

This structure makes troubleshooting easier. When a promotion fails, you need to know which link in the chain is broken: the condition is not met, the action is not configured, the application method did not work, or checkout is not displaying the result. If every coupon has everything enabled at once, diagnosis becomes slow and messy.

Modules Worth Enabling Based on the Use Case

Cart Conditions are useful in almost every serious promotion. They answer the question "when is this coupon allowed?" Even if the discount itself is simple, conditions based on cart total, category, role, or order history protect the store from unintended discounts. Premium includes additional conditions such as cart weight, user metadata, order history, shipping region, stock availability, and other contextual data, if those exist in your configuration.

BOGO should be enabled when the promotion is built around buying one set of products and getting another set at a discount or for free. This is a separate mechanic, not just "100% off a product." In BOGO scenarios, it is important to define exactly what counts as "Buy," what counts as "Get," which product group participates, and what happens if the customer changes quantities.

Add Products is useful for gifts, free samples, bonus items, and preset add-ons. Unlike BOGO, here you define in advance which product is added when the coupon is applied. The settings let you choose the price or discount type for the added product: Override price, Percentage discount, Fixed discount, or No discount. That determines whether the item is locked as a coupon-controlled line or remains a normal cart item.

Auto Apply should only be enabled for promotions that genuinely need to apply without customer interaction. It works well for threshold-based discounts, a gift with a qualifying cart, or automatic store credit. But if the customer should consciously choose the offer first, One Click Apply or a standard coupon code is usually the better choice.

Store Credits should be enabled when the store wants to maintain an internal customer balance: refund-to-credit flows, manual credit adjustments, cashback, or partial balance use at checkout. This module needs separate testing because behavior depends on customer authentication, balance, redemption limits, and cart composition.

What Not to Enable Without a Clear Scenario

Do not enable automatic application for every promotion "just in case." A coupon that applies on its own needs precise Cart Conditions and clear business logic. Do not enable Force Apply together with Auto Apply on the same coupon unless there is a real reason. In the FunnelKit documentation, the developer notes that Auto Apply runs in the background, while Force Apply is meant for coupons the customer explicitly enters or applies through a link. Also do not enable Add Products for an item that is frequently out of stock until you have decided how the store should behave when stock issues occur.

What to check immediately after enabling a module

Module	What to verify	How to roll back safely
Cart Conditions	The condition passes for the correct cart and blocks the wrong cart.	Remove the condition or temporarily disable the coupon without touching products.
BOGO	The customer gets the discount only with the correct "Buy" and "Get" setup.	Unpublish the coupon or replace the BOGO logic with a simple test coupon.
Add Products	The gift is added, quantity is locked where expected, and the product is removed together with the coupon.	Disable Enable Add Products in the specific coupon or turn off the module.
Auto Apply	The coupon appears in the cart only when conditions are met and disappears after they are no longer met.	Clear the Enable auto apply for this coupon checkbox.
Store Credits	The balance is visible to a logged-in customer, limits are enforced, and checkout recalculates correctly.	Disable automatic store credit application or turn off the module while keeping the credit history intact.

Cart Conditions: How to Build Accurate Discount Rules

Cart Conditions are one of the most important parts of Advanced Coupons Premium because they determine whether a customer qualifies for a coupon. In the official documentation, conditions are described as tests that run before the discount is applied. If the customer does not meet the criteria, the coupon will not apply. If the customer later stops meeting those criteria, for example by removing the required product from the cart, the coupon may be removed.

This behavior is useful for protecting your promo budget. Instead of giving a blanket discount to everyone, you can build a rule such as this: the customer is logged in, the cart contains a product from the target category, the cart total is above a threshold, and the customer's role is not on the excluded list. Premium is especially interesting for conditions tied to purchase history, total spending, user metadata, shipping region, stock availability, and other contextual data.

How Condition Groups Work

The Advanced Coupons documentation explains that you can combine conditions and organize them into groups. This matters because real promotions are rarely based on a single rule. For example, one scenario might be "a guest gets a gift with a cart above a threshold," while another might be "a logged-in customer gets the same gift at a lower threshold if they have already placed an order." In a case like that, condition groups are cleaner than creating two nearly identical coupons.

When designing groups, do not start with the interface. First write the rule in plain language. Then split it into required conditions and alternative paths. Required conditions should all be true at the same time. Alternative paths are better placed into separate groups so that you do not accidentally create a coupon that qualifies in too many cases.

Example of a Safe Rule

Suppose the store wants to discount an accessory only for customers who added the main product and reached the minimum cart amount. Start with the plain-language rule: "The coupon applies if the cart contains a product from the accessories category and the cart total is above the threshold." In the interface, that becomes two conditions: Product Category Exists In Cart and Cart Subtotal. After saving, test two carts: one qualifying and one non-qualifying.

If the qualifying cart gets the discount and the non-qualifying cart shows a clear failure message, the rule is working correctly. If the discount applies without the required product, the condition is too broad. If the discount still does not apply in the correct cart, review the product category, the threshold amount, WooCommerce tax logic, and whether another coupon is conflicting with it.

Common Cart Conditions Mistakes

The most common mistake is mixing up standard WooCommerce restrictions with Cart Conditions. The built-in Usage Restrictions and Usage Limits tabs are useful, but they do not replace the more advanced conditions in Advanced Coupons. If the promotion is complex, it is better to keep the main logic in one place rather than duplicate conflicting restrictions across multiple tabs.

The second mistake is enabling order-history conditions without testing them against the right user. A guest has no order history, and a new test account may have an empty record. The third mistake is using custom metadata or cart item meta without being sure that another plugin actually adds that data at the right moment. If the metadata only appears after checkout or only exists in the order, the cart condition will not see it.

Practical check: for every complex coupon, create a short table of "condition - test cart - expected result." That is faster than digging through logs after the campaign has already gone out in an email.

BOGO Promotions: How Not to Mix Up the Purchase, the Reward, and Repetition

BOGO in Advanced Coupons Premium is designed for "buy X, get Y" scenarios and their variations. In the official guide, the developer highlights several approaches: same-product BOGO, cross-product BOGO, and category-based BOGO. In the BOGO interface, it is important to configure not only the discount amount but both sides of the deal: what the customer must buy and what they receive as the reward.

For a store, this is fundamentally different from a simple 100% off coupon. If you create a free product using standard WooCommerce rules alone, customers often have to add the item themselves and the store owner gets very little control. A BOGO scenario makes the relationship between the purchase and the reward explicit: a product, a product group, a category, or a broader set, depending on your version and selected BOGO type.

How to Choose the Right BOGO Format

If the promotion is tied to a single product, such as "buy one bottle of shampoo and get a second one free," use a specific-product scenario. It is easier to troubleshoot: is the product in the cart, is the quantity sufficient, is the reward added, and is the discount calculated correctly? If the promotion should work across a product group, such as "buy any two shirts from the collection and get the third at a discount," you need a product-combination or category-based format.

Category-based BOGO is useful for large catalogs, but it requires caution. WooCommerce categories are often used not just for merchandising but also for navigation. If the category is too broad, the coupon may apply to products that should not be part of the promotion. If the category is too narrow, or the product is not assigned to it, the customer will not see the discount. That is why you should verify every included product and every exception before launch.

Repetition and Quantity

Repeating BOGO promotions can behave unexpectedly when the customer changes quantities. For example, in a "buy 2, get 1" scenario, you need to understand what happens with 4, 5, or 6 items. The developer regularly mentions fixes around same-product BOGO, variable products, and partial repeating cycles in the changelog, so for more complex promotions with variations and repeat logic, always build test carts with multiple quantity combinations.

For variable products, remember that WooCommerce treats variations as separate line items. If the customer can choose any color or size, verify that your chosen BOGO configuration supports that combination correctly. Otherwise, the discount may work for one variation but not for the full collection.

How to Explain BOGO to the Customer

Even a perfectly configured BOGO promotion may fail if the customer does not understand what needs to be added to the cart. Use clear coupon wording, a promotion notice, a campaign banner, or One Click Apply if you want to give the customer an explicit choice. For more complex BOGO campaigns, show the rules directly on the promotion page: which products are included, what the customer needs to buy, what will be added or discounted, whether variations are included, and whether the offer can be combined with other coupons.

Do not promise "a free gift automatically" if the customer actually needs to select the reward item. Do not say "all products in the category" if only part of the category is included through Cart Conditions or BOGO logic. And do not run the same promotion as both BOGO and Add Products at the same time unless the team clearly understands which mechanism is responsible for adding the item.

Add Products: Gifts, Samples, and Bonus Items in the Cart

Add Products is one of the most practical features in Advanced Coupons Premium for stores that offer free samples, gifts with purchase, bonus items, or special add-ons. The documentation describes it as a separate module that must be enabled under Coupons > Settings > Modules. Once enabled, an Add Products tab appears on the coupon screen, where you can enable the feature for a specific coupon, add a product, set the quantity, and choose the pricing or discount type.

The key detail with Add Products is that the behavior of the added item depends on the price setting. If the item is added with Override price, Percentage discount, or Fixed discount, the plugin may track it as a coupon-controlled line: lock quantity changes, hide removal, and remove the item when the coupon is removed. If you use No discount, the product may behave like a standard cart line. That is not a bug. It is an important piece of logic your support team should understand.

When Add Products Is Better Than BOGO

BOGO is a strong fit when the reward depends on a "Buy" and "Get" relationship. Add Products is more convenient when the store already knows exactly which product should appear in the cart. For example, a sample-size product with orders above a threshold, a free accessory with a core purchase, a printed catalog, extra packaging, a trial kit, or a bonus item tied to a specific campaign.

If the gift is the same for every qualifying customer, Add Products is easier to explain and easier to test. If the customer should choose one gift from several options, or if the campaign depends on product combinations, BOGO or a separate mechanic may be more appropriate. In any case, do not mix these approaches in the same coupon unless you have a clear reason, or it becomes hard to understand which mechanism added the item and why it remained in or disappeared from the cart.

How to Choose the Price Type for the Added Product

Override price works well when you need a guaranteed outcome, such as 0 for a free sample or a fixed promotional price. Percentage discount is useful when the bonus item should stay linked to its current price, for example 100% off for a free item or 50% off for a second accessory. Fixed discount is used when you need to subtract a specific amount. No discount is for cases where the product is added as a normal line item and should participate in cart logic before restrictions are checked.

The separate setting Add undiscounted products before coupon restrictions & cart conditions is only useful in special cases where a No discount item must appear before condition checks run. Use it carefully: lines with other discount types still follow the normal flow after the coupon is applied, and early insertion can confuse a store manager who does not understand the difference.

How to Test Add Products on the Storefront

1. Create a test coupon and enable Enable Add Products.
2. Add one product with a clear quantity, such as a free sample item.
3. Select Override price and set the value to 0 if the item should be free.
4. Save the Add Products data with the dedicated button if your interface version includes one.
5. On the storefront, add a qualifying product, apply the coupon, and check whether the gift appears.
6. Try changing the gift quantity and removing the coupon so you understand how the line behaves.

If the product is not being added, do not check only the coupon. The item may be out of stock, not purchasable, hidden, tied to the wrong variation, or the Add Products data may not have been saved. The developer documentation lists these separately as common reasons for the "coupon applies, but products are not added" scenario.

Auto Apply, URL Coupons, and One Click Apply: Reducing Friction Without Creating Chaos

Automatic coupon application sounds like an obvious improvement: the customer does not need to type a code, does not mistype characters, and does not forget the discount. But in WooCommerce, an automatic coupon needs to be especially predictable. If it appears and disappears for no obvious reason, the customer loses trust in the cart and support starts getting "why did the price change?" questions.

Advanced Coupons Premium offers several ways to simplify discount application. Auto Apply adds the coupon automatically when the conditions are met. URL Coupons let you apply a coupon through a link, for example from an email or a landing page. One Click Apply shows a notice with a button so the customer can actively accept the offer. These mechanisms serve a similar goal, but they differ in how much control the customer has.

When to Use Auto Apply

Auto Apply is best for rules the customer should not have to choose manually. Examples include free shipping above a cart threshold, a discount on a seasonal category, an automatic bonus for a qualifying product, or a role-based perk. In that kind of scenario, manual code entry only gets in the way. The customer meets the condition, the cart gets the discount, and checkout becomes simpler.

But Auto Apply needs clear Cart Conditions. An automatically applied coupon "for everyone" can conflict with personal coupons, partner codes, cashback, BOGO offers, and other discounts. If multiple coupons exist, configure individual use, compatibility, and priorities so the store does not give away unintended extra discounts.

When URL Coupons Are the Better Choice

URL Coupons work especially well in email campaigns, affiliate campaigns, landing page buttons, PushEngage notifications, and promotional blocks. The customer clicks the link, the coupon applies, and then they land on the right page. This is useful when the coupon should be tied to a specific channel rather than to every visitor.

Test URL Coupons in a real browser, not just by copying the link from the admin area. Redirects, site language, cache, UTM parameters, destination page, and cart contents all matter. In the changelog, the developer has mentioned fixes related to URL Coupons, external redirects, multilingual URLs, and FunnelKit, so this coupon type should be tested in the exact environment where the link will actually be used.

When One Click Apply Is Better Than an Automatic Coupon

One Click Apply is useful when you want to present an offer but still leave the choice to the customer. For example, "Add one more item from this category to get a free gift" or "You qualify for a members-only discount." The customer sees the notice, understands the condition, and clicks the button. That makes the discount feel less abrupt and gives you room to explain it.

If the offer is more complex, One Click Apply is often better than Auto Apply. An automatic coupon works best for an obvious benefit, while a notice with a button is better when the customer needs to understand the rules, choose an item, or explicitly accept a cart change.

Selection rule: use Auto Apply for simple, obvious promotions; use URL Coupons for external channels; use One Click Apply for offers that should be explained before the customer accepts them.

Store Credits: Customer Balance, Refunds, and Checkout Limits

Store Credits in Advanced Coupons are not regular discount coupons. They represent an internal customer balance. That balance can be used for refunds, manual credit grants, bonuses, cashback flows, and keeping customers within the store ecosystem. In the WordPress.org listing for the free plugin, the developer mentions a store credit dashboard, manual admin adjustments, refund to store credit, balance display in the customer account, and use at checkout. Premium adds additional controls, such as automatic use of the available balance and redemption limits per order.

Store credit requires careful setup because it affects money, refunds, and reporting. The customer must be logged in, the balance must be positive, the module must be enabled, and checkout must display the correct interface. If you use a custom checkout, such as Elementor or FunnelKit, review the matching documentation to see which fields appear automatically and which ones must be added to the template manually.

Automatic Store Credit Application

The Advanced Coupons documentation describes the Automatically apply available store credits amount setting under the Store Credits tab. If it is enabled, a logged-in customer with a positive balance may have store credit applied at checkout without entering anything manually. This is convenient for retention, but it needs clear control.

The test flow is simple: create a test customer, assign a small amount of store credit, add a product to the cart, go to checkout, and confirm that the balance is applied as expected. Then test the reverse scenario: a guest, a customer with no balance, an empty cart, a customer who manually removed the store credit, and a cart containing an Advanced Gift Cards product if that plugin is used on the site. The documentation notes that store credits do not apply when the cart contains Advanced Gift Cards products.

Redemption Limit

If the store does not want store credit to fully cover the order, you can use the maximum redemption percentage setting per order. The documentation describes Maximum percentage of store credits redemption allowed per order under Coupons > Settings > Store Credits. In practice, this matters for stores where internal credit should only cover part of the order rather than turning every purchase into a free one.

After changing the limit, test an order where the balance exceeds the cart total. Checkout should apply no more than the allowed share. Then verify how that appears in the order, emails, and analytics. If accounting or the order management team expects separate reporting for store credit, agree in advance where the team will review those orders.

What the Support Team Should Know

Support should understand a few typical facts. Store credit is usually visible only to a logged-in customer. If the customer removes auto-applied credit in the current session, it may not be applied again until a new scenario starts. If the order amount changes, the customer may need to apply the balance again through a notice. If there is no store credit field at checkout, check the module, the balance, authentication status, cart contents, and the checkout page type.

Practical Example: A Free Gift Above a Cart Threshold

Now let us build a concrete scenario that demonstrates the main strength of Advanced Coupons Premium: the coupon does not just give a discount, it checks the cart, adds a product, applies the rule, and lets you verify the result. The example is not tied to a specific price or category because those change quickly and depend on the store. The goal is a free sample item added when the order passes a defined threshold.

Goal

The customer adds products to the cart. If the cart total reaches the required threshold, the store automatically applies the coupon and adds a free sample product. The gift should be free, its quantity should not be editable, and if the coupon is removed, the gift should disappear from the cart. The store manager should be able to see both the coupon and the gift in the test order.

Preparation

Before configuring anything, you need a regular product that will serve as the gift. It must be published, purchasable, and either in stock or allowed for purchase if the store does not manage stock. It is helpful to give it an internal name that makes it obvious to the team that this is a promotional gift. You also need a test customer and a test cart that can fall both below and above the threshold.

• WooCommerce is active, coupons are enabled, and a base coupon works.
• The Add Products module is enabled under Coupons > Settings > Modules.
• Auto Apply is enabled or available for the automatic scenario.
• The gift product is published, purchasable, and not blocked by stock-management rules.
• You have a test payment method and a way to cancel the test order.

Configuration Steps

1. Create a new coupon under Marketing > Coupons or Coupons > Add New, depending on your site's menu structure.
2. Use a clear internal code, such as a test promo code, and add an internal description for the team.
3. For the main discount, choose the smallest safe value or leave the discount portion neutral if the actual action is handled through Add Products.
4. Open Cart Conditions and add a cart amount condition, for example Cart Subtotal above the required threshold.
5. Save the Cart Conditions with the separate button if your interface displays one.
6. Open the Add Products tab, enable Enable Add Products, add the gift product, and set the quantity to 1.
7. Under Price/Discount, choose Override price with a value of 0 or Percentage discount with a value of 100, depending on your version and promotion logic.
8. Save the Add Products data.
9. If the gift should be added without manual code entry, enable Enable auto apply for this coupon.
10. Publish the coupon and move on to storefront testing.

Verifying the Result

First, build a cart below the threshold. The coupon should not apply, and the gift should not appear. Then add enough products to bring the cart above the threshold. If Auto Apply is enabled, the coupon should apply automatically after recalculation and the gift should appear as a cart line item. If Auto Apply is not enabled, apply the code manually and verify the same outcome.

Try changing the gift quantity. For coupon-controlled lines, WooCommerce should prevent the customer from changing it, and once the coupon is removed, the gift should disappear. Then place a test order and confirm that the coupon, the gift line, and the final total are visible in the order. After the test, cancel the order and restore inventory if needed.

A Detail People Often Miss

If the gift is not being added, do not rush to blame Auto Apply. First check the gift product itself: status, stock, variation, purchasability, visibility, and whether the Add Products data was saved. Then review the Cart Conditions: does the cart total really pass the threshold, and are taxes or discounts being calculated differently than expected? Only after that should you investigate caching, a checkout conflict, or another pricing plugin.

How to Validate the Result Before Publishing a Promotion

Testing a coupon campaign should be just as mandatory as testing payments. It is not enough to see a green "coupon applied" message. You need to verify that the promotion works for the right customer, does not work for the wrong one, and is reflected correctly in the cart, checkout, order, emails, and reports.

Advanced Coupons Premium can affect several areas at once. BOGO changes the cart composition and totals. Add Products adds an item. Store Credits affect how the order is paid using internal balance. URL Coupons change the customer path. Auto Apply works in the background. That means the test needs to follow the full chain.

Minimum Test Set

• Qualifying cart: all conditions are met, the coupon applies, and the result matches expectations.
• Non-qualifying cart: the required product, amount, role, or order history is missing, so the coupon does not apply.
• Cart changes after application: a product is removed, quantity changes, or the total drops below the threshold.
• Checkout: the order total, taxes, shipping, payment methods, and coupon line all look correct.
• Order in the admin area: the coupon, gift, store credit, or BOGO lines are visible to the store manager.
• Customer email: order totals and line items are clear, with no unexpected text.
• Refund or cancellation of the test order: store credit and stock do not create unwanted side effects.

Testing After Site Changes

A coupon campaign may work today and break after another plugin is updated, the checkout is changed, caching is enabled, or a product category is modified. That is why active recurring promotions should have a short operating procedure: after updating WooCommerce, a checkout builder, the theme, a payment gateway, a multi-currency plugin, or Advanced Coupons itself, re-run the key promotion tests.

Pay especially close attention to cart/checkout blocks and custom checkout pages. The Advanced Coupons documentation includes separate articles for Elementor checkout and FunnelKit, which by itself tells you something important: even if the default checkout works, a custom checkout flow may require separate testing.

Compatibility with Checkout, Cache, Currencies, and Neighboring Plugins

Most coupon problems happen not because the coupon "cannot" apply a discount, but because multiple systems are modifying the cart at the same time. WooCommerce calculates products, taxes, shipping, and discounts. Advanced Coupons adds rules, gifts, auto-application, and store credit. A checkout builder may change where the coupon field appears. Cache may serve an outdated state. Multi-currency may recalculate amounts. A dynamic pricing plugin may alter the price before the coupon checks its conditions.

Cart and Checkout Blocks

Modern WooCommerce stores may use cart and checkout blocks. The Advanced Coupons changelog regularly includes fixes related to cart/checkout blocks, Auto Apply, Add Products, store credit, and BOGO. That does not mean blocks should be avoided. It means every promotion needs to be tested on the exact checkout experience your customer will actually use.

If the site has a traditional cart in one place and a block-based checkout elsewhere, test both entry points. If checkout runs through blocks, verify not only the final discount but also notices, button availability, behavior after quantity changes, and total updates.

Elementor Checkout

The Advanced Coupons documentation for Elementor checkout explains that compatibility depends on the Elementor Pro Checkout widget and certain conditions being met. The plugin can load its checkout scripts if it detects the correct widget. If a different widget, custom HTML, or a third-party add-on is used, automatic detection may fail. That is why testing on Elementor-based sites should include both the Elementor editor and the live checkout.

If the coupon field or store credit UI is not visible, check whether Elementor Pro is active, whether the actual Checkout widget is being used, whether the Store Credits module is enabled, and whether the customer is logged in. If the site uses caching, clear it after modifying the checkout template.

FunnelKit

With FunnelKit, the logic is different: the documentation says the required store credit, loyalty points, or gift card code fields must be added to the checkout template. Advanced Coupons Premium extends Force Apply for the FunnelKit checkout coupon field and supports URL Coupons on FunnelKit landing pages and funnel steps. But if the field is not added to the template, the customer may never see the redemption option.

When testing FunnelKit, do not check only the coupon. Open the funnel template, make sure the required field is added, save the template, and test the live checkout as a logged-in customer. If Force Apply does not work, verify that it is enabled in the coupon itself, and do not mix it with Auto Apply unless there is a clear reason.

Cache and Optimization

Cart and checkout should usually be excluded from full page cache. If a cache plugin or server-side cache serves outdated HTML, the customer may see stale notices, an incorrect coupon field, or outdated totals. JavaScript optimizers can also interfere: deferred loading, script combining, or aggressive minification sometimes break checkout recalculation.

A safe recommendation is to exclude cart, checkout, my account, and the store credit endpoint from full caching if such caching is enabled. If the problem disappears after clearing cache or testing in a private window, review your caching rules rather than blaming the coupon itself. There is no need to disable all optimization permanently; it is better to create a precise exclusion for cart and checkout pages.

Multi-Currency and Payment Plugins

The Advanced Coupons changelog includes fixes related to WooPayments Multicurrency, Aelia Currency, payment restrictions, and checkout payment handling. If the store accepts multiple currencies, test the coupon in every important currency. Pay special attention to store credit, BOGO, and Add Products because they can affect the final price, discount recalculation, and line-item display.

If the coupon works in the base currency but not in another one, do not assume the coupon settings are wrong. Review the currency conversion order, plugin compatibility, WooCommerce logs, and recent release notes. For payment methods, verify whether the coupon restricts available gateways and whether the available gateway list changes after the coupon is applied or removed.

How to Plan a Promotion Calendar Around Advanced Coupons Premium

Most coupon system errors do not appear at the moment someone clicks a setting. They happen earlier, during promotion planning. The team comes up with an offer, quickly creates a coupon, enables several features at once, and only after customer complaints starts clarifying who was supposed to get the discount. Advanced Coupons Premium is flexible enough to support complex promotion mechanics, but that flexibility requires discipline.

For every coupon, it helps to complete a short promotion card in advance. This is not bureaucracy. It is a way to keep the connection between the marketing idea and the technical settings. The card should include the goal of the promotion, the target audience, the eligibility condition, the coupon action, the application channel, the expected storefront result, the validation method, the deactivation date, and the responsible owner. If even one field cannot be filled in clearly, the coupon is not ready to publish.

Promotion Card for a Complex Coupon

Working coupon card before setup

Question	What to record	Related setting
Who can use the promotion?	Guests, logged-in customers, role-based groups, segments, regions, customers with order history.	Cart Conditions, role restrictions, customer/order conditions.
What should the customer do?	Add a product, reach a threshold, follow a link, choose a gift, place a repeat order.	Cart Subtotal, Product Category, Has Ordered Before, URL Coupons, One Click Apply.
What changes in the cart?	Discount, gift, BOGO reward, free shipping, store credit, hidden or replaced coupon.	Discount type, BOGO, Add Products, Store Credits, Shipping Overrides, Force Apply.
How does the customer learn about the promotion?	Email campaign, landing page, banner, URL coupon, button notice, automatic application.	URL Coupons, One Click Apply, Auto Apply, coupon notices.
How do you verify success?	Test cart, negative scenario, checkout, order, email, coupon report.	Coupon usage, order line items, cart notices, analytics, reports.

This card is especially useful for recurring promotions. For example, if the store runs a monthly gift-with-order campaign, the team does not need to rediscover every time why Override price was used, where the Add Products line is stored, or why the gift disappears with the coupon. You can simply copy the promotion card, update the products, threshold, and dates, and then rerun the test scenario.

How to Avoid Conflicts Between Multiple Coupons

Advanced Coupons Premium makes it possible to run many promotions in parallel, but the customer still sees a single cart. If Welcome coupons, BOGO, free shipping, store credit, and Auto Apply are all active at once, the result can become too generous or too confusing. That is why the promotion calendar should define in advance which coupons can stack and which should be mutually exclusive.

A practical approach is to split coupons into groups. The first group contains persistent service coupons, such as store credit or free shipping above a threshold. The second includes marketing campaigns, such as a seasonal BOGO offer. The third includes individual coupons, such as a support compensation code or a personal offer. For each group, decide whether it can combine with other groups. If not, configure individual use, Force Apply, or Cart Conditions so the conflict is not resolved randomly in the customer's cart.

Be especially careful with the "Auto Apply + personal coupon" combination. A customer may receive a personal support code, enter it at checkout, and then the automatic coupon comes back after the cart refreshes. If that was not planned, support ends up with a complicated case. It is better to define the priority in advance: does the personal coupon replace the automatic one, or does the automatic one remain the baseline while personal coupons cannot stack with it?

How to Record Campaign Results

A coupon campaign should have a measurable outcome. For a simple store, it may be enough to track coupon usage count, revenue from orders using the coupon, average order value, number of gifts, and refunds. For a more complex store, add segments: new customers, returning customers, orders using store credit, orders with BOGO, orders from URL coupons, and orders from a custom checkout.

Do not judge a campaign by application count alone. An automatic coupon may apply often while lowering margin without increasing average order value. A BOGO campaign may increase item count per order but create inventory complications. Store credit may improve retention while changing how payments appear in reports. Results are better evaluated against the original goal: clear out a category, increase repeat orders, raise average order value, bring customers back, test a new product through a sample offer, or reduce support load.

Operating Guidelines for the Store Team

When Advanced Coupons Premium is used regularly, a single-coupon guide is no longer enough. The store needs a lightweight operating process understood by the marketer, the WooCommerce administrator, support, and the developer. It does not need to be long. Its purpose is to make sure the promotion does not depend on one person who remembers where a module is enabled and why the coupon behaves the way it does.

Who Owns What

The marketer defines the promotion goal and audience. The WooCommerce administrator translates that into coupon settings: Cart Conditions, BOGO, Add Products, Auto Apply, URL, or Store Credits. Support gets a short explanation of what the customer should see and which questions may come up. A developer gets involved only if the campaign touches a checkout builder, custom pricing plugins, caching, multi-currency, or payment methods.

This split protects the store from two extremes. The first is a marketer enabling every setting without checking checkout behavior. The second is a developer being forced to hand-build every discount even though it could be configured through the interface. That is one of the strengths of Advanced Coupons Premium: most promotion scenarios can be delegated to an administrator, while the developer is reserved for edge cases.

How to Support Customers

Support does not need access to every setting. It needs a clear cheat sheet for current promotions. For each active coupon, note the name, who qualifies, what the customer needs to put in the cart, whether the code must be entered manually, whether the coupon should apply automatically, which gift or discount should appear, what the promotion does not combine with, and when the coupon expires.

If a customer says "the coupon does not work," support should not immediately send a generic screenshot to the developer. First ask or confirm: is the customer logged in, which products are in the cart, what is the cart total, what is the shipping region, are they entering the code manually or following a link, is another coupon present, and are they trying to use store credit together with an incompatible product? This first-pass triage usually separates a real technical issue from a non-qualifying cart very quickly.

How to Safely Disable a Problematic Promotion

The rollback path should also be clear in advance. For a standard coupon, it is usually enough to unpublish it or disable Auto Apply. For Add Products, you can clear Enable Add Products in the specific coupon or disable the module if the problem is broader. For Store Credits, do not delete balance data unless there is no alternative. It is safer to temporarily disable automatic application or change the redemption limit while preserving credit history.

If the issue affects checkout, it is better to disable only the problematic mechanic rather than the entire plugin. A full deactivation may remove the store credit UI, change which coupons are available, and affect already prepared campaigns. First stop the coupon, clear cache, validate checkout, and then investigate the conflict. If you need to roll back after an update, do it on staging or from a backup rather than by spontaneously deleting the plugin.

How to Preserve Promotion Knowledge

After each campaign, it helps to leave a short note: what was configured, what worked, which errors showed up, which traffic sources brought customers, how many support requests came in, and what should be changed next time. With Advanced Coupons Premium, this is especially valuable because the same mechanic can be used in very different ways. Today Add Products may deliver a sample, tomorrow a required accessory, and next week a bonus item for a VIP role.

If the team keeps these notes, the next campaign does not start from scratch. You already know that on your checkout, Auto Apply requires cache clearing after coupon changes, that BOGO on variations must be tested across different sizes, that store credit is invisible to guests, and that FunnelKit checkout requires a manually added field. That turns the plugin from a set of tabs into a controlled store tool.

Why the Coupon, Gift, or Store Credit Is Not Working

Advanced Coupons Premium is best diagnosed not with a "reinstall the plugin" mindset, but as a chain: the module is enabled, the coupon is published, the conditions pass, the action is configured, the cart recalculates, checkout shows the result, and neighboring plugins do not interfere. Below are the most useful symptoms and checks for a real store.

The coupon does not apply even though the code is entered correctly

Symptom: the customer enters the code, but WooCommerce shows an error or removes the coupon from the cart immediately. In the admin area, the coupon looks published.

Possible causes: Cart Conditions are not met, standard WooCommerce restrictions conflict with advanced conditions, the coupon has expired, usage limits have been reached, the cart does not contain the required product, the user does not have the required role, or another coupon is set to individual use.

What to check: create two test carts: one fully qualifying and one intentionally non-qualifying. If neither passes, temporarily disable conditions one at a time. If the qualifying cart only starts working after disabling standard Usage Restrictions, then part of the logic is duplicated in multiple places.

How to fix it: keep the main business logic inside Cart Conditions, and use standard restrictions only where they are genuinely needed: usage limits, email restrictions, or basic category limits. If the condition depends on order history, test it with a user who has a real order in the required status.

Auto Apply does not apply the coupon

Symptom: the coupon is supposed to appear automatically, but the cart stays unchanged. Manual coupon entry may still work.

Possible causes: Enable auto apply for this coupon is not enabled, conditions are not met, the cart/checkout is not recalculating, another individual-use coupon is blocking it, cache is serving an outdated cart, or a dynamic pricing plugin is changing the price earlier or later than expected.

What to check: open the cart in a private window, clear the cart session, build the smallest qualifying cart, and bring it up to the required condition. If the coupon appears only after a manual cart refresh, the issue may be recalculation or checkout JavaScript. If it still does not appear after refresh, review the conditions and the Auto Apply checkbox.

How to fix it: simplify the coupon to a single Cart Subtotal condition and test it. Then add conditions back one by one. If the conflict is caused by another pricing plugin, decide which system should calculate the discount first and avoid duplicating the same promotion in two tools.

The gift product is not added

Symptom: the coupon applies, but the Add Products item does not appear in the cart.

Possible causes: the Add Products module is disabled, Enable Add Products is not enabled inside the coupon, the Add Products lines were not saved, the product is out of stock, the variation is incomplete, the item is not purchasable, or early insertion is enabled only for No discount lines.

What to check: open the coupon, go to the Add Products tab, and make sure the product line is saved and still visible after a page reload. Open the product itself on the storefront and confirm that it can be added to the cart without the coupon. If it is a variation, choose the specific variation rather than the parent product.

How to fix it: enable the module, save the Add Products lines, replace the problematic variation with a purchasable one, and verify stock. For a free gift, use a clear discount type such as Override price 0, then re-test coupon removal behavior.

The gift remains after the coupon is removed

Symptom: the customer removed the coupon, but the item stayed in the cart.

Possible cause: the line was added with No discount or is behaving like a regular product. The Add Products documentation explains that No discount lines may remain because they are added as regular items rather than coupon-tracked gifts.

What to check: review the Price/Discount type on the Add Products line. If the item is supposed to disappear with the coupon, use a tracked discount type rather than No discount.

How to fix it: change the price type, save Add Products again, and rerun the test. If No discount is required for a precondition scenario, explain to the team that this item is not a free gift and may behave like a standard cart line.

Store credit is not visible at checkout

Symptom: the customer has a balance, but there is no store credit field at checkout, or auto-application does not trigger.

Possible causes: the user is not logged in, the balance is zero, the Store Credits module is disabled, auto-application is not enabled, the customer manually removed credit in the current session, the cart contains an Advanced Gift Cards product, or the custom checkout does not render the required field.

What to check: log in as a test user with a positive balance. Check the default checkout without a builder first. If everything appears correctly there, the issue is likely in Elementor, FunnelKit, or another template. If it does not appear anywhere, review the module, the balance, and cart contents.

How to fix it: enable Store Credits, verify the balance, remove the gift card product from the test cart, add the required field in FunnelKit checkout, or verify the Elementor Checkout widget. If the customer removed the credit manually, ask them to clear the cart or start a new session.

The coupon works on the default checkout but not in Elementor or FunnelKit

Symptom: on the standard checkout page, the coupon field, store credit, or Force Apply works, but not on the custom checkout page.

Possible causes: Elementor is using the wrong Checkout widget, FunnelKit does not include the Store Credits or Gift Card Code fields, a third-party checkout widget does not trigger compatibility support, cache is serving an outdated template, or the required version of the base plugin or Premium extension is not active.

What to check: compare the standard checkout with the custom one. In Elementor, verify that the Elementor Pro Checkout widget is present. In FunnelKit, open the checkout step and the Fields area, and confirm that the required fields have been added. After any change, clear cache and test again in a fresh session.

How to fix it: use a supported checkout widget or add the fields manually in FunnelKit. If a third-party add-on is unsupported, do not assume Advanced Coupons will recognize it automatically as a standard checkout.

After an update, strange notices or discount recalculations appear

Symptom: the promotion used to work, but after updating WooCommerce, the theme, a checkout builder, or Advanced Coupons, the recalculation logic changed, new notices appeared, or the coupon started applying differently.

Possible causes: changes in cart/checkout blocks, scripts, multi-currency compatibility, store credit calculation order, the BOGO engine, or rules from a neighboring plugin.

What to check: review the Advanced Coupons and WooCommerce changelogs, then rerun the minimum test set for your main promotions. Do not disable every plugin at once. Disable only the ones that affect pricing, the cart, checkout, or currency.

How to fix it: temporarily disable the problematic coupon, simplify its conditions, test on staging, and then add complexity back step by step. If the issue affects money or checkout, it is better to contact support with a description of the test cart, enabled modules, and the list of checkout-related plugins.

Limitations and Debatable Settings You Should Know About in Advance

Advanced Coupons Premium extends WooCommerce coupons, but it does not override how WooCommerce itself works. Coupons apply to the cart and the order, which means they depend on how WooCommerce calculates products, taxes, shipping, and restrictions. Standard WooCommerce documentation reminds us that regular coupons do not reduce shipping except in dedicated free shipping scenarios. If you are configuring shipping coupons or shipping overrides, test those separately because shipping is not a normal product line item.

Coupons should not be used as a universal replacement for pricing strategy. If the store constantly needs different prices for different roles, segments, or wholesale customers, it is better to combine Advanced Coupons with a dedicated role-based or wholesale pricing tool and reserve coupons for promotions. If everything is calculated through coupons, it becomes hard for the administrator to understand why the customer sees a particular total.

Do Not Combine Multiple Automations Without a Reason

Auto Apply, Force Apply, URL Coupons, One Click Apply, Add Products, and BOGO can all affect the same cart. Sometimes that is appropriate: for example, a URL coupon sends the customer into a funnel checkout and Cart Conditions restrict the promotion. But if a single coupon has Auto Apply, Force Apply, BOGO, Add Products, and individual use all enabled at once, diagnosis becomes difficult. Start with the smallest possible scenario and add mechanics only when you clearly understand why they are needed.

Be Careful with Always-On Promotions

A permanent automatic coupon can hide the store's real margin picture. Managers get used to the idea that a discount "applies somewhere automatically" and stop seeing which campaign is affecting the order. For long-running campaigns, use clear coupon names, coupon categories, internal descriptions, and regular report reviews. If the plugin shows coupons in order preview or the dashboard, use that for control, but do not confuse it with accounting.

Do Not Invent Code Customizations Without Evidence

For this product, the available sources already provide many built-in settings and documented scenarios, so there is no need to add an arbitrary PHP snippet without a confirmed hook or filter. It is safer to use built-in modules, checkout builder settings, cache exclusions, and native WooCommerce mechanisms. CSS tweaks for notice styling are only safe after reviewing the actual markup in your theme, so a universal code sample in a guide like this would be risky.

Safe improvement without code: create an internal checklist for every promotion: coupon name, goal, conditions, action, where it appears, who owns it, how to test it, and how to disable it. For coupon-driven scenarios, that is more useful than a random snippet.

Questions About Configuring and Using Advanced Coupons Premium

Can I use the plugin without coding knowledge?

Yes. Most scenarios can be configured through the WordPress admin area and the WooCommerce coupon screen. You do not need code for Cart Conditions, BOGO, Add Products, Auto Apply, URL Coupons, or Store Credits. But for more complex diagnosis involving custom checkout, multi-currency, or dynamic pricing conflicts, you may still need a developer to review logs, JavaScript, and the cart recalculation order.

How is Premium different from the free version of Advanced Coupons?

The free plugin already adds useful capabilities to WooCommerce coupons, including some BOGO features, URL coupons, cart conditions, coupon categories, role restrictions, and store credit. Premium expands that feature set with more advanced BOGO scenarios, additional Cart Conditions, Auto Apply, Add Products, store credit settings, and other premium features documented in the official docs and changelog. Before relying on a specific feature, check the developer's current comparison chart.

Why does the coupon work manually but not through Auto Apply?

Manual application proves that the coupon code exists, but it does not prove that the automatic scenario is configured correctly. Check the Enable auto apply for this coupon setting, Cart Conditions, cart recalculation, individual use, and cache. If the coupon should trigger from the cart total, start with the simplest possible test using only Cart Subtotal, then add the remaining conditions back afterward.

Can I use Advanced Coupons Premium with Elementor checkout?

Yes, but only if the compatibility requirements are met. The Advanced Coupons documentation describes the supported scenario with the Elementor Pro Checkout widget, where the plugin can load the necessary checkout scripts. If a different widget or a third-party add-on is used, automatic detection may not work. For store credit, also verify that the module is enabled and the customer is logged in.

Can I use the plugin with FunnelKit?

Yes. There is dedicated documentation for FunnelKit. The important part is adding the required fields to the checkout template: Store Credits, Loyalty Points, or Gift Card Code, if those are part of your setup. Advanced Coupons Premium also extends Force Apply for the FunnelKit checkout coupon field and supports URL Coupons on funnel pages, but all of that should be tested in the real checkout flow.

What should I do if the gift does not disappear after the coupon is removed?

First check the price type in Add Products. If the line was added with No discount, it may behave like a standard product and remain in the cart. For a gift that is supposed to stay tied to the coupon, use a tracked discount type such as Override price or Percentage discount, then repeat the coupon removal test.

Does the plugin affect site performance?

Any plugin that works with the cart and checkout adds checks. The most important practical risk is not that "the page became heavier," but that cart/checkout cache is misconfigured or scripts are conflicting. Exclude cart, checkout, and account pages from full page cache, test custom checkout pages carefully, and do not enable unnecessary modules without a real scenario.

Can I launch a promotion directly on the live storefront?

It is better to start with a test coupon, a test product, and a test order. For a simple coupon, a short verification may be enough, but for BOGO, Add Products, Auto Apply, and Store Credits, you should test the full path: qualifying cart, non-qualifying cart, checkout, order, email, and rollback. After that, you can download the installation file and move on to careful setup on your own site.

When Advanced Coupons Premium Is the Right Choice

Advanced Coupons Premium is worth using when your WooCommerce store has outgrown simple discounts and needs to manage promotions as a rules-based system. The plugin is especially strong where you need to connect cart conditions, coupon actions, and a clear customer-facing result: BOGO, free products, automatic discounts, email-link coupons, store credit, checkout compatibility, and precise troubleshooting.

The best rollout strategy is not to enable everything at once, but to choose one useful scenario first. For example, a free gift above a cart threshold, a BOGO deal for a specific category, or automatic store credit for logged-in customers. Build it against a test cart, verify the negative scenario, place a test order, and only then scale it into a real campaign.

If you only need a single simple coupon with no conditions, the plugin may be excessive. If you need a large dynamic pricing matrix without coupon logic, compare it with dedicated discount rules solutions. But if your goal is to make WooCommerce coupons manageable, testable, and understandable for the customer, Advanced Coupons Premium gives you enough tools to build a complete promotion system without hand-coding every campaign.