The WooCommerce Store Owner’s Pre-Holiday Audit: Discounts, Fraud Risk, and Conflict Checks

Most WooCommerce merchants do some version of a pre-launch checklist before they push a single campaign live. They check the dates, confirm the discount percentage, verify the products. That is the right instinct — but it is also far too narrow for a major trading season like Black Friday or the December holiday rush.

The problem with checking one campaign at a time is that most of the damage happens between campaigns, not inside them. A 20% off promotion that is perfectly configured in isolation can still cause serious problems if it runs on the same products as a BOGO deal you set up three weeks earlier. A customer you would have wanted to flag as high-risk can clear your checkout during a sale rush because nobody reviewed the segment distribution before the traffic arrived.

This guide is a store-wide audit — not a single-campaign checklist. It covers six areas that experienced merchants review four to six weeks before any peak trading period: campaign conflict and overlap, fraud risk distribution, payment gateway and chargeback health, scheduling and timezone integrity, coupon stacking behavior, and product readiness. Work through each section once, and you will have a far clearer picture of what is actually ready versus what just looks ready.

Why individual campaign checks are not enough before peak season

A pre-launch checklist for a single campaign is a useful habit. If you are running one campaign at a time with weeks between them, checking each campaign before it goes live is sufficient. Peak season is different.

During BFCM and the December holiday period, most active WooCommerce stores run three to ten campaigns simultaneously — sometimes more. Some are percentage-off promotions across broad product categories. Some are BOGO deals on specific lines. Some are spend-threshold campaigns that stack passively with everything else. Others are recurring promotions that have been live for months and were never designed with the peak-season load in mind.

When you have that many campaigns running at once, the individual-campaign checklist fails you for three reasons.

First, conflicts between campaigns are invisible at the campaign level. You can look at campaign A and find nothing wrong with it. You can look at campaign B and find nothing wrong with it. The problem only appears when both are active simultaneously and a customer buys a product that qualifies for both.

Second, fraud risk accumulates before the event. The customers who abuse return policies, exploit first-order coupon codes, or run chargeback schemes on promotional orders — they do not appear out of nowhere on Black Friday. Their behavioral signals are already in your order history. A store-wide review four weeks out lets you act on those signals before the traffic multiplies them.

Third, scheduling errors and timezone mismatches compound under pressure. A campaign that starts four hours late in a normal week costs you a few sales. A campaign that starts four hours late on Black Friday costs you a meaningful percentage of your daily revenue. These errors are entirely preventable but rarely caught unless someone explicitly looks for them before the period begins.

The individual-campaign checklist is still worth doing — for every campaign, before every launch. But it is not a substitute for a store-wide review that looks across everything at once.

Section 1: Discount conflict and campaign overlap review

Discount conflict review is the most technically complex part of a pre-holiday audit, and it is also the most commonly skipped. The reason is simple: you need to hold all your active campaigns in your head at once and think through which products they share. That is easy when you have two campaigns. It is almost impossible when you have eight.

What to look for

Start by listing every campaign that will be active at any point during the peak trading period — including campaigns that are already running and campaigns that are scheduled to start. Then work through each pair and ask two questions: do they share any products, and what happens to the price if both apply?

The three overlap patterns that cause the most damage are:

• Same-product percentage stacking. Two percentage-off campaigns applying to the same SKU. Depending on how your priority rules are set, one may override the other (fine), or they may compound (expensive). The compounding case is rarely intentional.
• Coupon stacking with an auto-apply campaign. A customer applies a coupon code for 15% off and also benefits from an auto-apply campaign running across all products. Unless you have explicitly controlled this, the customer may receive both discounts simultaneously. This is covered in more detail in Section 5.
• Priority ties on the same product. Two campaigns with equal priority targeting the same product create an ambiguous outcome. Depending on which campaign is evaluated first, customers may get different prices at different times — which looks like a pricing bug even though both campaigns are configured correctly in isolation.

How to audit this systematically

If you use Smart Cycle Discounts, the Campaign Intelligence system runs overlap analysis on every campaign before and during its active period. The four verdict states — good, caution, risk, and blocked — give you a starting point for each campaign individually. A risk verdict on any campaign during peak season deserves resolution before the period begins, not after.

The conflict detection in Smart Cycle Discounts identifies whether two campaigns share products and flags priority ties. What it cannot do is tell you whether the resulting discount combination is intentional or accidental. That judgment belongs to you. The tool surfaces the structural problem; you decide whether it is actually a problem.

For a deeper look at how WooCommerce discount conflict detection works and what each verdict state means in practice, the dedicated post on understanding WooCommerce discount conflict detection covers the mechanics in detail.

Checklist: discount conflict review

