Amazon price monitoring: comparable offers and actionable alerts

What Amazon price monitoring should record

Amazon price monitoring records comparable offers over time so you can investigate changes in price position, availability, and the Featured Offer. It is an observation workflow. Repricing is a separate action that changes your own selling price according to rules, costs, and commercial constraints.

Start with a practical question: did a close substitute become cheaper, did another seller become featured on the same ASIN, or did your own offer become unavailable? These questions need different comparison sets. Keep same-ASIN seller competition separate from the broader category's product positioning.

The aim is a reliable record with a useful next action. A price alert alone cannot tell you a competitor's margin, intention, sales, or reason for changing an offer.

1. Define a comparable offer before comparing prices

Record the context with every observation. Otherwise a change of child variant, delivery location, seller, or customer entitlement can look like a price cut.

Show a standard observed total and conditional promotions separately. A coupon may require activation, eligibility, a subscription, or a specific account; do not silently subtract it from every customer's price. Seller-side referral and fulfillment fees belong in your own margin calculation, not in the shopper's displayed total. You cannot infer a competitor's costs from its seller address.

Illustrative comparison: an item at €70 plus €5 mandatory shipping totals €75; another at €73 with free shipping totals €73 under the same tax and destination assumptions. The lower item price is not the lower delivered price.

2. Track price position within a defined product group

For same-ASIN offers, compare seller, condition, total price, availability, and delivery. For category positioning, first group comparable products by relevant characteristics such as capacity and pack size. A category-wide median combining different formats can be misleading.

Use a transparent calculation when the sample supports it:

distance from group median = (your comparable total / group median total − 1) × 100

If your comparable total is €90 and a clearly defined group's median is €100, the difference is −10%. This is an illustrative calculation, not a current category result. Report the number of priced products and excluded observations beside the median. Repeated children from one family can distort a benchmark, so document how families are handled.

Price position is descriptive. A higher-priced product can differ in capacity, delivery, reviews, features, or brand positioning. A low-priced product with a weaker bestseller position does not establish that further price changes would have no effect.

3. Interpret the historical air-fryer example carefully

The published July 2026 amazon.de sample report describes a board of 54 air-fryer products, with prices available for 48. Its rounded overall range is approximately €35–€240. Selected rows from that published snapshot are reproduced below; the currency and German marketplace are retained.

This is a selected display from the existing report, not the full priced subset, a current price comparison, or evidence of a daily trend. The products differ in capacity and format. The article does not provide exact collection timestamps, category node IDs, ASIN-level exports, promotion conditions, or reasons the other six board products lacked prices. Do not compute a category median from these selected rows.

The original report describes the analyzed product as second cheapest among the 48 priced products while at board position 12. That is a prompt to examine product comparability, offer conditions, listing quality, and account-side performance. It does not isolate a visibility problem or prove a price reduction would be ineffective.

4. Monitor the Featured Offer separately from item price

The Featured Offer is the offer presented for convenient purchase in Amazon's Offer Display, often called the Buy Box. The observed holder can change while the product title and your own price stay the same. Public observations may also vary with delivery context and time.

Amazon's official guidance considers competitive total pricing, delivery, order experience, and stock. Offer evaluation and the observed displayed offer are different facts. Amazon removed the separate seller-level eligibility gate in the EU and UK on July 20, 2026; US help describes the change as of September 2026. Check current rules for your store. FBA is not a guarantee of selection, and a lower price alone does not guarantee it either.

If your own offer is no longer featured, check the current account and offer status, inventory, delivery settings, and comparable total price. Save the observed seller and timestamp. Avoid assuming which input caused a change, or making a price cut before checking whether the item is even available.

For third-party offers, write “seller observed in the Featured Offer at this check” rather than “seller won all sales today.” A set of periodic observations is not an order ledger or a precise share of purchases.

5. Choose a cadence and inspect the history actually available

Choose the checking interval according to the decision and the cost of a missed event. A scheduled daily observation can support a periodic positioning review, but can miss an entire promotion or offer change between checks. Urgent operational decisions require fresher information and a way to verify it.

For Scoutvo monitoring, confirm the covered objects, events and current settings, then inspect the latest successful observation time. A schedule is not a measured freshness guarantee. Monitoring does not itself execute price changes. See the alerts page and verify coverage for the intended workflow.

Historical coverage depends on when monitoring started, successful collection, supported fields, retention, and the source. Read the actual first and last observations and gaps in your report. Own collected history and any externally supplied history must be labeled separately. A newly monitored product does not automatically have a full historical window; this guide does not promise a universal 90- or 365-day archive.

Missing values stay missing. Mark failed collection, unavailable offer, and stale carried-forward value distinctly. Never replace them with zero price or silently connect them into a continuous observed history.

6. Build alerts that specify a check and an action

Use relative price thresholds for broad comparability and absolute thresholds where margin or a known price boundary makes them meaningful. Five percent can be an initial review threshold for one workflow; it is not an Amazon rule or a universal optimum. Tune rules to volatility, commercial exposure, and alert burden.

• Comparable total-price change: compare the same offer context; include both values and timestamps.
• Observed Featured Offer seller change: keep it independent of a price threshold, with a priority matched to the ASIN.
• Availability or delivery change: route it to the person who can check inventory or offer settings.
• Collection failure or stale data: label it as a data issue rather than a market event.

Use deduplication and a recovery rule so the same unchanged condition does not repeatedly generate alerts. A dashboard review may be appropriate for low-priority movements; an urgent alert should have an owner who can act.

The change was detected on October 15. With no intervening observations, it may have occurred at any point after the previous check; its actual start time and duration are unknown. Express the event as an interval, not an exact timestamp. Even frequent snapshots cannot guarantee that every short-lived event was observed.

7. Verify the signal before changing your price

Open the current offer in the saved marketplace and delivery context. Confirm the child, seller, condition, shipping, promotion eligibility, and availability. Check whether the apparent drop came from a different seller becoming featured or a different variation being displayed.

For your own pricing decision, calculate an approved floor using your actual costs and fees. Consider contribution margin, inventory, and the purpose of the change. A competitor's visible total does not reveal its profitable minimum. Keep repricing controls separate from monitoring, and record any manual or automated action.

Evaluate outcomes with your own account data over a defined period, including price, stock, advertising, and Featured Offer context. A simultaneous rank movement is an association; bestseller rank is not a causal test of pricing. An alert can identify what changed in the observed offer, but not why it changed or what customers would have done at another price.

Use this record as one input to the broader competitor-analysis workflow. For definitions of BSR, estimates, and the Featured Offer, read the Amazon terms guide.

Frequently asked questions