Subscribe & Save Alert  ·  Included on Every Plan

Your SnS eligibility lapsed.
Recurring orders stopped silently.

SnS customers never re-evaluate. When eligibility drops, their next order simply doesn't arrive — and Amazon won't tell you. SentryKit fires the instant eligibility changes so you recover before the subscription pipeline empties.

30-day free trial
No credit card required
All ASINs monitored from day one
0
notifications from Amazon when SnS eligibility changes on your listing
Near
real-time detection — SentryKit monitors SnS status as it changes, not on a daily report
~1 in 5
SnS-eligible ASINs experience an eligibility change in any given quarter
30 days
free trial — full Subscribe & Save monitoring from day one, no card required
Two States, Two Types of Action

SnS eligibility lost fires the alarm.
SnS eligibility restored confirms the fix.

Subscribe & Save is recurring revenue that runs on autopilot — until it doesn't. SentryKit monitors both directions — so you know the instant eligibility drops (and subscribers stop receiving their orders) and the moment it's restored so you can confirm the pipeline is live again.

SnS Eligibility Lost
Your product is no longer eligible for Subscribe & Save — existing subscriptions are paused.
When SnS eligibility is removed, Amazon pauses all active subscriber orders on that ASIN. Customers with an active subscription will miss their next delivery. No new subscriptions can be created. The most common trigger is pricing — if your price rises above Amazon's competitive parity threshold for SnS, eligibility is removed silently and immediately. SentryKit catches it before another scheduled order date passes.
SentryKit alert includes
ASIN and product name affected SnS status change — eligible to ineligible Timestamp of eligibility change Near real-time — fires the moment status changes
SnS Eligibility Restored
Your product is re-eligible for Subscribe & Save — the subscription option is live again.
Once the eligibility trigger is resolved — pricing corrected, account health restored — Amazon re-enables SnS on the listing. SentryKit fires a restoration alert the moment eligibility returns, confirming the fix has taken effect. Existing paused subscribers can resume their orders, and new subscriptions can be created again. Close the loop — confirm SnS is back before assuming it.
SentryKit alert includes
ASIN now SnS-eligible again SnS status change — ineligible to eligible Timestamp of restoration Near real-time — fires as soon as eligibility returns
Most sellers discover an SnS eligibility loss when a subscriber emails to ask why their order didn't arrive — by which point days or weeks of subscription revenue have already been lost. SentryKit fires the moment eligibility changes, not after the damage compounds.
The Alert

Here's what lands in your inbox the instant
SnS eligibility changes on your listing.

SentryKit delivers the ASIN, the direction of change, and the timestamp — so you know immediately whether to investigate a loss or confirm a restoration, without manually checking the SnS programme dashboard.

SnS revenue runs silently. So does the loss of it.
SentryKit fires the instant eligibility changes — so you're not the last to know.
Start 30 Day Free Trial →
How to Fix It

Five steps to restore Subscribe & Save eligibility
after SentryKit fires the alert.

When SentryKit fires an SnS Eligibility Lost alert, you have a narrow window to restore access before subscribers miss an order cycle. These steps cover the most common causes — pricing, account health, and Seller Support escalation.

1
Open the alert — confirm the ASIN and the eligibility change timestamp
Review the SentryKit alert to confirm which ASIN lost SnS eligibility and exactly when the change occurred. Note whether a single ASIN or multiple ASINs changed — simultaneous losses across products usually indicate an account-level issue rather than a listing-specific one.
2
Go to Manage Inventory and check pricing for SnS price parity
Navigate to Manage Inventory in Seller Central and review the current listing price on the affected ASIN. Amazon requires that the SnS discounted price be competitive relative to recent sales price history. If your price has risen above the parity threshold, SnS eligibility is removed automatically.
3
Review Account Health for flags that may affect SnS eligibility
Open Account Health in Seller Central and check for any open violations, policy flags, or performance warnings. Account Health issues can result in SnS eligibility being suspended at the account or listing level, independent of pricing.
4
Adjust pricing to meet SnS parity requirements and recheck eligibility
If the root cause is pricing, lower the listing price to meet Amazon's SnS competitive parity requirements and save the change. Allow time for Amazon's systems to re-evaluate eligibility. SentryKit will fire a Subscribe & Save Eligibility Restored alert the moment SnS status returns — confirming the fix has taken effect without you having to check manually.
5
Contact Seller Support via Account Health if eligibility doesn't restore
If pricing is correct and Account Health shows no flags but SnS eligibility has not been restored after 24–48 hours, open a case through Seller Support via Account Health. Reference the affected ASIN, the eligibility change date from your SentryKit alert, and any pricing adjustments already made. Seller Support can investigate policy-level flags not visible in Account Health.
What SentryKit Monitors

Three signals that protect your recurring revenue
from silent SnS eligibility changes.

Recurring revenue is the highest-LTV, lowest-effort revenue on Amazon. SnS eligibility is the gate that keeps it flowing. SentryKit watches that gate so you don't have to.