• List all campaigns that will be active during the peak period (including recurring)
• Identify every pair that shares product scope
• Check priority settings for any shared products — confirm no ties
• Verify whether coupon-code campaigns and auto-apply campaigns can stack (and decide if that is intentional)
• Review any risk or blocked Campaign Intelligence verdicts and resolve before peak season begins
• Test one or two representative customer journeys manually, with the actual products and discount codes your customers will use

Section 2: Fraud risk and customer segment assessment

Peak trading seasons do not create new fraud — they amplify existing patterns. The serial returner who triggered five refunds in October is going to do more of the same in December, at higher order values and higher frequency. The customer who used your first-order coupon code four times under different email addresses in Q3 is primed to try again when your BFCM discount appears.

A pre-holiday fraud risk assessment is not about predicting who will misbehave. It is about reviewing your current customer risk distribution and making deliberate decisions about how you want to handle high-risk customers during the peak period — before the decisions are forced on you in real time.

Reviewing your customer risk distribution

If you use TrustLens, the Command Center dashboard gives you a segment distribution view across all six customer segments: VIP, Trusted, Normal, Caution, Risk, and Critical. TrustLens assigns every customer a trust score from 0 to 100 using eight behavioral detection modules (returns, orders, coupons, categories, linked accounts, shipping anomalies, chargebacks, and card-testing). Before a peak season, the numbers worth looking at are not the absolute counts — it is the proportions and the trends.

A store with 12% of customers in the Caution and Risk segments combined is in a different position than one with 3%. The first store needs to make active decisions about checkout restrictions and order review thresholds. The second store may be able to apply lighter-touch policies without meaningful exposure.

Specific questions worth asking during the audit:

• What percentage of your customer base currently sits in the Risk or Critical segment? Are those numbers higher or lower than three months ago?
• Do you have customers with multiple chargebacks in their history who are still able to complete checkout? That is worth a deliberate decision — whether to block, restrict, or simply monitor.
• Do you have linked accounts (multiple accounts sharing a shipping address, IP address, or payment method) in your Caution or Risk segments? Fraud rings tend to activate around promotional events.
• Are there customers with high return rates or coupon-then-refund patterns who have not yet triggered a manual review? Peak season is when those patterns become expensive.

Decisions to make before peak season, not during it

The value of reviewing fraud risk four to six weeks out is that you have time to think carefully rather than react. Three decisions that are worth making in advance:

Checkout restriction thresholds. Should customers in the Risk or Critical segment be blocked at checkout during the peak period? The right answer depends on your store’s history with those customers and how your return policy interacts with your promotional offers. If you have a generous return policy during the sale, high-risk customers have more leverage than they do during a normal week.

First-order coupon eligibility. If you are running a first-order discount as part of your BFCM promotion, review your linked-accounts data before the campaign launches. Customers with multiple accounts created specifically to harvest first-order codes are already in your data. Deciding now whether to add eligibility conditions to the coupon is easier than investigating fraud complaints after the sale.

High-value order review triggers. During peak season, order volume is high and review capacity is limited. Deciding in advance which order signals (trust score below a threshold, shipping address mismatch, unusually high order value) should trigger a manual hold — and assigning who handles those holds — takes pressure off the moment the sale is live.

Checklist: fraud risk assessment

• Review segment distribution: what percentage is in Caution, Risk, or Critical?
• Check for customers with multiple chargebacks who can still complete checkout
• Review linked-account clusters in the Risk and Critical segments
• Identify customers with coupon-then-refund patterns or high first-order coupon reuse
• Decide checkout restriction thresholds for the peak period
• Review first-order coupon eligibility conditions if running a new-customer promotion
• Set high-value order review triggers and assign review responsibility

Section 3: Payment gateway and chargeback health check

Your payment gateway is not just a transaction processor — it is also the entity that will suspend your account or place you in a monitoring program if your chargeback ratio climbs too high. Before a peak trading period, the time to check your ratio is now, not when the first warning letter arrives.

Understanding chargeback monitoring thresholds

Card networks maintain monitoring programs that trigger when a merchant’s monthly chargeback ratio exceeds certain thresholds. Visa’s VDMP (Visa Dispute Monitoring Program) and VFMP (Visa Fraud Monitoring Program) and Mastercard’s ECP (Excessive Chargeback Program) are the most common. The specific thresholds vary and change — check with your payment processor for current values — but the pattern is consistent: you get a warning, then fines, then potential account suspension if the ratio does not improve.

Peak trading months routinely produce higher absolute dispute volumes because order volume is higher. If your baseline dispute rate is already close to a monitoring threshold during a typical month, a significant spike in orders combined with a proportionate spike in disputes during a high-volume promotional period can push you across the line quickly.

What to check

