A product that can be ordered is not always a product ready to ship. Preorders and backorders need clearer information than an ordinary stock badge, especially when the expected date or payment arrangement can change after purchase.
Related service: Website and ecommerce development- 01Explain availability and payment terms
- 02Record the customer's selected option
- 03Track the expected supply event
- 04Communicate material changes
- 05Release eligible orders for fulfillment
SECTION 01
Separate availability, payment and fulfillment decisions
Ask the agency to document whether you are selling a future release, waiting for replenishment, or making an item after purchase. Each needs a different explanation. Define whether payment occurs now, partly now or later, then verify that the chosen store configuration supports it. Do not design a deposit journey around an assumption that every payment provider can collect the remainder automatically.
Shopify's preorder documentation describes supported purchase options and app requirements; these are platform-specific conditions, not universal capabilities. The business must also approve the commercial wording and applicable obligations. The development brief should focus on recording the accepted option, preserving its terms with the order and preventing normal fulfillment rules from treating unready items as dispatchable stock.
SECTION 02
Illustrative example: an upcoming desk organizer
Imagine a retailer launching a new desk organizer while also selling ready-stock accessories. The organizer page gives a clearly labeled expected release window and the supported payment arrangement. A shopper adds both products. Before checkout, the store explains whether it will ship them together or handle them separately, rather than letting the ready-stock accessory imply immediate delivery for the entire basket.
The supplier then moves the expected arrival window. Staff need a list of affected orders, the original expectation and an approved update process. The first release can make that review manual while keeping order states clear. Automated change notifications should follow only after the team can identify the correct affected customers and avoid sending the same update repeatedly.
SECTION 03
Test the transitions, not only the product badge
Acceptance should cover an ordinary product becoming preorder-only, a preorder becoming available, a delayed batch and a cancellation request. Verify how reservations interact with real stock, how unpaid balances are handled and what happens if a payment attempt fails later. Emails, account pages and staff queues should use compatible language about what has and has not happened.
A standard supported preorder extension may be sufficient; custom presentation does not justify replacing its payment logic. Ask for a capability check, recurring cost list and exit plan before choosing one. Handoff should explain who changes expected dates, who approves customer updates and how to export the outstanding commitments. Do not remove an extension without understanding what happens to open preorder records.
SECTION 04
Frequently asked questions
Are preorders and backorders identical?
No. An upcoming release and replenishment of an existing item create different expectations, even if some store tools handle both.
Can customers pay only a deposit?
Only when the actual commerce and payment setup supports that arrangement. Verify later collection and failure handling before promising it.
What if the expected release date changes?
Preserve the original order expectation, identify affected buyers and follow an approved update and cancellation-handling process.
PRIMARY REFERENCES
Sources and further reading
These references cover the standards, platforms, or published prices discussed in the guide. Worked examples and checklists are our editorial guidance.
- Shopify preorder purchase optionsShopify
- Understanding inventory statesShopify Help Center
EDITORIAL METHOD
About this guide
We use AI to assist with drafting and editing. Catapult AI Work is responsible for the published content. Examples illustrate possible approaches; they are not client case studies unless identified as such.
Budget examples are not Catapult package prices. Check linked provider pages for current fees and plan limits before making a purchase.
Read the editorial policy