Prestashop Request Info (GDPR Compatible) is a commercial module that adds an enquiry form to selected product pages in a PrestaShop store, letting shoppers ask about availability, specifications or a possible discount without leaving the catalogue. It is aimed at store owners who sell items that need a conversation before purchase — made-to-order goods, high-ticket products, or anything that regularly runs out of stock. The module costs $34 on ThemeForest and is sold by the developer behind the PrestaShop Store Argentina demo shop.
What Prestashop Request Info (GDPR Compatible) Plugins actually add to a product page
The core mechanic is simple: a button appears on the product page, and clicking it opens a form the shopper fills in to send a message to the store. The interesting part is how tightly the vendor lets a merchant control where that button shows up.
- Category-level targeting. The form can be switched on for chosen categories only, so a store can offer enquiries on furniture or custom printing while leaving fast-moving accessories on a straight add-to-cart flow.
- Product-level targeting by ID. Individual products can be added by their numeric ID, which is useful when one or two items need an enquiry route but their whole category does not.
- Out-of-stock triggering. The button can be configured to appear specifically on products with no stock, turning a dead end into a lead. That is the single most commercially useful setting in the module.
- Captcha protection. A captcha challenge sits in front of the form to cut down automated submissions, which matters because enquiry forms are a common spam target.
- PrestaShop’s own mail system. Submissions are sent through the platform’s existing mail configuration rather than a separate SMTP setup, so there is no second delivery pipeline to maintain.
- Messages stored in the support system. Rather than relying on email alone, enquiries can be saved into PrestaShop’s customer service (ticket) area, giving staff a record they can reply to from the back office.
- GDPR consent via a CMS page. A CMS page can be selected so the form links to the store’s privacy notice, which is the mechanism the vendor uses to support consent requirements under the EU data protection rules.
- Multilingual and multistore support. Stores running several languages or several shop instances under one installation can use the module across them.
- Theme independence and cross-browser behaviour. The vendor states compatibility with any theme and across browsers, which in practice means the form inherits the store’s styling rather than shipping its own fixed design.
Where this module fits, and where it does not
The clearest fit is a catalogue where price or availability depends on a conversation. Think custom-manufactured parts, wholesale enquiries with tiered pricing, furniture with configurable finishes, or machinery where the buyer needs a specification sheet before committing. In those cases a request-info button captures intent that would otherwise bounce to a competitor.
A second strong fit is the out-of-stock scenario. Most stores either hide sold-out products or leave them visible with a disabled cart button. Routing that traffic into an enquiry — “tell me when this is back” or “can you source it” — recovers demand that would otherwise be lost, and the vendor’s filter makes this a per-product decision rather than an all-or-nothing switch.
Agencies building PrestaShop sites for clients in the EU should also note the GDPR angle. Having a consent link wired into the form from the start saves a retrofit later, and the ticket-system storage gives the client an auditable record of what was submitted and when.
The wrong choice is a store that already runs a full customer service or CRM stack. If enquiries need to land in Zendesk, HubSpot or a helpdesk with SLA tracking, this module’s native ticket storage is a side channel rather than an integration, and the store would be better served by a form tool that connects to those systems directly. It is also a poor fit for stores that want a full quote builder with line items, calculated pricing or PDF output — this is an enquiry form, not a quotation engine.
Setting up Prestashop Request Info (GDPR Compatible) Plugins in practice
Installation follows the standard PrestaShop module route: upload the archive through the back office module manager and install it. The vendor lists compatibility with PrestaShop 1.7 through 1.7.8 across versions 3.0 to 4.2 of the module, so a store still on the 1.6 branch should confirm support before buying — the listing does not claim it.
Configuration is a short sequence. The merchant picks the categories where the button should appear, optionally adds specific product IDs, decides whether out-of-stock products should trigger it, enables the captcha, and selects the CMS page that carries the privacy text. Because delivery uses PrestaShop’s existing mail settings, there is no separate mail server to configure, provided transactional email already works on the store.
Realistically this is a thirty-to-sixty-minute job for someone comfortable in a PrestaShop back office, most of which is spent deciding which categories should carry the button and writing the privacy page it links to. The form itself is unstyled by design, so a small amount of CSS work may be needed to make the button match the theme’s typography and colour.
Strengths and limitations
Strengths
- Granular placement rules — categories, individual product IDs and out-of-stock status — give real control over where enquiries are invited.
- Enquiries are stored as support tickets, so there is a record in the back office rather than only an email in someone’s inbox.
- GDPR consent handled through a selectable CMS page, which is a workable approach for EU-facing stores.
- Captcha included, reducing the spam load that enquiry forms typically attract.
- Multilingual and multistore support built in, which matters for cross-border PrestaShop installations.
- Low one-off price relative to custom development of the same feature.
Limitations
- No visible sales history or rating on the listing, so there is no independent buyer feedback to weigh before purchase.
- Compatibility is stated for PrestaShop 1.7.x only; stores on 1.6 or on the 8.x branch are not covered by the vendor’s stated support.
- The form is a plain enquiry form — no configurable fields, no file upload for reference documents, no quote calculation.
- GDPR support is limited to linking a CMS page; the module does not provide consent logging, data export or automated retention rules.
- Styling is inherited from the theme, so matching a heavily customised design may require CSS work the vendor does not supply.
- No integration with external helpdesk or CRM tools is described.
How Prestashop Request Info (GDPR Compatible) Plugins compare with the wider category
Product enquiry tools sit in a crowded space alongside general form builders, dedicated quote-request extensions and the contact features bundled into larger e-commerce add-on suites. The general-purpose form builders win on flexibility: they can create any form, place it anywhere, and connect to dozens of external services. What they typically lack is native awareness of PrestaShop’s catalogue — knowing which category a product belongs to, whether it is in stock, and which product ID the enquiry refers to.
This module’s advantage is exactly that native awareness. The category filter, the product-ID filter and the out-of-stock trigger are not things a generic form plugin does without custom work, and storing submissions as PrestaShop support tickets keeps everything inside one back office. Against larger add-on suites, it is narrower but cheaper and lighter — no bundled features the store will never switch on.
The trade-off is depth. A dedicated quote-request extension with configurable fields and pricing logic will beat this module for stores that need structured quotations. For straightforward “ask about this product” enquiries, the extra capability is usually overhead.
Frequently Asked Questions
Is Prestashop Request Info (GDPR Compatible) compatible with PrestaShop 8?
The vendor only states compatibility with PrestaShop 1.7 through 1.7.8. No claim is made for the 8.x branch, so stores on a newer version should test on a staging copy or ask the developer directly before buying. Running it untested on an unsupported version risks layout or mail-delivery problems.
Does the module send enquiries to email or save them in the back office?
It does both. Messages are delivered through PrestaShop’s own mail system, and they are also recorded in the platform’s customer service ticket area. That dual approach means staff can reply from the back office and keep a history, rather than depending on an inbox that may lose or misfile messages.
Can the enquiry button be limited to products that are out of stock?
Yes. One of the module’s settings restricts the button to products with no stock, which turns a sold-out page into a lead-capture opportunity. Stores can combine this with category filters or specific product IDs, so the rule applies only where the merchant wants it.
How does the module handle GDPR consent?
It lets the merchant select a CMS page containing the store’s privacy notice, which the form links to. That satisfies the notice requirement, but the module does not add consent logging, data export tools or automatic deletion. Stores with strict data-retention obligations will need to manage those processes separately.
Verdict
This module earns its place in a PrestaShop store that sells products requiring a conversation before purchase, or that regularly runs items out of stock and wants to capture that demand. The category, product-ID and stock filters are the reason to choose it over a generic form plugin, and the ticket storage keeps enquiries inside the platform. Stores on PrestaShop 1.6 or 8.x should look elsewhere until support is confirmed, and businesses needing structured quotes, CRM sync or formal consent records will find it too thin. At $34 it is a low-risk addition for the right catalogue, provided expectations stay at “simple enquiry form” rather than “sales workflow”.
