eExtend is live: AI chatbot, translation and content in one subscription. 50% off. Code: Launch26 → Click here
When Should an Ecommerce Store Offer a Quote Instead of a Price?

Hiding your prices might save your margins on complex orders, but doing it on standard products will quietly kill your sales. Forced quote requests on predictable items only create friction and send ready buyers straight to your competitors.

Choosing between a fixed price and a custom quote isn't an all-or-nothing choice, it is a decision you must make product by product. Here is how to know exactly when to publish a price, when to quote, and how to balance both without losing customers.

The Core Trade-off: Transparency Versus Flexibility

A visible price and a request-a-quote button solve two different problems, and confusing them is where stores lose money.

A published price does quiet work: it filters out tyre-kickers, removes the fear of being overcharged, and lets a buyer check out at 11 pm without waiting for your reply. On a low-cost item, that speed is the sale.

The tension appears the moment a buyer's needs stop fitting one number. Picture a hotel furniture buyer who wants forty chairs in a bespoke fabric, or a workshop ordering aluminium cut to length at today's metal price. A single figure on the product page is either wrong for most visitors or leaves your margin exposed if costs move before the order lands.

PrestaShop gives you both routes in one catalogue. A product can keep its base price visible while a separate flow, such as the PrestaShop Quote Module, invites bulk and custom enquiries. The right answer is rarely a store-wide switch; it is a product-by-product call based on how much the final cost really varies.

Five Situations Where A Quote Beats A Fixed Price

Hiding prices only makes sense when the number on the screen would be wrong, misleading, or negotiable anyway. These five signals usually justify a quote instead of a price.

1. Bulk & B2B Orders

A trade buyer sourcing thousands of units rarely pays the same unit rate as a retail customer buying two. A fixed price either undercharges you or scares the buyer off. The PrestaShop Quote Module handles this cleanly: customers add products to their cart and request a quote with the quantity and details attached, and you send back a tailored offer with discount vouchers if you want to encourage a repeat order.

2. Custom and Made-to-order Goods

Engraved signage, bespoke furniture, mixed-material assemblies: the final figure depends on specification choices you can't pre-calculate on a product page. Quoting lets the customer describe what they need and lets you price it accurately, rather than publishing a base price that every order then contradicts.

3. Volatile or Commodity Pricing

If your cost moves with steel, resin, or shipping rates, a fixed catalogue price goes stale fast. Quoting gives you a legitimate window to confirm the current figure before committing. When you do reprice in bulk, the PrestaShop Bulk Price Update module saves you from editing products one by one.

4. Project & Contract Pricing

Some orders are really small projects: a full office fit-out, a trade show stand, a multi-line parts list. A quote turns a messy basket into one documented offer, which is easier for both sides to approve.

5. MAP-restricted Products

When a manufacturer sets a minimum advertised price, showing a lower figure publicly can breach your agreement. Quoting lets you present the compliant advertised price while handling negotiated terms privately. If a published price would be wrong, negotiable, or contractually risky, a quote is the honest option, not a hidden one.

Each case involves a number that genuinely varies per buyer or per order. If your price is the same for everyone, hiding it is costing you sales. That's where a dedicated hide price and add to cart button module earns its place, letting you switch specific products or groups to quote-only without breaking the rest of the catalogue.

When Hiding The Price Quietly Costs You Sales

Apply this treatment to a standard shelf product with a predictable cost, and you start losing orders you never see: the shopper leaves, buys elsewhere, and you get no signal that you turned them away.

Replace the figure with "Call for price", and you have added a step they did not ask for, at the exact moment they were ready to decide.

Someone comparing three similar products across tabs uses cost as the first filter, and a store that makes them email or phone usually gets dropped from the shortlist before the comparison even starts. First-time visitors are the most fragile group of all. They have no relationship with your brand yet, so a hidden price reads as either "expensive" or "something to hide", and both assumptions cost you the click.

Cart abandonment follows the same logic. If a shopper has to request a quote for a predictable item, the buying momentum breaks while they wait for a reply. Many simply don't come back to the tab.

