FAQ

Does Enquire require WooCommerce?

Yes. The button is hooked to a WooCommerce product-page action and the email uses WooCommerce product data. With WooCommerce inactive, Enquire shows an admin notice and registers nothing else.

Where are enquiries stored?

Nowhere. Each enquiry is emailed and nothing is written to your database, there is no enquiry table and no admin log. The email in your inbox is the record. Enquire keeps only two options, enquire_settings and enquire_db_version, both deleted when you remove the plugin.

Where do enquiries get sent?

To the Recipient email you set under WooCommerce → Enquire. Leave it empty and your site’s admin email is used. The shopper’s address is set as the Reply-To, so a reply from your inbox reaches them directly.

Can I move the button somewhere else on the product page?

Not from the settings. The button is fixed on the woocommerce_after_add_to_cart_form hook, directly under add to cart. There is no placement setting and no shortcode in the free edition.

How is spam handled?

Three layers, all on by default and not configurable: a nonce, a hidden honeypot field (a filled honeypot is silently dropped, the bot still sees “success”), and a 30-second per-visitor rate limit keyed by user ID or hashed IP. No CAPTCHA, so genuine shoppers see no friction.

My test enquiry never arrived. What now?

Enquire sends with wp_mail(), so delivery depends on your site’s mail setup. If the on-screen submit shows success but no email arrives, the issue is delivery, not Enquire. Confirm the Recipient email (or admin email) is correct, then install and configure an SMTP plugin so wp_mail() delivers reliably, and test again. Also check that you waited the 30-second rate-limit window between test submits.

Can I choose which fields are required?

Yes, name, email and message each have their own Require toggle, all on by default. One rule is not optional: an entered email must be a valid format even when Require email is off. Leaving email optional means a shopper can send without one, but you then have no Reply-To to answer.

Can I change the email subject?

Yes. The Email subject setting accepts the token {product}, which is replaced with the product name. The default is Product enquiry: {product}.

Is the form accessible?

Yes. It is a native <dialog> opened with showModal(), labelled by its title, with focus moved in on open and returned to the trigger on close. Escape and a backdrop click close it. Every field has a real label, required fields carry the required attribute, results are announced in an aria-live region, and the open animation is skipped under prefers-reduced-motion. Built with WCAG 2.2 AA in mind.

Does the button slow down my site?

No. The small CSS and one defer JavaScript file (no jQuery) load only on single product pages, and only while enquiries are enabled. Every other page is untouched.

Is there a hook for developers?

Yes, the enquire/enquiry_sent action fires after an enquiry is emailed successfully, passing the WC_Product and the sanitised submission. See the developer hook. There are no merchant-facing filters in the free edition.

Is there a Pro edition?

An Enquire Pro is planned for enquiry logging in wp-admin, file attachments, shopper auto-replies (built on enquire/enquiry_sent) and per-product recipients. The free edition is the complete enquiry-sending product, not a trial.