Store Radar
Store Radar monitors business metrics — order volume, average order value (AOV), conversion rate, and payment health — and alerts you when something deviates from the store's normal patterns.
How it works
Store Radar compares current metric values against the store's own historical baselines for the same time window (weekday + hour). Alerts are triggered when deviation exceeds the threshold for a sustained period, not a single dip.
All baselines are built from the store's own history — not industry benchmarks.
Metric status indicators
| Status | Meaning |
|---|---|
| Normal (green) | Current values are within the expected range |
| Alert (pink) | A significant deviation from baseline has been sustained |
| Not enough data (yellow) | Too few orders or sessions to compare reliably — not a configuration error |
| Learning | Shoptest is still building baselines from the store's history (expect this for the first 1–2 weeks) |
What each metric tracks
| Metric | How it is calculated |
|---|---|
| Order Volume | Rolling last hour compared to the typical level for this weekday + hour, built from several weeks of history |
| AOV | Multi-hour window of paid orders (excludes POS) compared to the weekday + hour baseline |
| Conversion Rate | Online orders divided by sessions, compared to the learned baseline; uses hourly or day-level pattern depending on available data |
| Payment Health | Gateway error rate and processing failure detection |
Configure alerts
- Before anything else, make sure notification channels are configured in Settings > Notification Channels. Without a channel, alerts fire silently.
- Review all four metric statuses on every store check-in.
- Check Payment Health daily — a gateway error rate above 10% requires immediate escalation.
Quiet Hours
Suppress notifications during a defined overnight window to avoid false alerts from low-traffic periods. Monitoring checks still run and are recorded.
- Go to Store Radar > Quiet Hours.
- Set the start and end time for the store's overnight window (e.g. 2:00 AM – 6:00 AM).
- Confirm the timezone matches the store's primary market — an incorrect timezone causes quiet hours to misalign with actual overnight periods.
Subscription Batch Hours
For stores running subscription products, mark the hours when subscription apps process bulk orders. Without this, bulk processing triggers false Order Volume alerts.
- Go to Store Radar > Subscription Batch Hours.
- Review the batch grid (Mon–Sun × hour) — batch windows can be auto-detected or set manually.
- Add manual overrides if auto-detection misses a known processing time.
- Revisit this whenever the store changes subscription apps or processing schedules.
Troubleshooting
All metrics show "Not enough data" or "Learning"
- This is expected on a newly connected store. Allow 7–14 days for reliable baselines to form before acting on alerts.
False alerts during overnight hours
- Configure Quiet Hours to suppress notifications during the store's low-traffic window.
Order Volume alerts during subscription renewal cycles
- Mark the subscription processing windows in the Subscription Batch Hours grid. Use manual override if auto-detection misses them.
Payment Health shows an alert
- Check the gateway error rate immediately. If above 10%, escalate to the payment provider and the store's development team. Review failed payment transaction details if available.