Competitor Price Monitoring: Build a Comparable Offer History

A competitor price monitoring strategy defines which offers you compare, the conditions under which you observe them, how often you check, and what evidence must exist before a pricing decision changes. Collecting more prices is useful only when the offers are comparable. A different pack size, seller, delivery location, or membership condition can make a real price look like a misleading discount.

Start with a small set of commercially important products and a documented comparison rule. Build a reliable observation history before connecting the feed to repricing. Residential proxies can provide a routing layer for permitted regional checks; they do not match products, extract prices, or guarantee access to a retailer.

Define the decision before collecting prices

Choose one operational question: whether a matched competitor changed its base price, whether your delivered offer is competitive in a particular market, or whether an apparent discount applies only to a promotion. These questions need different fields. Write the intended action and the evidence threshold beside each question so an alert does not automatically become a price change.

For example, a merchandiser may review a sustained difference on a high-volume product while leaving low-stock items alone. That is a business policy, not a universal pricing formula. Include margin, inventory, contractual constraints, and the cost of acting on an incorrect observation.

Match the offer, not just the product title

Use a stable identifier where one is available, then check attributes that can change the offer. Keep ambiguous matches in a review queue instead of forcing the nearest title match into a time series.

• Product identity: brand, model, variant, size, color, pack quantity, and condition.
• Seller: marketplace merchant, fulfillment arrangement, and whether the offer is actually available.
• Price basis: currency, tax treatment, shipping, mandatory fees, and the quantity required.
• Eligibility: membership, coupon, subscription, first-order offer, or account-specific pricing.
• Observation context: timestamp, location, source URL, and the relevant page evidence.

A two-pack at 18 and a single item at 10 are not directly comparable. Unit price may help, but delivery costs and purchase conditions still matter. Preserve the original offer alongside any normalized value so another person can audit the calculation.

Make regional observations reproducible

Use the same intended market and delivery context for repeated checks. An IP-associated location is only one input: a storefront can also use an entered postal code, account settings, cookies, or its own location database. Record what the storefront actually displayed rather than assuming that a requested proxy location proves the offer belongs to that market.

For platform-specific details, use the separate Shopify price monitoring guide. The strategy here covers cross-retailer matching, evidence, and decision rules; it does not replace a storefront-specific implementation.

Choose a schedule and a failure policy

Set collection frequency according to how quickly the decision becomes stale and how the source permits access. Prefer an authorized feed or API when it provides the required fields. A high-frequency crawler is not automatically a better source.

1. Start with a limited product set and record successful observations.
2. Separate an unavailable offer from a failed request or incomplete extraction.
3. Keep the last good observation with its original timestamp; never present it as newly collected.
4. Use bounded retries and backoff for transient failures. Investigate repeated rejection instead of increasing traffic.
5. Flag stale, ambiguous, or location-inconsistent observations for review.

An HTTP 200 response alone does not pass collection QA. Confirm the intended product, expected currency, seller, and usable price. Consent screens and error pages can also return successful HTTP responses.

Turn observations into reviewable alerts

An actionable alert should identify the matched offer, previous and current observation times, comparable price components, and the reason the change matters. Keep collection failures in an operational channel so they are not confused with competitor price changes.

Consider a marketplace listing that drops its item price but adds shipping. An alert based on item price alone can trigger an unnecessary discount. Reviewing delivered cost and the original evidence makes the difference visible before a pricing owner acts.

Where Magnetic Proxy fits

The Price Monitoring capsule provides proxy infrastructure for this type of workload. Your application still owns product matching, extraction, scheduling, history, and pricing decisions. Confirm the current connection options in the documentation and test the intended market with a small permitted workload.

Before expanding, review match quality, fresh-observation coverage, invalid extractions, and alerts dismissed as non-comparable. Improve these controls before increasing volume. The useful outcome is an auditable pricing decision supported by the right offer evidence.