Search behaviour has shifted too. Google's shopping surfaces and AI answer engines such as ChatGPT and Perplexity tend to favour pages that state a clear price for a clear product. A page that only says "contact us" gives those systems little to quote, so a competitor with a visible figure may get the mention instead. If you sell mostly standard retail lines, pair visible prices with a separate route for the exceptions, such as the PrestaShop Quote Module, which lets you keep standard items priced while quote-based products run their own path.

In PrestaShop terms, check your catalogue for products where the price is already fixed in the Catalog > Products screen and the buying decision is one unit. Those are the ones whose price should be visible. Save price hiding for the products covered earlier, where the figure truly moves with quantity or specification.

A hidden price is a filter that only pays off when the number behind it is genuinely unpredictable. Everywhere else, it quietly converts ready buyers into lost sessions.

How Do You Decide Per Product, Not Per Store?

A workshop that sells both a bag of fixings and a custom trailer should not hide every price to protect the large end. Classify each SKU with four questions, then set its behaviour in the PrestaShop product page accordingly.

  • Does the unit price move with quantity? If buying 50 costs less per unit than buying 5, a fixed price misleads. A PrestaShop Quote module such as Quotation Pro lets the customer build the order and ask for a figure, which suits tiered pricing far better than a single number on the page.
  • Is the item made or configured to order? Engraving, cut lengths, fabric colours and mixed component sets all change cost. Customisable products belong on quote.
  • Is there a manufacturer MAP or resale rule? If the supplier caps advertised pricing, showing your best price can breach the agreement. Quote-only keeps the catalogue visible while the real figure goes out privately.
  • Is it a commodity anyone can compare? A cable, a bulb, a standard bearing: buyers check three shops in a minute. Hiding that price loses the sale, so keep it visible.

Sort the results into a simple grid. Commodity plus fixed quantity stays priced. Commodity plus bulk stays priced with quantity breaks. Configured plus regulated becomes quote-only, and so does anything where the cost changes on inspection.

Product type Price changes with quantity? Made or configured to order? Show price or quote?
Standard hardware, fixed pack size No No Show price
Trade consumables in bulk Yes, tiered No Show price with quantity breaks
Custom signage or machined parts Yes Yes Quote
Branded goods under MAP Sometimes Often Quote

One hidden price on a commodity tells a buyer you are expensive; one shown price on a custom build tells them you did not understand the job. Apply the setting per SKU, and the store stays honest in both directions.

What A Quote Workflow Needs to Actually Convert

A quote request only converts when the buyer never has to wonder what happens next. The request has to sit exactly where the price would normally be, the form has to be short, and someone has to answer quickly.

On a product page, the customer's eye lands where the price sits. Put a clear button there, labelled something like "Add to Quote" or "Request a Quote", and let it add the item to the cart the way a normal purchase would. If the button is buried in a tab or a footer link, most buyers will assume the product is unavailable and leave.

The form itself should ask only what you genuinely need to price the job: quantity, any specification or variant, delivery timing, and a note field for special requirements. Every extra field costs you submissions. For a made-to-order build, a short description field is essential; for a bulk order of a standard line, quantity and delivery date may be all you need.

Speed is the part most stores get wrong. A quote that arrives days later has usually lost to a competitor who replied within the hour. Set an internal target, even if it is simply "same working day", and make sure notifications reach the right inbox.

The PrestaShop Quote Module is built around exactly this flow. Customers add products to the cart and request a quote rather than checking out, and you receive the request with its details in the PrestaShop back office. From there, you set your price, respond through the module, and the customer can convert the quote into an order without starting again. Instant messaging and email notifications keep both sides informed, and you can send a discount voucher by email if you want to nudge a hesitant buyer toward the order.

A quote workflow converts when the buyer can request, hear back, and order without ever leaving your shop.

Decide who owns quotes before you switch the button on. If quotes land in a shared inbox nobody checks, the flow breaks at the exact moment the buyer is most interested. Route them to a named person or a dedicated address, and review response times regularly, especially in the first month.

Quote Module Versus Fixed Price: A Quick Comparison

