A Black Friday Price Plan You Can Actually Reverse

By late November a store may be running several overlapping promotions across thousands of variants. The discounting itself is rarely the hard part. The hard part is that every one of those changes has to be undone, correctly, often while the team is exhausted and traffic is at its peak.

Decide the reversal plan before the discount plan

For each planned promotion, write down three things before you decide the percentage: where the original prices are stored, who is responsible for putting them back, and what the exact end time is in the store timezone. A promotion without those three answers is not ready to schedule.

Freeze the catalog before you start

Set a date after which nobody edits prices, adds variants, or reorganises collections outside the campaign plan. Changes made during the promotion are the most common reason a restore comes back wrong: the snapshot no longer matches the catalog it is restoring into.

Stage the campaign instead of firing it all at once

1. A small test collection, days ahead, to confirm the rules behave.
2. The main catalog, scheduled with an explicit end time.
3. Any late additions as a separate run, so they can be reversed separately.

Staging matters because it keeps the blast radius small. If something is wrong with the discount rules, you find out on twenty products rather than two thousand.

Name a rollback owner and give them a deadline

Someone must be accountable for the catalog being back to normal by a stated time, and they need the authority to stop a promotion early. Write the name and the time into the plan. This is the single cheapest safeguard on the list.

Plan for the boring failure, not the dramatic one

Bulk price updates on a large catalog run in batches under API limits, so a promotion can be half-applied when something interrupts it. Decide in advance what you do in that state: finish the run, or roll back what already changed. Deciding it at 2 AM on Black Friday is not a plan.

SaleGuard is built around this half of the problem: it snapshots the original price and compare-at price before anything changes, previews the exact result, restores from that snapshot at the end time, and keeps rollback available while the sale is still running.