Skip to content

FAQ

Yes. WooCommerce must be installed and active. If it is missing, Rezervo stays inactive and shows an admin notice instead of registering anything.

What happens when a product is marked as a pre-order?

Section titled “What happens when a product is marked as a pre-order?”

With the global toggle on, the product stays purchasable while its stock status is out of stock, its add-to-cart label changes to your configured button text, a reservation stub appears in the product summary, and the cart and order lines are flagged Pre-order: Yes.

Do I have to set a stock figure or use backorders?

Section titled “Do I have to set a stock figure or use backorders?”

No. The pre-order flag handles purchasability on its own, it filters WooCommerce’s purchasability, in-stock and backorder checks so the product stays buyable while out of stock. You do not fake stock or enable WooCommerce backorders. The product does need a price, though: a priceless product is left non-purchasable.

Yes, one: Expected release date on Product data > General, next to the Pre-order checkbox (product meta _preorder_release_date). It is optional. When it is set, the reservation stub adds an “Expected release: ” line under its fixed wording, formatted with your site’s date format; when it is empty, the stub shows the fixed wording only.

There is no “show release date” setting to switch that line on or off, and the date is not carried into the cart or onto the order line, it is shown on the product page.

Can each product have its own button text?

Section titled “Can each product have its own button text?”

No. The add-to-cart label is a single store-wide value, Default button text under WooCommerce > Pre-orders. There is no per-product override for the label. The per-product controls are the Pre-order checkbox and the optional Expected release date.

Can I pause pre-orders without editing every product?

Section titled “Can I pause pre-orders without editing every product?”

Yes. Turn off Enable pre-orders under WooCommerce > Pre-orders. Rezervo then registers none of its storefront hooks, so every flagged product behaves like a normal product. The per-product flags are preserved while paused, so turning it back on restores them all.

How do I end a pre-order when stock arrives?

Section titled “How do I end a pre-order when stock arrives?”

Set the product back to In stock, and untick Pre-order if you want the relabeled button and the reservation stub gone. It returns to normal stock-managed behaviour. Order lines already placed keep their Pre-order: Yes meta for fulfilment.

The cart and order flag is set against whichever product or variation is added to the cart, so a purchased variation of a pre-order product is still flagged on the order line. The relabeled button and reservation stub are driven by the single-product hooks reading the main product object, test your theme’s variable-product layout before relying on the stub showing for a specific variation.

Is it compatible with HPOS and the block cart/checkout?

Section titled “Is it compatible with HPOS and the block cart/checkout?”

Yes. Rezervo declares compatibility with WooCommerce HPOS (custom_order_tables) and cart_checkout_blocks. The Pre-order: Yes row shows in both the classic cart and the Cart/Checkout Blocks, and the order item meta is stored under HPOS.

Yes, with CSS. The stub reads its colours from --preorder-* custom properties (such as --preorder-accent, --preorder-surface, --preorder-text-color), each with a fallback. Set them on .preorder-stub from your theme. It ships a dark-scheme variant and respects prefers-reduced-motion. There is no theme template to copy, the stub is rendered directly by the plugin, not from a template file.

Three, all prefixed preorder/:

  • preorder/is_preorder (bool $enabled, WC_Product $product), the resolved pre-order flag for a product or variation, after parent inheritance.
  • preorder/release_date (string $date, WC_Product $product), the resolved release date in Y-m-d, or an empty string.
  • preorder/booted (action, passes the plugin instance), the extension point Rezervo Pro boots on.

There is no filter for the stub text or the button label. The label goes through WooCommerce’s own woocommerce_product_*_add_to_cart_text filters, which you can target with standard WooCommerce techniques, and restyling is done through the CSS custom properties above.

No. Everything runs on your own site against your own WooCommerce products. No data leaves the site.

Delete the plugin from the Plugins screen. Uninstall removes the preorder_settings and preorder_db_version options. Rezervo creates no custom database tables. The per-product _preorder_enabled and _preorder_release_date meta are intentionally left in place as product content; remove them manually if you want them gone.

Rezervo Pro is available and boots through Rezervo’s internal extension point. It adds incentive discounts, deposits, per-variation pre-orders and release emails; the free plugin documented here is complete on its own.