# Shopify BFCM Compare-At Price Recovery: Bulk Remove Sale Pricing

> How to bulk remove Compare At Price from Shopify products after BFCM, restoring your catalogue to full-price display without leaving stale sale badges visible for weeks.

- Published: 2026-11-05
- Author: Importier Team
- Category: Import Guides / File Imports
- Canonical: https://www.importier.app/blog/shopify-bfcm-compare-at-price-recovery

---

Shopify's Compare At Price field drives the "was $X, now $Y" display that BFCM campaigns depend on. Set it before Black Friday; your products show sale badges and struck-through original prices. Leave it set after Cyber Monday; your store shows the same sale messaging for the following week, two weeks, or indefinitely.

Stale sale badges are a consumer trust problem. A product page that shows "was $120, now $80" on December 10 either misleads buyers about whether the sale is still on, or trains them to ignore your pricing signals entirely. In several markets including Australia and the UK, persistent "was/now" pricing that misrepresents a genuine offer has specific legal implications under consumer protection regulations.

Clearing Compare At Price from several hundred products after BFCM is a bulk operation. This article covers how to do it correctly with Importier, and why getting the blank value right matters more than it looks.

<Callout label="Critical">
Clearing Compare At Price means setting the field to an empty value, not to zero. Setting Compare At Price to `0` in Shopify displays "$0" as the original price on the product page, creating a worse display than leaving the BFCM price in place. The correct removal is a blank cell in the import file.
</Callout>

## Why Compare At Price Removal Is Harder Than Setting It

Setting Compare At Price for BFCM is straightforward: add a column to your product import file, populate it with the original prices, push. Every product immediately shows the sale badge.

Removing it requires doing the inverse: setting the field to blank rather than setting it to a value. This is where merchants make errors, because a blank field in a CSV behaves differently from a zero or a missing column:

- **Missing column**: if the Compare At Price column is absent from the import file, Importier treats it as "do not touch this field." The existing Compare At value remains. This is the right behaviour for most imports but wrong for a cleanup import.
- **Zero value** (`0`): if the column is present and contains `0`, Shopify sets the Compare At Price to $0. The product page renders this as a crossed-out $0.00, which looks broken and confuses customers.
- **Blank value** (empty string): if the column is present and the cell is blank, Shopify treats this as "clear the Compare At Price." The sale badge disappears and the product displays at its regular price. This is the correct behaviour.

The difference between a missing column and a blank column is the distinction between "ignore this field" and "clear this field." For the BFCM price recovery import, the Compare At Price column must be present but blank.

## The Timing: When to Clear

The standard BFCM window runs from Black Friday (November 28) through Cyber Monday (December 1). Compare At pricing should be cleared by the morning of December 2.

Leaving it beyond December 2 creates several problems:

**Consumer expectation reset**: buyers checking back after Cyber Monday have already mentally processed the sale as over. A continued "was/now" display feels misleading rather than promotional.

**Legal considerations**: Australia's ACCC guidelines on "was/now" pricing require that the reference price (the "was") represents a genuine price at which the product was actually offered for a meaningful period before the sale. Using a BFCM Compare At Price that persists indefinitely creates exposure under these guidelines. The UK's CMA has similar requirements. Setting up a December 2 recovery import before BFCM opens is better practice than scheduling it reactively after the event.

**Gifting season pricing**: December is a high-revenue gifting period in its own right. Products displaying BFCM sale prices in December undercut the full-price December gifting revenue that follows.

<Divider label="Building the Recovery Import" />

## Preparing the Post-BFCM Recovery Import File

The recovery import file needs two things: a way to identify each product variant, and a blank Compare At Price column.

<table>
  <thead>
    <tr>
      <th>Handle</th>
      <th>Variant SKU</th>
      <th>Variant Compare At Price</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>merino-crew-neck-sweater-navy</td>
      <td>MCN-NVY-S</td>
      <td></td>
    </tr>
    <tr>
      <td>merino-crew-neck-sweater-navy</td>
      <td>MCN-NVY-M</td>
      <td></td>
    </tr>
    <tr>
      <td>merino-crew-neck-sweater-navy</td>
      <td>MCN-NVY-L</td>
      <td></td>
    </tr>
    <tr>
      <td>leather-tote-bag-tan</td>
      <td>LTB-TAN-ONE</td>
      <td></td>
    </tr>
  </tbody>
</table>

The Variant Compare At Price column is present, with blank cells. That blank signals "clear this field" rather than "ignore this field."

The fastest way to build this file is to export the BFCM import file you used to set the prices. That file already has the correct Handle and Variant SKU columns for every BFCM product. Add a Variant Compare At Price column, leave it blank for every row, and the recovery file is ready. You are reusing the same product scope; you are just clearing the field you previously set.

Do NOT include in the recovery file:
- Variant Price (do not change the BFCM sale prices until you are ready to restore original pricing separately)
- Descriptions (triggers AI regeneration)
- Tags or collections (removes BFCM sale collection membership you may want to preserve for post-event email campaigns)
- Status (do not change active products)

The recovery import is scoped to one operation: clear the Compare At Price. Everything else is left untouched.

![A printed import file on a desk with a column of product handle codes on the left and a column of blank Compare At Price cells on the right highlighted in yellow, representing the targeted blank-cell structure for BFCM price recovery.](/blog/shopify-bfcm-compare-at-price-recovery/01.jpg)

