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 | Listing-health sibling: incomplete attributes that can trip removals. |
vin_total_listings | Listing-health sibling: the catalogue base removals draw down. |
vin_active_listings | Listing-health sibling: live listings affected by takedowns. |
vin_xc_feed_rejection_vs_listings | Cross-channel sibling: feed validation failures that precede removals. |
vin_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. |