Category Change Alert  ·  Included on Every Plan

Amazon recategorised your listing.
Your BSR reset to zero.

Amazon silently shifts your Browse Node and your listing disappears from the category you rank in — SentryKit detects the change in near real-time so you can act before rankings and fees are lost.

30-day free trial
No credit card required
All ASINs monitored from day one
0
Amazon sends no notification when your product category changes
Near‑real‑time
Alert fires the moment your Browse Node shifts in catalog data
Before + After
Old and new Browse Node captured at the moment of change
30 days
Free trial — full category monitoring from day one
Two States SentryKit Tracks

Category shifted without you — or category restored. Both matter.

An unexpected Browse Node reclassification can erase your keyword ranking history overnight. Your listing is still visible — just in the wrong category. BSR resets. Keyword rankings evaporate. Referral fees shift. And Amazon doesn't say a word.

Category Changed
Browse Node shifted — listing removed from its ranking category
SentryKit detected that the Browse Node on your ASIN has changed. Your listing is still live but is now indexed under a different category — disrupting keyword rankings, BSR position, and potentially referral fee rates associated with the original node.
Browse Node — changed
WAS Kitchen & Dining › Baking › Baking Mats & Liners (Node 3736281)
NOW Industrial & Scientific › Food Service Equipment (Node 8090784)
Alert context
ASIN B08XLMN4QP · Premium Silicone Baking Mat Set BSR: Kitchen & Dining #1,842 → no longer ranked Referral fee rate: 8% → 12% (category change)
Category Restored
Original Browse Node confirmed — ranking recovery underway
SentryKit detected that your ASIN has been moved back to the correct Browse Node following your catalog correction. BSR will begin rebuilding in the original category and keyword ranking signals will start to recover as the listing is re-indexed.
Browse Node — restored
NOW Kitchen & Dining › Baking › Baking Mats & Liners (Node 3736281)
Alert context
ASIN B08XLMN4QP · Premium Silicone Baking Mat Set Restored via: Seller Central listing edit + Seller Support case Full change log: timestamped and saved for documentation
What the Alert Looks Like

The old Browse Node, the new one, the exact moment it shifted

Not "your category was updated." SentryKit captures both nodes at the moment of change — so you already know what shifted before you open Seller Central.

Stop finding out your category changed from a BSR anomaly
All 20+ alert types  ·  30-day free trial  ·  No credit card required
Start Monitoring Free →
How to Respond

When the category change alert fires — act in this order

Speed matters. Every day your listing sits in the wrong Browse Node, you are losing keyword ranking history that took months to build. SentryKit fires the moment it happens — here is what to do next.

1
Open the alert and confirm the old vs new Browse Node — verify the correct node ID
SentryKit includes both the previous and new Browse Node path in the alert. Open it and confirm the change is incorrect. Cross-reference Amazon's Browse Tree Guide for your marketplace to get the exact node ID you need to restore. Having the correct node ID before you open Seller Central speeds up the correction process significantly.
2
Edit the listing in Manage Inventory and correct the product type and Browse Node
Go to Seller Central → Manage Inventory → find the ASIN → Edit Listing. Update the product type and Browse Node to the correct values. Submit the update. If the correction does not take effect within 24 hours, escalate to Seller Support.
3
File a Seller Support case via Account Health if the change persists
Open a case via Account Health in Seller Central. Reference the ASIN, the incorrect Browse Node currently assigned, and the correct node ID. Include the timestamp from your SentryKit alert as documentation of exactly when the reclassification occurred — this accelerates the investigation and gives you a stronger basis for escalation.
4
If Brand Registered — use Brand Registry to correct catalog data and lock the category
Brand Registry holders can submit catalog corrections through the Brand Catalog Manager for priority processing. If a competing seller's flat file contribution caused the category shift, file a Report a Violation case in Brand Registry with documentation of your correct category assignment. Brand Registry gives brand owners priority in catalog contribution disputes and can help prevent repeat reclassifications.
Why SentryKit

The category reclassification Amazon didn't tell you about — caught in near real-time

Before and After Browse Node at the Moment of Change
Every category change alert includes both the previous Browse Node path and the new one, captured the instant the reclassification registers. You see exactly what changed, which category you left, and which one you landed in — before you open Seller Central.
Instant Ranking Impact Awareness
Category shifts affect BSR, keyword rankings, referral fees, and program eligibility simultaneously. SentryKit fires before any of these downstream effects compound — giving you the window to correct the node before ranking history is permanently lost in the original category.
Full Category History Log for Seller Support Cases
Every category change is timestamped and logged per ASIN. This history gives you the documentation you need for Seller Support escalations, Brand Registry cases, and BSR anomaly investigations — an auditable record of every reclassification event, ready to attach to your case.
SentryKit vs Manual

