At a glance
Bonanza Removed Listings (24h) is a real-time alert that counts item listings Bonanza has removed or rejected on your booth in the last 24 hours. Removals usually trace to a policy issue, a missing required attribute, or a feed-validation failure on the way to Google Shopping. It sits in the Nerve Centre alert layer and pairs with the listing-health and feed-validation cards below so you can see why listings dropped and how many are at risk.
| What it counts | Item listings removed or rejected by Bonanza on your booth within the last 24 hours. |
| Sample type | Backend API data from Bonanza, refreshed on the standard data refresh. |
| Why it matters | A removed listing stops selling on Bonanza and drops out of Bonanza’s Google Shopping distribution, so a spike is direct lost exposure. Owners and operations need to know the moment listings start coming down. |
| Reading the value | Zero is the healthy state. Any non-zero count is actionable - open the alert to see which listings dropped and the removal reason. |
| Currency | number |
| Time window | 24H |
| Alert trigger | >0 |
| Sentiment key | bon_alert_listing_rejection_spike |
| Roles | owner, operations |
Calculation
This is a real-time alert rather than a rolling metric. Vortex IQ tracks the listing status reported by Bonanza and counts any item listing that moved to a removed or rejected state in the trailing 24-hour window. The alert fires whenever that count rises above zero and surfaces the affected listings with their removal reason. See the At a glance summary above for the trigger and the worked example below for a typical fire.Worked example
A representative reading of Bonanza Removed Listings (24h) for a typical merchant on Bonanza. On 14 Mar 26 a booth wakes up to a removed-listings count of 12 after an overnight feed push stripped a required attribute from a category of apparel listings. The merchant opens the alert, sees all 12 share the same missing-attribute reason, repopulates the attribute, and re-submits the listings, which return to active and rejoin Google Shopping distribution. Caught early, the booth loses only a few hours of exposure rather than a full day. Vortex Mind traces the upstream cause to the overnight feed change, and Ask Viq lets the owner ask in plain English which categories were hit.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
bon_attribute_completeness | Listing Health sibling: Required-Attribute Completeness. |
bon_xc_feed_rejection_vs_listings | Cross-Channel sibling: Listings Failing Feedonomics Validation. |
bon_avg_bra_score | Listing Health sibling: Average BRA Score (Buy-it-Right Asking). |
bon_listings_active | Listings sibling: Active Listings. |
bon_importer_sync_health | Executive sibling: Importer Sync Health. |
Reconciling against Bonanza
Where to look in Bonanza’s own dashboard: Check your Bonanza booth under selling > items, where removed or rejected listings are flagged with a status and reason, and review any feed or Google Shopping eligibility notices. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. Vortex IQ uses a trailing 24-hour window by default; Bonanza dashboards may use calendar days. | Variable | Match the period range. |
| Time zone. Bonanza uses account time zone; Vortex IQ aligns to merchant reporting time zone. | Marginal | Confirm time zone match. |
| Filter scope. Profile-level filters (booth, channel, test orders) may narrow the Vortex IQ view. | Variable | Match filter settings. |