How to Schedule a Mid-Sale Product Drop for BFCM on Shopify

Importier Team9 min read
How to Schedule a Mid-Sale Product Drop for BFCM on Shopify
On this page

Most Shopify merchants run their shopify bfcm product launch as a single moment: everything goes live at midnight on Black Friday. The store gets a surge of traffic, some conversions, and then goes quiet on Saturday. The customers who browsed and left on Day 1 have no concrete reason to return.

A timed mid-sale product drop solves this. Hold back a portion of your BFCM catalogue, import it in draft before the sale, and schedule it to activate mid-sale at a time you choose. Returning visitors who saw nothing new on Friday find something worth buying on Saturday.

This is a product data workflow, not a marketing tactic. Importier's Scheduled Imports makes it practical to execute without touching your store during the busiest sales window of the year.

Why a single BFCM launch leaves the second day empty

The all-at-once launch model assumes that the peak conversion window is the first few hours. For many stores that is true. But it ignores the behaviour of returning visitors.

Shopify's BFCM merchant guide documents the multi-day pattern consistently: a meaningful share of BFCM conversions happen on Day 2 or Day 3, not at the midnight launch. These returning visitors already know the store. They did not buy on Day 1 for a reason: nothing felt urgent enough, or nothing was quite right.

New products visible for the first time on Day 2 give these customers a specific reason to act. The product is genuinely new to them. The sale is still running. The combination creates a real urgency signal that a "24 hours left" banner cannot match.

Setting up products for a staged BFCM release

The mechanism is Shopify's Status column in the standard product CSV. Products imported with Status=draft are invisible to customers. Products imported with Status=active are live and visible.

You can set both in a single import batch. Import your hold-back products with Status=draft alongside your main launch products with Status=active. The main products go live when the sale starts. The hold-back products sit invisible in your catalogue, fully described and priced, waiting for a scheduled activation.

Two groups of product cartons under contrasting lighting representing active and draft product status separation.

According to Shopify's product management documentation, a draft product is fully configured in the backend but not visible to customers via the online store channel. All product data, including descriptions, prices, images, and metafields, can be set on a draft product before it is activated.

This matters for the BFCM workflow. All the work of building the product data, writing descriptions, setting compare-at prices, assigning category metafields, and attaching images, is completed before the sale begins. At activation time, one field changes.

Building your hold-back product set

The hold-back set should be 10-20% of your BFCM catalogue. Too small and the Day 2 drop has no weight. Too large and the Day 1 launch feels incomplete.

Strong hold-back candidates:

  • Limited editions, exclusive colourways, or new variants not available year-round
  • Products with a natural reveal mechanic: a new flavour, a collaboration, a new size range
  • Accessories or complementary products to your Day 1 bestsellers. A customer who bought the main product on Friday may want the accessory on Saturday

Poor hold-back candidates:

  • Core bestsellers that drive initial conversion. They should anchor Day 1
  • Products with tight inventory where activating demand before you can fulfil it creates refund and review problems
  • Products with time-sensitive pricing where compare-at values need to be set correctly from the first day of the sale

A footwear merchant with 180 BFCM products used this approach before a recent sale. Their main catalogue of 168 products went live at midnight on Friday. Twelve limited-edition colourways were imported as Status=draft. Their analytics showed a returning-visitor spike on Saturday mornings between 9am and 11am. They scheduled those 12 products to activate at 10am Saturday.

The activation CSV had two columns: Handle and Status. Each row contained a product handle and the value active. Fifteen seconds to build. The entire BFCM weekend ran without a single manual intervention.

To identify and track hold-back products: add a column to your master product record before the import that flags each hold-back product. This gives you a clear record of which products are staged and when they are set to activate. See the master product record workflow for how to build one.

Athletic footwear pairs arranged on retail shelving with a small cluster separated representing a held-back catalogue selection.

How to schedule the mid-sale activation in Importier

The entire workflow is configured before BFCM begins. During the sale itself, no intervention is needed.

  1. 01
    Import your full BFCM catalogue
    Use Importier's 14-step import wizard. Set hold-back products to Status=draft in your source CSV; set main launch products to Status=active. All descriptions, pricing, compare-at prices, and category metafields are set for every product at this stage
  2. 02
    Verify draft products are invisible
    Check your storefront directly after the import. Draft products should not appear in collections, search results, or any sales channel. This confirms the hold-back is working before the sale begins
  3. 03
    Build the activation CSV
    Create a two-column spreadsheet with Handle in column one and Status in column two. Add one row per hold-back product with Status set to active. This is the entire file
  4. 04
    Create a Scheduled Import in Importier
    Navigate to Scheduled Imports, upload the activation CSV, set frequency to once, choose your activation date and time, and select your timezone. Scale plans support 2 scheduled imports; Enterprise plans support 10
  5. 05
    Confirm activation via Import History
    At the scheduled time, the batch runs automatically. Import History logs the file name, timestamp, and the number of products updated. This is your audit trail