Neither model wins outright, so line them up against the things that decide your margin: trust, how quickly a buyer can act, how much admin the sale eats, and which products you actually sell.

Criterion Fixed price on the product page Quote instead of price
Buyer trust High for commodity items where buyers can compare easily. Needs context: a clear reason to ask (bulk, custom, contract) keeps trust intact.
Conversion speed Fast: add to cart and pay in one flow. Slower: the sale pauses until you reply and the buyer accepts.
Margin control Locked at the price you publish. Negotiable per order, so you can protect margin on complex or large jobs.
Admin effort Near zero once prices are set. Higher per order, so it only pays off when order value justifies it.
Ideal product types Catalogues, spares, anything with a stable list price. Bulk orders, made-to-order builds, and items with volatile costs.

On PrestaShop specifically, the fixed-price side is the native product page. The quote side is usually handled by a module that adds a request step, such as the PrestaShop Quote Module | Request a quote | Quotation Pro at $49.00, which lets customers add products to the cart and request a quote, with instant email and messaging notifications so the request does not sit unanswered.

Some stores run both at once: publish prices on standard lines and switch to quote for the bulk or custom variants.

Quote-based pricing is a margin tool, not a conversion tool: it earns its admin cost only when the order value or customisation justifies the pause.

Getting The Balance Right On PrestaShop

Most stores don't need a single answer. They need both modes running side by side, and PrestaShop gives you the building blocks to run them without touching code.

Start with Customer Groups. Create a group for trade accounts and attach a specific price rule to it, so your retail visitors see the standard price while logged-in trade buyers get account pricing. This is the hybrid model: transparency for walk-in traffic, negotiated terms for the people who actually order by the pallet.

Then use Price Rules (Catalog Price Rules and Cart Rules) to handle volume. A tier that drops the price at fifty units, or a cart rule that applies only to a wholesale group, keeps the discount logic where PrestaShop already expects it, instead of in a spreadsheet.

  • Apply quotes per product or per category, not to the whole catalogue. A made-to-order machine belongs behind a quote; a fixed-cost accessory does not.
  • Keep prices visible wherever the cost genuinely doesn't move. Hiding a stable price only adds friction.
  • Reserve quote requests for the lines where specification, volume or lead time actually changes the number.

When you need both modes on the same store, the PrestaShop Quote Module | Request a quote | Quotation Pro adds an "Add to Quote" button alongside your normal cart, so customers can request pricing while your fixed-price lines keep selling. For stores that mainly need to switch the cart off on selected products, the Hide Price and Add to Cart Button module covers that narrower job.

What Does "Quote Instead of Price" Actually Mean in PrestaShop?

The product page invites a customer to request a price rather than showing a fixed figure and an Add to Cart button. A shopper adds items to a quote request instead of a normal cart, and you reply with a tailored figure.

The PrestaShop Quote Module by FME handles this flow cleanly. Customers add products to their cart and request a quote, which suits bulk orders that need specific details. It sends instant email and messaging notifications so you can respond quickly, and the admin can email discount vouchers to encourage repeat business. It also adds an "Add to Quote" button to products, so the request lives alongside your normal catalogue.

When Does A Quote Genuinely Beat A Fixed Price?

Four signals reliably point toward quoting. If you recognise your store in two or more of them, a quote workflow is probably the right call.

  • Price volatility. If material costs move frequently, a fixed price on a PrestaShop product page becomes a liability the moment it is published. A quote lets you price against today's cost.
  • Large or variable order sizes. When a buyer needs hundreds of units with custom labelling, the per-unit figure depends on quantity, packaging and delivery. A single price cannot cover that range honestly.
  • MAP and reseller rules. If you sell through distributors bound by minimum advertised price agreements, publishing a low or promotional figure can breach those terms. Quoting privately keeps you compliant.
  • Made-to-order complexity. A custom-finished item with configurable options has too many combinations for one price. Quoting lets you assess each build.

A hidden price is a feature only when the number is genuinely unknowable, or genuinely dangerous to publish. Everything else is friction.

When Does Hiding Prices Quietly Cost You Sales?