How sellers catch category changes — with and without SentryKit

Capability SentryKit Manual checks
Discover category changed ✓ Near real-time alert — fires the moment the Browse Node shifts ✗ Days or weeks — usually noticed only when BSR or sales drop
Old and new Browse Node captured ✓ Yes — both nodes recorded at the moment of change ✗ No — old node is gone once overwritten, no record retained
Timestamp for Seller Support cases ✓ Yes — exact time logged for escalations and Brand Registry ✗ No record of when the reclassification occurred
Monitoring across catalog ✓ All ASINs monitored simultaneously, 24/7 ✗ Manual spot-checking — one ASIN at a time, when you remember
Fee impact visibility ✓ Alert fires before fee change appears in monthly statements ✗ Fee change discovered in statements, weeks after the fact
Amazon notification ✓ None sent by Amazon — SentryKit fills the gap ✗ None sent, and no backup detection method
From Sellers Who Use It

What it feels like to catch a category reclassification before rankings disappear

★★★★★
"My silicone baking mat got moved from Kitchen & Dining into Industrial & Scientific overnight. I had no idea until SentryKit fired the alert. Got it corrected in 48 hours and avoided losing the BSR rank I'd spent months building."
Private label seller — Kitchen & Dining
★★★★★
"A competitor submitted a flat file that changed my Browse Node. I found out through SentryKit the same day — not a week later when I noticed my sales were off. The timestamp in the alert was exactly what I needed for the Seller Support case."
FBA seller — Sports & Outdoors
★★★★★
"I manage 40+ ASINs. I would never catch a category reclassification manually across that catalog. SentryKit alerts me the moment any Browse Node changes, with the old and new node right there. It's the only way to stay on top of catalog integrity at scale."
Brand owner — Home & Garden, 40+ ASINs

Know the instant your Browse Node shifts — before rankings disappear.

All 20+ alerts  ·  30-day free trial  ·  No credit card required

FAQ

Category Change Alert — common questions

A category change alert fires when the Browse Node or product category assignment changes on a monitored ASIN. SentryKit monitors the category assignment for every tracked ASIN continuously. When the Browse Node shifts — whether due to Amazon's catalog algorithm, a competing seller's flat file contribution, or a catalog error — you receive a near real-time alert containing the previous category, the new category, and a timestamp. This lets you immediately assess the impact on rankings, fees, and program eligibility, and begin a correction before downstream revenue effects compound.
Category changes happen through several channels sellers cannot directly control: Amazon's catalog algorithm reclassifying products based on listing attributes or customer behavior data; a competing seller submitting a flat file that includes a different Browse Node; an error in your own listing attributes triggering an automatic reclassification; or Amazon standardizing catalog structure across a category. Amazon sends no notification when any of these occur. SentryKit detects the Browse Node shift the moment it registers in catalog data and alerts you immediately.
No. Amazon sends no notification when your product's Browse Node or category assignment changes. There is no email, no Performance Notification, and no Seller Central alert for category reclassifications — even when the change was caused by a third party and moves your product into a completely unrelated category. Most sellers discover the change only when they notice a drop in BSR, keyword rankings, or sales — by which time significant ranking history may already be lost. SentryKit fills this gap by detecting the Browse Node change in near real-time and alerting you before the downstream impact begins.
A category reclassification affects your listing across several dimensions simultaneously. Keyword rankings are partially determined by your Browse Node — a shift can eliminate all keyword ranking signals built in the original category, requiring a full rebuild in the new node. BSR is category-specific, so your position resets entirely when your category changes. Referral fee rates vary by category, so moving from a low-fee to a high-fee node increases your per-unit cost immediately. Program eligibility — including Amazon's Choice, Subscribe & Save, and some promotional structures — can also change. SentryKit alerts you the moment the reclassification occurs so you can assess and respond before any of these effects take hold.
Go to Seller Central → Manage Inventory → find the ASIN → Edit Listing. Update the product type and Browse Node to the correct values. If the correction does not take effect within 24 hours, open a Seller Support case via Account Health referencing the ASIN, the incorrect Browse Node currently assigned, and the correct node ID. If you hold Brand Registry, submit the correction through Brand Catalog Manager for priority processing. The timestamp and category details from your SentryKit alert provide the documentation needed for any Seller Support escalation.
SentryKit monitors the Browse Node and product category assignment on every tracked ASIN continuously. When the category changes, an alert is sent in near real-time with the previous and new Browse Node paths and an exact timestamp. Every category change event is logged per ASIN so you have a full history for catalog correction requests, Seller Support escalations, and BSR anomaly investigations.