When evaluating a search engine for your e-commerce store, price is obviously a key factor. But beware: not all pricing models are created equal, and the one that looks cheapest at first glance may turn out to be the most expensive in the long run.
In this article we analyse the three most common pricing models. If you first want to understand which search features are essential, we recommend reading our dedicated article in the e-commerce search engine market, with the pros and cons of each, to help you choose the one that best suits your situation.
The Three Pricing Models Compared
Nearly all e-commerce search engines use one of these three models:
- Per-product pricing: you pay a monthly fee based on the size of your catalogue (for example, up to 5,000 products, up to 20,000, etc.).
- Per-request (query) pricing: you pay based on the volume of searches made by your users each month.
- Per-pageview pricing: you pay based on the total number of page views on your site, regardless of how many involve search.
Each of these models has different implications for your budget, especially during peak periods such as Black Friday, seasonal sales, or advertising campaigns.
Per-Product Pricing
This is the simplest and most predictable model. The monthly cost depends solely on how many products you have in your catalogue. It does not matter how many searches your users perform or how much traffic you receive: the price stays the same.
Advantages
- Total predictability: you know exactly how much you will spend each month. The budget is fixed with no surprises.
- No traffic penalty: if your marketing campaigns drive a spike in visitors, the cost does not change.
- Ideal for growing stores: as traffic increases, the cost per search automatically decreases.
- Easy to compare: you can instantly calculate the cost knowing only how many products you have.
Disadvantages
- If you have a very large catalogue but little traffic, you might pay more than with a request-based model.
- Some providers cap the number of searches even on product-based plans, partially negating the advantage.
Per-Request Pricing
In this model, you pay for every search query executed by your users. Some providers also count autocomplete requests as separate queries, which can rapidly inflate the numbers.
Advantages
- Low cost for low-traffic stores: if you have few searches per month, you pay little.
- Flexibility: you only pay for what you actually use.
Disadvantages
- Unpredictable costs: during Black Friday or a viral campaign, search volume can multiply 5-10 times. The bill follows accordingly.
- Growth penalty: the more successful your store becomes, the more you pay. The economic incentive is perverse.
- Hidden autocomplete costs: if every keystroke counts as a request, a user typing "red running shoes" generates up to 20 requests before even pressing enter.
- Budgeting difficulty: without a precise history, estimating future costs is very difficult.
Warning: always check whether the provider counts autocomplete requests separately. As documented by the Baymard Institute, a single search query with autocomplete can generate 10-20 API requests for each individual user search.
Per-Pageview Pricing
Some providers charge based on the total number of page views on your site. This model is the most problematic because it ties search costs to a metric — total traffic — that has no direct relationship with actual search usage.
Advantages
- In theory, the price is proportional to the size of your business.
Disadvantages
- Penalises non-search traffic: if a blog post goes viral, you pay more for search even though those visitors never used it.
- Discourages acquisition campaigns: every additional visitor costs money, regardless of their behaviour.
- Poor value correlation: a visitor who views one page and leaves contributes to the cost just as much as one who performs five searches and makes a purchase.
Comparison Table
Here is a quick summary to compare the three models:
| Feature | Per product | Per request | Per pageview |
|---|---|---|---|
| Cost predictability | High | Low | Medium |
| Traffic spike impact | None | High | High |
| Suited for growing stores | Yes | No | No |
| Budgeting ease | Very easy | Difficult | Medium |
| Hidden cost risk | Low | High | Medium |
Practical Tips for Choosing the Right Model
Regardless of the model you choose, here are some fundamental questions to ask the provider:
- Is there a pricing simulator? The most transparent providers offer a calculator that lets you estimate costs based on your real data (catalogue, traffic, search volume).
- What happens when you go over the limit? If you exceed your plan's limits, does the service stop, do costs increase automatically, or are you warned in advance?
- Is autocomplete included? Do autocomplete requests count toward your plan or are they billed separately?
- Are there features with additional charges? Analytics, custom synonyms, merchandising — verify that they are included in the base price.
- Is there a free trial? A 14-30 day trial lets you evaluate the service on your real catalogue before committing.
Which Model Should You Choose?
For most growing e-commerce stores, per-product pricing is the most sensible choice. Here is why:
- The catalogue changes slowly — you know in advance how much you will spend.
- You are not penalised for the success of your marketing campaigns.
- You can plan your annual budget with precision.
- You do not need to worry about seasonal spikes.
Per-request pricing can make sense for very small stores with large catalogues and minimal traffic, but in our experience, most merchants prefer the peace of mind of a fixed and predictable cost.
Whichever model you choose, the important thing is to understand exactly what you are paying for. For a complete guide covering all criteria, read our article on how to choose an AI search engine before signing a contract. Ask for a detailed quote, use the pricing simulator if available, and do not hesitate to ask for clarification on every line item. For a comprehensive overview of all best practices, also read our complete guide to ecommerce search optimization.
Frequently Asked Questions
Product-based pricing charges based on the number of items in the indexed catalog, while request-based pricing charges based on the number of searches performed by users. The former is more predictable, the latter scales with traffic.
For stores with a large catalog but limited traffic, request-based pricing is more cost-effective. For stores with few products but high traffic, product-based pricing offers more predictable costs.
Pageview-based pricing charges based on the total number of pages viewed on the site, regardless of whether the user actually uses search. It is the least transparent model and generally more expensive.



