Multiple items moved from active -> delisted in 24h, usually a category-wide ranging review. Direct revenue blocker; investigate the same day.
At a glance
Real-time alert that fires when 4 or more items in the supplier’s Costco catalogue flip fromactivetodelistedwithin a rolling 24-hour window. The companion to Items Delisted This Week: the weekly count tells you about portfolio churn, this 24-hour burst alert tells you about category-review events. A burst is structurally different from a drip: 4 items delisted across 7 days is normal portfolio churn (1 to 5 percent of catalogue per quarter is healthy); 4 items in 24 hours almost always means Costco’s buyer team has run a category review and made a coordinated cut. Investigate the same day; the buyer-conversation window is short.
Calculation
Calculated automatically from your Costco SIP data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
The same US household-goods supplier, 84 active items in catalogue. Reading taken at 09:00 PT on Wednesday 11 Mar 26.
The card fires because 4 items delisted in 24 hours with the same reason code, same category, same timestamp. Five things to notice:
- Same-timestamp + same-category + same-reason = category review event. This is not 4 independent decisions; it is one buyer decision cutting the supplier’s full paper-towel range. The buyer has decided to refresh the cleaning category and the supplier’s range is on the cut list. Treat as a P1 commercial incident.
- Estimated revenue at risk is roughly USD 92,000 per week.
(1840 × 18.99) + (1420 × 26.49) + (980 × 17.99) + (620 × 21.49) = USD 92,200. Annualised at typical buying cadence that is around USD 2.4M of shelf revenue gone unless reversed. The burst alert exists because dollar exposure of this magnitude justifies same-day buyer engagement. - The buyer-conversation window is the next 5 working days. Costco buyers move on quickly after category reviews; reaching out within 24 hours signals serious supplier engagement. Reaching out 2 weeks later signals the supplier is not paying attention and reduces reversal probability materially.
- Common reversal arguments for
category_review_cut. (a) Propose a refreshed range under new packaging that addresses whatever the buyer was responding to (sustainability claims, modern visual identity, premium-tier extension). (b) Volunteer to support a competitive category-test in a small set of stores. (c) Negotiate price-down in exchange for re-listing the existing range. The buyer’s underlying motivation determines which argument is viable. - Pair with Revenue at Risk and Items Delisted This Week. This card is the alert; those two cards provide the dollar context and trend context for the buyer conversation.
Sibling cards merchants should reference together
Item Delisting Burst is a category-review-event detector. Pair with these:Reconciling against the vendor’s own dashboard
Where to look in Costco’s own portal: Costco Supplier Portal → Item Master → My Items filter to Status: Delisted, Last 24 hours. The portal will show the same items as this card’s drill-down. Sort bylast_status_change descending to see the burst pattern (multiple items with timestamps within the same hour are usually a single category review event).
Why our number may legitimately differ from Costco’s portal:
Cross-connector reconciliation:
Known limitations / merchant FAQs
The card fired with 4 delistings but they have different reason codes. Is this a category review? Probably not. A category-review event typically delists items with the same reason code (category_review_cut is the most common). Mixed reason codes suggest 4 independent decisions that happened to land in the same 24-hour window: one velocity-based cut, one compliance failure, one case-pack-change failure. Less urgent than a coordinated category review but still worth investigating each independently within the normal 24-hour buyer-conversation window.
A burst fired at 03:00 PT. Costco’s portal showed the burst at 02:55 PT. Why the lag?
Item-master sync cadence. The card refreshes on each sync cycle; if your integration polls every 60 minutes, the burst can be up to 60 minutes behind the actual Costco-side timestamp. For higher-stakes operations configure a 15-minute poll cadence; for lower-stakes operations the 60-minute default is fine.
My catalogue is 800 items. The threshold of 4 fires too often. What now?
Raise the threshold. Suppliers with very large catalogues see normal portfolio churn at 1 to 3 delistings per 24 hours; a 4-delisting threshold creates alert noise. Configure the threshold to 6 or 8 at the integration level; the card itself will continue to track the count, only the alert behaviour changes.
My catalogue is 12 items. Even 2 delistings is a major event. Can I lower the threshold?
Yes. Configure the threshold to 2 at the integration level for small-catalogue suppliers. Below 2 the card becomes equivalent to the Items Delisted This Week card on a 24-hour window; alert noise is lower than expected because small-catalogue suppliers see fewer churn events per period.
Can I get the burst alert routed to the buyer-conversation team rather than ops?
Yes. The burst alert is fundamentally a commercial signal, not a technical signal. Route it to the sales / key-account team’s Slack channel or the commercial director’s email. Operations should still see it for context but the action is a buyer conversation, not a technical fix.
How quickly should I respond to a burst?
Within 24 hours for a buyer email; within 5 working days for a buyer meeting. The reversal probability decays steeply: same-day engagement on a buyer email has roughly 25 to 40 percent reversal probability for category_review_cut; week-2 engagement is 5 to 15 percent; beyond week-2 is mostly cosmetic.
The same items got delisted, then re-listed, then delisted again over 3 weeks. Did the burst alert fire each time?
Yes if the threshold was tripped each time. The card counts active → delisted transitions; a re-listing then re-delisting cycle is two transitions and counts twice. This pattern usually means the buyer is testing a category change, vacillating, or running a structured re-list pilot. Use the drill-down to see the full status-change history per item; treat each burst as an independent buyer signal.
Can I prevent bursts entirely?
Mostly no. Category reviews are buyer-team decisions; suppliers cannot prevent the buyer from running a review. What suppliers can do: (1) maintain strong commercial relationships so the buyer flags an upcoming review in advance, (2) keep Items with Field Drift at zero so technical-failure delistings do not contribute to a burst, (3) keep Fill Rate above 98 percent so velocity-based cuts have less basis. The technical hygiene reduces avoidable burst contributions; the commercial hygiene reduces frequency.
A 4-item burst with all gtin_invalid reason. Is this a category review?
No, this is a data-quality cluster. Costco’s GTIN validation has flagged 4 items at the same time, almost always because of a recent item-master submission that batched 4 items with bad GTINs. Fix: identify the corrupted submission, resubmit the corrected GTINs, request reactivation through the buyer. This category of burst is fully recoverable inside 5 to 10 working days.
Should I also configure the burst threshold per-category?
Higher-stakes operations sometimes do. Configure separate burst thresholds per Costco merchandise category if your portfolio spans multiple categories with different sensitivity (e.g. Cleaning category at threshold 3, Office Supplies category at threshold 6). The default threshold is portfolio-wide; per-category thresholds are configured at the integration filter layer.