MarginSonar alert example
What a MarginSonar alert actually looks like
This sample is based on a real internal demo alert from the current monitoring workflow. It shows how price, promo, stock, and shipping signals get turned into a short operator-ready summary instead of a noisy page diff.
Sample subject line
Subject: [Garden of Life] 3 new alerts — promo, price, shipping
Run context
- Account: Garden of Life pilot demo
- Generated at: 2026-03-21T02:51:00+00:00
- Brand: Garden of Life
- Observed page: DTC homepage
- Seller / channel: Direct-to-consumer
Why this format matters
- This is the style of plain-text daily alert the pilot is designed to send: short, evidence-backed, and commercially legible.
- The goal is not to dump a raw diff. The goal is to explain what changed, why it matters, and how urgently a team should act.
- Screenshot captures and extracted text stay available as supporting evidence when a buyer wants more context.
Alert body
Criticalprice_drop
Observed price moved from $39.99 to $31.99.
A visible competitor or reseller markdown can create margin pressure and may warrant same-day review.
Routing: Immediate alert
Highpromo_added
Detected promo messaging: 20% OFF.
A new public promo can change effective price and conversion economics quickly.
Routing: Immediate alert
Highfree_shipping_threshold_changed
Free-shipping threshold wording changed.
Shipping thresholds affect conversion math and basket-building behavior.
Routing: Same-day batch
Latest extracted fields
- Price: $25.59
- Promo: 20% OFF site-wide
- Stock: out_of_stock (flagged)
- Free-shipping threshold: visible in page
What buyers typically notice first
- Multiple changes from the same page are grouped into one alert instead of generating three separate notifications.
- Severity and routing are explicit — teams know what deserves same-day review versus end-of-day batching.
- Evidence stays available behind the summary, but the top layer is readable for operators and executives alike.
Want this format pointed at your own watchlist?
The clean next step is the intake page, where you can hand over SKUs, channels, and routing context in one place before dropping into a proof-pack or pilot request.