# Demand signals Source: https://docs.tightly.io/help/demand/demand-signals Reviewed: 2026-10-07 ## The question this page answers Which products need attention, what evidence explains the change, and what should I do next? ## What you see ::: shot page ::: Demand signals compares traffic, sales and stock. Findings carry their own evidence; a sales acceleration shows units and stock cover rather than an estimated money figure. The head shows **Explore in Ask**, the last nightly run's date and, once the run has loaded, **Flagged lines**. Check the run date before acting. **The six findings** are Hidden gem, Dead stock, Pricing resistance, Ghost revenue, Shelf warmer and Cooling trend. Read one finding's money against another's with care: two of them price stock at what you paid (Dead stock at units on hand times unit cost, Cooling trend at unit cost) and four price demand at what you sell. **The table** holds every flagged line, biggest money first, 25 at a time, with **Show {n} more**. Its columns are Product, Finding, Evidence, Money, Category and a menu. Evidence is two of the finding's own measures, such as views and add-to-carts over 30 days. Category is the line's capital quadrant, one of Winner, Traffic Driver, Sleeper and Bleeder, measured per warehouse: warehouses that disagree read Mixed, with the split on hover, and a line no warehouse has classified reads Not measured. Above the table sit the search (by product, variant or SKU), the Finding and Stock classification menus and the count of matching findings. An address that names a finding, as the link from Home does, narrows the table to that finding. Each line shows a named action, or **Review finding** when more context is needed. The More menu offers Why this line, then the action's door where one exists: Open in Smart Replenishment for Ghost revenue, Find a bundle for Dead stock and Shelf warmer, Open purchase orders for Cooling trend; then **Open the variant**. Pressing a row opens the same drawer. **The drawer** names the product, finding and SKU. **Potential impact** is followed by an evidence grid with each served measure. Missing measures show a quiet marker; focus or hover reveals the recorded reason. The document icons reveal the impact formula and any calculation context, and carry accessible descriptions. **Open the variant** and the finding's available navigation action sit in the footer. **Sales accelerating** identifies a variant selling faster for a particular channel and warehouse, comparing the last seven completed days with the preceding three weeks expressed per week. **Review replenishment** opens the same variant and warehouse. No money estimate is shown for this finding. **Launch running ahead** identifies a new item selling at or above its set multiple of what its plan or launch forecast expected over the same weeks (pace at least the ratio times expected). Whether stock cover is shorter than the supplier lead time is evidence on the row, not a condition for the finding. The evidence grid shows the first sale, units sold against expected, the pace and weekly pace, stock on hand and inbound, cover at the recent pace and the lead time; **Review replenishment** opens the variant. No money estimate is shown for this finding either, and the same sentence reaches the notification menu. **Recorded sales** identifies findings based on imported sales, including NetSuite. Sales and stock findings do not require Google Analytics; connecting GA4 adds traffic-based findings. Nothing is written here. There is no dismiss, snooze or resolve: each run replaces the last, so a finding leaves when the next run stops flagging it. ## What to do 1. Start at the top of the table, where the money is biggest, or choose a **Finding** and optionally a **Stock classification**. 2. Open **Why this line** before you act, to see the evidence behind the money. 3. Use **Open in Smart Replenishment** for Ghost revenue, **Find a bundle** for Dead stock or Shelf warmer, or **Open purchase orders** for Cooling trend. Use **Open the variant** to inspect Pricing resistance or Hidden gem. 4. On Sales accelerating, press **Review replenishment** to check incoming supply before saving a buying decision. 5. Come back after the next run; there is no dismiss, snooze or resolve. ## When it is empty or failed A tenant without the Demand signals capability sees: > Demand signals are not switched on for this tenant. Sales and stock findings remain available without Google Analytics. Connecting Analytics adds traffic evidence after its source has been reviewed and measured; a missing connection does not close this page. When Analytics mappings require review, or source evidence cannot be verified, the header identifies **Native sales and stock** as the evidence for current findings. Retained unreviewed traffic findings stay out of current counts and tables. Review each property's traffic findings, reporting days and price response under **Analytics sources** in Integrations. Once the page is open, the head may say: > Reading the book's signals. A failed read offers Try again: > The signals could not be read. Where the table itself fails, it reads, with Try again: > The lines could not be read. Where the table holds nothing, it reads 0 findings, with one of these on hover and a door to widen it again (Clear the search, All categories, Every finding): > No open demand signals. > No signals match that search. > Nothing to work for {finding}. > No matching finding carries {quadrant}.