Amazon Price Monitor: Track a Product in 2026

An Amazon price monitor saves you from reopening the same product page just to see whether the price has reached your target. Scrapeer’s public Amazon price-monitoring Flow checks one Amazon product, turns the displayed price into a number, compares it with your target, and creates a CSV report only when the threshold is reached.

That narrow scope is deliberate. You can see the product URL, price selectors, calculation, condition, and output columns on the canvas before running anything. It is a useful starting point for one repeatable price check, not a claim that every Amazon listing or regional storefront has identical markup.

The result: a CSV when the target is reached

The starter Flow asks for two values:

Input	Default value	What it controls
Product URL	https://www.amazon.de/dp/B07BDWD8B7	The Amazon product detail page to check
Target price	7	The threshold in the page’s own currency

It then follows a visible six-step path:

1. Open the product detail URL.
2. Extract the product title and displayed price text.
3. Normalize the price text into a number called currentPrice.
4. Calculate priceDelta as currentPrice - targetPrice.
5. Continue through the matching branch when priceDelta is at most 0.
6. Create a cloud CSV containing the product and comparison details.

The comparison now says exactly what the report needs: a negative delta means the price is below the target, zero means it is exactly at the target, and a positive delta does not qualify.

Current price	Target price	Calculated delta	CSV created?
6.99	7.00	-0.01	Yes
7.00	7.00	0.00	Yes
7.50	7.00	0.50	No

Inspect the interactive Amazon Flow to see the extraction, calculation, condition, and CSV Blocks before creating a project.

What the price report contains

When the target branch runs, the CSV contains seven columns:

Column	Value
Product	The extracted product title
URL	The Amazon product URL supplied at the start
Price text	The price as it appeared on the page
Current price	The normalized numeric value
Target price	The threshold entered for this Flow
Delta	Current price minus target price
Status	At or below target

Keeping both Price text and Current price is useful. The original text helps you review what the page displayed, while the normalized value can be compared or reused by later Blocks.

The current starter Flow does not send an email, webhook, or push notification. It writes a cloud CSV on the matching branch and records the comparison in the run log. If you need a notification, add that output explicitly after you have verified the extraction and condition.

Set up one reliable Amazon price check

1. Use a product detail URL

Start with one public product page under amazon.de, amazon.com, or amazon.co.uk. Search-result pages, category pages, wish lists, and URLs from other Amazon domains fall outside the current input rules.

Open the page manually first. Confirm that it shows the product and offer you intend to monitor, and check that your collection and use comply with Amazon’s applicable Conditions of Use and Sale.

2. Enter a target in the displayed currency

The Flow compares numbers. It does not convert currencies. If the page shows euros, enter a euro target. If it shows pounds or dollars, use that same currency for the target.

The input accepts zero or a positive number, but a realistic purchase threshold makes the result easier to interpret. A target of 0 will rarely produce the matching branch for a normal retail product.

3. Inspect the extracted title and price

Amazon product pages can show a main offer, alternative sellers, vouchers, subscriptions, or unavailable states. Run the Flow once in Liveview and confirm that:

• the extracted title names the expected product;
• priceText contains the main price you intended to monitor;
• currentPrice is the correct numeric value;
• the selected region and offer match your target.

Do this before adding a schedule. A recurring run only repeats the current selectors and logic. It does not make an unverified extraction more reliable.

4. Check the threshold branch

Compare the visible price with your target and predict which branch should run. If the current price is at or below the target, expect a CSV. If it is above the target, no CSV is the intended result.

For a first test, you can temporarily set the target slightly above the current price to exercise the output branch. Restore your real threshold before scheduling the Flow.

5. Review the CSV

When the condition matches, open the generated CSV and compare its Product, Price text, Current price, Target price, and Delta with the page and the inputs. A successful file creation is not enough if the wrong offer was extracted.

The source Flow and its public configuration were reviewed on July 23, 2026. This article does not present that source review as a retained successful run.

6. Schedule only after a manual check

After one correct run, use Scrapeer’s Scheduling controls to repeat the Flow at the interval appropriate for your decision. Price pages can change, so treat the first scheduled results as another review point rather than assuming the selectors will remain correct forever.

When the Amazon price monitor needs repair

The Flow cannot find the product title

The page may have loaded a consent screen, access page, unavailable listing, or different layout. Inspect the browser state in Liveview. If the intended product is visible, reselect the title element and update the title selector.

The price extraction times out

Check whether the page actually shows a primary price. Products with no current offer or with several buying options may not render the same price element as the starter example. Select the exact offer you need rather than broadening the selector until it matches unrelated numbers.

The normalized price is wrong

Thousands separators and decimal marks differ by locale. Compare priceText with currentPrice. If 1.299,00 € becomes the wrong number, repair the formatting step for that storefront before relying on the comparison.

The browser shows a CAPTCHA or access page

Do not treat text from an access page as product data. Reduce the run frequency, inspect whether the page is publicly accessible in your environment, and stop if access is not permitted. The correct response is not to force the Flow past a restriction.

No CSV appears

First inspect currentPrice, targetPrice, and priceDelta. When the current price is above the target, no file is expected. If the condition should have matched, inspect the Conditional and Create CSV Blocks for the first concrete error.

When to use a different Flow

The starter Flow is a good fit for one product URL and one threshold. Build a different Flow when you need:

• several products checked in one run;
• extraction from Amazon search or category results;
• stock, seller, delivery, voucher, or subscription details;
• comparison across regions or currencies;
• a notification on every run;
• a historical price table instead of threshold-only reports.

For several URLs, introduce an explicit list or table of inputs and loop over it. Keep each product’s title, URL, price, and status in the same row. For history, append every check with a timestamp instead of creating output only on the matching branch. For notifications, decide whether you want every result or only a transition from above target to at or below target. Transition-based alerts need stored state, not just a price comparison.

If your source is a local-business search rather than a product page, read how the Google Maps leads Flow creates an enriched CSV. For a public recruiting board and spreadsheet output, use the Ashby jobs to Google Sheets guide.

Common questions

Does the Flow send a price alert?

The current starter version creates a cloud CSV and writes to the run log when the target is reached. It does not send an email or push notification. Add the notification channel you need after validating the price extraction and condition.

Which Amazon regions can I enter?

The public input accepts product URLs from amazon.de, amazon.com, and amazon.co.uk. Other Amazon domains are not accepted by the current starter configuration.

Does it monitor the price continuously?

One run performs one check. After a verified manual run, you can schedule the Flow to repeat. The schedule determines how often it checks.

Why did the run create no CSV?

The most likely reason is that the current price was above the target, which is the intended non-matching path. Inspect priceDelta and the run log before treating the absence of a file as an error.

Start with one visible comparison

The useful part of this Amazon price monitor is not a vague promise of automation. It is the visible path from one product URL to a normalized price, an explicit threshold, and a seven-column report.

Open the Amazon price-monitoring Flow to inspect those steps, or download Scrapeer and test the starter Flow in Liveview before scheduling it.