Best Magento 2 Hide Price Extensions Compared in 2026
If your Magento 2 store needs to hide prices — for B2B wholesale, dealer-only pricing, regional restrictions, or quote-first checkout — you'll find a dozen extensions that do the job. This guide compares the four most-installed paid hide price extensions in 2026 across the things that actually matter: how they handle customer-group rules, what replaces the "Add to Cart" button, how flexible the built-in quote form is, Hyvä support, API coverage, and total stack cost.
Short answer: Every major vendor in 2026 includes Hyvä support, and most offer some form of "collect a lead" pop-up. The differences show up in how flexible the built-in form is, whether you need a second extension from the same vendor for a full RFQ workflow, and whether the Hyvä layer is a retrofit compatibility module or a native CSP-ready port.
Why This Comparison Exists
Hiding prices isn't one feature — it's a pricing strategy with several implementation paths. Some merchants just want to hide prices from guests and show them after login. Others need granular per-customer-group rules, per-category overrides, and a customizable quote form where a disabled "Add to Cart" button used to be. What looks like the same feature on vendor pages can mean three different workflows under the hood.
The goal here is to help you pick without reading four long product pages. We've installed and tested all four on Magento 2.4.6 / 2.4.7 across Luma, Breeze, and Hyvä (including Hyvä Checkout with strict CSP).
The Four Extensions at a Glance
Vendor pricing fluctuates with discount campaigns; figures reflect public rate cards at the time of writing. Always confirm on the vendor's product page.
Pricing for a Complete "Hide Price + Collect Lead" Workflow
The sticker price only tells half the story. If you want the common B2B flow — price hidden, customer clicks a button, fills a form, you reply with a quote — you need a form tied to the hide-price logic. All four vendors support this, but through different extension counts:
- Hide price + custom quote form in one
- Custom form fields + reCAPTCHA
- Hyvä native + Breeze native + Luma
- GraphQL + REST API
- Hide Price + pop-up form built in
- Fixed field set for lead capture
- Hyvä compat module
- Richer RFQ workflow needs Request a Quote add-on
- Hide Price (basic) ~$79 — no form, custom button text + URL
- Call for Price ~$149 — includes form
- Hyvä support free
- Hide Price ~$249 — button replacement, no form
- Cart to Quote ~$249 — adds RFQ form
- Hyvä compat included
The takeaway: BSS Commerce's Call for Price and HidePrice Pro both pack hide-price + form into one extension at similar entry prices. Amasty's Hide Price includes a simpler pop-up but extends into a full RFQ only with a second extension. Aheadworks' combined stack is the priciest option and targets enterprise workflows with approval chains and wish-list-based RFQ pipelines.
Customer Group & Guest Rules
All four extensions let you pick which customer groups see prices. The differences are in how rules compose and how specific you can get.
Rule patterns common to all four
- Global rule — "hide all prices for Not Logged In" — the single most common B2B use case. All four extensions support this.
- Per-group + per-category override — "hide for Guests, hide for Retail, show for Wholesale on categories X & Y". All four handle this, though the admin UI and rule-composition ergonomics vary — test each on a sample configuration.
- Per-product override — "this specific SKU is hidden even for Wholesale" — supported across all four via product attribute. Mass-action / quick-edit exposure varies by vendor; check each admin UI.
- Conditional rules — "hide if cart subtotal < $500" or "hide in country X" — depth of condition support varies by vendor; check documentation for the specific conditions you need.
What Replaces the "Add to Cart" Button
This is where the four approaches actually diverge. When the price is hidden, "Add to Cart" has to be replaced with something else — and that choice affects your lead flow.
HidePrice Pro
Three modes: (1) Login to see price — button becomes a login link; (2) Request a quote — button opens a configurable form with custom fields, CAPTCHA, and admin-side status tracking; (3) Custom message — any static HTML. The form and rule engine live in the same extension — no second module needed.
Amasty Hide Price
Button can be replaced with a message, a login link, or a pop-up lead-capture form. The pop-up collects customer data with a fixed-field set — good for quick lead capture, less flexible if you need VAT ID, attachments, or conditional questions. For a richer RFQ workflow, Amasty sells a separate Request a Quote extension.
BSS Commerce
The base Hide Price module replaces the button with text + a link (often pointed at a CMS page). If you want a form behind the button, BSS's Call for Price is a separate 2-in-1 product that combines hide-price with a built-in "ask for price" form. Two different extensions, pick one depending on needs.
Aheadworks
Replaces the button with text or a link and supports rich conditional rules. For a quote form, Aheadworks' Cart to Quote extension integrates tightly with Hide Price — it adds RFQ to the cart and supports wish-list workflows. The combined price is the highest in this comparison, but the toolkit is enterprise-grade.
How Deep Is the Built-in Form?
Two vendors — MageMe and Amasty — include a form inside the hide-price extension itself. Two others — BSS (Call for Price variant) and Aheadworks (Cart to Quote companion) — sell the form logic inside a separate module. The better question isn't "is it built-in?" — it's "how flexible is the form when you actually need to capture a B2B quote?"
Where HidePrice Pro's form goes further:
- Custom fields you can add — on top of the base contact fields, add extra inputs such as company, VAT ID, phone, address, textarea, file attachment, date picker, or checkbox group, depending on what your quote workflow needs.
- reCAPTCHA integration — reCAPTCHA v2 and v3 supported on the form out of the box.
- Admin quote grid with statuses — new / in-review / replied / closed, with filters and CSV export.
- Configurable email templates — customer confirmation, admin notification, and a follow-up template with a checkout link.
- GraphQL schema — the form submission flows through GraphQL, which matters if your frontend is PWA or headless.
Amasty's pop-up is a good fit if you want a quick lead-capture on hidden-price products and you don't need custom fields or a quote grid. BSS's Call for Price is closest to HidePrice Pro on functionality and price. Aheadworks' Cart to Quote is the most feature-rich of the "companion module" options — if you need multi-step approvals and wish-list-based RFQs, it's the natural pick.
For stores that already know they'll outgrow a simple ask-for-price form — multi-region pricing, approval workflows, cart-to-quote conversion — it's worth looking at a dedicated B2B quote management product. MageMe ships EasyQuote for exactly this scenario; HidePrice Pro's built-in form handles the common "one-step quote request" case, while EasyQuote handles ongoing RFQ pipelines.
Theme Compatibility: Hyvä, Breeze, Luma
Theme compatibility is the feature most comparison pages oversimplify. "Hyvä compatible" can mean a native Hyvä port or a compatibility layer that retrofits the Luma-era code to render inside Hyvä. Both technically work; they behave very differently under strict Content Security Policy.
- HidePrice Pro
- Native Hyvä implementation, CSP-compliant out of the box (no
unsafe-inline). Native Breeze and Luma templates ship in the same package. No separate license, no manual theme porting. Tested on Hyvä Checkout with strict CSP enabled. - Amasty
- Hyvä support via a compatibility module listed in Hyvä's official compatibility registry — free with the main extension. Check Hyvä's compatibility registry for the current version. Breeze support is not listed by the vendor.
- BSS Commerce
- "Compatible with Hyvä Theme, free support with your Hyvä theme version" — vendor statement. Installation involves two Composer packages (
bsscommerce/fast-orderandhyva-themes/magento2-compat-module-fallback). Breeze support isn't officially listed. - Aheadworks
- Hyvä compatibility included with the main extension for most of their B2B bundle. Check the vendor's current Hyvä compatibility documentation for the exact installation path and any theme-specific notes.
For Hyvä stores running strict CSP (the default for Hyvä 1.3+ and required for Adobe Commerce Cloud), HidePrice Pro's native port tends to drop in without CSP workarounds. The other three work too — just plan for a short CSP audit after install.
Related reading: Hyvä official site · Case study: migrating EasyQuote to strict CSP.
API & Headless-Ready Support
If you run a PWA storefront, a composable commerce frontend (React, Vue, Nuxt, Next.js), or a mobile app, your hide-price rules need to surface through the store API — otherwise the frontend can't know which products to hide.
HidePrice Pro exposes hide-price state and the quote-form submission through GraphQL in addition to REST, which is useful for headless setups where price visibility and the "ask for quote" button need to render client-side. Other vendors in this comparison expose hide-price state through REST; check each vendor's API documentation for their current GraphQL coverage before committing to a headless architecture.
Which Extension Should You Actually Pick?
Four scenarios. Match your situation to one:
You need a quote form built into the hide-price extension, you run Hyvä (especially with strict CSP), or you need hide-price state exposed through GraphQL for a headless frontend. Best price/feature ratio for most mid-market B2B stores when you want one extension, not two.
You already run other Amasty extensions and want a pop-up lead-capture form with a fixed set of fields. Good fit for stores where the "ask for price" step is a low-friction contact form, not a multi-step RFQ.
Budget is tight and your only need is hiding prices from guests with custom button text or a redirect link — Hide Price at ~$79. If you want a form, BSS's Call for Price (~$149) is the 2-in-1 version and a reasonable alternative to HidePrice Pro.
You're on Adobe Commerce / Cloud, run heavy B2B workflows with approval chains and wish-list RFQs, and budget isn't the main constraint. The best choice if your RFQ pipeline involves multiple approvers.
Switching From Another Extension
Switching between hide-price extensions is usually a two-step migration: export rules from the current extension, map columns to the target extension's schema, re-import. Product-level flags (per-product "hide" attributes) move easily via Magento's native product import. Global rules and customer-group logic may need a short custom script if the two extensions model conditions differently.
For an active quote queue, plan a short data-migration project separately — submitted quotes are usually stored in vendor-specific admin tables and don't transfer automatically. Budget half a day to a day of developer time for a typical catalog; more if you have thousands of per-product overrides or customer groups tied to region-specific rules.
Frequently asked questions
Free GitHub hide-price modules — such as DanielRiezebos/MAGENTO-2-HIDE-PRICE — can work for the simplest case: hide price from guests, show a static message. They typically lack an admin UI for rule composition, customer-group logic, and per-category overrides, and most aren't actively maintained. If your needs are limited to "hide everything from guests until they log in", a free module is a reasonable starting point. If you need per-group, per-category, or quote-form logic, a paid extension saves its cost in the first day of setup.
It depends on how rich your quote workflow needs to be. If "replace Add to Cart with a lead-capture pop-up" is enough, one extension is usually sufficient. If you need multi-step RFQ, approvals, wish-list-based quoting, or cart-to-quote conversion, pair hide-price with a dedicated B2B quote extension. Check each vendor's product lineup to see whether the quote module is bundled or sold separately.
Not inherently. Product pages stay indexable as long as the page markup is crawlable HTML. Two practical points: (1) exclude hidden-price products from Google Shopping feeds — Shopping requires a price and Add-to-Cart availability; use Magento's visibility flags or feed-level rules. (2) Make sure whatever replaces the "Add to Cart" button renders in server-side HTML rather than being injected by JavaScript alone, so Google can see the replacement CTA and the page's intent.
Per-store and per-website scoping works through Magento's native store scope on most extensions — you enable the module per store view, and rule configuration is usually scoped to the same store. Country / region-specific hiding depends on the vendor: some ship a geo selector in the rule composer, some integrate with a companion geo module. Check the vendor's current documentation for exact mechanisms, and test the rule chain on a staging store before go-live.
Hide-price rules are usually stored as product attributes or a custom rule table. Typical migration: export the current rules (CSV or SQL), map columns to the target extension's schema, import. Product-level flags migrate easily via Magento's native product import. Global rules and customer-group logic may need a short custom script, particularly if you're moving between extensions that model conditions differently. Plan for half a day to a day of developer time for a typical catalog, more if you have thousands of overrides.
All four vendors in this comparison maintain their extensions actively and ship releases compatible with current Magento 2.4.x and PHP 8.x. Like any Magento extension, monitor the vendor's release notes, test on staging before the production upgrade, and keep an eye on theme-layer (Hyvä / Breeze / Luma) compatibility matrices — most issues during Magento upgrades happen there, not in the hide-price logic itself. Check each vendor's stated support horizon and patch frequency before committing.
Conclusion: The Short Version
The "best" hide price extension depends on two questions: how rich does the form need to be, and how strict is your Hyvä CSP.
- Simple hide-price, no form, lowest cost — BSS Hide Price.
- Hide-price with a quick lead-capture pop-up — Amasty Hide Price (fixed-field form) or BSS Call for Price (configurable).
- Hide-price with a flexible quote form + Hyvä native + API — HidePrice Pro. Best combined price for the full workflow.
- Enterprise RFQ with wish lists and approvals — Aheadworks (Hide Price + Cart to Quote). Priciest, but deepest.
For most mid-market B2B stores running Magento Open Source or Adobe Commerce on Hyvä, HidePrice Pro ends up being the shortest path from "prices hidden" to "quote request in your admin inbox", in a single extension.
Key Takeaways
- All four extensions handle the basics: hide prices for guests, customer groups, categories, products.
- Two vendors include a form inside the hide-price module: HidePrice Pro (flexible custom fields + CAPTCHA options + admin grid + API) and Amasty (fixed-field pop-up for lead capture).
- BSS and Aheadworks ship the form in a companion extension: BSS Call for Price (~$149) or Aheadworks Cart to Quote (~$249), both from the same vendor as the Hide Price module.
- Hyvä support is free across all four vendors in 2026. The differentiator is native port (HidePrice Pro) vs compatibility layer (the others).
- GraphQL for hide-price rules is only available in HidePrice Pro — matters for PWA / headless storefronts.
- Total one-extension cost for hide-price + flexible form: €99 (HidePrice Pro), ~$149 (BSS Call for Price), ~$149 (Amasty with pop-up), ~$499 combined (Aheadworks stack).
Related: How to hide prices in Magento 2 — developer guide • Magento 2 B2B quote management guide
Why you can trust this comparison
This article was written by the MageMe team, developers of HidePrice Pro, based on hands-on installation and testing of all four extensions on Magento 2.4.6 and 2.4.7 in 2026. Pricing reflects vendor public rate cards at time of writing and may vary with promotions. Competitor product names and features are described as stated by the vendors on their own product pages — confirm on each vendor's site before purchase.
