The BFCM price change checklist for Shopify merchants

Updated August 2026 · Black Friday is November 27; Cyber Monday is November 30

Most BFCM post-mortems are not about traffic. They are about prices: a sale that went live at the wrong time, a discount that never showed on the collection page, or prices that quietly stayed low until the following Thursday.

This checklist covers the failures that actually cost money, from choosing the right discount mechanism through verifying every price after Cyber Monday.

First decide: discount code, or price change?

Automatic discounts and discount codes apply at checkout. On many themes the product and collection pages still show the original price, so a shopper sees no sale until reaching the cart. That works for “extra 10% off with code,” and poorly for “everything is 40% off this weekend.”

Changing the price puts the sale price on collection pages, search, product pages, and feeds. Set the compare-at price to the original price and the theme can render the familiar strikethrough.

If the sale is your headline, change prices. If it is a sweetener on top, use a discount.

Work backwards from November 27

The seven failures worth checking

1. Compare-at price was never set

A sale price without a compare-at price can look like ordinary pricing. Copy the current price into compare-at before lowering the price. Doing that in the opposite order can leave both values equal, with no strikethrough at all.

2. Prices never went back up

Every hour after Cyber Monday that a product sits at a sale price is lost margin. Schedule the revert when you schedule the sale. A revert left for Monday night is easily forgotten until Thursday.

3. Someone changed a price mid-sale

A person, ERP, supplier feed, or another app can change prices after your initial snapshot. A blind rollback then overwrites the newer value. Before relying on any tool, ask whether it detects that drift and reports the affected variants instead of silently replacing them.

4. The job half-finished

Shopify's Admin API is rate limited, so a large catalog cannot be updated in one request. A tool must pace, retry, and resume without leaving half the catalog on sale. Test at realistic scale before the weekend, not on twenty products.

5. Rounding produced the wrong-looking prices

Percentage math produces values such as $26.994. Decide whether the catalog should end in .99, .95, or whole numbers, and check cheap products by hand where rounding can materially change the discount.

6. Markets and currencies moved unexpectedly

Changing a base price can move automatically converted market prices, while manually fixed market prices might not move. Check at least one product in every important market before and after the change.

7. Nobody recorded what changed

When something looks wrong on December 2, you need to answer “what was this price on November 26?” in seconds. Keep the CSV export even if your pricing tool also keeps an audit history.

The short version

• Choose discount code versus price change deliberately.
• Export current prices and store the CSV somewhere findable.
• Set compare-at from the original before lowering the price.
• Test at realistic catalog scale.
• Confirm the rounding rule on inexpensive products.
• Schedule the revert at the same time as the sale.
• Check one product in every important market and currency.
• Freeze unrelated edits during the promotion window.
• Know how rollback handles a price changed after the snapshot.
• Verify every price after the sale ends.

Where PriceSafe fits

PriceSafe snapshots every affected variant before a change runs. Rollback restores those exact variants to their exact original values. If a price moved after the snapshot, PriceSafe holds that variant back and reports it instead of overwriting someone else's work. Scheduled sales take a start and end time together, so the revert runs on its own.

The free plan covers up to 50 variants per change, enough for a real dry run before committing the full catalog.