Restock Bot Alerts
Not all Costco gold restock alerts are created equal
In 2026 alone, Costco has listed 44 new precious-metal SKUs, 23 of them gold. That is already more than the 41 it listed in all of 2025, and nearly double the 24 from 2024. Costco keeps expanding its catalog and bringing more SKUs to market. And yet, when the market conditions are profitable, every restock still disappears in minutes, sometimes seconds.
If you buy gold at Costco, you already know the feeling. The alert comes in, you fumble for the link, you click, the page opens, and by the time you go to add it to your cart you get the dreaded message that the item is no longer available. Or worse, you make it to the cart, you are about to check out, and it goes out of stock right there.
The alert is where the game starts, so what better place to start this series than with alerts? There are a lot of ways to get a Costco gold restock alert now: paid services, free feeds, or build your own. It is fair to ask whether one alert is as good as another.
It is not, and I just spent fifteen weeks measuring exactly that. To me, an alert has to do three things to earn its place on your phone: reach you fast, reach you every time, and be worth acting on when it does. Fast, reliable, personalized. I built my service around those three, and to make sure I was delivering on that promise, I measured the first two against two other popular feeds. The third one I will show you.
1 of 3
Fast
There are about half a dozen ways to find out that a Costco SKU is back in stock. I have timed all of them. The cheapest ones to run are the slowest, because they watch the same page you could watch yourself, and that page is already a few minutes behind. The fast ones take real effort to keep running, day after day. That is most of the reason alert services cost what they cost.
Here is the part that matters to you. If you use a feed that watches the category page, or you watch it yourself, by the time a restock shows up there the people with the fastest alerts have already placed their orders. Some restocks are so small they sell out before they ever appear there. Either way, you were never in the race.
That is a big claim, so I tested it. From May 18 to September 3 I logged every gold restock alert from my service next to two others: a lower-priced alert service and an API feed that several other services rely on. To keep the comparison fair, I scored only 16 gold SKUs that all three of us alerted on during that window, which carry about two thirds of all the gold restocks I logged, including the 1 oz PAMP Suisse Lady Fortuna bar, the most restocked gold SKU at Costco this year. Every time any of us fired, I asked two questions: who was first, and who missed it.
Against the lower-priced service. Of 471 restocks we both alerted, mine was first on 469. The typical gap was 5 minutes 46 seconds. Not seconds. Minutes. On a gold bar that is the difference between buying and reading about it. And that is only the restocks we both saw. There were 429 more that my service alerted and that service never sent at all. If that service was your only alert, you never knew those restocks happened.
Against the API feed. This one is fast. During normal hours, weekdays from 4am to 10pm Pacific, I was first on 44% of the restocks we both caught (more on that later), we landed in the same minute on 38%, and I was slower on 18%. Call it even, with a small edge. I am not going to pretend otherwise.
Who alerted first, on restocks we both caught
16 gold SKUs, May 18 to September 3, 2026. Share of shared restocks.
Detection is only half the story. The other half is the last leg, from my system to your hand. My alerts arrive as push notifications and in Slack, and there is no limit on how many you get. If you are on your computer and use the browser extension, the Costco product page is already opening by the time you look at your phone. That part deserves its own post, and it will get one.
2 of 3
Reliable
Speed is only worth something if the restock alert actually comes.
Another finding of this analysis that surprised me was the gap in how many restocks each service caught at all. I expected some difference, from downtime, from noise, from ordinary variation. What I did not expect was that the lower-priced service would miss about half of the restocks that my service and the API feed both caught in the same window.
Restocks each feed caught
16 gold SKUs, May 18 to September 3, 2026. Of 964 restocks that at least one feed caught.
Excluding downtime, my service alerted 429 restocks that the lower-priced service never sent, and 94 that the API feed did not alert on. The API feed caught 64 that I did not, and the lower-priced service caught 6. My next job is to understand those 70 and bring them to zero.
New SKUs are the other gap that matters. Remember “restocks we both caught” from the API-feed comparison above? If some restocks were caught by both of us, then some were caught by only one of us. Most of those are ordinary restocks on SKUs everyone was already tracking. The ones that matter most are the new SKUs Costco had just released, because that is where the head start is measured in days, not minutes. When Costco lists a new item, somebody or something has to add it to the tracking system. From what I measured, on other feeds that step happens after the first restock, not before it, so their users do not hear about a new SKU until it has already come and gone at least once. My system, however, detects new SKUs and adds them to my tracking catalog automatically. That gives my subscribers a head start on new Costco SKUs, sometimes by several days.
Ten gold SKUs restocked for the very first time during the research window. Compared with the API feed, I alerted the first restock earlier on seven of them, by more than four days on each of a pair of Argor-Heraeus bars. On two, that feed beat me: one by two days and the other by four minutes. Compared with the lower-priced service, I was ahead on eight of the ten, by fifteen minutes to a full day, and it was ahead on one.
New gold SKUs this window: who alerted the first restock
Every gold SKU whose first-ever online restock fell between May 18 and September 3, 2026. All times Mountain. Under each feed: how much later or earlier than my alert.
| SKU | Listed by Costco | My first alert | API feed’s first alert | Lower-priced service’s first alert |
|---|---|---|---|---|
| PAMP Liberty at 250, 1 oz | May 13 | May 19, 11:35am | May 19, 1:06pm1.5 hours later | May 20, 9:45am22 hours later |
| PAMP Lady Fortuna, 10 g | May 18 | May 19, 11:35am | May 19, 11:38pm12 hours later | May 19, 11:50am15 minutes later |
| PAMP Lady Fortuna, 5 g | May 19 | May 20, 10:49am | May 20, 12:17pm1.5 hours later | May 21, 12:08pm1 day later |
| PAMP 250th Anniversary, 2.5 g | May 28 | May 28, 1:32pm | May 29, 8:00am18.5 hours later | May 28, 5:11pm3.5 hours later |
| PAMP West Coast Kayaker, 1 oz | Jun 9 | Jun 15, 11:52am | Jun 15, 1:24pm1.5 hours later | Jun 15, 1:07pm1.3 hours later |
| PAMP Good Luck Maneki Neko, 1/2 oz | Jul 2 | Jul 8, 1:37pm | Jul 6, 1:19pm2 days earlier | Jul 7, 11:23am1 day earlier |
| Argor-Heraeus, 1 oz | Jul 22 | Jul 24, 3:05pm | Jul 29, 3:46am4.5 days later | Jul 24, 7:36pm4.5 hours later |
| Argor-Heraeus, 10 g | Jul 22 | Jul 24, 3:05pm | Jul 29, 3:44am4.5 days later | Jul 24, 7:36pm4.5 hours later |
| PAMP Good Luck Phoenix, 5 g | Aug 10 | Aug 11, 12:25pm | Aug 11, 12:22pm4 minutes earlier | Aug 11, 1:12pm47 minutes later |
| Sunshine Minting Breakaway, 1 oz | Aug 3 | Sep 1, 11:15am | never | never |
The curious case of the missing Sunshine bar. Here is a clear example of a difference I did not expect to be this drastic. Costco listed the Sunshine Minting Breakaway gold bar (SKU 2095085) on August 3. It restocked for the first time on September 1 and seven more times over the next two days, and my subscribers got an alert for every one of them, eight restocks plus four price changes, twelve alerts in all. The other two feeds have yet to send a single alert on it. One had not added it to its system at all, while the other added it only after those restocks had come and gone.
Something else worth mentioning: ownership. The alert system I offer is my own code, end to end. Detection, pricing, filtering, delivery, and ultimately responsibility. Many alert services pass along a feed that somebody else runs. When that feed adds a SKU late, they add it late. When it goes quiet, they go quiet. Owning the whole thing matters for three reasons. For starters, every restock and price I log ends up in the dashboard’s analytics, available to all subscribers. It lets me measure my own service and run analyses like this one. And most importantly, it lets me react quickly when something goes wrong: fix it fast, then harden the code so it does not happen again. That is what reliable means to me. Not a promise that nothing will ever break, but a system where, when something does, it gets fixed quickly.
3 of 3
Personalized
Over time, a generic alert can simply turn into noise. By generic I mean the same ping everyone gets, with nothing on it but the fact that something restocked. For an alert to be truly useful, it needs the level of detail that makes it actionable for you, and neither of the feeds I measured offers it.
Think about it. Of the last fifty restock alerts you received, how many were actually a good deal for you, at your own profit and margin thresholds? If the honest answer is a handful, then the rest were noise. And a feed that pings you for every one of them trains you to ignore it. That is how the good deals get missed.
The layer on top of the alert, the one that adds value, is the part you customize. It starts in your dashboard, with a watchlist you can set up or change in a minute: the SKUs you care about, by metal, by weight or by name. That alone cuts the noise down to the SKUs you actually want to hear about. You can set that watchlist to alert you only at a Costco price you are willing to pay, or at a percentage over spot you are willing to accept. You can go further still and add the buyers you are interested in selling to and the payouts they are offering, so you are only alerted when a SKU meets your buy price, your sell price, or the margin between them. After that, an alert means one thing: this item just restocked at a price that makes it a good deal for you. You act instead of evaluate.
Yes, there are options out there that will alert you whenever a Costco SKU restocks, and some of them are quite fast. What those alternatives do not offer is everything that turns a stock signal into a decision: the filters, the margin math against live buyer payouts, the new SKUs that appear on their own, the alert that reaches your phone with the number you actually care about on it. That is the part that usually goes unnoticed. Yet once you put it to work, it does not just speed up your decisions, it puts your own numbers in front of you, so you do not have to work them out on the spot.
Personalize your alerts: set up your watchlist.
Don’t take my word for it!
Let's be honest: I built this service, so of course I believe in it. But none of that matters if you do not see it the same way. So do not take my word for it. Put my service to the test. Compare it against any other alternative you are exploring, and if you find a place where it falls short, tell me. Everything I have built here is the product of iteration, customer feedback and fair criticism, so I welcome any chance to strengthen my alerts and my service overall based on what you find. Please do not hesitate to reach out.
Not a subscriber? The free trial gives you seven days to put all of this to the test.
Thank you,
Carlos
Methodology: how I measured these restock alerts
Everything above comes from alert timestamps, side by side, on the same SKUs.
- Window: May 18 to September 3, 2026.
- Coverage: I selected 16 gold SKUs that all three services alerted on during the window, including the most restocked one, the 1 oz PAMP Suisse Lady Fortuna bar.
- What “first” means: timestamps were compared to the minute. The same minute counts as a tie, and only a full minute earlier counts as first.
- Exclusions: the numbers exclude the hours my service was down for maintenance, proxy problems or bugs. I excluded those hours for all three feeds.