Stock up for Subscribe & Save subscribers before low inventory pauses deliveries
Updated · By Ecomsellertool editorial team
Read Amazon's Subscribe & Save forecast per SKU through the Replenishment API, which replaced the old reports. Take subscription units out of the sales average, add the forecast units back for the lead time, and reorder when stock falls below that line. Alert when the next 30 days of deliveries are at risk, and track discount cost per SKU. A person approves every order, price and discount change.
- Amazon removed the GET_FBA_SNS_FORECAST_DATA and GET_FBA_SNS_PERFORMANCE_DATA report types on December 11, 2025, and points developers to the Replenishment API v2022-11-07 (checked November 13, 2026).
- The Replenishment API returns Subscribe & Save forecasts of shipped subscription units and subscription revenue for the next 30, 60 and 90 days, for sellers only.
- Its offer list shows each offer's eligibility, discounts, available inventory, stock risk and the health of the next 30 days of deliveries, such as deliveries at risk from low inventory.
- Amazon says deliveries may be paused when you lack inventory for upcoming orders or a lower-priced offer exists, and products that fall below its bar are removed, with subscriptions canceled.
- Sellers choose a base discount of 0%, 5%, 10%, 15% or 20%; Amazon funds an extra 5% when a customer has five or more enrolled products arriving together.
- In this recipe rules read the data and do the math; a person approves every purchase order, shipment, price change and discount change.
The step map: who runs each step
Trigger: A daily schedule after the FBA inventory sync, plus a weekly run for forecasts and discount cost.
| Step | What happens | Who runs it |
|---|---|---|
| 1 | Every morning rules call the Replenishment API's offer list for each Subscribe & Save offer: eligibility, seller-funded and Amazon-funded discounts, price, available inventory, stock risk, delivery conditions for the next 30 days and projected deliveries. | Rule |
| 2 | Once a week rules pull forecast metrics per offer (shipped subscription units for the next 30, 60 and 90 days) and last month's performance (shipped subscription units, active subscriptions and the share of units not delivered because of stock). | Rule |
| 3 | Rules split each SKU's sales into one-time and subscription demand, prorate the forecast to the SKU's lead time and compute the units needed before the next shipment lands. | Rule |
| 4 | SKUs whose FBA position, inbound shipments and open POs fall below that line are added to the draft purchase order and the next FBA shipment plan, with the worksheet line attached. | Rule |
| 5 | Rules alert the inventory owner the same day an offer reports deliveries at risk from low inventory, paused for price or because the offer is not buyable, or an eligibility change to suspended or ineligible. | Rule |
| 6 | Each week rules estimate seller-funded discount cost per SKU from subscription units, price and the funding tier, and flag SKUs where the cost crosses the limit your team set. | Rule |
| 7 | A buyer approves the purchase order and the FBA shipment, and a named owner decides any price or discount change in Seller Central. | Person |
6 rule steps · 0 AI model steps · 1 person step. A rule follows fixed logic you approve; an AI model handles messy input and its output is checked by rules; a person makes the calls listed below.
What stays with a person
- Every purchase order and FBA shipment before it is sent
- Every price change, including one to clear a price-paused delivery
- Every change to a seller-funded discount tier or a Subscribe & Save coupon
- Whether to opt a SKU out of automatic enrollment or remove it from the program
- The safety stock and the discount-cost limit for each SKU
Which tools can run it
- Seller Central's Manage Products page and a monthly Performance report download into a reorder spreadsheet, for a few enrolled SKUs
- Zapier, Make or n8n calling the Replenishment API through a small signed-request service, posting alerts to Slack
- Custom code on your accounts, joining the Replenishment API with FBA inventory, open POs and your reorder worksheet
Systems it connects
- Amazon SP-API Replenishment API v2022-11-07
- Amazon SP-API FBA inventory data
- Seller Central Subscribe & Save pages and reports
- Reorder worksheet or purchasing system
- QuickBooks Online, Xero or an ERP
- Slack or email
Build size: Medium
The API calls are simple; the work is splitting subscription from one-time demand without counting it twice, and keeping lead times and safety stock right per SKU.
A subscriber is the steadiest customer an FBA brand has. They order the same SKU every month without being asked. But a normal reorder sheet treats their units like any other sale, so a fast-growing subscription base stays hidden in the average until the stock runs short. Then Amazon pauses their deliveries, and if it keeps happening, the product can leave the program and the subscriptions go with it. This recipe puts Amazon's own Subscribe & Save forecast into the reorder plan, alerts while there is still time to ship, and keeps the discount cost in view. It is one page of our automation library.
How do you add the Subscribe & Save forecast to a reorder point?
Split demand in two, because the two halves behave differently. One-time buyers follow your sales average. Subscribers follow a schedule Amazon already knows. Amazon's forecast covers the subscribers, so take their units out of the average first, or you count them twice. Then add the forecast back for the lead time, which runs from placing the PO until the units are available in FBA. It extends the usual reorder point with safety stock on top.
Units needed before the next shipment lands = (average daily units − average daily subscription units) × lead time in days + forecast subscription units for the lead time + safety stock
Amazon gives the forecast in fixed windows: 30, 60 and 90 days through the API, and 15, 30, 60 and 90 days on the Manage Products page. Take the smallest window that covers your lead time and prorate it. For a 50-day lead time, use the 60-day forecast × 50 ÷ 60. Reorder when the inventory position (FBA available, plus inbound shipments, plus open POs) falls below the line.
Here is the worksheet for three SKUs from an illustrative supplements brand. The numbers are examples, not client data.
| SKU | Lead time | Daily units (30 in-stock days) | Subscription units a day | One-time units a day | Subscription forecast for the lead time | Safety stock | Units needed | Position | Status |
|---|---|---|---|---|---|---|---|---|---|
| Protein powder 2 lb | 50 days | 40 | 12 | 28 | 60-day forecast 900 × 50 ÷ 60 = 750 | 300 | 28 × 50 + 750 + 300 = 2,450 | 2,100 | Below: add to the draft PO |
| Vitamin D 120 ct | 35 days | 20 | 9 | 11 | 60-day forecast 660 × 35 ÷ 60 = 385 | 120 | 11 × 35 + 385 + 120 = 890 | 1,250 | Above: no action |
| Electrolyte sticks 30 ct | 30 days | 15 | 4 | 11 | 30-day forecast 240 | 90 | 11 × 30 + 240 + 90 = 660 | 600 | Below: add to the draft PO and alert |
The third row is the reason to do this. Its old reorder point, 15 a day × 30 days + 90, is 540, and a position of 600 looks safe. But its subscriptions are growing: Amazon forecasts 240 subscription units in the next 30 days, twice the 4 a day it shipped last month. The split version catches the shortfall a month before the average would.
Which Amazon signals should raise an alert?
The worksheet decides how much to buy. The alerts below decide how fast someone has to act. Each comes from fields in Amazon's listOffers reference (checked November 13, 2026), read every morning.
| Amazon signal | What it means | Who gets the alert | What they decide |
|---|---|---|---|
| Next 30 days of deliveries at risk from low inventory | Stock may not cover upcoming subscriber orders | Inventory owner | Speed up the open PO, send FBA stock from a 3PL or AWD, or accept the risk |
| Next 30 days of deliveries paused for pricing | Amazon paused deliveries over the offer's price | Pricing owner | Whether to change the price; see Buy Box loss alerts for the offer picture |
| Next 30 days of deliveries paused, offer not buyable | The listing cannot be bought, so deliveries stop | Listing owner | Fix the listing, suppression or stock |
| Eligibility changed to suspended | No new subscriptions; existing ones still ship | Program owner | Find the cause before it turns into ineligible |
| Eligibility changed to ineligible | No new subscriptions, and existing ones will be canceled | Owner, same day | Fix the cause, ask Selling Partner Support, or replace the offer |
| Share of units not delivered because of stock, in last month's offer metrics | Subscriber orders already missed | Inventory owner | Raise safety stock on that SKU |
Amazon's Subscribe & Save help page (checked November 13, 2026) explains why these matter. It says deliveries may be paused when you lack inventory for upcoming orders or when a lower-priced offer exists. It says performance reviews look at inventory levels, cancellations, feedback and delivery, and products that fall below the bar are removed from the program with their subscriptions canceled. Product eligibility also asks that the product was buyable for at least 85% of the past 30 days.
Where does Subscribe & Save data come from now that the reports are gone?
Not from the Reports API any more. Amazon's deprecation schedule lists GET_FBA_SNS_FORECAST_DATA and GET_FBA_SNS_PERFORMANCE_DATA as deprecated on June 25, 2025 and removed on December 11, 2025, and its changelog notice points to the Replenishment API v2022-11-07 instead (both checked November 13, 2026). Any workflow still calling the old reports is reading nothing.
The Replenishment API (checked November 13, 2026) supports Subscribe & Save and has three read operations: metrics for the whole seller account, metrics per offer, and the offer list. Its offer metrics guide says a forecast request returns shipped subscription units and subscription revenue for the next 30, 60 or 90 days, for sellers only. The app needs the Brand Analytics or the Inventory and Order Tracking role, and it calls Amazon through the Selling Partner API like any other.
Seller Central keeps a manual route too. Amazon's selection management page says Manage Products shows projected Subscribe & Save demand for 15, 30, 60 and 90 days. Its performance report page lists an offer-level download with seller funding %, subscriptions at period end, shipped units, sales and lost sales from stock-outs (both checked November 13, 2026). A small brand can start from that download.
How do you track what the discount costs per SKU?
Amazon's help page says you choose a base discount for enrolled products of 0%, 5%, 10%, 15% or 20%, and Amazon funds an extra 5% when a customer has five or more enrolled products arriving together. The base discount is yours to pay; the extra 5% is not. Amazon's program page for sellers says there are no added selling costs beyond standard selling and FBA fees (checked November 13, 2026), so the discount is the cost to watch. That same program page still describes a 0% discount you can raise to 5% or 10%, while the help page lists five tiers up to 20%. We follow the help page; confirm the tiers you see on Manage Products. Coupons and deals stack on top of the program discount, so they belong in the same weekly view.
Estimated monthly discount cost per SKU = subscription units shipped in the month × current price × seller-funded discount %
An illustrative example (not client data): the electrolyte sticks above sell at $25 with a 10% seller-funded tier and ship 240 subscription units a month. That is about $600 a month in discount. Raising the tier to 15% would make it about $900 before any change in sign-ups. The workflow lists that number per SKU beside its margin, so a person decides the tier with the cost in front of them. Treat the number as a floor. Amazon's help page says the seller-funded discount also applies to one-time purchases of enrolled products, such as top-off orders and reorders, and those units are not in the subscription count. Our supplier cost change alerts cover the cost side of the same margin.
What should stay with a person?
Every action that spends money or changes what a customer pays. Rules read Amazon's data, split demand, prorate forecasts and flag SKUs. A buyer approves each purchase order and each FBA shipment. Our low-stock alerts and draft POs recipe builds the draft, and the FBA inbound shipment recipe takes it from approval to a shipment. Price changes and discount tiers are decided by a named owner in Seller Central.
We also found no write operation in the Replenishment API, so the workflow cannot change a discount even if someone wanted it to. That suits this job. A discount raise brings more subscribers that you then have to stock, and a price cut to clear a pause moves your margin. Both are business calls. For brands whose demand also swings with seasons and promotions, our inventory and replenishment agent forecasts beyond the subscription base, and our stockouts page covers the wider signals.
Which tool should run it?
The simplest one that sees both Amazon's forecast and your open orders.
| Level | Fits when | What to watch |
|---|---|---|
| Manage Products and the Performance report into a spreadsheet | A handful of enrolled SKUs, one supplier | Someone has to download, paste and check the at-risk list by hand each week |
| Zapier, Make or n8n | A few dozen SKUs, POs in a sheet or QuickBooks | SP-API calls need signed requests and a token refresh, so a small service sits in front; log every run; see our Zapier vs Make vs n8n comparison |
| Custom code on your accounts | Many SKUs, FBA plus a 3PL or AWD, POs in an ERP | Can run on Ecomsellertool Growth OS beside the reorder worksheet and FBA inventory it needs |
The listOffers reference lists a default rate of 1 request a second with a burst of 1 (checked November 13, 2026), which is enough for a daily run. Our guide to automating Amazon operations shows where this fits with the rest of FBA planning.
Who builds Subscribe & Save forecast alerts for FBA brands?
Ecomsellertool builds this recipe on your own Amazon account, reorder worksheet and purchasing system. We have built on Amazon's seller APIs since 2017 and shipped 50+ tools for 100+ teams. We map your SKUs, lead times, safety stock and approvers first, then build the Replenishment API pull, the split-demand worksheet, the alerts and the discount-cost view. Send a project brief, or read how our workflow automation service works.
None of our published case studies is a Subscribe & Save workflow on its own, so here is the closest work we have shipped:
- Demand planning from order data. For Cheddy we built stock management that maps kits, multipacks and single-pack ASINs to warehouse components, and gathers ordering and delivery data to find trends and plan future operations.
- FBA inventory beside cost and profit. For Lavley we built analytics that read the FBA manage-inventory report for real-time stock, and a cost mapping module that keeps the history of each product's cost for accurate profit, the same join the discount-cost view needs.
You keep your accounts, your data and the custom code we build; the Growth OS base is licensed to you. If you are not sure subscriptions are where stock runs short, the free 24-hour diagnostic looks across the account first.
Get your Subscribe & Save alerts built
Send us how you plan stock for subscribers today
Describe the workflow you want automated. We reply with a written plan: scope, timeline and a fixed price.
Frequently asked questions
Where did the Amazon Subscribe & Save forecast report go in the SP-API?
Amazon deprecated the GET_FBA_SNS_FORECAST_DATA and GET_FBA_SNS_PERFORMANCE_DATA report types on June 25, 2025, said calls would return empty responses from July 25, 2025, and removed them on December 11, 2025. Its changelog tells developers to move to the Replenishment API v2022-11-07 or the Subscribe & Save page in Seller Central.
What happens to Subscribe & Save subscriptions when my FBA product runs out of stock?
Amazon says deliveries may be paused when you do not have enough inventory for upcoming orders. If an offer is unavailable for more than 7 days and you opted in to automatic enrollment, Amazon transfers its subscriptions to an identical available offer from you. Products that keep failing Amazon's bar, which includes inventory levels, are removed and their subscriptions canceled.
How do I forecast inventory for Subscribe & Save?
Use Amazon's own projection. The Manage Products page shows projected Subscribe & Save demand for 15, 30, 60 and 90 days, and the Replenishment API returns forecast shipped subscription units for 30, 60 and 90 days. Add those units to your one-time demand for the supplier's lead time, plus safety stock, and reorder when your inventory position falls below the total.
Who pays for the Subscribe & Save discount on Amazon?
Both, in parts. Amazon's help page says the base discount is funded by you, at a tier you choose: 0%, 5%, 10%, 15% or 20%. Amazon funds an additional 5% when a customer has five or more enrolled products arriving on the same day. Amazon's program page says there are no added selling costs for the program beyond standard selling and FBA fees.
Can the Replenishment API change my Subscribe & Save discount or price?
We found no write operation in the Replenishment API v2022-11-07 on November 13, 2026. Its three operations read seller metrics, offer metrics and offers. Discounts and enrollment are managed on the Manage Products page in Seller Central, which is where a person makes the change in this recipe.
Which roles does an app need to read Subscribe & Save data?
Amazon's Replenishment API page lists Brand Analytics or Inventory and Order Tracking as the roles, with at least one required, in the NA, EU and FE regions. To take part in the program at all, the seller needs a Brand Representative role on a brand in Brand Registry.