## Running the Recovery Import in Importier

<Steps items="Export your BFCM import file: open the file you used to set Compare At Prices before BFCM. | Add or modify the Compare At Price column: add a column labelled Variant Compare At Price. Leave every cell blank. Do not populate any value, including zero. | Upload to Importier: select Update existing products only mode. This prevents any new product creation if a Handle changes after BFCM (deletions, renames). | Map columns: map Handle to Product Handle, Variant SKU to Variant SKU, and Variant Compare At Price to Variant Compare At Price. Map nothing else. | Preview: the preview table should show all Compare At values changing to blank. If any row shows a price value being applied rather than cleared, check that cell for a stray zero or space character. | Push: execute the import. Shopify removes the Compare At Price from all matched variants simultaneously. | Verify on the storefront: open two or three product pages in a private window. Confirm the struck-through price and sale badge are no longer displayed. If they persist, check the product in Shopify Admin to confirm the field is blank, then wait for the CDN cache to clear (typically under 10 minutes)." />

## When You Are Restoring Original Prices at the Same Time

Some merchants run BFCM by reducing the actual Variant Price rather than using Compare At. After BFCM, they need to restore the original price as well as clear the Compare At.

For this scenario, the recovery file has three columns:

<table>
  <thead>
    <tr>
      <th>Handle</th>
      <th>Variant SKU</th>
      <th>Variant Price</th>
      <th>Variant Compare At Price</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>merino-crew-neck-sweater-navy</td>
      <td>MCN-NVY-M</td>
      <td>120.00</td>
      <td></td>
    </tr>
    <tr>
      <td>leather-tote-bag-tan</td>
      <td>LTB-TAN-ONE</td>
      <td>245.00</td>
      <td></td>
    </tr>
  </tbody>
</table>

Variant Price is the original full price (pre-BFCM) you want to restore. Variant Compare At Price is blank (clear). Both columns are present in the same file. This single import pass restores full pricing and removes the sale badge in one operation.

For merchants who set Compare At above the original price to create a larger-than-actual discount display: this is the import pass where you should also check whether the Compare At values used were compliant with your market's reference pricing requirements before next year's BFCM.

![A printed two-page BFCM price recovery plan showing the before column with sale prices and the after column with restored original prices and an empty Compare At column, representing the dual-column approach to full post-BFCM price restoration.](/blog/shopify-bfcm-compare-at-price-recovery/02.jpg)

## Preparing the Recovery Import Before BFCM Opens

Build the recovery import file immediately after you finish the BFCM setup import, not on December 1 when the sale is winding down and attention is elsewhere.

**The setup import creates the recovery file by subtraction**: take the BFCM import file, strip everything except Handle, Variant SKU, and Variant Compare At Price, blank the Compare At Price column, save as `bfcm-recovery-YYYY.csv`. That file is ready to run on December 2 without any additional preparation.

Naming convention: `bfcm-setup-2026.csv` (the import that sets BFCM prices) and `bfcm-recovery-2026.csv` (the import that clears them). Keep both files in the same folder. Next year, the recovery file from 2026 is the starting point for building the 2027 recovery file.

![Two labelled file folders sitting side by side on a wooden shelf, one labelled setup and one labelled recovery, representing the paired BFCM import files kept together for year-on-year reuse.](/blog/shopify-bfcm-compare-at-price-recovery/03.jpg)

<Compare
  withoutTitle="Manual post-BFCM price cleanup"
  withTitle="Importier recovery import"
  withoutItems="Each product updated individually in Shopify Admin; 200 products takes hours | Risk of setting Compare At to 0 rather than blank, displaying broken $0.00 on product pages | No systematic record of which products had Compare At Price set for BFCM | Cleanup happens reactively on December 2 under time pressure, increasing error risk | Products with stale sale badges remain live during the cleanup period"
  withItems="All BFCM products updated in a single import pass in minutes | Blank Compare At Price column in the import file correctly clears the field rather than setting it to zero | Recovery file kept alongside the setup file; identical product scope | Recovery file prepared at the same time as the setup file, before BFCM opens | All products updated simultaneously; no products remain with stale badges after the import completes"
/>

<PullQuote>
Build the recovery import file at the same time as the setup file. The first day after the sale is the wrong time to discover you need to reconstruct a 400-row spreadsheet from memory.
</PullQuote>

![A printed post-sale operations checklist pinned to a wall with the first item ticked in green and the remaining items unchecked, representing the December 2 BFCM recovery workflow status.](/blog/shopify-bfcm-compare-at-price-recovery/04.jpg)

The [BFCM catalogue emergency fixes guide](https://importier.app/blog/shopify-bfcm-catalogue-emergency-fixes) covers what to fix in the days before Black Friday, including a check for Compare At Price values across your catalogue before the sale opens. The recovery import in this article is the matching post-event step: the cleanup that follows a successful BFCM.

<TipBox />

If you are running BFCM Compare At Prices on a subset of your catalogue (selected products, not the full range), the recovery file needs to match that same subset exactly. Running the recovery import against a larger product set than the original BFCM setup import would clear Compare At Price from products that never had it set, which is harmless but wastes rows. Running it against a smaller set leaves some products with stale BFCM badges. Match the scope precisely.

Try Importier free at [importier.app](https://importier.app).
