Purpose: Track competitor pricing on a recurring basis to inform pricing strategy, identify promotional patterns, and spot market shifts before they impact your sales. This SOP covers three distinct methods, each suited to different setups, budgets, and data sources.
Who this is for: Amazon sellers, ecommerce operators, and agency teams running pricing intelligence for clients.
This is the most reliable, token-efficient, and scalable method for Amazon pricing. It uses a structured API feed rather than scraping, which means consistent data formatting and no risk of being blocked.
What you need:
Step 1 — Set up your Notion tracker database.
Before your first run, decide where your pricing data will live. You can either let the workflow create a new Notion database automatically, or point it to an existing one. If you're tracking multiple keywords, I'd recommend one database per keyword so you can filter and chart cleanly over time. The database schema should include: Product Title, Date Pulled, Keyword, Marketplace, Rank, ASIN, Price, Currency, Special Offers, Bought Past Month, Rating, Review Count, Amazon's Choice flag, and Delivery Info.
Step 2 — Run the flow manually first.
Before scheduling anything, run the full flow manually at least once in a Cowork task. Write out the full set of instructions as your prompt — this is important because you're going to reuse this same prompt almost verbatim for the scheduled task later. Here's an example:
"Track competitor pricing for the keyword 'magnesium glycinate' on the US Amazon Marketplace using the DataForSEO MCP. Call merchant_amazon_products_live_advanced with location_name 'United States' and language_code 'en_US'. From the results, filter to only organic results (type 'amazon_serp', exclude anything marked 'amazon_paid' or sponsored). Take the top 5 by rank_group order. For each result, extract: rank position, ASIN (data_asin), product title, price (price_from and currency), special offers (join with ' | ' if multiple, record 'None' if absent), bought_past_month, rating value, review count, Amazon's Choice status, and delivery info. Present in a table for my review. After I confirm, save to my Notion tracker database at [your Notion database URL], one row per ASIN, with today's date as the Date Pulled."
Verify the DataForSEO MCP tool parameters before calling — use tool_search to confirm the exact parameter names, as MCP wrapper parameter names don't always match the REST API documentation.
Step 3 — Verify the Notion output.
Go into Notion and confirm that all rows populated correctly. Check that the Date Pulled field has today's date, prices are in the right currency, and special offers captured accurately (or show "None" if there weren't any). This is your reference point — if future automated runs drift, you'll compare against this.
Step 4 — Convert to a scheduled task.