A competitor's advertised price changes from one amount to another. Before you react, check what changed with it. The new figure may refer to a different quantity, a promotional period, or an offer that now excludes delivery.
Price tracking is useful when it preserves enough context to support a business decision.
Define a comparable offer
Choose a small set of products or services that customers actually compare with yours. For each, record the product variant or service scope alongside the price.
Useful fields include currency, unit or quantity, tax treatment, delivery charges, minimum order, subscription term, and promotional conditions. A monthly price billed annually should remain distinguishable from a month-to-month price.
If a competitor publishes “from” pricing, retain that wording. Do not turn a starting price into an estimate for the complete job.
Keep the source and observation date
Save the source URL and the time the value was observed. When possible, retain the relevant excerpt or permitted snapshot so someone can check what the alert refers to.
Distinguish the first time you observed a change from the date it took effect. Unless the source states an effective date, a tracker can only establish that the page differed between observations.
Pages may also vary by region, currency selection, login, or customer segment. Record the conditions under which the comparison was made. An unavailable page should produce an unknown result, rather than a zero price or an assumed withdrawal.
Agree what deserves an alert
A useful rule names the field, condition, and recipient. For example, a business might want a review when the regular price of a directly comparable item changes, while collecting layout edits in a separate log.
Choose the checking frequency from the decision it supports and the access the source permits. A rapidly changing retail offer and an annual service price list have different needs. Test how many irrelevant alerts the rule produces before making it part of someone's daily work.
Use AI to summarize evidence carefully
AI can help turn a set of detected differences into a readable summary. Keep source links and the underlying values available to the reviewer. Ask it to distinguish observed facts from an interpretation, and check important prices and terms against the original page.
A lower published price does not establish why a competitor changed it, whether customers are buying, or how your business should respond. Those decisions need your costs, positioning, and customer conversations too.
Scope the collection before building
Try a representative sample of the proposed sources. Confirm how the information can be accessed, whether the fields are consistent, and what happens when a page changes structure. Source permissions, access restrictions, and any required specialist advice need to be resolved for the proposed use.
LifeVen's software and automation service can assess a defined collection-and-alert workflow as a software project. Bring the source list, the fields you need, and an example of the decision an alert would support. The agreed scope can then specify the integrations, review process, and maintenance responsibilities.