What does preorder mean? Difference from Backorder

Preorder

Typical cases include:

• a product that has not launched yet
• a new edition arriving on a known release date
• an item in production that the merchant wants to sell before finished stock is ready

The defining idea is purchase before normal availability, not simply "inventory is zero."

Preorder versus backorder

A preorder usually starts before ordinary availability. A backorder usually starts after an ordinarily available item has run out and the merchant expects replenishment.

A game releasing November 1 can be preordered in October. A replacement controller that usually ships every day but is temporarily unavailable might be backordered.

Both can involve delayed fulfillment, but the customer expectation is different. A preorder is often attached to a launch or availability milestone. A backorder is attached to a replenishment promise.

Availability date is not always ship date

Suppose a product is scheduled to arrive at the warehouse on October 10. The merchant may still need to:

• receive and count the shipment
• inspect units
• allocate stock to preorder customers
• pick and pack orders
• hand packages to a carrier

If the customer is told "ships October 10," the merchant has made a different promise from "available from October 10." Preorder messaging should therefore distinguish a release or availability date from the estimated fulfillment date when those are not the same.

Payment can happen at different times

Do not define a preorder by whether the customer is charged immediately. Shopify's current preorder documentation, for example, supports configurations that collect full, partial, or no payment at the time the preorder is placed, depending on the purchase option setup. Other platforms and payment methods can differ. The operator needs explicit rules for:

• amount due when the preorder is placed
• remaining amount due later
• stored payment method or later payment collection
• failed later payment
• cancellation before release
• refunds if release is delayed or canceled

A long preorder window can also create payment-authorization constraints if the implementation relies on an authorization that expires before fulfillment.

Preorder capacity should be finite when supply is finite

Suppose a merchant has confirmed 500 units in the first production run. If 40 units are reserved for reviewers, replacements, or retail partners, only 460 may be safe for direct-customer preorders. Accepting 700 preorders does not create more first-run inventory. It creates a second cohort with a later promise. A preorder record can therefore track:

• confirmed incoming quantity
• reserved operational buffer
• preorder quantity sold
• customer cohort or allocation batch
• expected release date for each cohort

If supply is uncertain, the cap should reflect confidence rather than the supplier's best-case number.

Preorders help forecast demand, but demand is not supply

Preorders can reveal demand before launch and reduce the uncertainty of a production decision. They can also create false confidence if the merchant assumes every preorder will convert to a completed, fulfillable order. Consider:

• payment failures
• cancellations
• fraud screening
• address changes
• supplier short-ships
• damaged inbound units

The useful forecast distinguishes orders requested from orders that can actually be fulfilled and paid.

Delay communication is part of the product

A preorder customer accepted delayed fulfillment in exchange for a future promise. If the promised date changes, silence erodes that bargain. A good delay workflow can include:

1. detect that the release or fulfillment promise is at risk
2. update the expected date
3. identify affected preorder cohorts
4. notify customers before the original promise passes
5. provide cancellation or other options where appropriate
6. prevent old dates from remaining on the product page or campaign creative

The storefront, order confirmation, help center, and campaign copy should not display conflicting dates.

Worked example

A merchant launches a limited keyboard with:

• 1,000 units confirmed for the first production batch
• 50 units held as quality/replacement buffer
• 950 preorder units available to customers
• expected warehouse arrival: November 3
• receiving and packing lead time: 2 business days

• The merchant should not promise all 950 customers "delivery November 3." That date is the expected inbound milestone

A more realistic promise might be "expected to begin shipping within 2 business days after the November 3 arrival," with additional transit estimates based on destination.

If the supplier later confirms only 900 usable units, the merchant has a defined exception: the final 50 customer orders need a revised allocation or cancellation path.

Preorder checklist

• Before enabling a preorder, define:
• what event makes the product normally available
• preorder capacity
• expected release or inbound date
• processing lead time after availability
• payment timing
• cancellation/refund behavior
• delay communication
• what happens when confirmed supply is short
• A preorder is a dated promise against future availability. Good preorder operations make the date, capacity, payment state, and exception paths explicit