Detecting Pricing Changes Before Your Customers Do

A competitor drops their price on your best-selling product by 12% at 2 AM on a Tuesday. By the time you notice on Thursday, your conversion rate on that SKU has already declined for two days. You matched the price, but you lost 48 hours of sales and now you are playing catch-up.

This is the core problem with manual competitive monitoring: the window between a pricing change and its impact on your business is measured in hours, and most operators do not have systems in place to detect changes within that window.

The Speed of Pricing Changes in Ecommerce

Ecommerce pricing moves faster than it ever has. Dynamic pricing tools are mainstream. Promotional calendars are compressed. Flash sales spin up and wind down in 24-hour cycles. In categories like electronics, beauty, and supplements, prices on popular SKUs can change multiple times per week across the competitive set.

The acceleration is driven by tooling. Your competitors—whether they are solo operators or large DTC brands—have access to the same repricing software and analytics platforms. The operators who fall behind are not the ones with worse products. They are the ones with slower information loops.

Detection speed is not about obsessively checking prices every five minutes. It is about having a system that surfaces meaningful changes fast enough that you can evaluate and respond before the change materially affects your business. For most categories, that means detection within a few hours, not a few days.

What "Real-Time" Actually Means for Monitoring

The phrase "real-time monitoring" gets thrown around loosely. In practice, truly real-time price tracking—checking every product on every competitor site every few minutes—is neither practical nor necessary. The overhead is enormous, and the vast majority of checks would show no change.

What matters is the monitoring interval relative to the rate of change in your market. For fast-moving categories (electronics, fashion basics, supplements), checking key competitors every few hours gives you detection within a reasonable window. For slower categories (furniture, specialty equipment, luxury goods), daily checks are usually sufficient.

Bonesaw's monitoring schedules are designed around this principle. Rather than burning resources on constant polling, it runs targeted scans at intervals that match the typical change velocity of ecommerce stores. When a price change is detected, you get the alert, not a dashboard you have to remember to check.

The distinction matters because alert-based detection is fundamentally different from dashboard-based detection. Dashboards require your attention. Alerts demand it. If your competitive intelligence depends on someone remembering to open a tool, you will miss things.

Detecting Bulk Price Changes vs. Individual SKU Changes

Not all price changes carry the same signal. A single SKU dropping in price might mean a clearance on that specific product, a data entry error, or a targeted competitive move. Fifty products in the same category dropping by a similar percentage on the same day is a strategic repricing event.

The distinction matters because your response should be different. Individual SKU changes usually warrant a product-level decision: match, hold, or differentiate. Bulk changes warrant a category-level or store-level strategic review.

Bonesaw tracks product count changes alongside pricing, which makes bulk movements visible. If a competitor's average price in a category drops by 10% and they simultaneously added 20 new products, the narrative is different than a flat repricing on existing inventory. The first suggests they found a new supplier or shifted sourcing. The second suggests margin pressure or aggressive competitive positioning.

Detecting these patterns requires monitoring at the catalog level, not just the SKU level. A tool that only shows you individual price changes will miss the forest for the trees.

Anomaly Detection for Pricing

The challenge with monitoring hundreds or thousands of competitor SKUs is separating signal from noise. A product going from $49.99 to $47.99 is a 4% change—notable, but probably not urgent. The same product going from $49.99 to $29.99 is a 40% drop—that is either a clearance, a pricing error, or an aggressive move that demands attention.

Anomaly detection solves this by establishing baselines for each product and flagging changes that deviate significantly from normal patterns. Rather than alerting on every price movement, the system learns what "normal" looks like for a given product's price history and only surfaces changes that are statistically unusual.

Bonesaw's anomaly detection uses z-score analysis against rolling baselines. A price change is flagged when it falls outside the expected range based on that product's historical pricing behavior. This means a product that regularly fluctuates between $45 and $55 will not trigger an alert at $47, but a product that has been stable at $50 for three months will trigger an alert at $42.

