> ## 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. # Suspended Listings, OnBuy > Listings OnBuy has hidden from search until issues are fixed, direct revenue blocker. How to read it, why it matters, and how to act on it. **Metrics type:** [Key Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Marketplace](/nerve-centre/connectors#connectors-by-type) > Listings OnBuy has hidden from search until issues are fixed, direct revenue blocker. ## At a glance > Live count of OnBuy listings hidden from buyer-side search until the seller fixes the underlying issue. The single most reactive lever for OnBuy revenue: fixing a suspended hero SKU can move the headline by 5 to 20% within a week. | | | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | `COUNT(listings WHERE status = 'suspended')` from `GET /v2/listings`. Suspension reasons fall into image quality, missing required attributes, MAP / RRP policing, supplier price-mismatch, and brand-gating. | | **API endpoint** | `GET https://api.onbuy.com/v2/listings?status=suspended`. Paged at 100 per call; suspension reason in `suspension_reason` field. | | **Currency** | n/a (count). Per-listing revenue exposure tracked in [`onbuy_revenue_at_risk`](/nerve-centre/kpi-cards/onbuy/revenue-at-risk). | | **Tax / fees** | n/a. | | **Refunds** | n/a. | | **Cancellations** | n/a. | | **Channel scope** | OnBuy only. | | **Time window** | `RT` (real-time count). Polled every 15 minutes. | | **Alert trigger** | `>0`. Even one suspended listing is actionable; this is a "to-do list" card, not a "trend" card. | | **Sentiment key** | `missing_attrs`. | | **Suspension types** | image\_quality (\~40% of cases), missing\_attribute (\~25%), price\_policing (\~15%), brand\_gating (\~10%), other (\~10%). Distribution from anonymised aggregate seller data. | | **Recovery time** | 24 to 72 hours after fix is submitted. OnBuy reviews queued. | | **Roles** | owner, operations. | ## Calculation Calculated automatically from your OnBuy data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading. ## Worked example **A small UK fashion accessories seller, snapshot at 27 Apr 26 09:00 BST.** The seller has 240 active listings on OnBuy and the alert opened with "5 suspended" overnight. | Listing ID | SKU | 30D velocity | ASP | Suspension reason | Fix | | ---------- | --------------------- | ------------ | --- | ------------------------------------------- | --------------------------------------- | | OB-114902 | scarf-charcoal-wool | 18 / mo | £24 | image\_quality (background not white) | Re-shoot on white seamless paper | | OB-114921 | hat-fedora-tan | 12 / mo | £35 | missing\_attribute (no `material`) | Add material attribute in console | | OB-115044 | wallet-black-leather | 9 / mo | £42 | price\_policing (Amazon UK price 18% lower) | Match price or raise dispute with OnBuy | | OB-117210 | belt-brown-30mm | 4 / mo | £19 | image\_quality (resolution \<1000px) | Replace with 1000x1000 image | | OB-119884 | bracelet-silver-chain | 2 / mo | £16 | missing\_attribute (no `gender`) | Add gender attribute | ```text theme={null} Total suspended count 5 Combined 30D velocity loss 45 orders Combined revenue exposure (gross) £1,316 / 30D Days to fix (in-house) ~4 hours total Days to OnBuy reinstate after fix 24-72h Expected revenue recovery £900-1,100 within 30D ``` **What it means for this seller.** Five suspensions is a lot for a 240-listing catalogue (\~2%). But the fix is fast: a half-day of work clears all five and recovers roughly £1,000 of monthly revenue, equivalent to roughly 8% of their OnBuy take. The price-policing case is the only one needing strategic thought, if Amazon UK genuinely sits 18% below their OnBuy listing the long-term answer is either matching the Amazon price (and accepting the lower margin) or removing the listing from Amazon (which is rarely an option). The other four are pure ops: image standards and attribute completeness. The key insight: had this seller been monitoring [`onbuy_alert_suspension`](/nerve-centre/kpi-cards/onbuy/listings-suspension-burst) (the 24h burst alert), they would have seen the suspensions land overnight and could have actioned them by 11am instead of finding out via the daily Vortex digest. ## Sibling cards merchants should reference together | Card | Why it matters next to Suspended Listings | What the combination tells you | | ------------------------------------------------------------------------------------------ | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- | | [Revenue at Risk](/nerve-centre/kpi-cards/onbuy/revenue-at-risk) | The £ value of suspensions. Ranks them by impact, not just count. | High count + low risk = many low-velocity listings; low count + high risk = a hero SKU got hit. | | [Listings Suspension Burst (24h)](/nerve-centre/kpi-cards/onbuy/listings-suspension-burst) | New entries to this bucket in the last 24h. | Burst >2 in 24h = category policy change, not random; engage OnBuy seller support before fixing one-by-one. | | [Active Listings](/nerve-centre/kpi-cards/onbuy/active-listings) | The denominator. | Suspended as % of active. Above 3% = systemic ops issue. | | [Total Revenue](/nerve-centre/kpi-cards/onbuy/total-revenue) | The downstream effect. | Sustained suspensions correlate with 5 to 20% revenue drag depending on which listings hit. | | [OnBuy vs DTC Price Gap](/nerve-centre/kpi-cards/onbuy/onbuy-vs-dtc-price-gap) | Diagnoses price\_policing suspensions. | If suspensions cluster on listings with a wide DTC-OnBuy gap, OnBuy is enforcing price parity rules. | | [Catalogue Drift vs Amazon UK](/nerve-centre/kpi-cards/onbuy/catalogue-drift-vs-amazon-uk) | Diagnoses cross-marketplace policing. | Drift on a suspended listing = supplier or rights-holder enforcement, not ops issue. | | [Listing Quality Score](/nerve-centre/kpi-cards/onbuy/listing-quality-score) | The leading indicator. | Listings scoring \<60 are 4x more likely to suspend within 90 days. | | [eBay Suspended Listings](/nerve-centre/ebay/ebay_suspended_listings) | Peer marketplace comparison. | If both eBay and OnBuy suspended the same brand, the issue is rights-holder driven, not platform-specific. | ## Reconciling against the vendor's own dashboard **Where to look in OnBuy's own dashboard:** > **OnBuy Seller Console (`https://seller.onbuy.com`) -> Listings -> Filter: Status = Suspended** The list shows each suspended listing with its `suspension_reason` field, exactly the data we surface. OnBuy adds a "Reinstate" button per listing that opens an inline correction form for the most common fixes (image upload, attribute entry). **Why our number may legitimately differ from the Seller Console:** | Reason | Direction | Why | | ------------------------- | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Sync lag** | Ours lower for newly-suspended | Our poll is every 15 minutes; new suspensions can land in the Console first. | | **Reinstatement lag** | Ours higher after fix submission | After you submit a fix, the Console updates immediately to "Pending review"; OnBuy's API status flag flips only once review completes (24 to 72h). | | **Status taxonomy** | Either | OnBuy distinguishes "Suspended" (auto-suspended by algorithm) from "Removed" (manual takedown by seller-support). We count both as suspended; the Console separates them. | | **Bulk-suspended events** | Same | Category-wide policy changes can mass-suspend. The number can spike by 50+ in a single sync; this is rare but real. | **Internal identity (within OnBuy):** `onbuy_active_listings + onbuy_suspended_listings + onbuy_inactive_listings = onbuy_total_listings` If the three components do not sum to the total, raise a sync issue. ***
Documentation cross-reference (for agencies running multiple platforms) The "suspended listings" concept is universal to marketplaces but with different mechanics: * [`ebay.ebay_suspended_listings`](/nerve-centre/ebay/ebay_suspended_listings) * [`amazon.amazon_suppressed_listings`](/nerve-centre/amazon/amazon_suppressed_listings) Shopify and BigCommerce do not have an equivalent (they are DTC, no curation layer).
## Known limitations / merchant FAQs **Why was my listing suspended?** Check the `suspension_reason` in our [`onbuy_alert_suspension`](/nerve-centre/kpi-cards/onbuy/listings-suspension-burst) drilldown or open the listing in OnBuy Seller Console. The five common reasons are: image quality (background, resolution), missing required attributes (material, gender, age-group), price policing (your price diverges from a brand-set MAP or sits below cost-floor), brand gating (you are listing a restricted brand without authorisation), and category mis-classification (item shouldn't be in the chosen tree). **How fast can I get a listing reinstated?** After fix submission, 24 to 72 hours typically. Image fixes are fastest because OnBuy's image checker auto-passes once the new image meets the spec. Attribute fixes take longer because they go through manual review. Brand-gating issues can take weeks (you need to upload a brand-authorisation letter). **Why did multiple listings suspend at once?** Two possibilities. Either OnBuy rolled out a category-wide policy change (e.g. tightened image rules in beauty, started gating a new brand), or your supplier feed pushed prices below an MAP threshold. Check the [`onbuy_alert_suspension`](/nerve-centre/kpi-cards/onbuy/listings-suspension-burst) burst alert; if 5+ listings suspended in 24h with the same reason, it is a policy change. Engage seller support with a single ticket rather than fixing each individually. **Will fixing the listing restore my position in search?** Mostly. OnBuy's algorithm has a memory of suspended listings; reinstated listings start at the bottom of the relevance ranking and re-rank up over 7 to 21 days based on click-through and sales velocity. Plan for revenue to come back in waves, not all at once. **Can I appeal a suspension?** Yes, via Seller Console -> Listings -> Suspended -> Listing -> "Dispute". For genuine errors (e.g. OnBuy's image checker incorrectly flagged a white-background image as non-compliant) the appeal works within 48 hours. For substantive issues (your image actually does have a coloured background) appeals are wasted; just fix and resubmit. **Why would my listing suspend without me doing anything?** Three reasons. First, OnBuy refreshed an algorithm rule (image standards tightened, attribute set expanded). Second, a brand owner submitted a take-down request (rare, but happens with luxury or controlled brands). Third, your supplier feed updated a field that violated a rule (e.g. cost dropped below MAP, missing attribute previously not required is now required). **Is OnBuy more or less strict than Amazon UK or eBay UK?** OnBuy sits in the middle. Amazon is by far the strictest (24/7 algorithmic suspension, often unappealable). eBay is the most permissive (suspension is rare and usually only for outright policy violations). OnBuy lands closer to eBay than Amazon: image and attribute standards are enforced but the bar is reasonable, and human review of appeals is fast. **My listing was suspended for "price too low". Why is that an issue?** OnBuy enforces some MAP (Minimum Advertised Price) policies on behalf of brand owners, especially in electronics, beauty, and homeware. If your supplier feed undercuts a brand-set MAP, OnBuy auto-suspends. Resolution: either raise your price to MAP+ or remove the listing. You cannot appeal MAP cases directly with OnBuy; you need the brand owner to release you from the policy. **Action playbook:** 1. **Open [`onbuy_alert_suspension`](/nerve-centre/kpi-cards/onbuy/listings-suspension-burst)** for the per-listing breakdown. 2. **Sort by velocity x ASP descending** (use [`onbuy_revenue_at_risk`](/nerve-centre/kpi-cards/onbuy/revenue-at-risk) as the proxy). Fix the highest-impact suspensions first. 3. **Image issues:** re-shoot or run existing images through a 1000x1000 white-background check before upload. 4. **Attribute issues:** bulk-edit in Seller Console -> Listings -> Edit Multiple. A single CSV upload can fix 50+ in one go. 5. **Price-policing:** check [`onbuy_xc_dtc_price_gap`](/nerve-centre/kpi-cards/onbuy/onbuy-vs-dtc-price-gap) and [`onbuy_xc_catalogue_drift`](/nerve-centre/kpi-cards/onbuy/catalogue-drift-vs-amazon-uk) to confirm whether the issue is internal (your price too low) or external (Amazon UK undercut). *** ### Tracked live in Vortex IQ Nerve Centre *Suspended Listings* is one of hundreds of KPI pulses Vortex IQ tracks across OnBuy 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.