Refreshing cached metrics
Watchlist rows show cached metrics — the SellerScore and sub-scores as of the last refresh. Cache age is shown on each row. When you want fresh numbers, refresh manually.
In this guide:
- When to refresh
- How to refresh
- What gets refreshed
- Best-effort behavior on watchlist load
When to refresh
A watchlist row is most useful when its cache is recent. Practical thresholds:
- < 1 day: Probably fine for casual review.
- 1–3 days: Refresh before you act on it.
- > 3 days: Definitely refresh; data may have shifted.
- > 1 week: Don’t trust the score; refresh first.
Stale rows are surfaced via the age column. Sort by age (stale-first) to triage refreshes.
How to refresh
Three ways:
- Single-row refresh. Tap the ⟳ icon on any row.
- Pull-to-refresh the whole list (best-effort — see below).
- Bulk-refresh stale items. Top-right of the watchlist → Refresh stale (> 30 min).
A refresh re-fetches:
- Sell price.
- BSR.
- Reviews + ratings.
- Fees (FBA, referral).
- All six sub-scores.
- Data quality.
- Score reasoning (if cache is over 48 hours old).
The refresh does not regenerate the AI brief on every refresh — that’s a 48-hour cache regardless of how often you refresh metrics.
Cost
Free today. Watchlist refresh is bundled into your subscription with no per-refresh credit charge.
In a future release, if scaling demands it, refresh may move to a small credit cost (something like 0.1 credit per refresh — much cheaper than a full new search). We’ll communicate well in advance if this changes.
Best-effort behavior on watchlist load
When you open the watchlist, Hilal best-effort refreshes any rows whose cache is over 30 minutes old, in the background. You don’t pay for these refreshes; you just see fresher numbers when they finish.
This means:
- You typically don’t need to manually refresh — opening the watchlist often does it for you.
- If the upstream data sources are temporarily unavailable, the load doesn’t fail; rows just show their previously-cached numbers.
What if a refresh shows nothing?
Two reasons a refresh might leave a row’s metrics unchanged:
- Cache was fresh. If a row was refreshed within the last few minutes, the system may skip the refetch. Wait, then retry.
- Upstream outage. Some data sources (Google Trends, mostly) have intermittent availability; the refresh may have completed but with the same numbers it had before.
If a refresh consistently fails (the row gets a yellow “couldn’t refresh” badge), the product may have been delisted from Amazon — open the detail and check the “Open on Amazon” link.
Coming soon: scheduled / automatic refresh
Today, refreshes are manual or best-effort-on-load. Coming soon:
- Scheduled refreshes — choose a per-row refresh cadence (daily, weekly).
- Automatic refresh on stale — when a watchlist row crosses an age threshold, refresh in the background and surface a “refreshed” indicator.
→ Historical tracking + alerts (coming soon) covers the related forward-looking work on persisted history and threshold-based push notifications.