Watch competitor prices weekly, only speak up when something moves
Recipe template · not yet tested on this site
This page is a recipe template, not yet tested here. Run logs, tokens and time go in after re-testing; until then no estimated numbers are filled in.
When to use
Competitor pricing pages get checked by hand every week. Miss one and you miss the repricing window, yet only two or three SKUs usually change.
Preparation
- Host version
- To fill (record the exact rc version when testing)
- Model
- To fill
- Mode / permissions
- Standard mode + modify-within-workspace is enough to start
- Plugins required
- None (add name & version after testing if used)
- Input materials
- Keep in a separate workspace; back up originals first
Full instruction
Run a competitor price sweep every Monday morning.
The watch list holds public product page URLs. Steps:
1. Open each page and read only publicly visible price and specs, recording the capture time. If a page fails or demands a login, record 'capture failed + reason' and do not attempt any workaround.
2. Compare against the previous snapshot and output only what changed: SKU, old price, new price, delta, URL.
3. If nothing changed, output a single line 'no changes this week' with the sweep timestamp.
4. Save the result as this week's snapshot, keeping the previous ones.
5. Finish with: pages swept, succeeded, failed, and each failure reason.
Output a table. No analysis, no recommendations.Run log
| Item | Value | Note |
|---|---|---|
| Time spent | to be tested | |
| Result | to be tested | |
| In / out tokens | to be tested | |
| Leftovers | to be tested |
Output
After a successful run, list files and screenshots here, and note whether originals changed.
Acceptance checklist
Tap to tick each item off as you verify.
- Every changed SKU is listed and its old price matches the previous snapshot
- Failed pages are listed separately, never silently skipped
- Pages swept equals succeeded plus failed
- Snapshot updated, earlier snapshots still traceable
- No workaround attempted against login walls or anti-bot pages
Failures & boundaries
- When prices live in images or are rendered by script, no number is readable and the page lands in the failure list
- Only publicly visible prices are covered; member pricing behind a login is out of scope
- Fetch frequency and compliance are the operator's responsibility; no proxy pools or bypasses are offered here
- This is a recipe template; it has not been run end to end on this site yet
- Blocked on: Needs real competitor pages with a stable, long-term price source. We have no such target, and a synthetic page cannot reproduce the noise that decides this recipe: caching, A/B tests, and regional pricing.