How to Monitor Competitor Prices: A Step-by-Step Plan

In short: to monitor competitor prices, decide which pricing decisions the data must support, choose a limited set of competitors and products, match comparable items, set a monitoring frequency per product group, validate every run, and turn the results into a fixed routine of reports and actions. Start small and expand only when a commercial question asks for it.

Most teams know what their competitors charge in a vague sense. Few can say how their own prices compare on the products that matter, today, with data they trust. The gap is rarely a lack of tools. It is a lack of choices: which competitors, which products, how often, and what to do with the result.

This step-by-step plan covers those choices, in the order in which they are best made.

Step 1: What decision should the price data support?

Start with the decision, not the data. Price monitoring is useful when it changes something: a price adjustment, a campaign, a negotiation with a supplier, a margin discussion. Write down two or three questions the data must answer, for example:

• Where are we more than 5% more expensive than the market on our best-selling products?
• Which competitor starts promotions first, and how long do they last?
• Where do we leave margin on the table because we are cheaper than we need to be?

These questions decide everything that follows: the number of competitors, the product range and the frequency.

Step 2: Which competitors should you monitor?

Monitor the competitors your customers actually compare you with, not the ones you happen to know. Mix three groups: direct competitors, the market leader that sets the reference price, and the channels where customers compare, such as marketplaces and comparison sites. Five to ten competitors is a workable range for most teams. More competitors rarely give more insight; they mostly give more data to check.

Step 3: Which products should you start with?

Start with the products that carry your revenue or margin, and with the products customers compare most often. A core range of a few hundred items is often enough to start. Add the long tail later, at a lower frequency.

A simple way to see why this matters (illustrative example, fictional numbers): a retailer monitors 200 core products at 5 competitors. That is 1,000 price points per run, or about 30,000 per month with a daily run. Monitoring 5,000 products at 10 competitors would give 50,000 price points per run. The second set is 50 times larger per run, and in practice most of it is never looked at.

Step 4: How do you know you are comparing the same product?

A price is only useful if it belongs to the same product. For branded goods with a barcode, matching on EAN covers a large part of the range. For everything else, such as own-brand products, bundles, spec-driven products or services, you need matching on attributes: which properties must match exactly, which may deviate within a margin, and how to score the rest. We explain the approach in Matching without a barcode: how to compare prices when there's no EAN.

Two things are worth settling before you collect anything: the unit you compare on (per piece, per metre, per month) and whether prices include delivery, shipping costs and VAT.

Step 5: How often should you monitor prices?

Match the frequency to how fast prices move, not to what is technically possible. A practical split:

• Daily for fast-moving, heavily promoted categories and for the products you compare most.
• Weekly for categories with stable prices.
• Event-driven around campaigns and peak periods such as Black Friday or the sales.

More frequent is not automatically better. Each extra run adds cost and data to review. Choose the lowest frequency that still lets you react in time.

Step 6: How do you keep the data reliable?

Price data that cannot be trusted is worse than no data, because people stop using it. A reliable process has a few fixed habits:

• Store every price with the product, the competitor, the date and time, and the source page.
• Validate every run: did the page load, is the price plausible, did the product still match?
• Flag sudden changes, such as a price that drops by 80% overnight, for a human check before they reach a report.
• Watch for website changes that silently break collection, such as a new page layout or a renamed field.
• Only monitor prices that are publicly available. Pages behind a login are usually out of scope.

Step 7: How do you turn price data into decisions?

Data that lives in a spreadsheet nobody opens changes nothing. Give the results a fixed place in the weekly or monthly routine. Three outputs cover most needs:

• A price position index per product group. If your price is €100 and the average of matched competitors is €96, your index is about 104: you are roughly 4% above the market (illustrative numbers).
• Alerts for changes that need a quick reaction, such as a competitor undercutting you on a top product.
• A periodic overview of promotions, price moves and gaps, discussed by the people who set the prices.

Agree in advance who acts on which signal. An alert without an owner is just a notification.

Spreadsheet, tool or managed service?

There are three ways to run this plan. A spreadsheet works for a handful of products and one or two competitors, but breaks as soon as the range grows. A monitoring tool works well when your products have EANs and your competitors are mainstream webshops. A managed service fits when matching is hard, when prices sit behind configurators or quote flows, or when your team has no capacity to keep collection running. The question is less "which is best" than "where does the effort sit in our situation".

Common mistakes

• Monitoring everything at once instead of starting with a core range.
• Comparing headline prices without checking that the products are equivalent.
• Ignoring delivery costs, VAT or minimum order quantities.
• Collecting data without an owner who acts on it.
• Treating the first setup as final, while competitors change their sites and ranges all the time.

Competify is a Dutch company that delivers competitive intelligence and web data as a managed service. We help you make the choices in this plan, build and maintain the collection, match and validate the results, and deliver them through a dashboard, API or file transfer. Read more about competitor price monitoring for complex markets, or get in touch for an introductory conversation.

If prices in your market only appear after configuration, read Configurator scraping: how to monitor prices behind a configurator.