At a glance
Depop Removed Listings (24h) is the alert that fires when Depop takes down any of your listings in the last 24 hours. Removals usually mean a policy or content flag: a prohibited item, a brand or counterfeit issue, a banned keyword, or a photo that breaches guidelines. Even one removal is worth investigating, because a spike can signal a pattern that risks the whole shop’s standing if it continues.
| What it counts | The number of your listings removed by Depop in the trailing 24 hours, listed individually with the affected items. |
| Sample type | Backend API data from Depop, refreshed on the standard data refresh, evaluated in real time. |
| Why it matters | A removed listing is lost revenue and a compliance signal. A sudden cluster of removals can precede stricter account-level action, so spotting it within the day lets you correct listings before the pattern hardens. |
| Reading the value | Zero is the healthy state. Any removal warrants a look at the reason; a same-day cluster is the real alarm. |
| Currency | count (removed in 24h) |
| Time window | 24H |
| Alert trigger | > 0 |
| Sentiment key | dep_alert_listing_rejection_spike |
| Roles | owner, operations |
Calculation
The card counts listings removed by Depop within a trailing 24-hour window and lists the affected items. Vortex IQ reads listing status changes from the Depop integration; the removal reasons surfaced depend on what Depop exposes for each item.Worked example
A representative reading of Depop Removed Listings (24h) for a typical branded-resale shop on Depop. On 21 Jun 26 the alert jumped from zero to four removals in one afternoon. Vortex Mind grouped them and found all four shared a brand name in the title that had been flagged for authenticity. Rather than relist blindly, the seller revised the descriptions to remove the disputed claim and added proof-of-purchase photos before relisting. No further removals followed and account standing was unaffected. To review what was taken down, ask Ask Viq for listings removed by Depop in the last day with their reasons.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
dep_total_listings | Catalogue sibling: removals shrink your active listing count. |
dep_listing_quality_score | Listing Health sibling: poor listings are likelier to be flagged. |
dep_xc_feed_rejection | Cross-channel sibling: feed-validation failures often share a root cause. |
dep_marketplace_health_score | Composite sibling: removals can pressure shop standing. |
dep_revenue_at_risk | Outcome sibling: removed listings are revenue taken offline. |
Reconciling against Depop
Where to look in Depop’s own dashboard: Depop notifies you of removals in the app and may show the reason against the affected listing. Reconcile by matching the Vortex IQ list to those notifications for the same 24-hour window. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Window boundary. The card uses a trailing 24 hours; app notifications are timestamped individually. | Marginal | Align the time window. |
| Removal vs expiry. A listing that lapsed or sold is not a removal. | Variable | Confirm the status change reason. |
| Refresh timing. A removal registers on the next refresh. | Marginal | Force a manual refresh. |