Work backward through the actual schedule
List design approval, materials, tooling, production, inspection, rework, transit, receiving, and dispatch. Ask which steps can overlap and which depend on completion of the previous step. A supplier's production lead time may exclude materials procurement, sample approval, or freight.
Record the evidence behind each duration and the owner of each dependency. A promise based on a single best-case sequence is fragile. Include realistic room for unresolved work, but do not invent a buffer and call the entire schedule verified. If a critical technical question remains open, a notification list may be more appropriate than paid preorders.
Calculate cash with a refund scenario
Imagine 200 hypothetical preorders at $50, generating $10,000 gross. If $7,000 is committed immediately to production and $1,000 to other costs, only $2,000 remains before any payment fees or taxes. Forty full refunds would consume that $2,000. The example illustrates exposure, not a recommended reserve percentage.
Model obligations and cash timing before treating preorder receipts as development profit. Determine how cancellations, failed payments, platform holds, and shipment changes affect the balance. A business can show many orders and still lack enough available money to complete production or provide required customer remedies.
Make the promise consistent and supportable
State the product's actual stage and the intended shipping period clearly where customers decide to pay. Distinguish shipment from arrival. Avoid one date in an advertisement and a conflicting date in checkout. Keep a record of the representation attached to each order.
The FTC merchandise-order guidance addresses shipping promises, delays, consent, and refunds for covered sales. Review the detailed guide for the specific situation rather than assuming the word preorder creates an exemption. Platform rules and other applicable requirements may also matter. Obtain qualified advice when the structure or jurisdiction is uncertain.
Respond to a delay before customers must chase you
When evidence shows the original promise cannot be met, update the schedule and customer process promptly. Explain the relevant status, the revised information you can support, and the applicable options. Do not offer repeated optimistic dates merely to reduce incoming messages.
Track notices, customer responses, cancellations, and refunds by order. Fix new-order promises as well as existing-order communication. If you cannot support further commitments, pause additional paid orders while resolving the backlog. A smaller, honestly managed launch is more useful than a large backlog financed by continuously accepting new promises you cannot yet fulfill.
Keep a promise register for overlapping order groups
Preorders accepted on different dates may carry different shipping representations. Maintain a record for each group rather than replacing the website date and assuming older customers now share it. Store the order confirmation, promised period, relevant notices, responses, and final outcome. This is especially useful when production is divided into waves or when a supplier delay affects only one configuration.
Check how the commerce platform handles dates and payment status. A global banner may change without altering confirmations already sent. A canceled order may remain in a fulfillment export. A refund may be initiated but not yet completed. Reconcile these states so the team neither ships canceled merchandise nor tells a customer money has been returned when the transaction is still unresolved.
Before opening another wave, compare current obligations with available stock, credible incoming supply, and cash reserved for remedies. New orders should not conceal the cost of an older backlog. If the schedule improves, communicate only what is supported and avoid promising every customer an earlier date before allocation is confirmed. The purpose of the register is accurate individual treatment, not merely a reassuring public status update that leaves specific orders unanswered.
Test the delay workflow before it is needed. Confirm who prepares notices, who approves dates, how customer choices are captured, and how refunds reach the payment system. Use a harmless internal test record where the platform permits it. A drafted email is not a functioning process if replies disappear into an unattended inbox. Check that support can identify the correct order group and original promise. This practical rehearsal reduces confusion if a real delay requires many individual decisions at once.
Decision checklist
- Is the shipping window supported by the full dependency chain?
- Are refund and platform-hold scenarios included in cash planning?
- Are promises consistent at every purchase step?
- Can delay notices and customer choices be tracked per order?