Request type
Competitor price monitoring
Check a product set every morning. See what changed.
Planned
Planned. Activates with scheduling.
Who asks for this
Ecommerce teams pricing against a competitor set.
Say it like this
“Check these 120 product URLs every morning and show me any price or stock change since yesterday.”
What you supply
- Product URLs or a saved workflow
- Frequency and timezone
- Spending limits
What you get back
Your table · 4 rows shownIllustrative
| product_nametext · collected | competitortext · collected | price_yesterdaycurrency · collected | price_todaycurrency · collected | changecurrency · derived | in_stockboolean · collected |
|---|---|---|---|---|---|
| Linen Crew Tee | Store A | 38.00 | 34.00 | -4.00 | true |
| Canvas Weekender | Store A | 148.00 | 148.00 | 0.00 | true |
| Wool Beanie | Store B | 32.00 | 32.00 | 0.00 | false |
| Ripstop Shell | Store B | 210.00 | 189.00 | -21.00 | true |
collected from the page · derived at no cost · extra work raises the estimate
Workflow
How the agent handles it.
- 1
You save a product workflow and pick a frequency.
- 2
Each run reuses the plan.
- 3
We compare with the last run.
- 4
You see new, changed, and gone.
- 5
We notify you on completion or failure.
Cost and limits
What moves the price, and where the answer can be no.
Cost drivers
- Products per run
- Frequency
- Stock checks need a product-page visit
Where we say no first
- Runs never overlap. A slow run waits.
- History retention is capped.
Early access
Want competitor price monitoring?
Describe the sources, the columns, and roughly how many rows.