> ## Documentation Index > Fetch the complete documentation index at: https://docs.sourcedock.io/llms.txt > Use this file to discover all available pages before exploring further. # Alerts, in depth > One made-up morning on Alerts: every row, what makes it show, what clears it, and what to do. > [!NOTE] > > **Scenario for this page:** the demo store's Alerts at 5 PM on its seed day, with 19 things to look at. Bluey plane (10 bought at \$10.00): 4 never came from the store, 40 days before the seed day. Darn Tough socks (10 at \$12.00): 2 never came. Grogu plush (\$12.00 cost): Amazon lost 1, 55 days before, and 5 days are left to claim it. Uni-ball pens: you marked 2 fewer sent than Amazon got. Find them on Alerts (press T) under **Everything**. The pictures show the demo store; the walk below keeps its made-up blender, truck and lamp. Alerts is the list of things that need a look. The short tour is [Alerts](https://docs.sourcedock.io/desk/alerts.md). This page walks one made-up morning, in the order the screen shows it. Press T on any page to open Alerts. The key does nothing while you type in a box. Most rows below are about three of your products. "Home Blend 600" is a blender, `B0EXAMPLE1`. "Red Hauler" is a toy truck, `B0EXAMPLE2`. "Desk Glow Lamp" is a lamp, `B0EXAMPLE3`. Today is October 28. The page title is **Alerts**. Under it, this morning reads "29 things to look at." The bell button at the right opens the sound and pop-up switches. A screen reader calls it **Sounds and pop-ups**. ![The page title Alerts, and under it the line 19 things to look at.](https://mintcdn.com/sourcedock/4cpclnZ0nomRxBsq/images/deep-dives/alerts-in-depth/01-demo-title.png?fit=max\&auto=format\&n=4cpclnZ0nomRxBsq\&q=85\&s=9976302d20854e6ee1fae3c743a92902) Demo store: the top of Alerts. Notice the line under the title counts 19 things to look at. ## What the chips count **SHOW ME** is the row of filters. A screen reader calls it **Show me**. Each chip shows how many rows sit in it, after the ones you hid. **Everything** shows the whole list. ![A row of chips after the words Show me: Everything 19, Claims ready \$110.00 6, Possible claims 1, Not received 1, Selling slowly 1, Not on pace 1, Selling out fast 1, Fix counts 8, Buy next 0, and Early warnings 0.](https://mintcdn.com/sourcedock/4cpclnZ0nomRxBsq/images/deep-dives/alerts-in-depth/02-demo-chips.png?fit=max\&auto=format\&n=4cpclnZ0nomRxBsq\&q=85\&s=8f2b2271a62aa89b17711ce8e71e10da) Demo store: the Show me chips. Notice Claims ready shows \$110.00, the same Ready to claim total as the Desk. | Chip | Count | | - | - | | **Everything** | 29 | | **Claims ready** | 2, and "\$29.60" | | **Possible claims** | 1 | | **Not received** | 3 | | **Selling slowly** | 1 | | **Not on pace** | 1 | | **Selling out fast** | 1 | | **Fix counts** | 10 | | **Buy next** | 4 | | **Early warnings** | 4 | Add the chips after **Everything**: 2 + 1 + 3 + 1 + 1 + 1 + 10 + 4 + 4 = 27. Two more rows sit in a box on top. They show under **Everything** only, so 27 + 2 = 29. The "\$29.60" on **Claims ready** is your Ready to claim total, the same figure the Desk shows. This morning it is the two claim rows added up: \$21.00 + \$8.60 = \$29.60. If your Ready claims have units but no dollars, the chip shows the units, never "\$0.00". While SourceDock checks your claims again, a grey bar takes the place of that money and count. A screen reader hears "Claims ready is updating". The list then has one row, **Ready to claim: updating**, with the line **SourceDock is rechecking this store's claims. They show here when it's done.** Each row has a bold title, a small tag, and a grey line after the tag. A claim row's tag says **Claim**. Every other row's tag is its chip's name. The two rows in the top box have no tag. The title and grey line are the alert's short words. A pop-up uses its longer title and line. ## The box on top These two rows sit above the cards, and only under **Everything**. "Rating dropped from Good to At risk" Grey line: "Account health · rating 180, At risk". Button: **Open Health**. Account health is Amazon's score for your seller account. The bands are **Good**, **At risk**, and **Critical**. Here the band fell from Good to At risk, and the score on that check is 180. If the same check also found a new IP complaint, the title is "1 new IP complaint" instead. Two or more say "complaints". The row shows a band drop or new IP complaint from the last 7 days. A newer drop or complaint is a new row. If you hide this one, it stays hidden for that check. This row exists only while **Health strip on desk** is on, your plan includes Account health, and a store is picked. That switch lives on Account > Features. While it is on, the Desk shows Account health in place of **Needs you**. See [Account health](https://docs.sourcedock.io/desk/account-health.md). **Recovery sync failed** Grey line: "Last full sync was 2 days ago." Button: **Review**. A sync pulls your Amazon numbers into Capital Recovery. This row shows only when the last pull failed. A slow pull that did not fail is never a row. The day count is whole 24-hour days since the last full pull, so "2 days" means at least 48 hours but under 72. If no time is stored, the line is **Capital Recovery has not checked Amazon recently.** The row leaves when a later pull works. ## Purchases The card name is **Purchases**. The count reads "9 alerts". A card shows ten rows, then **View more**. This one has nine, so there is no **View more**. Each row's button is the word at its right. A card can also have a **View all** button. It opens Purchases on just the orders the rows count. Its hover says **Opens Purchases showing just these purchases.** It shows only when every row on the card names its orders, there are at least 2 orders, and no more than 5,000. This morning the refund row and the auto-cancel notice don't name their orders that way. So this card has no **View all**. Pick **Fix counts**, and the card shows it. ![The Purchases card with 6 alerts and a View all button. Rows: 6 units never arrived from the store (Open orders), 1 purchase may be missing Sent (Mark sent), Count too low on 1 order, Sent count typo on 1 product with Amazon got 2 more than you marked sent, Too many marked sent on 1 product, and Add what you paid for 2 products (Add cost). Each row has a clock and an X.](https://mintcdn.com/sourcedock/4cpclnZ0nomRxBsq/images/deep-dives/alerts-in-depth/03-bluey-purchases-card.png?fit=max\&auto=format\&n=4cpclnZ0nomRxBsq\&q=85\&s=7613e0878d83c1a42e9c861b209f012f) Bluey plane and Darn Tough socks: the Purchases card. Notice 6 units never arrived leads the card, with an Open orders button. "8 units never arrived from the store" Grey line: "Mark them never arrived, or enter how many came." Tag: **Not received**. Button: **Open orders**. Say one order of 20 blenders is at least 14 days old. You counted 12 in, and you marked none as sent. Units that came in are the larger of what you counted and what you marked sent, never more than you ordered. That is 12. Still out is 20 minus 12, minus write-offs you already answered. You answered none, so 8 are still out. An order younger than 14 days adds 0. So does an imported order still on the status the import gave it. The row leaves when those 8 are counted in or marked never arrived. It waits until your purchases have loaded. Its pop-up adds that you can open each order. “2 purchases may be missing "Sent"” Grey line: **Amazon has the units; your orders don't say they shipped.** Tag: **Fix counts**. Button: **Mark sent**. Amazon holds units of products that two of your orders don't show as sent. The row asks. It never says you forgot. The pop-up title is **Forgot to mark Sent?** The row leaves when those orders are marked sent, or the gap is gone. It waits until SourceDock has read your starting stock. "Count too low on 1 order" Grey line: **Amazon holds more. Fix the received count.** Tag: **Fix counts**. Button: **Review**. One order's received count is under what Amazon holds. The pop-up title is **Count too low. Amazon holds more units than your purchase orders count**. The row leaves when the received count catches up. "Sent count typo on 1 product" Grey line: "Amazon got 4 more than you marked sent." Tag: **Fix counts**. Button: **Review**. Amazon received more than you marked sent. The 4 is all of these gaps added up, not the biggest one. The row shows only when the shipment row SourceDock saved shows that gap. The pop-up title is **Sent count typo. Amazon got more than your orders say were sent**. "Too many marked sent on 1 product" Grey line: **Check for a cancelled shipment or a typo.** Tag: **Fix counts**. Button: **Review**. This is the other way around. Your orders say more were sent than your shipments told Amazon. The pop-up title is **Marked too many sent. Your orders say more were sent than your shipments told Amazon**. "Add what you paid for 1 product." Grey line: **Open Purchases and type the cost.** Tag: **Fix counts**. Button: **Add cost**. This row is about purchases SourceDock made from Amazon's records, Found at Amazon or imported from Amazon, that have no cost. They count while they still have units or have already sold some. A cancelled one is left out, and so is one where you said you don't know the cost. One that your own unsent order covers is left out too, because that one asks you to mark the order sent. When the purchases and the products differ, the title adds the purchases, like "Add what you paid for 1 product (2 purchases)." A blank cost is never read as \$0. The row waits for your purchases and the no-cost check. If that check fails, the row is left out. "1 product sold more than you bought." Grey line: **Check the counts.** Tag: **Fix counts**. Button: **Review**. Say another order bought 10 blenders, and its books have used 12. Used units are sold, plus ones you shipped yourself, minus returns, plus unfulfillable, lost, damaged, and disposed, minus units later found. 12 is over 10, so it counts. Equal is not over. The count is products, not orders. The row waits until Capital Recovery's books are in. "Refund not received: \$64.00 from Toy Barn, cancelled Oct 10" Grey line: **Still counted as out. Mark the refund on Write-offs when it comes.** Tag: **Not received**. Button: **Review**. "Toy Barn" is the source you typed on that order. Without one, it is the link's website, else "the store". "Oct 10" is the cancel day, read in UTC. The money counts as out until you mark the refund on Write-offs. The row comes back each week, starting Monday (UTC), even if you hid it, until you answer. If the same order still has an auto-cancel notice, this row waits, so one order is never two rows. This morning they are different orders, so both show. "SourceDock cancelled your Oct 1 order of 6 × Red Hauler. Nothing from it was marked received or sent in 14 days. If it came or is still on its way, uncancel it." There is no grey line. Tag: **Not received**. Button: **Open**. This notice comes from the **Auto-cancel purchases that never arrive** switch. The 6 is the units on that order. The 14 is the day count set when SourceDock cancelled it. The button opens that order on Purchases, where you can uncancel it. The notice shows for 14 days after the cancel. It leaves sooner if you answer the refund question, uncancel the order, or edit it. ## Recovery The card name is **Recovery**. The count reads "15 alerts". Ten rows show, then **View more**. **View less** closes it again. Its **View all** opens Capital Recovery on just these products. The hover says **Opens Capital Recovery showing just these products.** It shows only when every row on the card names its products, and there are at least 2. Unlike Purchases, there is no top limit. A very long list still opens the same products. This morning two early warnings don't name products, so there is no **View all** under **Everything**. Pick **Fix counts**, and it shows. Claims with 6 or fewer days left lead the card, soonest first. Claims that may be too late come right after them. Claims with more time sit lower, after the dock and missing-unit rows, by days left. ![The Recovery card with 13 alerts. First row: \$12.00 ready to claim, 1 unit of Mattel Star Wars Grogu Plush Toy, 5 days left. Then 1 product came up short at the dock, 1 product Amazon can't find, \$8.00 ready to claim for the whale shark plush with Claim by Dec 2 (35 days left), more claims with later days, 1 product needs a look, 1 product with a return issue, and View more.](https://mintcdn.com/sourcedock/4cpclnZ0nomRxBsq/images/deep-dives/alerts-in-depth/04-grogu-recovery-card.png?fit=max\&auto=format\&n=4cpclnZ0nomRxBsq\&q=85\&s=ac75d661d112775ef68754188fce1a1c) Grogu plush: the Recovery card. Notice Grogu's \$12.00 claim with 5 days left is first, and the whale's claim with 35 days left sits after the dock rows. "\$21.00 ready to claim" Grey line: "4 units of Home Blend 600. 5 days left." Tag: **Claim**. Button: **Open**. The 4 units and the \$21.00 are the blender's Ready claim lines added up. "5 days left" means the last day is 5 days from today. The line reads **Last day to claim** on the last day and **1 day left** the day before. From 2 to 7 days, it reads like "5 days left". Past 7 days, it names the day, like "Claim by Dec 12 (45 days left)". **Open** opens the claim lines on Capital Recovery. Some Ready claims are units Amazon counted in a box and then took back. Then the row also shows **I didn't send these**. The row leaves when that product has no Ready claims. Needs a look, a window not open yet, and a window that has passed are never Ready. "\$8.60 ready to claim" Grey line: "1 unit of Red Hauler. May be too late to claim, but Amazon may still accept it." Tag: **Claim**. Button: **Open**. The box's early claim-by day has passed, but its claim still stands. So the late words take the place of the day count. One unit says "it", and more say "them". In the few extra days past a claim's last day, the line just says **May be too late to claim**. If a product's Ready claims have units but no dollars, the title is **Ready to claim** with no money. "1 product came up short at the dock" Grey line: "Amazon counted 6 fewer than you sent." Tag: **Fix counts**. Button: **Review**. A closed shipment said 20 blenders, and Amazon checked in 14. 20 minus 14 is 6. Units Amazon paid for or denied come off that 6, and this morning both are 0. Extra units past what you bought are a typo, not missing. Open boxes don't count, and a box whose claim time is over drops off. A short with no purchase behind it is the next row, not this one. The row waits until your inbound shipments load. It leaves when payments and denials cover the short. The pop-up title is **Amazon counted fewer at the dock than they recorded as shipped**. "1 product may be short at the dock" Grey line: **Check how many you bought first.** Tag: **Fix counts**. Button: **Review**. No purchase backs this short, so the row never asks you to open a case. It leaves when a buy count explains it, or the short is gone. "1 product Amazon can't find" Grey line: **Checked in, then missing.** Tag: **Fix counts**. Button: **Review**. Amazon checked units in, and they are not in stock or in sales. The list it opens can include units Amazon is still looking for. It is not a claim until Amazon logs a loss. The pop-up title is **We cannot account for some units Amazon counted in**. "1 product needs a look" Grey line: **Check it before you claim.** Tag: **Possible claims**. Button: **Review**. Amazon may owe you for some units, but check first. Two or more products read "need a look" and **Check these before you claim.** This row does not wait for inbound shipments. It stays off **Needs you**, because the Desk's Found for you tiles show it. ![The Recovery card showing one row: 1 product needs a look, tagged Possible claims, with the line Check it before you claim and a Review button.](https://mintcdn.com/sourcedock/4cpclnZ0nomRxBsq/images/deep-dives/alerts-in-depth/08-bic-needs-a-look.png?fit=max\&auto=format\&n=4cpclnZ0nomRxBsq\&q=85\&s=48c053825822ae1e586425c5a7289983) BIC pens: the Possible claims chip picked. Amazon took 1 pen pack out of stock 35 days before the seed day and never paid. Notice the row says needs a look, not ready to claim. "1 product with a return issue" Grey line: **The buyer got a refund, and the item never came back.** Tag: **Fix counts**. Button: **Review**. Two or more read **Buyers got refunds, and the items never came back.** Its tag is **Fix counts**, so **Claims ready** never counts this money twice. This row stays on **Needs you**. **Reorder soon** Grey line: "1 winner running low". Tag: **Buy next**. Button: **Review**. Restock reminders are on unless you turn them off. See [Restock reminders](https://docs.sourcedock.io/desk/restock-reminders.md). By default they look at products with ROI at least 5%. They remind you when 10% of the units you bought are left, with a 21-day lead time. A product that sold fewer than 3 in the last 30 days gets no reminder, and neither does a run under 7 days old. Under the row, up to three products show, then "and 1 more" if there are more. This morning there is one, the lamp. You bought 240 and 24 are left, which is 10%. It sold 90 in the last 30 days, which is 3 a day. 24 divided by 3 is 8 days left. Its chip is **Reorder today**, because 8 days is less than the 21 days a new order takes. The chip counts the days until you should reorder: days left minus lead time. When that is above 0, the chip reads like "In 8 days". With none left, the chip is **Out of stock**, and the days come off the line. The line under the name reads "Sells about 3 a day · 8 days left · ROI 48%". Under 2 a day, it counts by the week, like "about 9 a week". ROI there is a whole percent. The pop-up title is "1 product to reorder". Its line is "It makes money and is down to 10% of what you bought." If you remind by days instead, it says the stock will run out before a new order can reach Amazon. The row itself keeps **Reorder soon**. The row waits until your Amazon stock, inbound shipments, and purchases have all loaded. It leaves when nothing needs a reminder. If you hide it, it stays hidden until a new product joins it. Once a day per store, when a product joins the list, your phone can say "Recovery: 1 product to reorder." The bell's email icon does not send reminders. The **Restock reminders** card on Account > Features does. Its **Email** switch starts off, and its **Phone notification** switch starts on. The email's subject is "1 product to reorder". It ends with **You get this email at most once a day, only when a product needs a reminder. Change it in Account > Features.** "2 products selling slowly" Grey line: "1 had no sales in the last 30 days · 1 is selling too slowly to pay back". Tag: **Selling slowly**. Button: **Review**. One row holds up to three parts, joined with a dot. A run is one stretch of stocking a product, and each run lands in one part at most. The title counts all the parts, so 1 plus 1 is 2. ![The Recovery card showing one row: 9 products selling slowly, with the grey line 7 had no sales in the last 30 days · 2 are selling too slowly to pay back, and a Review button.](https://mintcdn.com/sourcedock/4cpclnZ0nomRxBsq/images/deep-dives/alerts-in-depth/05-demo-selling-slowly.png?fit=max\&auto=format\&n=4cpclnZ0nomRxBsq\&q=85\&s=5ae2a7eadb2657c8bf86ab5813de052c) Demo store: the Selling slowly chip picked. Notice the title adds the two parts: 7 with no sales plus 2 too slow is 9. The truck has units on Amazon's shelf, and Amazon last sold one 40 days ago. That is 30 days or more. It still has "\$16.00" out, which is at least \$5.00. Still out is the loss on its Capital Recovery row, never below \$0. With no profit figure yet, it is money spent minus money back. Units sitting with you don't count here. The truck drops off this part after a sale, when less than \$5.00 is out, or when nothing is on Amazon's shelf. The blender has sales. It needs to sell 210 more units to earn back its cost, and it sold 30 in the last 30 days. 210 divided by 30 is 7 months. That is over 6, so it lands on the second part. The 30 days are the last 30 days it was in stock, looking back at most 90 days. A run younger than 30 days is scaled. One 10 days old with 4 sales sells 4 divided by 10, times 30, which is 12 per 30 days. This part only counts while the run still has enough units left to earn back its cost. It leaves when the months drop to 6 or fewer. A third part is for a product with no sale at all since it arrived, 21 days or more, with units for sale. A product already in the 30-day part never lands here too. It reads "1 hasn't sold since it arrived 3+ weeks ago". This morning nothing is in it, so those words are not on the row. "2 products not on pace to pay back" Grey line: **At their last 30 days' pace, these products won't earn back what's left of their cost in 90 days.** Tag: **Not on pace**. Button: **Review**. Both the truck and the blender are here. The truck sold 0 in a full 30 days, and 0 sales flags on its own. The blender needs 210 more and sells 30 every 30 days. 210 divided by 30 is 7, and 90 days is 3 times 30. 7 is over 3, so it flags. With one product, the line is **At its last 30 days' pace, this product won't earn back what's left of its cost in 90 days.** ![The Recovery card showing one row: 11 products not on pace to pay back, with the line At their last 30 days' pace, these products won't earn back what's left of their cost in 90 days, and a Review button.](https://mintcdn.com/sourcedock/4cpclnZ0nomRxBsq/images/deep-dives/alerts-in-depth/06-demo-not-on-pace.png?fit=max\&auto=format\&n=4cpclnZ0nomRxBsq\&q=85\&s=51080ee5f815cc38f26babb86d501db3) Demo store: the Not on pace chip picked. Notice the grey line says these products, because there are 11. The test needs an open lot, a known cost, a run that started 30 or more days ago, units for sale, and units still to sell to earn back the cost. So a buy from last week never flags. The row leaves when the pace catches up, or the cost is earned back. The truck is on this row and on the slow row. The slow row says it is not selling. This row says its cost won't come back in 90 days. They answer different questions, so both can show. "1 product selling out fast" This row is the 11th in the card, so this morning it sits behind **View more**. ![The Recovery card showing one row: 2 products selling out fast, with the line At their last 30 days' pace, the units left run out within 30 days, and a Review button.](https://mintcdn.com/sourcedock/4cpclnZ0nomRxBsq/images/deep-dives/alerts-in-depth/07-demo-selling-out-fast.png?fit=max\&auto=format\&n=4cpclnZ0nomRxBsq\&q=85\&s=af61abb56195aeff10bcabd6faacf3fa) Demo store: the Selling out fast chip picked. Notice the row counts 2 products. Grey line: **At its last 30 days' pace, the units left run out within 30 days.** Tag: **Selling out fast**. Button: **Review**. The lamp has 24 left and sold 90 in the last 30 days. 24 divided by 90 is about a quarter of a month, about 8 days. That is under 1 month, so it flags. The truck sold 0, so it has no pace, and it is not here. The row leaves when more than 30 days of stock are left, or nothing is left to sell. The 8 days here is the same math as the lamp's "8 days left" under **Reorder soon**. The reorder chip is the one that differs, because it takes off the lead time. ## Early warnings These four are the last rows in the Recovery card. They are heads-ups that compare the store with its own past. They carry no dollars, so they stay on Alerts, off **Needs you**, and out of the Desk's wheel count. They never buzz your phone. The button is **Review**, or **Open** when the row names one product. **More boxes are coming up short** Grey line: "Amazon counted fewer units than you sent in 4 of your last 12 boxes. That's more than usual for you. Check your box labels and counts." The 4 and the 12 are the warning's own counts. When most short units went to one warehouse, the title names it, like "More boxes sent to PHX7 are coming up short". "More returns marked damaged at PHX7" Grey line: "2 of your last 8 returns there were marked damaged. Usually it's 1 in 10 for you." "2 of 8" is the latest stretch. "Usually" is the older stretch. A share of 0.1 is 1 divided by 0.1, which is 10, so it reads "1 in 10". A share of 0 reads "almost none". Under one half, it reads "1 in" a number of 2 or more. At one half or more, it reads a number of 10 or less, then "in 10". When returns came back damaged across warehouses, the title is **More of your returns are coming back damaged**. **You're paying Amazon's low-stock fee** Grey line: "Desk Glow Lamp ran low, so each sale costs about \$1.20 more. Send more units to stop the extra fee." Button: **Open**. The extra is the fee now minus the fee before: \$4.40 minus \$3.20 is \$1.20. **Shipping fee went up on this product** Grey line: "The fee on Red Hauler went from \$5.10 to \$5.85 a unit. Amazon's size for it didn't change. Ask Amazon why." Button: **Open**. The size did not change, so the row does not guess at a reason. ## Vault Vault is where you save products you might buy. The card name is **Vault**, and the count reads "2 alerts". Both rows have the tag **Buy next** and the button **Open**. The Vault card has no **View all**. "Trail Mug down to 19 offers" Grey line: "Your alert: 20 or fewer offers · Profit +\$9.86 · ROI 44.8%" You set an alert for 20 offers or fewer, and the check saw 19. Profit above \$0 gets a plus. A loss gets a minus. ROI shows one decimal. When more than one part of your alert hit, the title uses the first, in this order: offers, profit, ROI, then the two sell-price parts. Profit and ROI are left off the grey line when there is no figure for them. The row shows for 7 days. The same alert fires at most once a day while it stays true. Each firing is its own row, so hiding today's does not hide tomorrow's. On the Desk, two or more Vault rows become one line, like "2 Vault alerts". Your phone can say "Vault: 1 product hit your alert." "Puzzle Cube now at 24% ROI" Grey line: **It makes money now.** You saved this product 30 calendar days ago, on September 28, counted on your clock. Its price was checked in the last 3 days, and its ROI is at least 20%. The ROI rounds to a whole number, so 24.4 reads 24. At most 3 of these show, real ROI first, highest first. A buy cost under \$1.00 makes the ROI hard to believe. Then the title is "Check the buy cost of Puzzle Cube", and the grey line is **Its ROI can't be trusted.** With no sales estimate, the grey line is **It has no sales estimate.** The pop-up title adds the days: "Puzzle Cube now at 24% ROI, 30 days after you added it". ## Scout Scout watches storefronts you pick. It is on for everyone, so this card shows whenever you have new finds. The name is **Scout**, and the count reads "1 alert". See [Scout](https://docs.sourcedock.io/source/scout.md). "3 new finds on Blue Shelf Deals" Grey line: **Review them on Scout.** Tag: **Buy next**. Button: **Review**. There is one row for each storefront with new finds, up to five, then one more row for the rest, like "4 new finds on other storefronts". One find reads "find". Hiding a row holds while that storefront's finds pile up. Scout rows are never on **Needs you**. The Scout pill on the bar counts the same finds. ## The bell Open the bell. There is one line per area. **Purchases**, **Recovery**, and **Vault** always show. **Scout** and **Health** show once they have rows, so this morning all five show. ![A panel with three lines, Purchases, Recovery and Vault, each with a chat bubble, an envelope and a speaker icon. Under them: Sound, Pick one, a menu set to All, and four tones, Dock bell (two-tone, picked), Sonar ping, Tick and Ship's whistle, then the line Plays when a new alert pops up, only where Sound is on.](https://mintcdn.com/sourcedock/4cpclnZ0nomRxBsq/images/deep-dives/alerts-in-depth/09-demo-bell.png?fit=max\&auto=format\&n=4cpclnZ0nomRxBsq\&q=85\&s=c5d1938435f92838881edf09f36e62ed) Demo store: the bell opened. Notice only Purchases, Recovery and Vault show, because the demo store has no Scout or Health rows. Each line has small icons: a chat bubble for pop-ups, an envelope for email, a speaker for sound, and a phone. The hover says what a tap does, like "Mute toast for purchases" while Purchases pop-ups are on. The envelope's hover says "Email for purchases: coming soon". It never turns on and sends nothing. The pop-up and sound choices are kept in this browser. | Area | Pop-up starts | Sound starts | Phone starts | | - | - | - | - | | Purchases | on | on | on | | Recovery | on | on | on | | Vault | off | off | on | | Scout | on | off | off | | Health | on | on | on | The phone icon shows once phone alerts work in this browser. On an iPhone in a Safari tab, a tap shows how to add SourceDock to your Home Screen first. Phone choices are saved with your login. Until one of your devices is set up, every phone icon stays dim. Scout's phone also needs Scout alerts on, and Health's needs **Health strip on desk**. See [Phone app](https://docs.sourcedock.io/get-started/phone-app.md). Under the switches is **Sound**. **SAME AS ALL** means the area you picked has no tone of its own, so it plays the All tone. Any other time it says **PICK ONE**, even with **All** picked. A screen reader calls the menu **Sound for**. Its choices are **All**, **Purchases**, **Recovery**, and **Vault**, plus **Scout** and **Health** once they have rows. A screen reader calls the tone list **Alert sound**. The tones are **Dock bell** (**TWO-TONE**), **Sonar ping** (**PING**), **Tick** (**TICK**), and **Ship's whistle** (**SWEEP**). The line under them reads **Plays when a new alert pops up, only where Sound is on.** A tone picked under **All** sets every area. Tones are saved with your login. ## Pop-ups Pop-ups and chimes happen while the Desk or Alerts is open. The Vault page also pops and chimes for Vault alerts while it is open, using the bell's **Vault** switches. The first list after you open the page is not news, so it does not pop or chime. After that, a new row pops up if its area's pop-ups are on. One chime plays, in the tone of the top new row whose area has sound on. A pop-up stays 15 seconds, and pointing at it pauses it. One new row shows its long title and line. Several new rows from one area read "2 new Purchases alerts" over the top row's title. Rows from several areas read "4 new alerts". Under that, each area shows a dot in its color, then its name and count, like "Vault 3" and "Purchases 1", in rank order. The strip on top shows the area in capitals, like **PURCHASES**, or **ALERTS** for a mix, then **now**. The buttons are "Open Purchases" (that area's name, or "Open Alerts" for a mix) and **Snooze**. **Snooze** hides every row in that pop-up until the start of tomorrow, on your clock. The X closes it. A screen reader calls it **Close**. ## Phone buzzes Only some rows can buzz your phone: a Vault alert firing, new Scout finds after Scout alerts are on, the daily reorder line, and an auto-cancel notice. Early warnings never buzz. Every other row stays on the page. The lock screen title is **SourceDock**. It shows counts only, never product names or dollars, so anyone near your phone sees nothing private. There is one line per area, in the page's order. With four or more areas, two lines show, then a line like "And 2 more." A tap opens Alerts on **Everything**. | What buzzes | What the line says | | - | - | | An auto-cancel notice | "Purchases: 1 thing to check." | | The daily reorder line | "Recovery: 1 product to reorder." | | A Vault alert | "Vault: 1 product hit your alert." | | New Scout finds | "Scout: 3 new finds." or "Scout: 12 new finds on 3 storefronts." | A buzz waits until the oldest waiting notice is 5 minutes old, so a burst is one buzz. That buzz carries every notice that is waiting. You get at most 5 buzzes a day, on your clock. At the limit, the rest wait and get looked at again each hour. Vault and Scout share one quiet clock: at most one buzz with either of them every 3 hours. Purchases and Recovery skip that clock, but they still count toward the 5. A notice held back by these limits goes out with the next buzz. A phone that is off gets a waiting buzz for up to 24 hours. Some notices never buzz, but their rows stay on the page. That covers anything from before your first phone was set up, and anything that came while that area's phone icon was off. It also covers notices on a paused plan, and a notice SourceDock could not look at within 24 hours. ## Hide a row The X on a row is **Hide for 7 days**. It hides the row for 7 days from now. The clock next to it has the hover **Hide for a different window**. It opens **HIDE THIS ALERT FOR**, with **1 hour**, **Until tomorrow**, **7 days** marked **DEFAULT**, **30 days**, and **Custom...** ![A small menu titled Hide this alert for, with 1 hour, Until tomorrow, 7 days marked Default, 30 days, and Custom.](https://mintcdn.com/sourcedock/4cpclnZ0nomRxBsq/images/deep-dives/alerts-in-depth/10-demo-hide-menu.png?fit=max\&auto=format\&n=4cpclnZ0nomRxBsq\&q=85\&s=b5ab18fe6460ec61c2b01d3c532a8ba8) Demo store: a row's clock pressed. Notice 7 days is marked DEFAULT, the same as the X. **Until tomorrow** lasts until the start of the next day on your clock. **Custom...** shows a date box. A screen reader calls it **Hide until date**. The button is **Hide until this date**. A bad date says **Pick a real date.** A date already past says **That window has already ended.** A custom hide lasts through the end of that day. A small note then shows at the bottom right. It reads **TOAST**, then "Hidden for 7 days", then the row's title, then **Undo**. "Until tomorrow" reads "Hidden for tomorrow", and a custom date reads "Hidden for a custom window". A screen reader calls its X **Dismiss toast**. The note lasts 8 seconds. **Undo** brings the row back, with no pop-up. A hide is kept in this browser, and signing out clears it. Hidden rows leave the chips, the count, and the bar badge. A hide is for one row, and for one product when the row names one. So hiding the blender's claim does not hide the truck's. Some rows come back on their own. The refund row comes back each Monday (UTC) until you answer it. A Vault alert that fires again is a new row. **Reorder soon** comes back when a new product joins it. The health row comes back with a newer drop or complaint. ## Needs you and the badges **Needs you** is the short list on the Desk. It shows 3 rows, then **See more in Alerts** when Alerts has more. Its X is **Hide for 7 days** too. This morning **Health strip on desk** is on, so the Desk shows Account health in its place. Turn that switch off, and the health row leaves Alerts. **Needs you** comes back. **Needs you** leaves some rows to other places. Claim rows and the Needs a look row belong to the Desk's Found for you tiles. Scout rows belong to the Scout badge. Early warnings with no dollars stay on Alerts. Two or more Vault rows become one line. The order puts "8 units never arrived from the store" first, then "1 product came up short at the dock". Rows with a dollar figure come next, biggest first, then the rest in Alerts order. This morning no other row has a dollar figure. So the third row is "1 product may be short at the dock". The **Alerts** pill on the bar shows the full row count, "29". The bar sits at the bottom of the screen at first, and you can move it. Over 99, it reads **99+**. A screen reader hears "Alerts, 29 open". It is the last count the Desk or Alerts worked out. The Desk's wheel counts fewer, because it leaves out early warnings with no dollars. 29 minus 4 is "25 alerts". While the list loads, is paused, or fails, the wheel says **Alerts** with no number. A failed read can keep the last good counts for the same store. **Needs you** cuts the list further, so three places can show three numbers from one list. While Amazon's numbers are still matching, after a first sync, a rebuild, or an import, Recovery and Purchases rows are held. The health, refund, auto-cancel, Vault, Scout, and early warning rows still show. If the list is empty, you see **Amazon's numbers are still coming in. Alerts show once they're in.** A Canada store shows money with "CA\$" in front. A Mexico store has no Recovery rows. ## When the list is empty or stuck | What happened | What you see | | - | - | | The list is loading | **Checking the desks...** | | The read failed | **Could not load alerts. Open Purchases or Capital Recovery and try again.** | | The plan lapsed on a payment | "Alerts is paused", then **Nothing was deleted. We could not take payment - update your card and this turns straight back on.** Button: **Update payment** | | There is no plan | "Alerts pauses without a plan", then **Nothing was deleted. Choose a plan to turn this back on.** Button: **See plans** | | Nothing to show, and you hid nothing | **Nothing needs you.** | | Nothing to show, and you hid some | **Nothing needs you. Hidden alerts come back when their window ends.** | | **Claims ready** is empty | **No claims ready right now.** | | **Possible claims** is empty | **No possible claims right now.** | | **Not received** is empty | **No late purchases right now.** | | **Selling slowly** is empty | **Nothing selling slowly.** | | **Not on pace** is empty | **Everything is on pace.** | | **Selling out fast** is empty | **Nothing is selling out fast.** | | **Fix counts** is empty | **No counts to fix.** | | **Buy next** is empty | **Nothing new to buy.** | | **Early warnings** is empty | **No early warnings right now.** | | A link to one row, and that row is gone | **That alert was fixed or hidden. Nothing to do here right now.** | On a paused plan, a store with a delete date reads that date in place of "Nothing was deleted", like "SourceDock deletes your Amazon store data on Nov 30. Pick a plan before then to keep it." On the Desk, a failed read says "Could not load Alerts. Open the related tools to review them." A partial read says "Showing what loaded. Could not load Alerts." If **Needs you** is empty while Alerts still has rows it leaves out, it says **Nothing else needs you right now.** With nothing anywhere, it says **Nothing needs you. Good time to go find the next deal.** The link is **Check Scout** when Scout is on, and **Open Vault** when it is not. While **Needs you** loads, you see three grey bars and no words. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.