Pre-order launches and the promises you cannot keep

What a pre-order actually is

Financially it is attractive: cash before stock, demand signal before committing to a manufacturing run, and a launch that builds anticipation.

Operationally it is a set of promises made about a future you do not control. Your supplier's timeline, freight, customs, and quality all sit between the payment and the delivery, and none of them are within your influence once the order is placed.

Pre-orders go wrong less often because of a delay than because of how the delay was communicated, and that comes down to what was promised at the point of sale.

The four commitments that cause trouble

1. A specific ship date. The most common and the most dangerous. A date on the product page becomes the thing customers hold you to, and it is usually your supplier's optimistic estimate with nothing added for the parts that routinely slip.

2. An implied quantity. If the page does not say the run is limited, customers assume availability. Overselling a fixed run means either disappointing people or absorbing an unplanned second production run.

3. Silence about the mechanics. When are they charged? Can they cancel? What happens if it slips? Customers who cannot find answers to these ask, and each question is a support conversation you could have prevented with a sentence.

4. A quality expectation set by renders. If the only images are mock-ups, the physical product will differ in some respect, and the gap between the render and the item is where returns come from.

Wording a date you can survive

The instinct is to quote the earliest plausible date, because it sounds better and converts better. It is precisely backwards.

Take your supplier's estimate and add the things their estimate excludes: their own slippage, freight, customs, and receiving. Then add a buffer. Publish that date.

Shipping early is a small delight that costs nothing. Shipping after a published date is the failure that generates cancellations, chargebacks and reviews, and the difference between the two is entirely a wording decision made before launch.

Where you genuinely cannot estimate, say so plainly and give a window with a review date: expected in a stated month, with an update on a specific date whether or not anything has changed. A committed update date is worth more to customers than a precise ship date you are unsure of.

What the page needs to say

• That it is a pre-order, unmistakably, in the buying area rather than in small print further down.
• The expected date, conservative, with a note that it is an estimate.
• When payment is taken. Now or at dispatch. This is a genuine decision with cash-flow implications, and customers should not have to guess.
• The cancellation position. Whether they can cancel before shipping and how. Stating it plainly reduces both anxiety and support volume.
• What happens if it slips. One sentence promising to tell them and to offer a refund. This is the sentence that converts a delay from a betrayal into an inconvenience.

Communicating a slip

It will happen on some pre-order eventually. Three rules, and the first is most of it.

Message before the date passes. A customer told on the morning of the promised date is dealing with a business on top of it. The same customer chasing two days later is not, on identical facts.

Give a new date you can beat, and explain briefly what happened without a long apology. They want the date, not the supplier saga.

Lead with the refund option on a second slip. On a first delay, options belong in a list. On a second, put the refund first: a customer who has waited through one delay has earned a frictionless exit, and offering it plainly is what keeps them willing to buy from you again.

The wider version of this is in backorder communication that does not generate tickets.

The internal side

Most pre-order failures are internal information failures rather than supplier failures.

Somebody knows the shipment slipped. It arrived in an email, or in a conversation between two people, and never reached whoever answers customers. So support tells a customer it is on schedule, and it is not, which is considerably worse than saying nothing.

Three things prevent it. Supplier updates go somewhere shared rather than into one inbox. Whoever answers customers is in that room. And a slip is treated as an alert with a named owner rather than a fact somebody might notice.

Keep a single list of who has pre-ordered what and what they have been told, so that a second update goes to the right people and says something consistent with the first.

Deciding whether to run one at all

Pre-orders suit some situations and are a poor trade in others, and the decision is worth making explicitly rather than because a competitor did it.

Good fit: a product with genuine anticipation, a manufacturing run you need demand data to size, a customer base that has bought from you before and trusts you to deliver.

Poor fit: a first product from a new store with no track record, anything where the supply chain has multiple untested steps, or a situation where you are using customer money to fund production you could not otherwise afford. The last one is common and it is where pre-orders cause real damage, because a delay you cannot absorb becomes a refund you cannot fund.

If the honest answer is that the pre-order is financing the production run, be aware you are taking on the risk of a delay with no buffer, and size the launch accordingly.

Sizing the run

The second-order problem after dates: how many to accept.

Accepting unlimited pre-orders sounds like upside and creates an obligation you may not be able to meet at the price you quoted. If the run is fixed, cap the pre-orders below the run size, leaving margin for quality rejects and for the units you will need to replace damaged deliveries.

If demand exceeds the cap, that is a good problem and a much better position than overselling. A waiting list for the second run costs nothing and converts well, because the people on it have already demonstrated intent.

After it ships

Two things worth doing in the week after delivery, while the customers are still engaged.

Ask the pre-order customers how it went. They waited for it, which makes them unusually invested and unusually willing to answer. Their feedback about the waiting experience is the most useful input for the next launch, and it is available only briefly.

Write down what actually happened to the timeline. Where the slippage came from, how much, and whether your published date held. That single note is what makes the next pre-order date realistic rather than optimistic, and it is the thing nobody records because by then everyone has moved on.

The sentence that matters most

Of everything on a pre-order page, one line does the most work: what happens if it slips.

A commitment to tell customers promptly and to refund on request converts a delay from a betrayal into an inconvenience. It costs nothing to write, it is a promise you can always keep, and it is the difference between a customer who waits and one who files a chargeback.

Most stores omit it because mentioning delay feels like inviting it. The omission is what makes the delay expensive when it arrives.

Managing the waiting period

Between payment and delivery there is a stretch of silence, and silence is what turns a patient customer into an anxious one.

Two updates are usually enough. One at roughly the halfway point, saying where things are even if the answer is that everything is on track. One when it ships, referencing the original date so the customer can see you met it.

The midpoint update is the one stores skip, on the reasoning that there is nothing to report. Nothing to report is the report. A customer who paid two months ago and has heard nothing does not know whether you have forgotten, and the message costs five minutes to send to everyone at once.

Common questions