When to Pause a WooCommerce Campaign (And How to Do It Without Losing the Data)

The scenario is more common than people plan for. A campaign is three days into a two-week run. Stock on three of the featured products drops to zero. Or a supplier call reveals the margin on a specific range is much thinner than expected. Or customer service flags a wave of confused orders where two promotions stacked in ways nobody intended.

You need to stop the campaign. The question isn’t whether — it’s how. What happens the moment you pause it? Do your product prices snap back instantly, or is there a lag? Does the analytics history disappear? And when you want to restart, do you reactivate the same campaign or build a new one?

This guide answers all of that with verified information, not guesswork. The mechanics described here apply specifically to Smart Cycle Discounts, verified against the current plugin code.

When mid-campaign pausing is the right call

Pausing a WooCommerce campaign is the right action when the situation is temporary — when you expect to resume, or at least need time to evaluate before committing to an end. The alternative is letting the campaign expire naturally (reaches its scheduled end date) or deleting it, which are both permanent.

The clearest reasons to pause mid-run:

• Stock drops unexpectedly. A campaign running across 30 SKUs hits a stock-out on five of them. You want to stop promoting those products without ending the sale on the rest. Depending on how the campaign is scoped, pausing may be the right call — or you may need to edit the product selection first. See the guide to handling out-of-stock products in active campaigns for the full decision tree.
• A margin problem surfaces late. Supplier costs changed, or you discover the discount is deeper than you intended on a subset of products. Pausing buys time to review the discount config without the campaign continuing to generate orders.
• A conflict emerges with another campaign. Two campaigns turn out to be overlapping in ways Campaign Intelligence didn’t catch before launch — or a colleague launched a second campaign without checking what was already active. Pausing one stops the compounding while you sort out the discount conflict cleanly.
• A customer service problem requires breathing room. Support flags a pattern of orders that look wrong — prices customers didn’t expect, or a promotion being used in a way that wasn’t intended. Pausing the campaign while you investigate is much cleaner than letting it continue.
• An operational emergency unrelated to the campaign. A site issue, a payment gateway outage, a logistics problem. Sometimes you want to pause not because the campaign is wrong, but because you don’t want to be generating discount orders while something else is on fire.

Pausing is not the right call when the campaign is simply finished. If it has reached its end date or you no longer plan to run it, let it expire or archive it. Pausing creates an expectation — to you and to the data — that this campaign will resume. If it won’t, expire or archive it so your campaign list reflects reality.

The six campaign lifecycle states — what each one means

Smart Cycle Discounts tracks campaigns through six distinct lifecycle states. Understanding what each one means — and what transitions are available — makes pausing and recovering from it a lot less confusing.

Two states in this table are terminal: Expired and Archived. Once a campaign reaches either of those states, it cannot be reactivated directly — you can only move it back to Draft to edit and re-launch, or archive it permanently. Paused is explicitly not terminal. Its whole purpose is to allow resumption.

What pausing actually does: storefront prices, orders, filters

When you pause a Smart Cycle Discounts campaign, the status field in the database changes from active to paused. That single change drives everything else. Here is what happens across every part of your store.

Storefront prices return to full price immediately

Smart Cycle Discounts does not write discounted prices to WooCommerce’s stored _sale_price meta field. Discounts are applied at render time through WooCommerce’s price filters (woocommerce_product_get_price, woocommerce_product_get_sale_price, woocommerce_get_price_html) and at cart totals calculation via woocommerce_before_calculate_totals.

Because no stored price was ever written, there is nothing to clean up when you pause. The next time a product page renders, the price filter runs, the engine queries for active campaigns, finds none for that product (because the campaign is now paused), and returns the regular price. The “Sale!” badge disappears, the strikethrough vanishes, and the discounted price is gone — all without any bulk database update.

This means price reversion happens on the next page load, not on a schedule or batch job. For a store with page caching, there may be a brief period where cached pages still show the old discounted price, but no new visitors will see it once the cache regenerates normally.

Orders placed before the pause are not affected

Completed orders captured the discounted price at the moment of the transaction. Those order records are untouched by pausing the campaign. There is no retroactive adjustment — which is the correct behavior. Customers who completed a purchase under the promotion keep the price they were shown.

