At a glance
Mercari Suspended Listings (24h) counts how many of your listings Mercari took down in the last day for policy reasons. A sudden spike is rarely random, it usually points to a feed or compliance problem hitting many listings at once.
| What it counts | Listings suspended by Mercari in the trailing 24 hours, for reasons such as prohibited items, intellectual-property infringement, or other policy violations. |
| Sample type | Backend API data from Mercari, refreshed on the standard data refresh. |
| Why it matters | Suspended listings stop selling instantly, and a cluster of suspensions can flag your account for closer review. Catching a spike early lets you fix the root cause before it spreads or escalates. |
| Reading the value | Zero is normal. Any count above zero deserves a look; a sharp jump signals a systemic feed or compliance issue rather than a one-off takedown. |
| Currency | number |
| Time window | 24H |
| Alert trigger | >0 |
| Sentiment key | mer_alert_listing_rejection_spike |
| Roles | owner, operations |
Calculation
The card counts listings whose Mercari status moved to suspended within the trailing 24-hour window. It reads the live listing state returned by the Mercari integration and tallies only those flagged in the last day, so the figure rolls forward continuously as older suspensions age out of the window and new ones enter.Worked example
A representative reading of Mercari Suspended Listings (24h) for a typical Mercari reseller. Suppose you bulk-list a batch of branded sneakers and, illustratively, 12 of them are suspended overnight for suspected IP infringement on the brand name in the title. The card jumps from 0 to 12 and the alert fires on>0. That pattern, many listings of one type going down together, tells you it is a feed or wording issue, not a random takedown. The action is to review the suspension reason, correct the offending titles or attributes, and resubmit. Cross-reference mer_listings_active to see the dent in your live inventory and mer_total_revenue to gauge the sales exposure. Vortex Mind traces the upstream cause, for example a single template field that breached policy across the batch, and Ask Viq answers plain-English questions like “which listings were suspended today and why”.
Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
mer_listings_active | See how far suspensions have cut into your live, sellable inventory. |
mer_listing_quality_score | Poor listing quality often correlates with policy takedowns. |
mer_brand_completeness | Mislabelled brand attributes are a common IP-suspension trigger. |
mer_total_revenue | Quantify the sales exposure created by the removed listings. |
mer_listings_expiring | Pair takedowns with natural expiry to see total at-risk inventory. |
Reconciling against Mercari
Where to look in Mercari’s own dashboard: In the Mercari app or web, open your Listings and filter to inactive or removed items, and check your notifications or inbox for the takedown messages that explain each suspension. Compare that list against the count the alert reports. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. This card counts a trailing 24 hours; Mercari may group suspensions by calendar day or show them all-time. | Variable | Match the period range. |
| Time zone. A suspension near midnight can fall inside or outside the 24-hour window depending on the account time zone. | Marginal | Confirm time zone match. |
| Filter scope. Profile filters may include or exclude certain listing types from the count. | Variable | Match filter settings. |