How to Plan Ecommerce Preorders and Backorders

A preorder accepts demand before the product is available for ordinary fulfillment. A backorder accepts or retains demand after available inventory is exhausted. Both create a shipment commitment that depends on evidence outside the checkout page. Before opening either path, name the product, quantity cap, sales channel, order window, expected ship date, payment treatment, cancellation method, fulfillment location, and owner who can stop sales when the evidence changes.

For United States internet merchandise orders, the FTC says a seller needs a reasonable basis for an express or implied shipment representation. If the seller makes no shipment statement, the rule generally requires a reasonable basis for believing shipment can occur within 30 days. The FTC guide identifies anticipated demand, supply, fulfillment-system capacity, and transaction records as relevant evidence. A product launch date from a supplier is therefore only one input; receiving, inspection, allocation, and outbound capacity also belong in the promise.

Treat this guide as an operating framework, not legal advice. The FTC guide notes that state and local requirements may also apply, and Shopify instructs merchants using preorders to comply with the laws of the jurisdictions of the business and its customers as well as applicable platform and payment terms. Confirm the current requirements for the markets, products, payment method, and sales channels in scope before taking orders.

Do not convert a supplier purchase order directly into available inventory. Keep at least four quantities visible: units available to sell now, units committed to ordinary orders, units incoming but not received, and units promised through preorder or backorder. Add a dated exception for units under inspection, damaged, or otherwise unavailable. This prevents a shipment in transit from being counted as both incoming supply and inventory that can already fulfill an order.

Shopify allows a merchant to continue selling when tracked inventory reaches zero or below, and it identifies preorders and expected restocks as possible uses. That control changes storefront availability; it does not prove that the inventory or fulfillment capacity exists. Shopify also notes that location settings and order-routing rules affect how out-of-stock items are assigned. Review the control at the variant and fulfillment-location level so an oversell setting at one location does not create an unsupported promise across the network.

Set the order cap from the most constrained credible input. Begin with supplier-confirmed quantity, subtract quality and receiving risk reserved by the team, then compare the result with warehouse receiving and outbound capacity for the promised period. Keep a manual stop condition for a supplier slip, failed inspection, allocation change, payment issue, or warehouse constraint. When the stop condition is met, close or reduce the order window before the next customer receives the outdated promise.

The order record should preserve the promise the customer saw, not just the current product page. Store the order time, promised shipment date or window, quantity, payment status, customer contact route, inventory pool, fulfillment location, supplier or purchase-order reference, and any later notice. If the storefront wording changes, the order still needs a record of the earlier representation that governed the transaction.

Shopify documents preorders as a purchase option managed through a preorder app and notes that the available configuration can collect full, partial, or no payment at order time. The payment structure changes the operational record and the customer's expectation, so test authorization, capture, cancellation, and refund behavior before opening sales. Keep the preorder label and expected timing visible through product, cart, checkout, confirmation, and order-status experiences supported by the chosen setup.

Create an exception queue that joins commerce, customer service, and fulfillment. A supplier delay should identify every affected order and promise date. A receiving shortfall should show which orders can still be allocated and which require a customer decision. A cancellation or refund should update the commerce record and release any reserved inventory. Test these paths with non-customer records so the first real exception is not the first time the team discovers a missing notification or refund step.

A delay workflow needs a trigger before the promised shipment time passes. Compare the latest supplier, inbound, receiving, and allocation evidence with every open promise. When the evidence no longer supports the date, move the affected orders into a notice queue with the revised date if one can be supported, the reason data required by the applicable workflow, and the customer's available choices. Do not wait for a support complaint to reveal that an order cannot ship as promised.

The FTC guide says that when a seller cannot ship within the stated time, or within 30 days when no shipment statement was made, the seller generally must seek the customer's consent to the delay. If the required consent is not obtained, the guide calls for a full and prompt refund. It also explains required elements of a delay-option notice and distinguishes situations based on whether the revised shipment date is definite and how far it extends. Use the current FTC text and qualified counsel to design the exact notice and response treatment for the business.

Make cancellation available through a route the customer can actually use, and preserve the request time and resolution. Keep delay consent separate from marketing consent or a general account preference. If an order is cancelled, release the allocation, stop the fulfillment request, process the applicable refund, and confirm each state rather than assuming one system updated the others. A refund submission is not the same as a completed refund, so reconcile the payment record before closing the exception.

When inventory arrives, record received quantity, accepted quantity, rejected quantity, available date, and location. Allocate accepted units according to the documented order rule, then move each order to fulfillment with its original promise and any approved revised date attached. Do not close the preorder program when the purchase order arrives. Close it only when every order is shipped, cancelled, refunded, or held under a documented customer-approved delay.

The FTC guide states that the seller remains responsible for rule compliance when a fulfillment house or other agent causes the delay. That makes provider communication part of the control. Require the fulfillment provider to report receiving exceptions, capacity constraints, and shipment failures quickly enough for the seller to act before customer promises expire. Monitor the provider's event timestamps against the commerce records rather than relying on a weekly summary after deadlines have passed.

Review the program with counts that reconcile: orders accepted, units promised, units received, units accepted, orders shipped on the original promise, orders shipped on an approved revised promise, cancellations, and completed refunds. Keep those results descriptive. One launch does not prove a universal demand forecast or fulfillment rate. Use the observed gaps to change the next quantity cap, promise, supplier buffer, notification trigger, or provider requirement, then test the revised workflow again.