Skip to content
parallel

Running Shopify pre-orders on a large catalogue

How to run Shopify pre-orders across thousands of products. Where the data should live, how to handle mixed baskets and how to keep ship dates clear.

Design and build

Matthew Collins, the 9th of July 2026

Pre-orders look simple on a small store. Add a button, take the money, ship when the stock lands. Now try it on a catalogue of thousands, with moving release dates and customers who buy several items at once. That simple button turns into a stream of support emails.

Running pre-orders at scale is a data and rules problem, not a button problem. You need one reliable place for each product's status and ship date. You need a clear rule for baskets that mix pre-order and in-stock items. And you need the ship date visible everywhere the customer looks, from the collection page to the confirmation email.

Why do pre-orders get harder as the catalogue grows?

On a small store, one person knows every release date. On a large one, nobody does. Dates arrive from suppliers, change without warning and apply to hundreds of products at once.

Star Action Figures is the clearest example we've worked on. More than 4,000 products across 114 franchises, with pre-orders central to how collectors buy. Before the rebuild, pre-order dates were unclear and every point of confusion became a support ticket.

The problems we see on large pre-order catalogues are consistent.

  • Release dates held in product titles or descriptions, where nobody can update them in bulk.
  • Products left on pre-order long after stock arrived, or switched too early.
  • Baskets that mix a figure shipping next week with one shipping in six weeks.
  • Customers who didn't realise they'd bought a pre-order until the confirmation email.

Each one is fixable. The fix starts with where the data lives.

Where should pre-order data live?

In structured fields, not in text. We store pre-order status and expected ship date as metafields on the product or variant. That gives you one source of truth that the theme, apps and emails can all read.

It also makes bulk work possible. When a supplier moves a release by a month, you update one field on the affected products, not hundreds of descriptions. Exports and imports handle the rest.

A few rules we follow.

  1. Keep the date and the status separate. "Pre-order" is a status. "Expected October" is a date. They change at different times.
  2. Decide whether dates are exact or approximate, and show them consistently. A month is often more honest than a day.
  3. Put pre-order logic on the variant when variants release at different times.
  4. Automate the switch. When stock is received, the product should move from pre-order to in stock without anyone remembering to do it.

Shopify Flow handles that last step well. If building the workflow feels daunting, Sidekick can now draft Flow automations from a plain description, which you then test and activate.

Catalogue structure matters too. With Shopify's variant limit now at 2,048, you have more room, but more room isn't always better. Our note on variants or separate listings covers when a release should be its own product.

Should pre-orders and in-stock items share a basket?

This is the decision that causes the most grief. A pre-order is a promise about a date. When it shares an order with an in-stock item, someone's expectation usually breaks.

There are three workable approaches.

  • Block mixing. The cart keeps pre-orders and in-stock items apart, and the customer checks out separately.
  • Allow mixing and ship together. Everything waits for the latest item. This only works if customers are told clearly before paying.
  • Allow mixing and split shipments. Each item ships when ready. This is kinder to customers but costs more in postage.

For Star Action Figures, we built checkout protection so collectors didn't end up with confusing mixed orders. The right answer depends on your margins and your customers. What matters is picking one rule and making it visible.

For B2B stores on Shopify Plus, there's another option. You can send pre-order orders to review automatically using order review rules, so your team checks them before they're confirmed.

How should customers see a pre-order?

Everywhere, and the same way each time. A customer should never be surprised that they bought a pre-order.

  • On collection pages, a clear badge on the product card. Star Action Figures uses a distinct purple badge so it's obvious at a glance.
  • On the product page, the expected ship date next to the price, not below the description.
  • In the cart, a line showing which items are pre-orders and when they'll ship.
  • In the confirmation email, the same dates again, with what happens if they move.
  • In the account area, the current status of each pre-order.

After the rebuild, Star Action Figures saw pre-order support tickets drop substantially, because customers understood ship dates before checkout. That's the goal. Clarity at the point of purchase saves hours of support later.

What about payment and date changes?

Decide early whether you take full payment at order, a deposit, or payment on shipping. Pre-order apps handle these differently, so the choice affects which app fits. It also affects your cash flow and your refund process.

Plan for dates that slip. Write the email you'll send when a release moves, and decide whether customers can cancel for free. A clear, early message keeps trust far better than a vague one sent late.

Where parallel helps

We design and build Shopify stores for catalogues where pre-orders are part of the business model, not an afterthought. That covers the data structure, the theme, the app choice and the automations that keep it running. See how we approach Shopify design and build.

If your pre-orders are generating more tickets than sales, send us a brief and we'll show you where to start.

Tell us where you are stuck.

The messier the commerce problem, the more useful we are. Book a call or send the brief.