What determines whether price monitoring data is trustworthy?
Product matching determines it. A monitoring platform must decide that your SKU and a competitor listing refer to the same product, and every downstream number inherits that decision. Matching on EAN, GTIN or MPN is reliable. Matching on product title is not: a 128GB variant matched to a 256GB listing produces a price gap that looks like an opportunity and is actually an error.
The second factor is crawl freshness. A price collected yesterday describes yesterday's market. Price2Spy checks up to eight times per day, and PriceEdge states it processes more than 100 million prices daily; whether that cadence reaches your specific competitor pages is a question to test during a trial rather than to read from a datasheet.
The third is coverage honesty. Every crawler fails on some sites — bot protection, login walls, dynamically rendered prices. Ask what percentage of configured URLs returned a price in the last run, not how many sites the vendor supports in principle.
How does price monitoring differ from price optimisation?
Price monitoring reports; price optimisation decides. A monitoring tool tells you that three competitors dropped below your price this morning. An optimisation tool changes your price in response. Minderest, Dealavo and Price2Spy sit primarily on the monitoring side. Omnia Retail, 7Learnings, Pricefx and PriceEdge sit on the decision side and use monitoring as an input.
The distinction matters at purchase time. A team that buys monitoring and expects prices to move by themselves has bought the wrong layer, and a team that buys an optimisation platform without a monitoring source has bought an engine with no fuel.
What is MAP monitoring and which brands need it?
MAP monitoring tracks whether resellers advertise a product below the Minimum Advertised Price a brand has set, and MSRP monitoring tracks deviation from the suggested retail price. The buyer is a manufacturer or brand owner, not a retailer: the goal is protecting positioning across a distribution network rather than winning a price comparison.
Minderest and Dealavo both offer MAP/MSRP compliance tracking. Price2Spy supports the same use case through alerts and screenshot capture, which matters because enforcing a MAP policy against a reseller requires evidence of the breach, not a line in a report.
How many competitors and URLs should you monitor?
Start narrow. Monitoring every competitor on every product produces a dataset nobody reads and a bill that scales with URLs. The useful starting set is the products that carry most of the margin, against the three to five competitors that customers actually compare you with.
Pricing models follow URL counts, which makes this a budget decision as well as an analytical one: Price2Spy prices at 500 and 2,000 URL tiers, and most vendors scale similarly. Widening coverage after the first month, once it is clear which comparisons move decisions, costs less than starting wide and pruning.
Where does price monitoring commonly fail?
It fails silently. A crawler blocked by bot protection returns no price rather than an error a human notices, and the affected products quietly drop out of the comparison. Ask for a coverage report per run and treat a falling match rate as an incident.
It fails on variants. Colour, capacity, bundle and pack size are where matching goes wrong, and they are also where margin differences hide. A validation pass over the matched pairs before trusting the data is the single highest-value hour in any monitoring implementation.
It fails on currency and tax. A price collected in a market with different VAT treatment is not comparable to yours until it is normalised, and a monitoring tool that reports gross against your net makes every gap look wrong by exactly the tax rate.