The practical benefit is fewer false alarms. If your alerting system sends you 50 notifications a day, you will start ignoring them. If it sends you three, and all three are genuinely unusual, you will act on them.

Setting Up Alerts That Matter

The difference between useful alerts and noise comes down to specificity. Vague alerts ("a price changed on a competitor") are useless at scale. Effective alerts answer three questions: what changed, by how much, and why should you care.

Structure your alert rules around business impact rather than raw thresholds. A few principles that work well in practice:

Prioritize your money-makers. Set tighter alert thresholds on your top-revenue products and wider thresholds on long-tail items. A 5% price drop on your best seller matters more than a 15% drop on a product you sell twice a month.

Use percentage thresholds, not absolute values. A $5 price drop on a $200 product is noise. A $5 drop on a $15 product is a 33% change that needs attention. Percentage-based thresholds normalize across your catalog.

Separate alert channels by urgency. Bonesaw supports multiple alert destinations—email, Slack, Discord. Route high-severity alerts (large drops on key products, site-down signals) to channels you monitor actively. Route informational alerts (weekly digest, minor changes) to channels you review during planning time.

Review and prune regularly. Your alert rules should evolve with your business. Products that were critical six months ago may be less important now. Competitors you were watching closely may have become less relevant. Audit your alert configuration quarterly.

Integrating Price Intelligence Into Your Workflow

Detection is only useful if it connects to a decision-making process. The most common failure mode is operators who set up great monitoring but have no defined workflow for acting on the data.

A practical workflow looks like this. Alerts surface changes. A daily review (15 minutes, not an hour) triages alerts into three buckets: respond now, investigate further, or ignore. Responses are executed through your existing pricing tools or processes. The key is that the review happens on a fixed schedule, not ad hoc.

For teams, assign competitive intelligence review to a specific person or rotate the responsibility weekly. If everyone is responsible, no one is. The daily review should produce a short list of actions: "match competitor X on SKU Y," "hold pricing on category Z, monitor for another week," "investigate why competitor W dropped prices on their entire catalog."

Bonesaw's daily digest feature is designed to support this workflow. Rather than requiring you to log in and browse dashboards, it delivers a summary of the most important changes to your preferred channel at a scheduled time. The digest covers not just pricing changes but also product additions, removals, and anomalies—giving you a complete picture in a single review.

The operators who extract the most value from competitive monitoring are not the ones with the most sophisticated tools. They are the ones who built a consistent, lightweight review process and stuck with it.

Frequently Asked Questions

How quickly can I detect a competitor's price change?

With automated monitoring, detection typically happens within the same day the change occurs, often within a few hours depending on scan frequency. The exact timing depends on when the competitor updates their site relative to your monitoring schedule. For most ecommerce categories, same-day detection is fast enough to respond before the change has a significant impact on your business.

Should I set up alerts for every competitor product?

No. Alert fatigue is real, and monitoring every SKU across every competitor will generate more noise than signal. Focus alerts on your top-revenue products and categories where pricing is most competitive. Use broader summary reports (like a daily digest) to keep general awareness of changes across the full competitive set without being overwhelmed by individual notifications.

How do I tell the difference between a real price change and a temporary glitch?

Look at persistence and context. A genuine strategic price change will typically hold for more than 24 hours and often coincides with other signals—updated promotional messaging, changes across multiple SKUs in the same category, or social media activity. Glitches tend to be isolated to a single SKU, show extreme deviations, and revert quickly. Bonesaw's anomaly detection helps by flagging statistically unusual changes, but confirming intent still requires a quick manual check.

What is the right number of alerts per day?

There is no universal number, but a useful heuristic is that you should be able to review and triage all your alerts in under 15 minutes during your daily review. For most operators, that means somewhere between 3 and 10 actionable alerts per day. If you are consistently getting more than that, your thresholds are too sensitive or you are monitoring too broadly.

Does Bonesaw access private or internal competitor data?

No. Bonesaw monitors publicly accessible storefront pages—the same product listings and prices that any visitor would see. It does not access internal dashboards, private APIs, or customer data.