> ## 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. # Vinted Removed Listings (24h), Vinted > Vinted Removed Listings (24h) for Vinted 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 > **Vinted Removed Listings (24h)** is a listing-integrity alert tracked from Vinted data. It counts items Vinted has taken down in the last day, typically for catalogue, prohibited-item, or policy reasons. A removal spike often signals a systematic issue, a brand or category that tripped a rule, a bulk upload that breached guidelines, or an account-level flag, and each removed listing is lost visibility and lost potential sales until corrected or relisted. | | | | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | The number of your listings removed by Vinted in the trailing 24 hours. Each removal is listed so you can see which items and why. | | **Sample type** | Backend API data from Vinted, evaluated over a trailing 24-hour window. | | **Why it matters** | Removals erase listings from search and can escalate to account restrictions if a pattern persists. Catching a spike early lets you correct the root cause before it spreads across the catalogue. | | **Reading the value** | Any value above zero warrants a look. A single removal may be a one-off rule trip; a cluster points to a systematic catalogue or policy issue. | | **Currency** | count | | **Time window** | `24h` | | **Alert trigger** | Fires when one or more listings are removed by Vinted within the trailing 24 hours. | | **Sentiment key** | `vin_alert_listing_rejection_spike` | | **Roles** | owner, operations | ## Calculation Calculated automatically from your Vinted data. Vortex IQ tracks listing status transitions and counts items moved to a removed state by Vinted within the trailing 24-hour window. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading. ## Worked example *A representative reading of **Vinted Removed Listings (24h)** for a typical Pro seller on Vinted.* The card normally sits at zero. On 18 Mar 26 a bulk upload of forty items goes live and by the next morning the card shows seven removals: all seven were a sportswear line whose images carried a logo overlay Vinted flagged, plus one item that landed in a restricted category. The fix is to re-edit the photos to remove the overlay and recategorise the restricted item, then relist. The structural lesson is to pre-check imagery rules before the next bulk upload. For deeper investigation, use Vortex Mind to see whether removals cluster by brand, category, or upload batch; for natural-language exploration, ask Ask Viq. ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | ------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- | | [`vin_attribute_completeness`](/nerve-centre/kpi-cards/vinted/brand-size-condition-completeness) | Listing-health sibling: incomplete attributes that can trip removals. | | [`vin_total_listings`](/nerve-centre/kpi-cards/vinted/total-listings) | Listing-health sibling: the catalogue base removals draw down. | | [`vin_active_listings`](/nerve-centre/kpi-cards/vinted/active-listings) | Listing-health sibling: live listings affected by takedowns. | | [`vin_xc_feed_rejection_vs_listings`](/nerve-centre/kpi-cards/vinted/listings-failing-feedonomics-validation) | Cross-channel sibling: feed validation failures that precede removals. | | [`vin_revenue_at_risk`](/nerve-centre/kpi-cards/vinted/revenue-at-risk) | Executive sibling: revenue exposed when listings disappear. | ## Reconciling against Vinted **Where to look in Vinted's own dashboard:** Vinted notifies sellers of removals through the in-app notifications and the affected item's status, and surfaces policy reasons where a rule was breached. Reconcile by reviewing recent removal notices against this card's 24-hour list. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | -------------------------------------------------------------------------------------------------------------------------- | --------- | ------------------------------------------ | | **Window boundary.** Vortex IQ uses a rolling 24-hour window; in-app notices accumulate without a fixed window. | Variable | Compare against the same 24-hour span. | | **Status timing.** A removal notice may appear before the listing status updates in the API. | Marginal | Allow for short notice-to-status lag. | | **Self-deletions excluded.** Items you delete yourself are not removals; Vortex IQ counts only Vinted-initiated takedowns. | Lower | Exclude your own deletions when comparing. | **Cross-connector reconciliation:** complement with attribute completeness and feed validation for the full integrity picture. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does Vinted Removed Listings (24h) update?** It refreshes on the standard data refresh (typically every 30-60 minutes for live integrations) and reports over a rolling 24-hour window. Force a manual refresh after relisting to confirm the count clears. **Q: Why does my Vinted dashboard show a different number?** The common reasons are window-boundary differences (rolling 24 hours versus accumulating notices), short notice-to-status lag, and the fact that items you delete yourself are not counted as removals. Align the window and exclude self-deletions before assuming a real divergence. **Q: How does Vinted Removed Listings (24h) relate to other listing-health metrics?** A removal spike often traces back to attribute or feed-validation issues, so track it alongside attribute completeness and the feed-validation card. The removals card is the symptom; those siblings often hold the cause. **Q: Can I customise the alert threshold?** By default the card flags any removal above zero, but the spike sensitivity is configurable per profile in the Sensitivity tab. Raise it if occasional single removals are normal for your catalogue volume. *** ### Tracked live in Vortex IQ Nerve Centre *Vinted Removed Listings (24h)* is one of hundreds of KPI pulses Vortex IQ tracks across Vinted 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.