If you use TrustLens and have connected your Stripe or WooPayments account, the Chargeback Ratio Speedometer in the dashboard shows your blended calendar-month ratio against Visa, Mastercard, Amex, and Discover monitoring thresholds. Review it as part of your pre-holiday audit.

If you are on another gateway and entering disputes manually, the same review applies — just done through your payment processor’s reporting dashboard. What matters is the trend: is your dispute rate rising, flat, or declining? A rising trend before a peak period is a signal worth taking seriously.

Beyond the chargeback ratio itself, two other payment infrastructure checks are worth including in the audit:

• Card-testing exposure. Card-testing attacks — where bots probe your checkout with stolen card numbers to identify valid ones — tend to cluster around high-traffic events when the noise of legitimate declines provides cover. If you have experienced card-testing activity in the past three months, verify that your detection and mitigation are configured before peak season begins. TrustLens’s Card-Testing Defense module monitors decline velocity in 60-second and 10-minute rolling windows and locks out device fingerprints involved in attacks.
• Gateway configuration and fallbacks. If you use multiple payment gateways, verify that your fallback routing is configured correctly. A gateway outage on Black Friday with no fallback is a recoverable problem only if you have thought about it in advance.

Checklist: payment gateway health

• Pull your current chargeback ratio (blended across card brands)
• Check whether you are approaching any card-network monitoring thresholds
• Review dispute trends for the past three months — rising, flat, or declining?
• Verify card-testing defense is active and appropriately configured
• Confirm payment gateway fallback routing (if you use multiple gateways)
• Check that manual chargeback entry is up to date if you are not on Stripe or WooPayments

Section 4: Scheduling and timezone validation

Scheduling errors are the most embarrassing category of peak-season failure because they are entirely preventable and immediately visible. A campaign that was supposed to start at midnight local time but was scheduled in UTC without adjustment goes live several hours late. Your social posts, email sends, and paid ads are all pointing to a discount that does not exist yet.

This section is short because the checks are straightforward. The reason to include it as a dedicated audit item — rather than something you do casually — is that scheduling errors compound in exactly the kind of environment peak season creates: multiple campaigns being set up by multiple people, some of them duplicated from last year’s campaigns that may have had different timezone assumptions.

What to verify

For every campaign that will be active during the peak period:

• Timezone alignment. Confirm that the campaign’s scheduled start and end times reflect your store’s configured timezone, not the server timezone. These are often the same, but not always — especially if your store was set up by someone in a different region or migrated between hosts.
• Year correctness. This sounds absurd, but a campaign duplicated from a previous year and not updated will fail silently. WooCommerce will not warn you that the scheduled start date is in the past.
• End date buffer. For time-sensitive promotions (a 24-hour flash sale, a “cyber Monday only” offer), verify that the end time has a small buffer beyond the advertised cutoff. A campaign set to expire at exactly the cutoff on a high-traffic day may have edge cases with orders in progress at that moment.
• Recurring campaign carry-over. If a recurring campaign (a weekly sale, a daily flash deal) is set to continue through the peak period, confirm that it will not conflict with the seasonal campaigns you are adding. The recurrence settings may need a pause or an end date added specifically for the peak weeks.

Smart Cycle Discounts flags campaigns with scheduling inconsistencies — dates in the past, timezone gaps, or recurring patterns that create unintended overlaps — as part of the Campaign Intelligence health evaluation. Reviewing the dashboard before peak season gives you a consolidated view of which campaigns have scheduling cautions attached.

Checklist: scheduling validation

• Verify timezone configuration for every scheduled campaign
• Confirm start and end years are correct (no carryover from previous years)
• Add end-time buffers to time-sensitive promotions
• Review recurring campaigns for conflicts with seasonal campaigns during the peak window
• Confirm that campaigns scheduled to activate automatically have the correct trigger conditions

Section 5: Coupon and discount stacking audit

Discount stacking is one of the most frequently misunderstood areas of WooCommerce pricing. Whether a coupon stacks with a campaign depends on how the campaign was set up, what the coupon type is, and how your store’s coupon settings are configured. Most store owners do not have a clear picture of all the combinations that are possible until one of them produces an unintended result at a bad moment.

The two stacking scenarios worth reviewing

Auto-apply campaigns plus coupon codes. Smart Cycle Discounts campaigns can be set to auto-apply at checkout or to require a specific code. If you have an auto-apply campaign running across broad product categories — say, 10% off everything — and you also plan to distribute a coupon code for an additional 20% off, those two discounts may apply simultaneously to the same order. Whether that is intentional depends on your margin structure. Before the sale, decide explicitly: are these meant to stack?

