Skip to main content
The three inventory-side reports in 247CloudHub Analyse answer the buyer’s three questions: what is sitting and tying up cash, what is moving fast and may stock out, and what is the current state of every SKU in the catalogue right now. Each is filtered by date range and exportable to CSV. Together they replace the three-tab spreadsheet most multichannel buyers used to live in.

​
Inventory Age report

Path: Home, Analyse, Inventory Age Status Summary. This report lists every SKU in the catalogue with the dates that matter for ageing analysis: when it was first added, when stock was last updated, and how many units have sold in the window.
ColumnWhat it means
SKUInternal SKU.
Product TitleProduct name. Empty rows are typically variant placeholders that share a parent description.
Date AddedWhen the SKU was first created in CloudHub, dd MMM yy hh:mm:ss tt. The age clock starts here.
Last Stock UpdatedThe most recent stock-quantity update for this SKU, from any source (PO receipt, marketplace sync, manual edit).
No.of Products SoldSales count inside the chosen date window.
The pattern most buyers use: filter to the last 90 days, sort by No.of Products Sold ascending, and look at the rows with old Date Added values and zero sold. That is the dead-stock list. Exported to CSV, it becomes the working file for a markdown campaign or a clearance run on a discount channel. Use cases:
  1. Quarterly clearance review. Pull the report for the trailing 90 days, identify SKUs older than 12 months with zero or low sales, route them to a markdown profile in Repricing [Compete] or list them on a clearance channel.
  2. Insurance and write-off audit. Report the value of stock older than 24 months for the year-end stock provision your finance team needs.
  3. Reorder triage. Sort by Last Stock Updated ascending to find SKUs that have not been replenished in months. Match against the Fast Selling Products report to see which of those are currently selling well, which is the urgent reorder list.
Common gotcha: rows without a Date Added (sometimes seen for very old SKUs) are typically catalogue items that predate a CloudHub data migration. They are still tracked operationally but their age clock starts at the migration date, not the original create date. Treat them as the oldest cohort for clearance purposes.

​
Fast Selling Products report

Path: Home, Analyse, Fast Selling Products Summary. This report shows the same catalogue grid but with the unit count by channel for the date window.
ColumnWhat it means
SKUInternal SKU.
Product TitleProduct name.
AmazonUnits sold via Amazon in the window.
eBayUnits sold via eBay.
PlayUnits sold via the Play marketplace.
WebsiteUnits sold via the direct webstore.
FNAC, Priceminister, Rakuten, Trademe, Cdiscount, GameUnits sold per regional or category-specific marketplace.
Each channel column is independently sortable. Click the column header to sort descending and see “the top sellers on Amazon UK in this window”, “the top movers on eBay in this window”, and so on without leaving the report. Use cases:
  1. Channel mix. A SKU selling 200 units on Amazon and 5 on eBay is an Amazon SKU. A SKU evenly split is a true multichannel SKU. The mix tells you where to spend marketing.
  2. Repricing prioritisation. Flag the top 50 SKUs by Amazon volume and prioritise them in the Buy Box repricing rules. This is exactly what the Repricing [Compete] module reads against.
  3. Hero card priority. Inventory cards in the Nerve Centre rank by recent velocity. Fast Selling Products is the report that supports that ranking.
Common gotcha: a SKU showing zero across every channel does not necessarily mean the listing is broken. It can mean the listing is correctly published but no buyer has bought it in the window. Use the Order Stages report to confirm that orders are flowing in general before spending engineering time on a “broken listing” assumption.

​
Products report

Path: Home, Analyse, Products. The Products report is the snapshot of right-now state for every SKU.
ColumnWhat it means
SKUInternal SKU.
Product NameProduct name.
Current QuantityUnits physically available right now (after pending-order allocation).
Pending OrdersNumber of orders that are placed but not yet dispatched.
Awaiting POUnits on open purchase orders not yet received.
Use cases:
  1. Stockout watch. Filter to SKUs where Current Quantity is below a threshold and Pending Orders is above zero. That is the ship-from-thin-air list, in priority order.
  2. Replenishment urgency. Sort by Awaiting PO descending to see which SKUs already have replenishment in flight. Those are not the ones to chase.
  3. Catalogue cleanup. Filter to Current Quantity of zero and zero pending orders for the last 90 days. That is the candidate set to deactivate or merge.
Common gotcha: Current Quantity reflects CloudHub’s internal stock count, which is the source of truth for the multichannel sync. If a marketplace shows different available stock to what this report says, the channel sync is the issue, not the Products report. See Optimise Profiles for the configuration that drives those sync rules.

​
How the three reports work together

The buyer’s weekly trade review uses all three:
  1. Open Fast Selling Products, last 7 days. Identify the top movers across channels.
  2. Cross-reference with Products report. Check current quantity for each top mover. Anything below 14 days of cover is the urgent reorder list.
  3. Cross-reference with Inventory Age report. For top movers older than 6 months that are running low, decide whether to reorder or to mark down and clear.
Run weekly, this is the discipline that keeps the catalogue tight and the cash freed up.
NeedWhere to go
Live inventory KPI per connectorNerve Centre, the connector card
”Why is SKU DK001B selling slower than last month?”Vortex Mind, Daily Revenue Leakage with the SKU as a filter
”What is my inventory age across all channels right now?”Ask Viq, plain-English query
”Open a markdown action for SKU DK006”Actions Kanban, route from a Vortex Mind finding

​
Common questions

Why is the Inventory Age report missing a SKU I just added? Newly created SKUs appear once their first stock update lands, which is typically at the next inventory sync. Allow up to one sync cycle. If it still does not appear, check the SKU is Active (not blocked) under Vendor Central Inventory or the Common Inventory. The Fast Selling Products report shows 0 across all channels for a hot SKU. Why? Either the SKU did not actually sell in the window (check a wider date range), or the marketplace channel is mapped to a different Order Source label and the column is reading the wrong feed. Confirm by exporting a Sales report and pivoting on Order Source for that SKU. Can I export all three reports together? Each report exports independently. For a combined view, export each CSV and pivot in Excel, or use Ask Viq for a conversational join across the three. Does Pending Orders include orders that are on hold? Yes. Any order that is not yet dispatched counts as pending, including orders parked in Order on Hold stage in Customer Services.

​
Next steps