Pre-Orders vs Waitlists vs Back-in-Stock: Which to Use When (2026)

Pre-orders work when you have a confirmed ship date and want cash up front. Waitlists work when timing is uncertain and you're testing demand. Back-in-stock alerts work when a proven product is temporarily sold out. Most stores reach for the wrong one first.

Every Shopify app store listing in this category promises the same thing: capture the lost sale. But pre-orders, waitlists, and back-in-stock alerts solve fundamentally different problems. Pick the wrong one and you'll either tank your cash flow on refunds, train your customers to ignore your emails, or rack up disputes for orders you can't fulfill.

We've built and supported all three patterns across client stores, from twelve-SKU drop brands to two-thousand-SKU replenishment shops. After enough back-and-forth between Shopify-native flows and a shelf of third-party apps, we built Restokly to handle pre-orders and back-in-stock alerts in one place. This guide is the version of the comparison we wish we'd had at the start, with the three-question framework we still use when a merchant asks "which one do I install?"

What Each One Actually Is (Plain English)

Pre-order: the customer pays now (or commits to pay) for a product that hasn't shipped yet. You have a ship date. The customer accepts the wait in exchange for guaranteed delivery and often early access.

Waitlist: the customer leaves their email to be notified when a product launches or returns. No payment. No commitment. You're collecting interest signal, not revenue.

Back-in-stock: a specific notification trigger fires when a sold-out product returns to inventory. The customer signed up because they wanted that specific variant. They're warm, not cold.

The three are often bundled into a single app's marketing page, which is exactly why merchants confuse them. Restokly bundles two of the three (pre-orders and back-in-stock) because they share infrastructure, but the customer journeys, conversion rates, and risks are still distinct. Treat them that way and you'll pick the right tool at each step.