Hiding a price on a standard, well-defined product is usually a mistake. If a shopper can buy the same item elsewhere with a visible price, a blank price tag reads as "expensive or evasive," and they leave. Price is one of the most-scanned elements on a product page, and removing it gives the buyer nothing to compare.

Wholesale buyers are also busy. Many will skip a form that asks for company details before they have any sense of cost, especially for lower-value items where the purchase does not justify a back-and-forth. And if your competitors show prices on every SKU, a hidden price signals a smaller or less established operation.

A related but different case is hiding the Add to Cart button entirely, for example when a product is out of stock or trade-only. That is a separate setup and can be handled with a PrestaShop Hide Price and Add to Cart Button Module, while quoting covers items that still need a bespoke figure.

How Do You Decide Per Product Rather Than For The Whole Store?

Ask three questions for each product. Can the price be set today and held for a month? Is the typical order a single unit or a small fixed quantity? Would a distributor object to the figure appearing publicly? If all three answers point to "yes," show the price. If any answer is "no," quoting earns its place.

For example, a store selling standard gaskets should display prices, because buyers compare them constantly. The same store's custom-fabricated assemblies, priced per project, should sit behind a quote request. Keeping both on one PrestaShop catalogue, with the "Add to Quote" button only on the custom lines, gives you the best of both.

What Else Has To Be Right Once You Start Quoting?

Quoting only beats a fixed price if your response is fast and your catalogue data stays accurate. A quote request that sits unanswered for days loses the sale just as surely as a hidden price does.

Build a response routine. Answer within a working day, confirm the specification in writing, and set a validity period so the figure cannot be applied months later against changed costs. The instant notifications in a quoting module exist exactly so requests do not fall through the cracks.

Keep your underlying prices current as materials and supplier costs shift, since your quotes are built from them.

So What Should A PrestaShop Owner Actually Do?

Start with a short audit, not a redesign. List your products and mark each one as "fixed price," "quote," or "borderline." Most fixed-price items should stay exactly as they are.

Then apply the four volatility signals to the borderline products. If material costs, order size, MAP rules or made-to-order complexity apply, move it to quoting. Everything else keeps a visible price and an Add to Cart button.

Finally, track how many requests convert on the products you moved, and compare against what those items sold before. That evidence, not a general opinion about hiding prices, tells you whether quoting is working. In PrestaShop, choosing to quote instead of price is a per-product decision you can make one line at a time, and the stores that get it right treat each SKU on its own merits.

Take Away

The question "should I hide prices in PrestaShop?" almost always hides a better question: which specific products actually need it? Answer that SKU by SKU and the strategy writes itself. Standard retail lines keep their visible price and carry the store's day-to-day conversion. Bulk, custom, MAP-restricted and volatile lines move behind a quote request, where a tailored figure protects your margin and starts a real conversation.

That split is not a compromise; it is how a serious trade catalogue has always worked. The product page does the filtering, the quote does the pricing, and neither one is asked to do a job it cannot do. What you avoid is the default mistake: blanking every price to protect the handful of complex lines, and losing the straightforward orders that keep the lights on.

If you want to run both modes on one PrestaShop catalogue, the PrestaShop Quote Module | Request a quote | Quotation Pro at $49.00 adds the "Add to Quote" route to the products you choose, with instant email and messaging notifications so no request sits unanswered and discount vouchers you can email to bring a hesitant buyer back.

Frequently Asked Questions

Should I hide prices on my whole PrestaShop store?+–
Rarely. A store-wide hide punishes your standard catalogue items, which sell best with a visible price. Switch only the products whose cost genuinely varies, such as bulk, custom or MAP-restricted lines, and keep everything else priced.
What information should a quote request form ask for?+
Quantity, specification or variant, delivery timing, and a short note on special requirements. For a standard bulk line, quantity and delivery date may be enough. Every extra field reduces the number of people who finish the form, so ask only what you need to price the job.
How fast should I respond to a quote request?+
Same working day is a sensible target. Quotes that arrive days later usually lose to a competitor who replied within the hour. Route requests to a named person or dedicated inbox and check response times regularly, especially in the first month.