In this article
A pre-order reveals customer interest, but it also creates an operating promise. Receiving a hundred orders is insufficient evidence of success if nobody knows when stock will arrive or how many parcels the team can prepare daily. Define the batch before expanding promotion.
Separate order acceptance from payment collection
Shopify’s pre-order documentation describes options for full, partial or no payment when an order is placed. These are platform options, rather than universal availability across every store or country. Check your setup, then explain what will be charged, when and how changes will be communicated.
Base the limit on the weakest stage
Consider reasonably expected supply alongside receiving, inspection and packing capacity. In a hypothetical example, a store expects eighty units but can prepare twenty orders daily. Its promise should not imply that all eighty customers will receive their orders on one day. Distinguish warehouse arrival from dispatch and delivery.
Define an explicit stopping point
Assign an owner to close the batch at its limit and define what happens if confirmed supply falls. Test the ordering experience when the allocation is exhausted. Late manual checks are inadequate while an advertisement continues bringing orders. Maintain a single record of accepted orders, allocations and changes.
Update the promise before complaints arrive
Assign responsibility for contacting affected customers when supply information changes. Reference the order, revised timing and next step under the store’s policy and obligations. After the batch closes, compare promises with actual outcomes and record the cause of each departure. Use that review to adjust the next limit instead of repeating an unsupported promise.