Analytics history is preserved completely

Pausing does not delete or archive the campaign’s analytics data. Revenue generated, order counts, product performance data — all of it remains attached to the campaign and is still visible in the analytics dashboard. The activity log records the status change (old status: active, new status: paused), but the historical performance data is unchanged. This is specifically why pausing is preferable to deleting when you still want to reference campaign performance or might want to resume.

Carts in progress at the moment of pausing

Cart prices in WooCommerce are recalculated on each cart update and at checkout. A customer who had a campaign-discounted cart item at the moment you paused the campaign will see their price revert to full price the next time their cart recalculates — usually on the next page load, when they change quantity, or when they proceed to checkout. This can create a jarring experience for customers mid-purchase, so pausing during peak shopping hours is worth avoiding when the problem allows for it.

How Campaign Intelligence handles a paused campaign

Campaign Intelligence in Smart Cycle Discounts provides verdict states — the advisory layer that reads your campaign’s health and flags issues. Understanding what it does when a campaign is paused matters if you’re using it to guide decisions.

When a campaign is paused, Campaign Intelligence continues to have access to the campaign’s data and can still run its analysis. The Campaign Overview Panel still loads intelligence data for a paused campaign — the engine calls recommend_for_campaign() regardless of status, and the overview panel prepares the intelligence section for any campaign it opens. The intelligence verdict (Good, Caution, Risk, Blocked) is based on the campaign’s configuration and historical data, not solely on whether it is currently active.

What changes is the context the engine uses. For active campaigns, the engine positions the campaign as active in its planning model. For paused campaigns (which don’t match the active or expired branch in the engine), the campaign is treated as a future-positioned campaign — similar to how scheduled campaigns are analyzed. This means intelligence signals will reflect the campaign’s configuration quality and any conflicts, but won’t have the real-time order-flow data that accumulates only while it’s running.

The practical implication: if you pause a campaign because Campaign Intelligence flagged a concern, you can still open the campaign overview and read the detail on what the flag was. The verdict won’t disappear because you paused. This is useful — it lets you act on the intelligence signal without losing it before you’ve fixed the underlying issue.

For a deeper look at what Campaign Intelligence evaluates and how to read its verdict states, see the guide to Campaign Intelligence.

Reactivate vs. duplicate-and-reschedule — choosing the right path

Once you’ve paused and addressed whatever caused the pause, you have two options: reactivate the original campaign, or duplicate it and create a fresh campaign with new dates.

When to reactivate the original

Reactivation is the right choice when:

• The pause was operational rather than strategic (stock issue is resolved, conflict is fixed, site problem is over)
• The campaign’s remaining scheduled period still makes sense — the dates haven’t passed and there’s still promotional time left
• You want the analytics to continue accruing on the same campaign record, so the full run is captured in one place
• Nothing about the campaign configuration needed to change

Reactivating a paused campaign from the campaigns list sets the status back to active directly. The campaign resumes from where it was. The activity log records the transition as a “resume” action (distinct from a fresh activation), so you can see the pause-and-resume event in the history.

When to duplicate and reschedule

Duplicating creates a new campaign as a Draft, with the original campaign’s full configuration copied but the dates cleared and performance metrics reset. This is the right path when:

• The original campaign’s window has fully passed — the dates are in the past and there’s nothing to resume
• You want to run a modified version of the same campaign at a later date, without the paused original sitting in your active list
• The pause revealed a configuration problem that requires editing the campaign (discount type, product selection, scheduling) — in which case editing the paused campaign and then reactivating is also valid, but duplicating gives you a clean record with no historical confusion
• You want to keep the original campaign’s analytics intact as a finished record, and start fresh analytics for the next run

When you duplicate, the new campaign gets draft status and cleared start/end dates. This is intentional — it prevents accidental activation of a campaign with stale or expired dates. You set the new dates, review the config, and launch when ready. The original paused campaign can then be archived to remove it from the active view.

There is no single right answer between reactivate and duplicate — it depends entirely on whether the campaign is worth continuing as-is or whether starting fresh serves your reporting and planning better. The decision tree above is a practical shortcut.

The clean pause-and-resume workflow, step by step

