Skip to main content
CloudHub manages a multichannel catalogue that includes the merchant’s own direct webstore alongside Amazon, eBay, and other marketplaces. The five Website reports under Analyse are the direct-store counterpart to the marketplace-focused reports. They share a unified dashboard layout that surfaces the trading picture for the webstore in one screen. The five reports are:
  1. Website Customers, customer count, repeat rate, and segment view
  2. Website Products, the product-side trading view
  3. Website Sales, the revenue line for the webstore
  4. Website Reviews, the buyer feedback feed
  5. Website Refresh Statistics, the data freshness state for the website feed
All five render the same dashboard frame with five widgets, then drill into the report-specific detail underneath. The shared frame is intentional: it gives a webstore manager a consistent shape every time they open the surface, so the eye knows where to look.

​
The shared dashboard frame

Every Website report opens with the same five-panel layout at the top.
PanelWhat it shows
Sales Report (line and bar chart, Last 30 Days default)Total Sales (cyan line) and Average Order (purple bars) per day. The picker top-right swaps to Last 7 Days, Last 30 Days, or Last 90 Days.
Lifetime card gridLifetime Sales, Average Per Order, Lifetime Order Count, Units Ordered. The four headline cumulative numbers.
Average chartPer-channel running average overlay so you can see how the webstore is trending against the marketplace channels.
KPI strapTotal Revenue, No.of Units Ordered, Avg.Order Value for the visible window.
Fast Selling Lines, Top 10The current top 10 SKUs by units sold in the last 30 days.
Count of OrdersA small grid of order counts by account name across Yesterday, Last 3 Days, Last 7 Days, Last 14 Days, Last 30 Days.
Sales Revenue (pie)Channel-share donut showing how the revenue split between accounts (Amazon, eBay, the website, and so on).
The dashboard is the daily-trade view. Each report below fills in the specifics for the question that report answers.

​
Website Customers report

Path: Home, Analyse, Website Customers. The Customers report tracks the customer base of the direct webstore (not marketplace customers, since marketplaces typically own the customer relationship and pass anonymised buyer IDs). It surfaces:
  1. New customer count per day. Visible inside the Sales chart as the bar count, and aggregated in the Lifetime Order Count card.
  2. Repeat customer rate. Inferred from the order-count column (a customer with multiple orders in the window is a repeat customer).
  3. Top channels for customer acquisition. The Sales Revenue pie shows which entry points (the website itself versus marketplace-driven traffic that converts on the website) drove customer growth.
Use cases:
  1. Marketing ROI. Compare new customer count by week against marketing spend by week to see cost per customer acquired.
  2. Retention triage. A flat or declining repeat-customer rate is a retention conversation, not an acquisition one.
  3. Channel arbitrage. If the webstore acquires customers cheaper than marketplaces but converts to lower lifetime value, the strategy is to drive more marketplace customers to the website on second purchase.

​
Website Products report

Path: Home, Analyse, Website Products. The Products report focuses on the product mix that sells on the webstore specifically, distinct from the marketplace mix in the Fast Selling Products report. The Fast Selling Lines top-10 list at the bottom of the dashboard is the centrepiece. The columns are SKU, Item Name, Current Qty, and Sold Last 30 Days. Sort by Sold Last 30 Days to see the webstore-specific top sellers. Use cases:
  1. Webstore exclusives. A SKU that sells well on the website but is not in the marketplace top sellers may be a webstore exclusive worth promoting more aggressively.
  2. Inventory allocation. If a SKU sells double the volume on the website versus eBay, the buyer should allocate stock accordingly when supply is tight.
  3. SEO content roadmap. The top webstore sellers are the SEO content priority list. Each top SKU deserves a dedicated content treatment to compound search traffic.

​
Website Sales report

Path: Home, Analyse, Website Sales. The Sales report is the revenue-line view scoped to the webstore. The Lifetime Sales card on this report and the Total Revenue strap show the same figure because the scope is “the webstore alone”. Use cases:
  1. Channel mix tracking. Compare Lifetime Sales here against the same metric in the marketplace-channel cards in the Nerve Centre. The split tells you whether the brand is becoming more or less direct over time.
  2. Promotion impact. A spike on the Sales Report chart that lines up with a promotional date is the visual proof the promotion worked. A flat chart is the proof it did not.
  3. AOV trend. Avg.Order Value moving up over weeks is a sign of basket-building or premium-mix. Moving down can mean either price competition or a discount campaign that kicked in.

​
Website Reviews report

Path: Home, Analyse, Website Reviews. The Reviews report shows the volume and tone of buyer reviews left on the webstore in the date window. Volume is the core trading signal. Use cases:
  1. Quality-of-launch check. A new SKU should pull reviews in the first 30 days of being listed. A new SKU with zero reviews after 30 days has a discoverability problem, not a quality problem.
  2. Cohort comparison. Compare reviews-per-order rate across cohorts to see whether buyers from one campaign leave more reviews than buyers from another. Useful for marketing channel evaluation.
  3. Negative review triage. Filter to negative reviews and route them to Customer Services for response. The Customer Services console has the order context to address each one.

​
Website Refresh Statistics

Path: Home, Analyse, Website Refresh Statistics. This is the freshness-of-data view for the webstore feed. CloudHub runs scheduled refreshes that pull customer, product, sales, and review data from the connected store; this report shows when each refresh ran, whether it succeeded, and what the row counts looked like. Use cases:
  1. Trust the dashboard. A merchant looking at the dashboard is implicitly trusting that the data is current. If the last refresh ran 3 days ago and failed, the dashboard is stale and you need to fix the refresh before drawing conclusions.
  2. Rate-limit triage. Some platforms (Shopify, BigCommerce, Adobe Commerce) rate-limit API calls. If a refresh fails consistently with a rate-limit error, the Optimise Profiles settings need to widen the refresh interval.
  3. Feed-quality check. A successful refresh that returned zero rows usually means the upstream platform changed an API path or the auth token expired. Verify and re-authenticate.
NeedWhere to go
Live website KPINerve Centre, the website connector card (Shopify, BigCommerce, Adobe Commerce, Magento)
“Why did webstore conversion drop yesterday?”Vortex Mind, Checkout Failure or Daily Revenue Leakage
”Show me my last 5 negative website reviews”Ask Viq, plain-English query
”Open a fix for the failing checkout step”Actions Kanban

​
Common questions

Why do all five Website reports show the same dashboard frame? Intentional design. The shared frame is the trading view, and the report-specific scope drills below it. A merchant who learns the dashboard once knows it everywhere on the Website tab. The Sales Report chart is empty for the last 7 days. Why? Either there genuinely were no website sales (unlikely for an active store), or the Website Refresh Statistics report shows a failed refresh in the last 7 days and the data did not land. Check refresh status first. Can I switch the date window on the chart? Yes. The picker in the top-right of the Sales Report card swaps between Last 7 Days, Last 30 Days, and Last 90 Days. Does the Website Customers report include marketplace buyers? No. Marketplace buyer relationships are owned by the marketplace (Amazon, eBay), and the marketplace passes only an anonymised buyer ID to CloudHub. Website Customers is direct-store only.

​
Next steps