Feed alerts and disapproval risk
How to read a feed finding, why Rabbot calls it disapproval risk rather than a verdict, and what to do when one lands.
What “disapproval risk” means
Rabbot’s feed cross-check compares your product feed against your live storefront and flags where they disagree. A finding from that cross-check is disapproval risk: the same kind of gap a channel’s own review catches products out on, read off your own data. The point of the framing is timing. You get the warning before a decision is made, while you can still fix it.
What a finding tells you
Each finding names three things: the product, the field where the feed and the page disagree (price, availability, a required identifier, or missing product data), and what changed. That is enough to go and fix the source, usually a stale sync, a manual price edit, or an app that stopped updating stock correctly.
How fast an alert reaches you
Rabbot re-checks a product as soon as your store reports a change to it, sweeps your full catalogue daily, and runs its channel checks daily as well. A mismatch that opens on a Tuesday is a finding on Tuesday, and it reaches you the same day: one email when it opens, plus a Slack post if the finding is critical and you are on a paid plan with Slack set up. A missing-product-data finding is a warning rather than a critical one, so that one takes the email route only. The weekly digest is a separate roundup of what is still open, not a same-day route. The Notifications section covers both.
What to do when a finding lands
Start with the product named in the finding. Check the field flagged, usually price or stock, against what your feed is actually sending. If a supplier app or a manual edit caused the drift, correct it at the source rather than in Rabbot, since Rabbot reflects what your store and feed report rather than storing its own copy of your catalogue.
Once you fix the underlying data, the next cross-check picks up the correction and the finding clears on its own.
If you disagree with a finding
Some flagged differences are intentional, a temporary price change during a sale, for example. Use the option covered in Dismiss as intentional to tell Rabbot the gap is expected. Rabbot then stops raising that finding on that product for as long as the gap stands, whatever the numbers do next. It comes back only once the feed and the page agree again, closing the finding, and then drift apart later.
Which channels this covers
Feed alerts apply to any channel you have added in Settings: Google, Meta (Facebook & Instagram), and, for stores in the pilot it is open to, TikTok Ads (Beta). The cross-check itself is one check rather than one per channel, so a product whose feed and page disagree raises a single finding, however many channels you have connected.
Still stuck? Email support@rabbot.ai and a real person reads it.