Product Events
Each supported price increase or decrease is stored as an immutable event with the product and event time.
Supported price events
Illustrative values from one store
Everyday Backpack
Price decreased
Travel Bottle
Price increased
Canvas Weekender
Price decreased
Currency gate
Both values need the same known currency.
Check cadence
Manual checks and one daily scheduled check.
Who it is for
Ecommerce, retail, growth, and founder teams often reopen the same competitor product pages, copy prices into a sheet, and try to remember what changed. That process becomes unreliable as the store list grows.
The manual problem
How detection works
Price monitoring starts with a compatible store and a one-time catalog import. Later checks can then identify supported movement from the saved value.
Content Radar checks public access, catalog structure, and server-visible product data before saving a store.
The first import records the products and supported prices available at setup. It creates the reference point without creating price events.
A manual Check for changes or the daily scheduled check compares supported product prices with the saved baseline.
A supported increase or decrease becomes a Product Event and appears in Recent changes and the in-app alerts feed.
Store compatibility
Content Radar can work with compatible public Shopify, WooCommerce, and structured custom stores. Compatibility depends on the storefront response, catalog structure, and stable product signals. The platform name alone is insufficient.
Currency requirement
Content Radar records a price increase or decrease only when the previous and current values carry the same known currency. Unknown or mismatched currencies do not produce a price event.
Valid example
$84 USD to $72 USD produces a supported decrease event. Unknown and mismatched currencies are excluded.
Review the evidence
Detected changes use the existing Product Monitoring records and review surfaces. The price page is a focused entry point into that workflow.
Each supported price increase or decrease is stored as an immutable event with the product and event time.
Review the latest product movement for one store or across the workspace without reopening each storefront.
Price events enter the in-app alerts feed with read and unread state. External product notifications are not included.
Best fit
Not the best fit
Current limits
These limits define the supported workflow and should be considered before adding a competitor store.
Content Radar detects supported price increases and decreases when a compatible public store exposes readable product prices and both compared values use a known, matching currency.
Some public Shopify, WooCommerce, and structured custom stores are compatible. Each store must pass a bounded compatibility check for public access, supported catalog structure, and server-visible product data before it is saved.
No. The one-time baseline import records the starting product catalog. Price events begin with later manual or scheduled checks that can compare a supported current value with the saved value.
Supported increases and decreases are stored as Product Events. They also appear in Product Monitoring Recent changes and the in-app alerts feed.
No. It does not match products across stores, compare your own prices with competitor prices, recommend prices, or change prices.
A user can run Check for changes manually, and the configured Product Monitoring schedule runs once per day. The schedule is not user-configurable.
Related pages
Import the baseline catalog, run a later check, and review supported price changes with the product context attached.