Keep each client scope clear
Agree the question, sources and intended audience before reading data. Do not treat a shared account or a report file as permission to combine private client material.
REWALTO / FOR AGENCIES
Agencies buy the same products as everyone else (Data, Reports, Watches and the API) and use them for their clients. Scope the client question, compare the commerce records Rewalto covers, and write a report that separates the data from your own interpretation. Check coverage and dates before you promise a client a view.
THE DECISION COMES FIRST
A client needs to know what changed, why it matters and where the evidence stops. Start with a defined question rather than a large recurring deck. Keep the client scope, source coverage and permitted use clear from the beginning. Rewalto can support the data side of your analysis without implying a private client integration or a resale licence.
PLAN THE QUESTION
Choose an example and the fields you need. This planner outlines a request without running it or spending credits.
The table describes covered listings, not sales share, campaign effectiveness or every product in the market.
REQUEST STRUCTURE / NO DATA LOADED
| Brand | Product | Pack size | Retailer | Pin code | Listed price |
|---|---|---|---|---|---|
| No records loaded. Check catalogue coverage before requesting data. | |||||
{
"audience": "For Agencies",
"question": "Which covered products belong in the client comparison?",
"scope": [
{
"label": "Client brief",
"value": "One defined category decision"
},
{
"label": "Comparison rules",
"value": "Comparable products and pack sizes"
},
{
"label": "Coverage",
"value": "Named retailers and relevant locations"
}
],
"requestedFields": [
"Brand",
"Product",
"Pack size",
"Retailer",
"Pin code",
"Listed price"
]
}Changing this layout does not run research, collect data or create a watch.
FROM SCOPE TO DECISION
A useful result starts with a consistent scope and ends with a conclusion the data can support.
Agree the question, sources and intended audience before reading data. Do not treat a shared account or a report file as permission to combine private client material.
The catalogue shows current status, coverage and rate. Check the applicable terms before sharing records with a client. Preview entries remain Coming soon; planning an example makes no paid request.
Use the report studio for supplied records, tables and written conclusions. HTML downloads and browser Print to PDF are available. A report can also repeat every month, and watches, which alert you when something changes, are live.
CHECK BEFORE YOU START
Availability, coverage and rates come from the catalogue. A planning example does not establish that the requested records are held.
Coverage and prices are not substituted with example values. Review the catalogue before making a data request.
FOLLOW THE QUESTION
BEFORE YOU GET STARTED
The same products as everyone else: Data, Reports, Watches and the API. Agencies use them to scope client analysis and compare covered commerce records.
Use the data catalogue and the coverage and freshness guide before promising a client a view.
Do not assume so. Check the applicable dataset licence and permitted sharing terms before onward distribution. A downloaded file does not create a resale right.
No. These workflows support evidence-based analysis and supplied-data reports. They do not offer a white-label platform or promise custom branded automated delivery.
No. Public listing changes need careful interpretation. A causal claim requires a suitable evaluation design and evidence beyond the comparison table.
FROM A QUESTION TO USEFUL DATA