The column mapping step, step 3 of Importier's import wizard, is what makes this safe during a live sale. When you configure the schedule, you map Handle and Status, and nothing else. Importier does not write to price, description, compare-at, images, or any other field. The only change that reaches Shopify is the status update.

Why column mapping is the BFCM safety rule

During a live sale, the risk of a bulk import overwriting prices or descriptions is real. A price that resets mid-sale, or an AI-generated description that reverts to a supplier default, creates visible problems at the worst possible time.

Importier's column mapping means the activation import has a fixed scope. The source file has two columns. Two columns get mapped. Everything else is untouched.

Industrial circuit breaker panel with two green switches activated and remaining switches off representing selective column mapping.

This is the same minimum-column principle covered in the BFCM restock import guide: when topping up sold-out inventory mid-sale, only map Handle, Variant SKU, and Variant Inventory Qty. The fewer columns mapped during a live sale, the lower the risk of an accidental overwrite.

Without Importier
Manual activation mid-sale
  • Must log in to Shopify admin during the sale
  • Risk of accidentally editing wrong fields while navigating
  • No precise audit trail of what changed and when
  • Time pressure during a live sale increases error risk
With Importier
Scheduled Import with column mapping
  • Configured before the sale begins: zero intervention required during the sale
  • Only Handle and Status fields mapped; nothing else can be overwritten
  • Import History logs the exact activation timestamp and product count
  • Scheduled for a specific time and timezone, not dependent on manual availability

The hold-back products were fully described, priced, and photographed before BFCM started. The only thing that changed at 10am Saturday was the Status field.

Timing your product drop for maximum re-engagement

The activation time matters as much as the activation date. Midnight on Saturday creates no re-engagement value. Most returning visitors are not browsing at midnight. Mid-morning Saturday, between 9am and 11am, is when returning visitors are most likely to be browsing with intent.

Check your own store analytics before setting the schedule. Look at your returning visitor traffic patterns from previous BFCM periods. If your store serves a predominantly Australian or UK audience, the timing relative to the sale start is different from a store whose audience is primarily US-based.

Importier's Scheduled Import time picker includes timezone detection, so the activation fires at the correct local time regardless of where the merchant is based. Set the time in your audience's timezone, not yours.

If you are running a multi-day BFCM campaign that extends through Cyber Monday, consider a second drop for Monday morning. Each activation is a separate scheduled import with a separate CSV. Scale plans support 2 scheduled imports; Enterprise plans support 10, which is enough for a phased release across the full BFCM weekend.

Managing the hold-back after the sale

Once the sale ends, some merchants want to return hold-back products to draft status to maintain scarcity for future campaigns. This is the same workflow in reverse: a CSV with Handle and Status=draft, scheduled for the sale end time.

Open commercial filing cabinet drawer with colour-coded hanging folders representing a structured archive of import history records.

Others prefer to leave the activated products live. The decision depends on whether the hold-back products are genuinely limited (a production run that will not be repeated) or just strategically sequenced (products that will be part of the regular catalogue after BFCM).

Import History retains batch records for 60 days with a CSV download option. For post-BFCM reviews, you can retrieve the activation batch to see exactly which products were activated and when. This is useful for inventory reconciliation and for planning the hold-back strategy for the following year.

Key takeaways

  • A shopify bfcm product launch does not have to be a single moment: holding back 10-20% of the catalogue for a Day 2 drop gives returning visitors a specific reason to come back
  • Import hold-back products with Status=draft in Importier's import wizard; the full product data, descriptions, pricing, and metafields, is set before the sale starts
  • Build the activation CSV with two columns: Handle and Status=active; one row per hold-back product
  • Importier's Scheduled Imports runs the activation at the configured date, time, and timezone without manual intervention during the sale
  • Column mapping in the activation import maps Handle and Status only: live prices, descriptions, and metafields are not touched
  • Import History logs the activation batch with a precise timestamp and product count, giving you an audit trail for every product drop
  • Scale plans support 2 scheduled imports; Enterprise plans support 10, covering a multi-drop weekend campaign

See how Importier handles this at importier.app. Scale and Enterprise plans include Scheduled Imports for timed product activations.

Ready when you are

Set up your first import in under five minutes.

Importier brings products into Shopify with AI descriptions, category metafields, and data enrichment on every run.

Free for your first 10 products. No credit card needed.

Install on Shopify