When Pre-Orders Pay Off (and When They Don't)

Pre-orders work when you have:

• A confirmed ship date inside 8 weeks (per Shopify's own preorder guidance)
• Demand validation as your primary goal, not launch-day revenue
• A limited drop where scarcity is the actual product
• A customer-service workflow ready to absorb "where's my order" emails at week 5

Pre-orders quietly hurt you when:

• Your ship date slips past 8 weeks. Refund requests start climbing fast, usually around week 6.
• Margins are thin and your payment processor holds the float. PSD2-region Stripe holds can sit at 7 days, which means cash you thought you had isn't there yet.
• You're charging full price upfront in the EU. That triggers a 14-day withdrawal right that customers absolutely will use if they read about a delay on social media.
• You skip the deposit option. Full-payment pre-orders look great on the dashboard and terrible on the chargeback report.

A twelve-SKU capsule fashion brand we worked with last year ran their first pre-order on a winter coat. They priced the deposit at 30%, advertised a January ship date, and pulled around 340,000 CZK in deposits across two weeks. Then their fabric supplier slipped. The ship date moved to February, then to March. By week six of delays, refund requests hit 14% of orders. The brand had the cash float, but the customer-service load (around 25 minutes per email exchange) cost more than the cash-flow benefit they'd gained. The lesson: pre-orders are a cash-flow tool only when you can also handle the refund tail.

This is exactly why Restokly defaults to deposit pre-orders with automatic delay notifications and customer-facing self-service cancellations. The mechanics that hurt the capsule brand above are the ones we tried to take off the merchant's plate by default.

When Waitlists Earn Their Keep

Use them for:

• Pre-launch demand testing for a product that doesn't yet exist
• Drop culture or capsule releases where the waitlist itself becomes the marketing
• Email list building when you can't justify a paid ad spend yet
• Markets you're testing before committing to inventory (a new country, a new category)

Skip them when:

• The product is already live somewhere else. Customers don't sign up for waitlists for items they can already buy.
• You can't follow up within a week of launch. Lists go cold fast. Two weeks in and you're sending to a graveyard.
• You're treating list size as the success metric. It isn't. Conversion-to-purchase from waitlist signup is the only number that proves the channel works.
• You don't have the engineering capacity to segment by source, market, or product line. An undifferentiated waitlist blast performs worse than no waitlist at all.

A waitlist is a low-commitment instrument. That's the feature and the bug. More people will sign up than would pre-order, which feels great. Far fewer will buy. If your conversion-to-purchase rate from a waitlist drops below 8%, the list is mostly noise.

The Czech and EU context matters here too. Under GDPR, a waitlist email is a separate consent from your general marketing list, even if the customer is the same person. Bundling them is a violation. Most stores using off-the-shelf apps don't realize this until an audit forces the fix.

When Back-in-Stock Is the Right Call

Use them for:

• Proven bestsellers with predictable restocks (your top 20% of SKUs by revenue)
• Recovering the roughly 70% of stockout visitors who otherwise leave for a competitor
• Building urgency via SMS when restock units are limited (98% open rate vs 30–40% on email)
• Demand forecasting on slow movers (signup volume tells you which SKUs to restock first, and which to discontinue)

Skip them when:

• The product is permanently discontinued. Set proper 301 redirects to the closest active SKU instead.
• Restock is more than 60 days out. Offer a pre-order or waitlist, not a back-in-stock signup that goes nowhere.
• You don't have a reliable inventory signal. Alerts that fire without real stock arriving destroy more trust than they recover.

A specialty olive oil store we audit for runs around 200 SKUs, with bestsellers selling out every other month while slow movers gather dust. They installed a back-in-stock app two years ago. Last quarter the dashboard told them three useful things: their top three oils accounted for 71% of all back-in-stock signups, their notification emails converted at 31%, and one SKU they kept dutifully restocking was being signed up for primarily by competitor scrapers. They cut the SKU. The "demand" signal had been noise the whole time.

That last point is the unspoken benefit of back-in-stock alerts. The signup data is a demand-forecasting tool, not just a sales-recovery channel. Use it both ways. (The Restokly demand dashboard surfaces top products by signup volume for exactly this reason, the most-requested out-of-stock SKUs are the ones you want to look at first when planning your next purchase order.)

The Decision Framework (One Question at a Time)

Here's the three-question flow we use at the start of every stockout-strategy conversation:

1. Has this exact product been sold and shipped before?
   • Yes → Back-in-stock alert is your default. The customer knows what they're getting; you know your restock pattern.
   • No → Continue to question 2.
2. Do you have a confirmed ship date within the next 8 weeks?
   • Yes → Pre-order. Charge a deposit, not the full price, especially in the EU.
   • No → Continue to question 3.
3. Are you trying to validate demand before committing to production or inventory?
   • Yes → Waitlist. Build a list, but commit to following up within a week of any launch decision.
   • No → You're probably solving the wrong problem. Don't deploy any of the three until the underlying decision is clearer.

Three questions. No app store research required. We've used this framework on scoping calls for two years and it's still the cleanest way to cut through the vendor pitches.

Combining All Three (The Product Lifecycle View)

The three strategies aren't actually competing. They cover different phases of a single product's life. The honest answer for most stores is "use all three, in this order":

• Pre-launch: Waitlist. Build interest while the product is still being designed or sourced.
• Launch week: Convert the waitlist into pre-orders. The list that signed up six months ago is your warmest possible audience.
• Ongoing: Back-in-stock alerts between restocks. The waitlist becomes a permanent feature on every sold-out variant.
• Sunset: Discontinue, redirect, don't keep collecting signups. Be honest with the customer.

The mistake most stores make is collapsing this lifecycle into a single tool decision. "We need a pre-order app" or "we need back-in-stock alerts" is the wrong shape of question. The right one is "where in this lifecycle is this product, today?"

Shopify Implementation: When You Need an App

Shopify gives you partial versions of all three out of the box. Whether you need a paid app depends on volume, segmentation needs, and how much you care about the boring details.

What Shopify ships natively:

• "Continue selling when out of stock" toggle at the variant level (works for both backorders and basic pre-orders)
• Theme-level customization for a notify-me button (any developer can wire this in 3–4 hours)
• Order tagging and notes (enough to manually track pre-order vs in-stock for low volumes)

When native is enough:

• Under 1,000 SKUs and under 50 stockout signups per month
• Single-language store, single market
• You don't need partial payments or scheduled balance charges
• A developer hour is cheaper than a recurring subscription

When you need an app:

• Variant-level waitlists (size and color, not just product)
• Multi-language notification templates
• SMS in addition to email
• Partial payments, deposits, or scheduled charges
• B2B pre-orders with different payment terms
• A demand dashboard your team will actually open

The market for these apps is busy. STOQ and Notify! lean back-in-stock-first; PreProduct and Purple Dot lean pre-order-first; Klaviyo bolts back-in-stock onto its email platform. Each works, with different trade-offs and pricing models.

Restokly is our take on the same problem: pre-orders and back-in-stock in one Shopify-embedded admin, with sensible defaults baked in. Deposit pre-orders with auto-charged balances. Throttled restock alerts (capped at 2× available inventory by default, so a 20-unit restock doesn't trigger 500 angry emails). Custom-domain sending for inbox placement. Visual email editor that anyone on your team can use. Unlimited subscribers on every plan, including the free tier. The math we used while building it: a free plan that's actually usable up to 30 pre-orders and 100 back-in-stock emails per month, then $9/month if you outgrow it. Under that, the app costs you nothing. Over that, you should be making enough recovered revenue that the subscription is rounding error.

For a hands-on look at the native Shopify pre-order setup before you commit to any app, this walkthrough covers the "continue selling when out of stock" flow without dependencies:

EU and Czech Considerations Nobody Tells You About

If your store sells into the EU, three things matter that the US-focused app vendors barely cover:

GDPR consent: A waitlist or back-in-stock signup is a separate marketing consent from your general newsletter opt-in. You cannot bundle them in a single checkbox. Your app's default form probably does exactly that. Fix it before an audit forces you to.

14-day right of withdrawal: An EU customer who pre-orders has 14 days from delivery to return the item for any reason, full refund. This is non-negotiable. If your pre-order ship date plus your processing time pushes the withdrawal window into your fulfillment week, you're going to absorb returns at the worst possible moment. Plan for it.

Charge-later under PSD2: If you're using Stripe or any PSD2-region processor, "charge the customer in 6 weeks when the product ships" is a clean pattern legally. "Charge them now and refund later if anything slips" creates a withdrawal-rights and chargeback exposure that grows with every week of delay.

Czech-specific logistics: Zásilkovna pickup-point delivery is the default for most Czech customers. If your pre-order takes 6 weeks and the customer only has 7 days to collect from the pickup point, you'll burn returns on logistics alone. Configure the carrier window to match the order pattern, or default to home delivery for delayed-ship items.

These are the boring details that decide whether a pre-order strategy works in this market or doesn't. They're also the details that vendor blogs based out of New York or Toronto never quite get to.

What Breaks in Production (The Stuff Nobody Mentions)

After enough launches you start seeing the same failure modes, regardless of which app the merchant picked:

The week-six refund spike. Pre-orders sail through the first month. Around week six, with no shipment in hand, the refund requests start. Plan for it. Have a draft email ready. Communicate before customers ask.

Notify-me firing on items that never restock. A back-in-stock signup with no inventory plan behind it trains your customers to ignore your emails. Worse, it trains your future signups to ignore them. The reputational damage outlasts the SKU.

Double-charge collisions. One store we picked up had "continue selling when out of stock" toggled on at the variant level for 2,000 SKUs, then later installed a pre-order app that also managed the same behavior. For three months, certain variants ran both systems in parallel. When demand spiked over Black Friday, customers got charged twice, once via the standard checkout, once via the pre-order app's billing flow. The merchant didn't notice until chargebacks started landing in mid-December. Around 3,000 EUR in disputes. The fix took an hour. The damage took longer.

The "we'll figure it out later" SKU. Every store has them. The ones you don't really want to restock but didn't discontinue. They collect signups, you don't fulfill, and a year later you have a dead audience receiving emails that never lead anywhere. Audit your alert-eligible SKU list quarterly.

If any of these patterns sound familiar from your own setup, the free Restokly plan is enough to test a clean version against your existing flow before you commit to anything paid. Install it from the Shopify App Store; the Notify Me button and pre-order plans are live within a couple of minutes.

Frequently Asked Questions

Bottom Line

Three rules, in order:

1. Ask the three questions before you install anything. Has this product shipped before? Do you have a confirmed ship date? Are you validating demand? The answer points to one tool, not three.
2. Use all three across the product lifecycle, not in parallel for the same SKU.
3. Plan for the boring stuff: refund tails, EU withdrawal windows, inventory signals, audit-able consent. The app is the easy part. The operational discipline is the work.

The honest version of this comparison is that most stores don't need a more expensive app. They need a clearer answer to the three-question framework and the operational pattern to back it up. If your answer to the framework points to pre-orders, back-in-stock, or both, the free Restokly plan is a fair place to start: 30 pre-orders and 100 restock emails a month, unlimited subscribers, no card required. Outgrow it and the paid plans pick up where it leaves off.

If you're looking for a companion read, our piece on back-in-stock email subject lines goes deep on the next layer of the same problem: once the alert fires, what gets opened.

Josef Rousek is the developer behind Restokly. He's been shipping product since 2010 and was on the founding team at Digismoothie before building Shopify apps and e-commerce systems for brand-conscious merchants. Restokly is the Shopify app he wished existed while running pre-orders and back-in-stock flows on client stores.