Marketz
← Marketz home

Product

Know which products
need your next review.

Portfolio Insights brings your tracked research set into one review. Inspect coverage and concentration, then use brand, seller and category views to find the products behind the signal.

Separate review readiness and evidence gaps from commercial signals.

Inspect concentration inside the tracked product cohort.

Follow an action priority back to products, sources and history.

Actual interface · example data · interface shown in English
01

Set the portfolio boundary first.

Use Watchlist filters and tags to define the product group, then open its analysis for a 7-, 30-, 90- or 180-day view. A supplier-review cohort, a brand investigation and a price-review list should not be blended simply because they share a workspace.

Read the included records and available observations alongside the headline result. Portfolio analysis concerns your tracked or selected cohort, not a census of the marketplace.

02

Read readiness and concentration together.

Portfolio Insights brings price, rank, stock and indicator-value trends together with price/stock/buyer-indicator coverage and fresh, stale or unknown counts. Inspect brand/category and top-product concentration, including the largest contributors, before interpreting a group total.

A brand or category can account for a large part of a small tracked set without dominating Amazon or eBay. Coverage and readiness labels organize investigation; they do not measure the probability of a successful purchase or launch.

03

Drill into brands, sellers and categories.

Use the group views to narrow the question. Brand details expose product/seller counts, price ranges, top-product concentration and captured trends or volatility. Seller details show the observed product/brand mix and available listing/feedback context; category details lead into the contributor products. Return to source dates and inspect partial or truncated results rather than treating the list as complete.

Keep data types distinct. Amazon product-level buyer indicators span the ASIN’s sellers; they are not one seller’s realized revenue. eBay listing counters have a different period and variation scope. Do not turn grouped indicators into audited market share.

04

Use the review queue to choose a concrete next step.

The five-item attention queue uses deterministic research heuristics, including available price, stock, rank and rating context. Inspect below-30-day-mean records, seven-day BSR movement or rating drops alongside data coverage. Observed Buy Box seller diversity is not a measured win rate. A product can deserve attention because its price changed, its captured evidence is stale or its comparison still needs checking.

Return to the relevant listing, history or candidate rather than accepting a queue item as a trading instruction. Export the supported Watchlist cohort or send an available scoped review when you need to share the investigation. An email digest is not a full reproduction of every portfolio chart.

ILLUSTRATIVE DECISION CASE

From a portfolio total to a supplier question.

Brand and seller views help identify the records that deserve individual investigation.

When reviewing a brand

If one brand dominates your selected cohort, open the contributing products. A single item may drive the total. Check when its price and buyer indicator were captured before using the cohort summary in a supplier conversation.

When investigating a seller

Review the brands and products associated with a seller, then inspect available offers and feedback. Check stock, delivery and condition on the individual listing. An Amazon product-level buyer indicator or an eBay lifetime listing counter cannot establish that seller’s monthly revenue.

Questions about this workflow

Is a concentration percentage the brand’s market share?

No. It describes the cohort and metric shown. Inspect the products and coverage behind it.

Does the action queue tell me what to buy?

No. It prioritizes investigation. Source checks, actual costs and your own operational requirements remain necessary.

Put your next product decision into context.

Explore the workspace or define a research scope around the product you make.