Here is a concrete sequence for pausing a campaign cleanly and coming back from it without issues.

Common mistakes when pausing mid-run

Most of the problems people run into when pausing campaigns aren’t about the pause itself — they’re about what happens before or after.

Pausing when the campaign should be archived

If you pause a campaign with no intention of ever reactivating it, it sits in your Paused state indefinitely — showing up in your campaign list, potentially factoring into store health assessments, and creating confusion for anyone looking at the campaign later. If a campaign is done, archive it.

Reactivating without checking the end date

This is the most common operational mistake. The campaign was paused, days or weeks pass while the issue is sorted out, and then it gets reactivated without verifying that the end date is still in the future. The campaign goes active and expires within the same cron cycle. Check the end date before reactivating, every time.

Pausing a scheduled campaign without understanding the transition

Scheduled campaigns (those set to auto-activate on a future start date) can also be paused. Pausing a scheduled campaign means it will not auto-activate when the start date arrives. To get it running again, you need to either reactivate it manually (which sets it directly to Active, bypassing the scheduled activation) or leave it in the transition path that will respect the schedule. Review the allowed transitions table above before pausing a campaign that hasn’t launched yet.

Assuming the pause affects all products immediately, including cached pages

Pausing removes the campaign from the active discount lookup — but your store’s page cache may still serve old HTML that shows discounted prices. Most page caching systems clear cached pages within minutes on a normal purge schedule, but if you need immediate accuracy everywhere (for a margin emergency, for example), manually purging the cache after pausing is worth doing.

Not investigating the root cause before reactivating

A pause that leads straight back to a reactivation without any change is just a momentary hiccup. If Campaign Intelligence surfaced a concern, or if a stock problem caused the pause, the issue needs to be resolved — not just waited out. Reactivating into the same conditions that caused the pause will likely cause the same problem again. The campaign priority guide is useful if you paused because of an unintended conflict between two active campaigns — understanding priority is often the fix.

Frequently asked questions

Does pausing a WooCommerce campaign delete the analytics data?

No. Pausing a Smart Cycle Discounts campaign changes only the campaign’s status field. All analytics data — revenue generated, order count, product performance — remains intact and visible in the analytics dashboard. The activity log records the pause event, but it does not remove historical data. If you reactivate the campaign later, new analytics data accrues on the same record, so the full campaign run is captured in one place.

How quickly do prices return to normal when you pause?

Prices return to their regular (undiscounted) values on the next page load after the pause. Smart Cycle Discounts applies discounts at render time through WooCommerce’s price filters, so there is no bulk database update to run and no cleanup process. The moment a product page loads after the pause, the filter checks for active campaigns, finds none, and returns the regular price. If you have page caching enabled, cached pages may still show old prices until the cache regenerates — usually within minutes under a standard cache schedule.

Can I pause a campaign that hasn’t started yet (Scheduled status)?

Yes. A campaign in Scheduled status can be paused. The effect is that the automatic activation on the start date will not fire — the campaign will remain paused rather than going active when the start time arrives. To reactivate, you can set it back to Active manually or back to Scheduled so the auto-activation fires on the next eligible window. This is useful if you want to delay a campaign that’s already in the queue without fully dismantling the scheduling configuration.

What happens to a recurring campaign when it is paused?

For recurring campaigns, pausing works the same way — the status becomes paused and discounts stop applying. If a recurring campaign is paused mid-cycle, the current cycle stops. What happens when you reactivate depends on the recurrence mode and the timing: a campaign in continuous recurring mode will resume applying discounts if it’s currently within an active recurring window; a fixed-cycle recurring campaign will follow its next scheduled activation based on the campaign’s recurrence configuration. If you’ve used recurring campaigns to run a consistent weekly or daily promotion, the setup and recovery logic is covered in more detail in the guide to recurring WooCommerce sales.

Should I pause or delete a campaign that isn’t performing?

Pause if you want to keep the analytics data and potentially revisit the campaign. Delete if you genuinely don’t want any record of it — but be aware that deletion is permanent and removes both the campaign config and its analytics history. In most cases, pausing (and eventually archiving) is the safer choice. Archiving hides the campaign from your active list while preserving everything for future reference.