At a glance
Fruugo Rejected Listings (24h) is a live alert surface counting listings Fruugo newly rejected in the last 24 hours. A spike is the earliest warning that a feed regression or policy breach has slipped through, before it spreads across every country locale Fruugo distributes to. Because one feed fault can reject the same SKU in many markets at once, even a small count can mask a large blast radius. The alert fires on any rejection above zero, so a clean board is the only healthy state.
| What it counts | Listings moved into a Rejected state by Fruugo within the trailing 24 hours. |
| Sample type | Live alert list, one row per newly rejected listing |
| Why it matters | Rejections remove listings from sale and signal a feed or policy fault that can cascade across locales if left unchecked. |
| Reading the value | Zero is healthy. Any count is a live regression; rows show the SKU, the affected locales, and Fruugo’s stated rejection reason. |
| Currency | count |
| Time window | 24H |
| Alert trigger | >0 |
| Sentiment key | fru_alert_listing_rejection_spike |
| Roles | owner, operations |
Calculation
The card counts listings that transitioned into Fruugo’s Rejected state during the trailing 24-hour window and groups them by the rejection reason Fruugo returns. Because a single source product fans out into per-country, per-language listings, one upstream fault can produce many rejection rows. The window resets on a rolling basis so a fresh spike stands out from older, already-handled rejections.Worked example
A representative reading of Fruugo Rejected Listings (24h) for a typical merchant on Fruugo. On 12 Mar 26 the card jumps from 0 to 18 rejections overnight (illustrative) after a feed transform stripped the HS commodity code from a product group, tripping Fruugo’s VAT distribution rule across the German, French, and Dutch locales. The operations lead catches it on the morning board rather than from a drop in orders days later. Vortex Mind investigates which feed change introduced the fault and which locales are hit, and Ask Viq answers “what reason is driving today’s rejections” in plain English so the team fixes the BigCommerce source once and clears all 18 in the next import.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
fru_rejected_listings | Listing Health sibling: Rejected / Reviewing Listings. |
fru_feed_ingestion_health | Listing Health sibling: Feed Ingestion Success (last 24h). |
fru_vat_compliance_gaps | Listing Health sibling: Listings Missing VAT Metadata. |
fru_xc_feed_rejection_vs_listings | Cross-channel sibling: Listings Failing Feedonomics Validation. |
fru_alert_account_health_drop | Nerve Centre alert: Feed Ingestion / VAT-Gap / Cancel Threshold. |
Reconciling against Fruugo Merchant Portal
Where to look in Fruugo’s own dashboard: Open the Fruugo Merchant Portal and filter the listing status view to Rejected, then sort by the most recent status change to isolate the last 24 hours. The rejection reasons shown there match the reasons Vortex IQ groups by, but the Portal does not raise a spike as a single live alert. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Portal counts all current rejections; this card counts only the trailing 24 hours | Vortex IQ lower | Compare against the Portal’s all-time rejected total, not just the recent slice. |
| A rejection was resolved and re-accepted within the window | Vortex IQ higher | Re-check the listing status; resolved items clear on the next import. |
| Portal status lags the latest ingestion result | Either | Wait for the Portal to publish the newest import before reconciling. |
fru_rejected_listings for the full standing backlog and fru_xc_feed_rejection_vs_listings to see whether the cause sits upstream at the Feedonomics validation stage, and let Vortex Mind trace the regression to its source.
Known limitations / merchant FAQs
Q: How often does this card update? It refreshes on each twice-daily Fruugo ingestion and continuously as listing statuses change, with a rolling 24-hour window. Q: Why might the Fruugo Merchant Portal show a different picture? The Portal shows the full standing set of rejected listings, while this card isolates only those rejected in the last 24 hours. Portal status can also lag the newest import briefly. Q: How does this relate to the sibling cards? This card is the 24-hour spike detector;fru_rejected_listings holds the full backlog, and fru_xc_feed_rejection_vs_listings shows whether the rejections originate upstream in Feedonomics validation.
Q: Can I customise the alert threshold?
The default fires on any rejection above zero. You can raise the threshold to a count that matches your catalogue size or scope it to specific locales if you expect routine low-level churn.