Marketz
← Marketz home
All guides

Research workflow

A useful research brief
ends with a specific next decision.

Collecting more rows is not the same as resolving a business question. A useful brief connects the product you are investigating, the evidence available and the decision that still needs to be made.

REPORTING WORKFLOW · EXPLANATORY DIAGRAM

A review with a defined scope.

  1. 01
    Choose the records

    Market, products, tags and reporting period

  2. 02
    Review the evidence

    Recorded changes, source links and capture dates

  3. 03
    Share or export

    Supported summaries, CSV and Excel

Email

English or Turkish email preference; daily, weekly and monthly options follow the configured scope.

WhatsApp optional channel

Requires a ready connection and an agreed recipient. Content and language support differ from email.

This diagram explains the reporting workflow, not an actual report or a delivery confirmation. Channel setup is a prerequisite, not a claim that a production account is connected.

Write the decision before collecting the evidence.

A reseller might ask whether a particular pack deserves a sourcing follow-up. A manufacturer might ask which competing offer formats to investigate before planning a launch. A team monitoring an existing range might ask which recorded changes need attention today.

Define the product, marketplace and relevant pack or variant. Name the time window and explain whether the scope is a selected portfolio, a filtered set or a single product. That boundary makes the findings easier to interpret and prevents a small research pool from sounding like the entire market.

Keep evidence and assumptions in separate columns.

Include source links, capture dates, listing identity, package context and the available price history. Label buyer indicators and cumulative listing counters according to what they measure. Missing information should remain a question, not quietly become zero or certainty.

Your planned sale price, fulfillment choice, fee budget and inventory quantity belong in an assumptions section. A cost model can support a conditional assessment; it does not turn those assumptions into observed business results. Record the unresolved checks beside the conclusion.

Choose the report that fits the review rhythm.

Marketz’s daily email brief can contain up to five eligible recorded price drops and up to five unverified arbitrage candidates. Use it to choose which records to open, not as a purchase instruction or proof that a candidate remains available.

Weekly and monthly reviews use rolling seven-day and thirty-day periods. A single-product brief focuses on the active product, recent change labels and thirty-day context where available. These formats organize different review tasks; they are not interchangeable statements of transactions or realized profit.

Give the reader a route back to the product.

A report should lead to the underlying evidence and a named follow-up: inspect the original offer, confirm the selling unit, update a cost input or commission a more specific investigation. A summary is useful because it focuses attention, not because it replaces those checks.

Email reporting supports English and Turkish. WhatsApp depends on connection readiness and should be assessed separately; email language support does not establish bilingual WhatsApp delivery. Delivery acceptance also does not prove that a person has read the report. Keep delivery status, research evidence and the eventual commercial decision distinct.

Product scope checked against the Marketz implementation and Hubz catalog on 1 November 2026.

Put your next product decision into context.

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