A WooCommerce pre-order changes more than the label shown on a product page. It affects when a product is treated as available, how payment is collected, what customers see during checkout and how the resulting order is completed or cancelled. A deliberate configuration helps avoid misunderstandings about release timing, payment obligations and fulfillment.
WooCommerce Pre-Orders provides product-level settings, an optional future availability date, two payment models, pre-order-specific emails and tools for handling active orders. It also imposes a documented checkout restriction: one pre-order product cannot be combined with other products in the same order. Before launch, separate the extension’s documented behavior from store-specific operating decisions and verify how the selected payment gateway handles payment upon release.
What WooCommerce Pre-Orders Change in the Store Workflow
When pre-orders are enabled for a product, the normal relationship between product availability, checkout and fulfillment changes. The product becomes an active pre-order, and the store must define how customers will be informed and when payment will be collected. The parent order then follows a workflow that may remain active until the pre-order is completed or cancelled.
An optional future availability date and time determines when the product stops being treated as a pre-order. Once that moment is reached, the product behaves as a regular product. This change in product treatment does not replace the administrative work required for existing pre-orders. Merchants should still plan how active orders will be completed, how payment will be collected and how customers will be notified.
The payment choice also affects operations. Upfront payment uses the normal checkout flow, while payment upon release postpones collection. Deferred charging is not automatically available through every gateway. Automatic collection depends on a supported gateway and securely retained payment details; other gateways require the customer to pay later after receiving an email.
Configure the Product and WooCommerce Pre-Order Release Date
Begin with the product-level Pre-Orders settings. Enable pre-orders for the selected product and, when the launch timing is known, set an optional future Availability Date/Time. Treat this date as an operational setting rather than merely descriptive text: it determines when the product’s pre-order treatment ends.
The availability date and time can also be reflected in customer-facing information across the product, cart, checkout, order and email messaging. Use the same timing consistently in those areas so that customers can understand when the product is expected to become available and what their order represents before that point.
If the release schedule changes, review and update the date through the pre-order management area. Changing the date to the present or to a past date does not itself complete existing orders. Completion remains a separate workflow, so the store should deliberately decide when to process active pre-orders and when to communicate the change.
Configuration applies at product level. For a variable product, all variations are treated as pre-order items; individual variations cannot be configured independently as pre-orders. This should be considered when planning the product structure, availability messaging and order handling.
Release-date settings and customer-facing labels
Plan the date together with the labels and explanatory messages customers will see. The wording should make clear that the item is a pre-order, identify the expected availability timing and explain whether payment is collected during checkout or later. If the date changes, update the relevant customer communication as well as the product setting.
When the configured date and time is reached, the product stops being treated as a pre-order and behaves as a regular product. Existing orders still need appropriate completion or cancellation handling, so the release transition should be included in the store’s launch procedure.
Choose Upfront or Payment Upon Release
WooCommerce Pre-Orders supports two charging models. With upfront payment, the customer pays during checkout through the normal payment flow. This gives the store a paid order at the start, but cancellation and refund handling must still be defined clearly.
With payment upon release, payment is postponed until the pre-order is completed. A supported gateway may be able to charge securely saved payment details automatically. If the selected gateway cannot support that workflow, the extension can send a payment-required email so the customer completes payment later. The email path requires customer action and should not be presented as automatic collection.
Choose between these models according to the store’s inventory plans, cash-flow approach, cancellation process, refund handling and customer-communication policy. There is no universal choice that applies to every store. In either model, prepare for declined payments, expired payment details or other gateway errors that may require the customer to act.
Gateway verification before choosing deferred payment
Before enabling payment upon release, verify the current documentation for the selected gateway, the extension and the merchant configuration. Confirm whether the required saved-payment or later-payment workflow is supported for the payment method being offered. Do not assume that a gateway listed for one setup will behave identically in another configuration.
Do not store raw card numbers or payment credentials in WordPress. Deferred payment should use the gateway’s supported secure saved-payment workflow or a payment-required email. Payment providers may receive customer and order information, so review the store’s privacy notice and customer-facing disclosures for the relevant jurisdiction and provider.
Configure Customer Messaging Before Launch
Customer communication should explain the complete transaction path before the product is offered. Configure the pre-order-specific confirmation, availability, cancellation and payment-required emails through WooCommerce email settings. Check the wording and timing of each message rather than relying only on default expectations.
Align product-page, catalog, cart, checkout, order and email text with the configured availability date and payment model. Customers should be able to tell whether they pay immediately or later, what the expected release timing is and what action may be required when payment upon release is used.
Also explain what happens if the release date changes. A revised date should not leave customers guessing about fulfillment or payment. If an order is cancelled, the store should communicate that outcome and handle any required refund separately when payment was collected upfront.
Make the separate-order behavior visible before checkout. Customers may not expect a pre-order to remove other items from their cart, so clear wording can reduce surprise and support requests. A payment-required email also does not guarantee successful payment or fulfillment; it is a request for the customer to complete the next step.
Manage, Complete and Cancel Active Pre-Orders
Active pre-orders can be handled individually, by product or in bulk through the pre-order management screens. Use available filters to review orders by customer, product, availability date, pre-order status or order status. This makes it easier to organize a release when many customers or products are involved.
Completing a pre-order can initiate payment collection when a supported gateway can charge saved payment details. Otherwise, the customer may receive a payment-required email. After the pre-order is completed or cancelled, the parent order returns to normal WooCommerce order management.
WooCommerce statuses help distinguish payment and fulfillment stages. Pending payment indicates that payment has not been completed, while processing, completed, cancelled and refunded represent different points in the order lifecycle. The appropriate status depends on the actual payment and fulfillment state, not only on the intended release date.
Cancellation requires particular care. Cancelling an upfront-paid pre-order does not automatically reverse the charge through the pre-order cancellation action. A separate refund may be required under the store’s normal refund process and according to the payment gateway’s capabilities. Review whether payment was collected before treating cancellation as fully resolved.
Bulk completion, cancellation and customer messages
Before applying a bulk action, filter the list by the relevant product, availability date, pre-order status or order status and review the result. Bulk completion and cancellation can send status-change emails, and administrators may add an optional customer message. Use that message to clarify the action, especially when timing, payment or cancellation conditions have changed.
After the action, review the resulting parent-order statuses and check which customers were notified. For deferred payment, identify orders awaiting customer action. For upfront payment, identify cancellations that require separate refund processing.
Understand the One-Pre-Order-per-Order Checkout Limit
The extension restricts a cart to one pre-order product. A pre-order cannot be purchased alongside other products, and customers must place separate orders for multiple pre-order products. If a pre-order is added to a non-empty cart, the existing cart contents are removed.
This is documented extension behavior related to the complexity of the pre-order checkout process and the prevention of payment-processing conflicts. It is not a universal WooCommerce rule and should not be generalized to every pre-order plugin or solution.
Test this behavior before launch and explain it clearly in the storefront. The message should tell customers that a pre-order requires a separate order and that adding it may clear products already in the cart. This is especially important when the store sells both regular products and several upcoming products.
Pre-Launch Testing and Troubleshooting Checklist
Use a staging site to test the complete workflow before making the pre-order available. The objective is to verify the actual behavior of the configured product, gateway and customer emails rather than relying on assumptions about deferred payment or order status changes.
- Product setup: confirm that pre-orders are enabled at product level and that the availability date and time are correct.
- Release transition: test what happens when the configured date and time is reached and verify that the product is treated as regular.
- Payment: test upfront payment, payment upon release, payment failures and the customer-action path where a payment-required email is used.
- Gateway behavior: verify whether saved payment details can be charged through the selected supported workflow.
- Customer emails: review confirmation, availability, cancellation and payment-required notifications.
- Order management: test individual and bulk completion, cancellation, parent-order statuses and refund procedures.
- Checkout: confirm the one-pre-order-per-cart restriction, including what happens when the cart already contains other products.
- Stock and disclosures: test stock behavior and review privacy wording when payment-provider data sharing or saved payment methods are involved.
Also test a changed release date and confirm that existing orders are not treated as completed without the intended administrative action. Review applicable local requirements for deferred charges, refunds, disclosures and payment-provider data sharing, without treating this operational checklist as legal or tax advice.
Configuring WooCommerce pre-orders successfully requires more than selecting a product option. Set the product-level pre-order and release date, choose upfront payment or payment upon release, and verify the selected gateway’s actual capabilities. Then configure customer emails, explain the separate-order checkout restriction and define how active orders will be completed, cancelled and refunded.
Finally, test the entire path on staging, including release timing, payment failures, customer action, order statuses, emails, stock behavior and cart restrictions. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.