Price on Request for WooCommerce

Taking the text that says $25.00 off a product page is the easy half of hiding a price. The same number is printed in shop grids and search results, read by the product blocks, handed to the script that runs variable products, written into the structured data search engines read, and returned by the Store API that every block on your site asks. A shopper who knows a product's link can also try to add it to a cart without ever seeing the price.

This takes the price and the buy button off the products you choose, puts your own wording in their place, such as Price on request, and lets the shopper ask: a short enquiry form on the product page, or one plain button that opens a link, calls a number or writes an email. It then closes each of those other routes. It was tested on real WooCommerce as a visitor fetching the pages, with order storage on and off, rather than by looking at one page.

You choose who is not shown prices: every product in the shop, only the products you tick on their own screens, whole categories or tags with their sub-categories, visitors who are not logged in, or products that are out of stock. Shop managers see what visitors see unless Pro's preview mode is on, so what you check is what customers get.

The enquiry form asks for a name, an email address, a phone number if the shopper wants to give one, and a message, with the product already filled in, and a consent box the shopper must tick. The wording they agreed to is kept with their enquiry. You are emailed each enquiry, the shopper can be sent a confirmation, and every enquiry is kept on a Price enquiries screen under WooCommerce with a status and private notes your team can see and the shopper cannot. The form carries nothing that can expire inside a cached page, so it works behind a page cache. A hidden trap for robots, a limit on how many enquiries one connection can send in an hour and a cap on the size of every field make misuse harder, and none of them is a promise that no unwanted enquiry gets through. WordPress's own tools for exporting and erasing personal data work with the enquiries, and old enquiries can be deleted after a number of days you choose.

Where a price is hidden, a direct request to buy is refused too. The add to cart link, the AJAX button and the Store API all say no, a hidden product that is already in a cart is taken out of it, and both the classic checkout and the block checkout refuse an order that holds one. Sorting by price and price filters are withheld from anyone who has something hidden.

Pro decides when to hide. Its rules are read from the top and look at the customer's role, country, logged-in state, a product attribute, stock status, cart value or the time, and each rule can bring its own wording and its own button, including one that sends the visitor to log in and brings them back to the product. A list of approved customers is shown prices that stay hidden from everyone else, and an enquiry you set to Approved shows the person who asked the price once they sign in with the email address they used. Pro can switch the price off for one variation of a variable product, lets shop managers see the real prices in preview mode while visitors do not, moves your rules in and out of a spreadsheet as a CSV file, lets you write the enquiry emails in your own words, and sends you a reminder when an enquiry has waited too long.

What it cannot reach, so you know before you rely on it: a theme or plugin that reads a product's stored price itself and prints it somewhere else, an SEO or product-feed plugin that writes its own price tags, and a page cache that kept a page from before you hid the price. Clear your cache after changing a rule. The Store API will still say which products are on sale, though never what they cost. The prices that WooCommerce's management API gives a signed-in shop manager are left alone on purpose, because that is how your own tools read the real prices. If the separate PluginCity Quote List for WooCommerce plugin is active, Pro can show its Request a quote button instead of this form, but that hand-over is a pair of filters that has not yet been tried against a released copy of that plugin. An express payment button that builds its own order without using the cart has not been tried either.

It runs on your own website. Enquiries are kept on your own site, and Pro contacts PluginCity for its licence and its updates, and for nothing else.

If a Pro licence lapses, nothing is deleted and nothing breaks. Your rules, your approved customers and your email wording stay saved and stay on the screen you set them on, where you can read them but not change them, and prices go back to being hidden or shown by the shop's main settings alone. That is the safe way round: a price is never shown that those settings would have hidden. The licence screen lists exactly what is being left as it is, and renewing switches it all back on as you left it.