Selling a product before it arrives creates a second deadline for your store. Taking the order is the first job. Collecting any remaining payment, telling the customer what changed and getting the order into fulfilment are the jobs that follow.
That is why choosing a WooCommerce pre-order plugin takes more thought than comparing countdown timers. Two extensions can display almost identical product pages while creating very different payment and shipping workflows.
One might take the full amount at checkout. Another might email a payment link when stock arrives. A third might charge a saved payment method automatically, but only through a particular gateway integration. Those differences matter more than the badge on the product image.
We compared six options, including Webkul’s WooCommerce Pre Order Plugin on WPBay, using current product listings and documentation to check pricing, payment behavior and practical restrictions.
WPBay sells the Webkul plugin included here. The other products are linked to their developers or official listings.
Decide when the customer should pay
Start with the promise you want to make at checkout.
If the customer pays everything today, your pre-order system mainly needs to communicate the delay and keep the paid order out of the normal dispatch queue. This is often the most straightforward arrangement for a small product launch.
If you collect a deposit, you need to account for two payments. The customer should see what has been paid, what remains and when the balance becomes due. Shipping can complicate that calculation, especially if it is collected later.
If you collect nothing today, decide whether the customer must return to pay or whether your payment integration can initiate the charge later. “Pay on release” is sometimes used to describe both arrangements. They are quite different once the release email lands.
An unpaid reservation should also be counted separately from money received. Otherwise, a launch report can look healthy while the store still has a long list of customers who have not completed payment.
WooCommerce pre-order plugins compared
The prices below were checked on November 4, 2026. They reflect the currency and purchase route shown when checked; taxes, localization and promotions may change the final total.
| Plugin | A good reason to consider it | Price checked | Main purchasing caveat |
|---|---|---|---|
| WooCommerce Pre-Orders, by Woo | Upfront or release-time payments through a documented gateway system | $179 for one year | One pre-order product per order; no other products alongside it |
| YITH Pre-Order for WooCommerce | A free starting point, with broader payment controls in Premium | Free; Premium €139.99 with one year of updates and support | Automatic charging depends on supported integrations |
| Webkul WooCommerce Pre Order Plugin | Deposits and balance collection with a one-time license | $39 one-time, one site on WPBay | Automatic balances require the supported WooCommerce Stripe integration |
| Bright Plugins Pre-Orders for WooCommerce | Stores that need a choice of mixed-cart and split-order arrangements | Free; Pro from $129/year, one site | Confirm the precise modes and deposit setup in the current version |
| Addify Advanced Pre Order and Backorder | Pre-orders and backorders with role restrictions and manual pay-later | $129 for one year through WooCommerce Marketplace | Its documented pay-later flow sends a payment link |
| Pre-Orders for WooCommerce, by YoOhw Studio | Free product and variation availability management | Free | It does not provide its own deferred-payment collection system |
There is no single winner for every store. For automatic charging without an upfront payment, start with Woo’s extension and YITH’s supported integrations. For a deposit workflow on a modest license budget, Webkul deserves a closer look. For dates, notices and normal checkout payments, a free plugin may cover the requirement.
WooCommerce Pre-Orders, by Woo
WooCommerce Pre-Orders supports payment upfront or upon release, optional availability dates and manual or automatic release handling. It works with simple and variable products, and the current one-year plan costs $179.
Its most important restriction is in the documentation: an order can contain only one pre-order product and no other products. Adding a pre-order to a cart containing ordinary products empties that cart and adds the pre-order. Several different pre-order products require separate orders.
That can be a sensible arrangement for a store selling one major release. It is much less convenient for a retailer expecting customers to combine a new release with accessories or other upcoming products.
For charging upon release, supported gateway integrations can collect payment without the customer returning. The extension also has a Pay Later gateway that emails customers so they can complete payment manually.
The distinction should guide the purchase. If avoiding a second customer checkout is the reason for buying, confirm support for your exact gateway extension before committing. Having Stripe or another payment provider installed is not enough by itself; the extension and payment flow need to support the relevant integration.
I would put this on the shortlist for a clearly separated launch purchase. I would look closely at alternatives if combined baskets are central to the store.
YITH Pre-Order for WooCommerce
YITH Pre-Order for WooCommerce gives you a free entry point and a paid upgrade. The free WordPress.org version includes product-level pre-orders, availability dates, pre-order pricing and payment when the customer places the order.
Premium is currently listed at €139.99 with a year of updates and support. It adds broader controls, including manual pay-later and automatic charging through supported integrations. YITH identifies its Stripe, Stripe Connect and Braintree integrations for release-time charging. A deposit workflow is available through integration with the separate YITH Deposits / Down Payments plugin.
The free version is worth considering for a shop that wants to announce an item, display its expected availability and take the full payment now. You can evaluate the basic purchasing experience before deciding whether the more involved payment workflow is necessary.
For an existing YITH store, the integration route may be convenient. Work out the total cost of the required extensions, though. A pre-order license and an additional payment or deposit extension are separate parts of the budget.
Also decide what your customer should hear when a date changes. A reservation made for one launch date may still be valid after a delay, but the original confirmation is no longer enough communication.
Webkul WooCommerce Pre Order Plugin on WPBay
Webkul’s WooCommerce Pre Order Plugin is the one-time purchase in this comparison. The WPBay listing currently offers a one-site license for $39 and describes full or partial payments, variation-level scheduling, guest pre-orders and optional mixed-cart restrictions.
Its balance collection documentation is particularly relevant to deposit-based selling. It describes fixed or percentage deposits and automatic balance collection through the official WooCommerce Stripe Gateway when the product is restocked. The documented fallback for a failed charge is a payment link sent to the customer.
That makes it worth evaluating for a seller taking reservations on goods that are not ready to dispatch. A furniture shop, for example, could take a deposit while an item is being prepared and collect the balance when it becomes available.
Pay attention to shipping. The listing’s current changelog says full-payment pre-orders collect shipping at checkout, while partial-payment pre-orders defer shipping to the later balance payment. Check both examples against the delivery methods you use.
The $39 price makes Webkul attractive, but the decisive question is whether the complete deposit-to-balance order is clear to your customer and your team. Try the guest payment route as well as the logged-in route, and confirm your installed gateway matches the documented integration.
Bright Plugins Pre-Orders for WooCommerce
Pre-Orders for WooCommerce from Bright Plugins is interesting when the store needs more control over mixed baskets. Pro starts at $129 annually for one site.
The developer’s mode documentation describes arrangements for holding an order until everything is available, separating in-stock purchases from pre-orders, or separating individual pre-order products. Those are useful distinctions for a shop selling several releases with different dates.
However, its sales page and modes guide describe the mode choices differently. Confirm the behavior exposed by the current version or demo before buying for a particular splitting rule. The sales page also describes pay-later as an emailed payment link; do not assume that wording means a saved card will be charged automatically.
For a record store selling releases due on different Fridays, splitting by release could be more useful than a single order held until the last item arrives. It also means more orders to reconcile, more shipping decisions and potentially more customer emails.
Bright also markets deposit compatibility and sells a separate Deposits plugin. Ask which purchases are required for your intended combination rather than assuming every deposit arrangement is included in the pre-order license.
This is a candidate to investigate for fulfilment flexibility. Settle the exact order structure before judging the storefront presentation.
Addify Advanced Pre Order and Backorder
Advanced Pre Order and Backorder, by Addify, combines launch pre-orders with controls for backordered products. Its WooCommerce Marketplace price is $129 for a one-year plan.
Published capabilities include user-role restrictions, availability dates, adjusted pre-order pricing and controls to prevent different purchasing arrangements from sharing a cart. Those features make it relevant to stores where some customers should receive access before others.
The documentation explains the pay-later flow: customers receive an email containing a link to pay when the product is available. It also documents separate restrictions for mixing pre-orders with in-stock items and mixing pay-later purchases with paid purchases.
Consider a wholesale business offering an upcoming collection to approved trade accounts. Eligibility may be more important than a countdown display. You need to know who can reserve stock, what they will be charged and whether retail customers can see or purchase the same offer.
Addify is worth comparing for that kind of policy-driven setup. It is a less direct match if the central requirement is automatic card collection without a return visit, because the documented manual payment route does not establish that capability.
The price above uses the WooCommerce Marketplace listing. Compare the terms at the actual checkout if purchasing through another channel.
Pre-Orders for WooCommerce, by YoOhw Studio
Several products share almost the same name, so check the author. The free Pre-Orders for WooCommerce by YoOhw Studio adds an “On preorder” stock status, availability dates, variation support, quantity limits and customer notifications.
It also lets a customer record a delivery preference for a mixed cart, including in classic and block checkout. Its FAQ explicitly says payments remain with WooCommerce and the active payment gateways; the plugin is not a separate pre-order payment processor.
That is a useful boundary. If your requirement is to display a future availability date, accept the normal checkout payment and track the pre-order, you may not need to buy a more extensive billing system.
Recording “send available items separately” should still be checked against your actual fulfilment process. A saved customer preference does not, by itself, establish that orders, shipping charges or warehouse tasks will be split automatically.
The free plugin is worth trying on a representative product and variation before paying for features you may not use. If the business later needs deposits or automatic release-time charges, reassess the payment system deliberately.
Also look beyond the product page when evaluating it. The useful result is an order your team recognizes as delayed, with enough information to handle the customer’s request correctly.
A pre-order is not the same as a backorder
A backorder usually concerns an established product that is temporarily unavailable. A pre-order often concerns a product that has not launched yet. A store can use both, but the customer expectations may differ.
Someone replacing a familiar part may accept an estimated replenishment date. Someone ordering a limited release may expect a place in a particular production batch. Your stock settings and wording need to match that promise.
Native WooCommerce backorders may be sufficient for a basic replenishment situation. They should not be treated as evidence that a launch has a complete deposit, notification and release workflow.
A waitlist is different again. An email address requesting a restock notification is an expression of interest. It is not a paid order or necessarily a reservation of inventory.
Keep those categories separate when estimating demand. Two hundred subscribers, two hundred unpaid reservations and two hundred paid purchases give you different information about what to produce.
Mixed carts can decide which plugin you need
Imagine a customer buys a £25 accessory that is ready now and a £150 product expected next month.
If you hold the entire order, the accessory waits too. That can be acceptable when explained clearly before payment. It becomes a support problem when the customer reasonably expects the accessory this week.
If you create separate orders, decide how shipping is charged. Free shipping earned by the original basket may need a defined policy after splitting. Discounts should also produce a total your team can reconcile without guessing.
Now add another pre-order with a later date. An extension that separates “available now” from “pre-order” may still leave both future products together. If the customer expects each release separately, that distinction needs to appear in the chosen workflow.
Start from the shipment you intend to send. Then follow the order records, payment records and customer messages that are supposed to produce it. “Supports mixed carts” is too broad a phrase to settle those decisions.
For stores whose customers commonly build combined baskets, this issue can outweigh a substantial difference in plugin price.
Check the balance calculation with a real example
Suppose an item costs $240 and the customer pays a 25% deposit. The product deposit is $60, leaving $180 of the product price unpaid. Shipping and tax still need their own treatment under the store’s configuration.
Change the quantity to two. Confirm whether the deposit scales correctly, how the remaining amount is shown and which payment includes shipping. Apply one of your normal coupons and inspect the result again.
Then complete the balance payment. The combined records should let you understand what the customer paid without accidentally counting the same product value twice in an export or report.
A later catalog price change deserves attention as well. The customer placed an order at an agreed price. Check how your chosen plugin preserves that agreement and what happens if the product is on sale when the final payment is requested.
These examples are acceptance checks for your store, not a promise that all six plugins implement deposits. Use them only for the payment arrangement you intend to offer.
Automatic charging also needs a failure route. Stripe’s save-and-reuse documentation distinguishes saving a payment method for a future transaction from taking a payment now and describes the agreement needed for later use. Choose a supported integration that handles that setup; adding a card field to a form is not a substitute.
Rehearse release day before advertising a date
A release date should not be the first time you find out what the plugin does to an order.
Create a small set of test purchases using the payment provider’s test mode. Let the date pass, release another product manually, and move a third product’s date later. Inspect the customer messages and the order states after each change.
For automatic tasks, check how your site runs scheduled work. The WordPress Cron handbook explains that default WP-Cron is triggered by page loads. If a plugin relies on that mechanism, a quiet site may not process the task at the exact clock time shown on the product page. Ask your host about reliable scheduling when timing matters.
Keep payment and fulfilment separate during the rehearsal. Making a product available should not tell the packing team that an unpaid order is ready to ship. Equally, a fully paid order should remain identifiable while it is waiting for stock.
Try a declined balance payment and a customer cancellation. Confirm whether cancelling a paid pre-order also initiates a refund or whether someone must do that separately. Do not infer a refund from the order-status label.
Finally, use the actual product template and checkout on your store. A custom add-to-cart form, block checkout or express payment route can expose a different path from the developer’s demo. Test the route customers will use.
What customers need to see
Clear pre-order wording can prevent more support tickets than a dramatic countdown.
Show the expected availability near the purchasing controls. Explain whether payment is taken now, later through a link, or automatically through the supported setup. If the amount is a deposit, display the remaining obligation clearly.
Use a dispatch estimate carefully. “Available on December 10” does not necessarily mean “delivered on December 10.” Production, packing and transit still take time.
When a supplier changes the date, update affected buyers as well as the product page. Someone who ordered last month should not have to revisit the catalog to discover that the schedule moved.
The confirmation email should give the customer something useful to keep: the product, the agreed amount, the payment arrangement and the expected timing. Your support team should be able to find the same information on the order.
Frequently asked questions
Does WooCommerce include pre-orders?
WooCommerce supports backorders, but a dedicated extension is useful when you need a defined pre-order state, release notices or a particular deferred-payment workflow. Choose according to the process you are promising the customer.
What is a good free WooCommerce pre-order plugin?
YITH offers a free version for taking upfront pre-orders. YoOhw Studio’s free plugin is worth considering for availability dates, variations and order notices while retaining WooCommerce’s normal payment handling. Test the one that matches your product type and checkout.
Can a WooCommerce pre-order plugin take a deposit?
Some can, either directly or through another extension. Webkul documents partial payments and balance collection. YITH documents a separate Deposits / Down Payments integration. Check the complete license requirement and shipping calculation.
Can customers be charged automatically when stock arrives?
Yes, with a supported plugin and gateway combination. Check the exact integration, how the customer authorizes later payment and what happens if collection fails. A release email containing a payment link is a manual payment flow.
Is there a one-time purchase option?
Webkul’s WooCommerce Pre Order Plugin is currently listed on WPBay at $39 for one site as a one-time purchase. Check the current listing and its support terms before ordering.
Which one would we choose?
For a single launch where the pre-order is purchased separately, Woo’s extension is a sensible place to begin. YITH offers a free route for upfront orders and paid integrations for more involved payment arrangements.
Webkul is worth a close look when deposits and a one-time license matter. Bright deserves consideration when splitting orders is central to the store, while Addify suits shops that need role restrictions alongside pre-order and backorder controls. YoOhw provides a free option for stores that mainly need dates, notices and product-level tracking.
Before buying, finish one representative order in a staging store, including release and any final payment. The right plugin is the one that leaves the customer informed and the order ready for your team to fulfil.
