WooCommerce "This Product Cannot Be Purchased"? Causes & Fix

A customer gets to checkout and WooCommerce refuses with "Sorry, this product cannot be purchased." The cart looked fine; the sale dies at the last step. Nearly always it's one of two things — no price, or the product isn't actually published. Here's how to tell which.

Last updated: 16 Jul 2026 · ~6 min read

What "cannot be purchased" actually means

Before creating an order, WooCommerce re-checks every item in the cart against one question: is this product purchasable? An item passes only if it still exists, it's published, and it has a price. Fail any of those and checkout stops with this notice — no order, no charge. It's a guard rail, not a bug: WooCommerce would rather block the sale than take money for something with no price.

The catch is what customers see: an item sitting happily in the cart, then a hard stop at checkout. Products can be added to a cart and only fail this check later — which is why an edit you made this morning surfaces as a checkout failure this afternoon.

The most common causes (most likely first)

1. The product or variation has no price setThe Regular price field is empty. On a variable product, check the individual variation, not just the parent — a variation with a blank price inherits nothing and can't be bought. Often the product page shows no price at all, or a price range that's missing one end. The #1 cause.
2. The product reverted to Draft or PendingYou can add it to the cart and check out as admin, but customers can't — WooCommerce allows an unpublished product for users who can edit it. So the perfect test is a private window: if the product page 404s when logged out, that's your answer. Usually follows an edit where Save draft was clicked instead of Update, or a scheduled post that never published.
3. The specific variation is disabled or priced only on the parentThe parent product is published and priced, but this one variation isn't enabled, or its own price field is blank. The customer picks that exact combination and only that combination fails. Reproduce by selecting the same options the customer did.
4. A plugin is filtering the product out of being purchasablePrice is set, status is Published, and it still refuses. A wholesale, membership, role-based-pricing, catalog-mode or multi-currency plugin can declare a product unpurchasable — commonly for one user role, or when no price exists for the currently selected currency. Tell: it fails for some customers and not others, or only in one currency.
5. The item was trashed or deleted while sitting in a cartThe product no longer exists but an old session still holds it, so checkout can never validate it. Almost always an old cart rather than a live one — emptying the cart and re-adding fixes it instantly, and no current product page is affected.

Where to look first

• Find out which item it is. If more than one product is in the cart, remove them one at a time and retry checkout — the notice doesn't name the item, so this is the fastest way to isolate it.
• Open that product and look at the price. Empty Regular price? That's cause 1 — set one and retest. Remember 0 counts as a price; blank does not.
• Check the status pill and test logged out. Draft or Pending is cause 2. If it says Published, load the product URL in a private window — a 404 there while it works for you means it isn't really public.
• Variable product? Check the exact variation. Under the product's Variations, confirm the one the customer chose is enabled and has its own price (cause 3).
• Priced and published and still blocked? Deactivate wholesale, membership, catalog-mode or currency plugins one at a time and retest as a guest (cause 4). Empty and rebuild the cart first to rule out cause 5.

How to know you fixed it

Frequently asked