WooCommerce native coupons plus campaign discounts. WooCommerce’s native coupon system and Smart Cycle Discounts operate at different levels of the pricing stack. Smart Cycle Discounts sets sale prices at the product level; WooCommerce coupons apply at the cart level. The interaction between them is not always immediately obvious, especially when you have multiple campaigns running. Test a representative cart scenario — the products your customers are most likely to buy in combination — with your actual coupon codes before going live.

Checklist: coupon and stacking audit

• List all active and planned WooCommerce native coupons for the peak period
• List all auto-apply campaigns running during the same window
• For each combination: is stacking intentional? Does the margin support it?
• Test representative cart scenarios with both coupon and auto-apply campaign active
• Verify URL auto-apply links if used in email or social campaigns
• Confirm that single-use coupon codes (if used) are generated and distributed correctly

Section 6: Stock and product readiness

Discounting a product you are out of stock on is not just a missed sale — it is an experience problem. The customer sees the sale price, goes to checkout, and either cannot add the item or completes the order only to receive a backorder notification. In the best case, they are disappointed. In the worst case, they file a complaint or a chargeback.

Stock readiness is a separate operational track from the discount audit, but it deserves a place in the same review window. Four to six weeks is enough time to reorder inventory, identify which products will realistically sell out during the peak period, and decide whether to include them in your promotional campaigns at all.

What to review

For every product included in a peak-season campaign:

• Current stock level. What is the on-hand quantity today? Based on your sales velocity during a normal week, and assuming peak-season traffic is two to three times that, will the product last through the promotional period?
• Reorder lead time. If stock will run low, do you have enough time to reorder before peak season begins? Four to six weeks may or may not be sufficient depending on your supplier’s lead time.
• Out-of-stock behavior. How does WooCommerce behave when the product sells out mid-campaign? Is it removed from the sale automatically? Does it still appear with the sale price visible but “out of stock”? The default behavior may not be what you want.
• Discount intensity relative to margin. High-volume products with thin margins deserve a second look before they go into a percentage-off campaign. A 30% discount on a product with 35% gross margin leaves very little room for returns, fraud, or fulfillment costs.

Campaign Intelligence in Smart Cycle Discounts evaluates stock exposure as part of campaign health scoring — it surfaces campaigns where high-discount intensity is combined with low-stock products. If you see stock-related caution flags in the dashboard, those are worth resolving before peak season rather than explaining after it.

Checklist: stock and product readiness

• Review current stock levels for every product in a peak-season campaign
• Estimate whether stock will last through the promotional period based on expected traffic
• Identify products that may need to be excluded from campaigns due to stock risk
• Confirm out-of-stock behavior is configured as intended (remove from sale vs. show as unavailable)
• Review margin on high-discount products — does it leave room for returns and costs?
• Resolve any stock-related Campaign Intelligence caution flags

Frequently asked questions

How is this different from the standard pre-launch checklist?

The standard pre-launch checklist evaluates a single campaign in isolation before it goes live — dates, discount type, product selection, conflict check. The store-wide pre-holiday WooCommerce audit reviews all active and planned campaigns together, plus dimensions that exist at the store level rather than the campaign level: fraud risk distribution, chargeback ratio, payment gateway health, and cross-campaign stacking behavior. Both reviews are necessary. The audit covers what the individual checklist cannot see.

How far out should I do this audit?

Four to six weeks before the peak trading period is the target window. Earlier than that, you are reviewing campaigns that may not yet be planned or scheduled. Later than that, some issues become difficult to resolve in time. For BFCM specifically, that means late September to mid-October. For the December holiday period, early to mid-November.

Do I need Smart Cycle Discounts and TrustLens to run this audit?

No. The six sections of this audit are frameworks that apply regardless of which tools you use. Smart Cycle Discounts and TrustLens are mentioned because they surface specific signals — Campaign Intelligence verdicts, customer segment distribution, chargeback ratios — that make each section faster to complete. Without them, the same checks are still worth doing; they just require more manual review of your WooCommerce order data, coupon reports, and payment processor dashboard.

What should I do if I find a serious conflict or fraud risk close to the peak period?

Triage by severity. A campaign overlap that produces a marginally better discount than intended is a different problem than a campaign overlap that could produce a 90% discount on a high-margin product. Similarly, a small cluster of Risk-segment customers is different from a known fraud ring with linked accounts actively browsing your store. Deal with the most consequential issues first, and be honest with yourself about which issues you can realistically fix before launch versus which ones you need to monitor live.

The honest bottom line

Peak trading seasons reward preparation disproportionately. The stores that struggle are not usually the ones running bad promotions — they are the ones running good promotions that silently interact with each other, with their fraud exposure, or with their stock position in ways that were never reviewed.

This audit does not guarantee a flawless sale. It gives you enough information to make good decisions in advance instead of reactive ones under pressure. That is the real value of doing it four to six weeks out, not the night before.