> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Rejected / Reviewing Listings, Fruugo > Rejected / Reviewing Listings for Fruugo stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Card class:** [Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Marketplace](/nerve-centre/connectors#connectors-by-type) ## At a glance > **Rejected / Reviewing Listings** is the count of listings currently held in Rejected or Reviewing state, neither of which can sell yet. Because Fruugo localises and distributes only listings that clear review, every listing stuck here is lost shelf space across all the country marketplaces it would otherwise reach. Sitting in the Listing Health category, it is the queue owners and operations clear first, since each entry is revenue that cannot ring up until the block is resolved. | | | | --------------------- | --------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | Listings currently in Rejected or Reviewing state, not yet eligible to sell on any Fruugo marketplace. | | **Sample type** | Live snapshot of blocked-listing count. | | **Why it matters** | Every entry is shelf space and potential revenue sitting idle until the rejection reason or review is cleared. | | **Reading the value** | Lower is better, with zero the goal. Any positive number is a queue to work down; a spike usually traces to one feed event. | | **Currency** | count | | **Time window** | `RT` | | **Alert trigger** | `>0` | | **Sentiment key** | `fru_rejected_listings` | | **Roles** | owner, operations | ## Calculation The card counts the listings whose current Fruugo status is Rejected or Reviewing, taken as a live snapshot, so it reflects exactly what is blocked from selling at this moment. Listings that are Active are excluded, and a listing clearing review or having its rejection resolved drops out of the count on the next status refresh. ## Worked example *A representative reading of **Rejected / Reviewing Listings** for a typical merchant on Fruugo. Suppose the card jumps from 4 to 57 on 12 Mar 26, tripping the configurable above-zero alert hard (illustrative figures). A spike that size is rarely 57 separate problems. Vortex Mind investigates and finds 50 of them share one rejection reason, a missing required attribute introduced by a feed mapping change that morning, while the other seven are genuine review holds. Ask Viq "what is the most common reason my listings were rejected today" returns the dominant reason and the affected SKU list in plain English, so operations can fix one feed mapping and clear fifty listings in a single pass rather than triaging them one by one.* ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | -------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | | [`fru_alert_listing_rejection_spike`](/nerve-centre/kpi-cards/fruugo/fruugo-rejected-listings-24h) | Listing Health sibling: Fruugo Rejected Listings (24h). | | [`fru_active_listings`](/nerve-centre/kpi-cards/fruugo/active-listings) | Listing Health sibling: Active Listings (across all locales). | | [`fru_total_listings`](/nerve-centre/kpi-cards/fruugo/total-listings) | Listing Health sibling: Total Listings. | | [`fru_vat_compliance_gaps`](/nerve-centre/kpi-cards/fruugo/listings-missing-vat-metadata) | Listing Health sibling: Listings Missing VAT Metadata. | | [`fru_attribute_completeness`](/nerve-centre/kpi-cards/fruugo/required-attribute-completeness) | Listing Health sibling: Required-Attribute Completeness. | ## Reconciling against Fruugo Merchant Portal **Where to look in Fruugo's own dashboard:** Open the Fruugo Merchant Portal and review the products or listings management area, filtering by Rejected and Reviewing status. The portal usually shows the rejection reason against each listing, which is the authoritative detail this card summarises into a count. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | -------------------------------------------------------------------------------------------------------------------------- | ---------------- | ------------------------------------------------------------------------------------------------------- | | Snapshot timing relative to the twice-daily feed import | Either | Re-check after the next import cycle; rejections and review clearances often land at import boundaries. | | Status grouping: Vortex IQ combines Rejected and Reviewing into one count, the portal may list them under separate filters | Either | Sum both portal filters before comparing to this single number. | | A listing was resolved in the portal but the status has not refreshed into the card yet | Vortex IQ higher | Allow for the next status refresh; recently cleared listings drop out shortly after. | **Cross-connector reconciliation:** If the count spikes, cross-reference [`fru_alert_listing_rejection_spike`](/nerve-centre/kpi-cards/fruugo/fruugo-rejected-listings-24h) and [`fru_attribute_completeness`](/nerve-centre/kpi-cards/fruugo/required-attribute-completeness), then let Vortex Mind group the rejections by shared reason and trace them back to the originating feed change. ## Known limitations / merchant FAQs **Q: How often does this number update?** It refreshes in near real time as a live snapshot, but status changes are driven by Fruugo's twice-daily feed import re-evaluating your listings, so the count tends to move at import cycles rather than continuously. **Q: Why does the Fruugo Merchant Portal show a different number?** The usual causes are status grouping and refresh timing. This card combines Rejected and Reviewing into one count, while the portal may list them under separate filters, and a listing you just resolved in the portal may take until the next refresh to drop out here. **Q: How does this relate to the 24h rejection spike card and Required-Attribute Completeness?** This card is the live standing count, [`fru_alert_listing_rejection_spike`](/nerve-centre/kpi-cards/fruugo/fruugo-rejected-listings-24h) flags a sudden surge in the last day, and [`fru_attribute_completeness`](/nerve-centre/kpi-cards/fruugo/required-attribute-completeness) often explains why listings were rejected in the first place. Read together they show the size, the velocity, and the cause. **Q: Can I customise the alert threshold?** Yes. The default fires whenever the count is above zero, since any blocked listing is lost shelf space, but the threshold is configurable. Larger catalogues sometimes set a small tolerance so only a meaningful queue pages the team, while merchants who run a tight catalogue keep the zero trigger. *** ### Tracked live in Vortex IQ Nerve Centre *Rejected / Reviewing Listings* is one of hundreds of KPI pulses Vortex IQ tracks across Fruugo and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.