🔔
Lost and restored alerts — both directions covered
SentryKit fires when SnS eligibility is removed and when it's restored. You know the moment you need to act and the moment the fix has taken effect — without manually checking the SnS dashboard.
🔄
Subscription pipeline protection — catch it before orders miss
SnS orders run on a schedule. Every day of eligibility loss is a missed delivery cycle for active subscribers. Near real-time detection means you catch the change in time to investigate before the next order date arrives.
💡
Pricing correlation context — understand what triggered the change
Because SentryKit also monitors price changes, you can correlate a Price Change Alert with an SnS Eligibility Lost alert to identify whether a pricing decision caused the eligibility loss — giving you a clear path to the fix.
SentryKit vs Manual Monitoring

What manually monitoring SnS eligibility actually costs you.

Manual checks require logging into Seller Central, navigating to the SnS programme dashboard, and reviewing each ASIN individually — a process most sellers do weekly at best. A lot can drain silently in a week.

Scenario Manual monitoring SentryKit
Eligibility change detected Next time you manually check (days to weeks) Near real-time
Amazon notification sent to seller None — Amazon does not notify SentryKit fires immediately
Subscriber orders paused (how long before you know) Unknown — until a subscriber complains Same day as eligibility loss
Restoration confirmed Manual check after fixing — easy to forget Automatic restoration alert fired
Coverage across all monitored ASINs One at a time, manually Every tracked ASIN, always on
Pricing correlation to diagnose cause Separate manual investigation Cross-reference with Price Change Alert
Time investment per week 30–60 min across catalogue Zero — SentryKit runs continuously
From Amazon Sellers

What sellers say about catching SnS eligibility changes before the damage compounds.

★★★★★
"One of our top supplement ASINs lost SnS eligibility after a price change and we had no idea for nearly two weeks. We found out because a subscriber emailed to ask why their order hadn't arrived. SentryKit would have caught it the same day. We set it up immediately after that."
Private label seller — health & wellness, US marketplace
★★★★★
"Subscribe & Save is about 40% of our monthly revenue on our core SKUs. Before SentryKit I had no system to know when SnS eligibility dropped — I'd check the dashboard maybe once a week. Now I know within the hour and can act before the next order cycle."
Amazon FBA seller — home essentials brand, 6-figure monthly revenue
★★★★★
"The restoration alert is just as valuable as the loss alert. I fixed the pricing issue but I kept second-guessing whether SnS was actually back. SentryKit fired the restoration alert within the hour of eligibility returning — I could confirm the fix without logging back in to check manually."
Seller — pet supplies niche, Subscribe & Save heavy catalogue

Stop finding out from your subscribers.
Start finding out from SentryKit.

Near real-time SnS eligibility monitoring on every tracked ASIN. Included on every plan. 30-day free trial, no credit card required.

Frequently Asked Questions

Everything you need to know about Subscribe & Save
eligibility and how SentryKit monitors it.

Subscribe & Save (SnS) is Amazon's subscription programme that lets customers set recurring orders on eligible products at a discount — typically 5% to 15% off. SnS customers have higher lifetime value, lower churn, and re-purchase without ever making a new buying decision or seeing a competitor's listing. When a product is SnS-eligible, it benefits from recurring, predictable revenue. When eligibility is lost, that subscription pipeline drains silently — existing subscribers are paused and no new subscriptions can be created.
The most common cause of SnS eligibility loss is pricing — specifically, the listing price rising above Amazon's competitive price parity threshold for SnS. Amazon requires that the SnS price be competitive relative to recent purchase price history. Other causes include account-level policy violations, category-specific eligibility changes made by Amazon, product condition changes, and in some cases, listing suppression that affects SnS status.
No. Amazon does not proactively notify sellers when a listing loses or regains Subscribe & Save eligibility. Sellers who rely on manual checks — looking at Manage Inventory or the SnS programme dashboard — may not discover an eligibility loss for days or weeks. During that window, existing subscriber orders are paused and new subscriptions cannot be created, meaning the revenue impact compounds silently. SentryKit monitors SnS eligibility near real-time and alerts you the moment the status changes.
Start by checking your listing price — pricing above Amazon's competitive parity threshold is the most common cause of SnS eligibility loss. If a price adjustment is needed, lower the price to meet parity and wait for Amazon's systems to re-evaluate. Also review Account Health for any open violations that may be affecting eligibility. If eligibility does not restore within 24–48 hours of a price correction, open a Seller Support case via Account Health referencing the affected ASIN.
When a listing loses SnS eligibility, Amazon pauses existing subscriber orders for that ASIN — customers with active subscriptions will not receive their scheduled shipments until eligibility is restored. Customers may receive an email notifying them of the pause. If eligibility is not restored quickly, some subscribers may cancel their subscription or switch to a competitor's product. This is why rapid detection is critical — every day of eligibility loss risks permanent subscriber attrition.
SentryKit uses a compliant monitoring system to track Subscribe & Save eligibility status on every ASIN you monitor. When eligibility status changes — either lost or restored — SentryKit fires an alert near real-time with the ASIN, the direction of the change, and a direct link to Seller Central. This means you learn about an eligibility loss in time to act, rather than discovering it when recurring revenue has already stopped.