![](https://rewalto.com/brand/neo/assets/sample-hero-light.svg)![](https://rewalto.com/brand/neo/assets/sample-hero-dark.svg)

[All use cases](https://rewalto.com/use-cases)

REWALTO / FOR ANALYSTS

# Build the comparison before the conclusion.

Analysts use Rewalto to build the comparison before the conclusion: define comparable records, keep missing values visible and turn the evidence into a report another person can check. Every result carries its source and collection time, so the work can be repeated.

[Explore workflow examples](#examples)[Check available data](#available-data)

THE DECISION COMES FIRST

## Do these records support the comparison, or are differences in scope driving the result?

A useful analysis starts with the unit being compared. The same brand, product name or city can hide differences in pack size, seller, location and collection time. Write those choices down before looking for a pattern. Rewalto can help you inspect available data and organise supplied records, while the catalogue remains the source for current coverage and availability.

PLAN THE QUESTION

## Try a workflow that fits your day.

Choose an example and the fields you need. This planner outlines a request without running it or spending credits.

### Your workflow planner

Planning onlyNo credits used

Compare prices without mixing productsSeparate missing checks from unavailable stockPrepare a reviewable report

### Which records describe the same item closely enough to compare?

1. Define the product, variant and pack size that belong in the comparison.
2. Keep sources and pin codes separate until you have checked their context.
3. Review unmatched records before summarising a difference; exclude or label them rather than forcing a match.

#### Choose the fields your question needs

Product identifierVariantPack sizeSourcePin codePrice

Different prices do not establish why the difference exists or whether a customer completed a purchase.

REQUEST STRUCTURE / NO DATA LOADED

### Make the scope easy to review.

Comparison unit
:   Exact product, variant and pack size

Source scope
:   Named sources with comparable location context

Selected fields, not returned records

| Product identifier | Variant | Pack size | Source | Pin code | Price |
| --- | --- | --- | --- | --- | --- |
| No records loaded. Check catalogue coverage before requesting data. | | | | | |

Review the planning brief

```
{
  "audience": "For Analysts",
  "question": "Which records describe the same item closely enough to compare?",
  "scope": [
    {
      "label": "Comparison unit",
      "value": "Exact product, variant and pack size"
    },
    {
      "label": "Source scope",
      "value": "Named sources with comparable location context"
    }
  ],
  "requestedFields": [
    "Product identifier",
    "Variant",
    "Pack size",
    "Source",
    "Pin code",
    "Price"
  ]
}
```

Copy planning brief[Check matching data](#available-data)

Changing this layout does not run research, collect data or create a watch.

FROM SCOPE TO DECISION

## Make the work repeatable.

A useful result starts with a consistent scope and ends with a conclusion the data can support.

01

### Write the comparison rules

Specify the question, unit, sources, geography and period. Decide how unmatched products and unknown values will appear before producing a summary.

02

### Check the evidence window

Inspect catalogue coverage and freshness. Keep collection dates and source context in your working table so a later reader can distinguish an old value from a current check.

03

### Share the limits with the result

Explain exclusions beside the relevant conclusion. Use the report studio for supplied-data presentation. A report can also repeat every month, and Watches, which alert you when something changes, are live.

CHECK BEFORE YOU START

## Current data, current limits.

Availability, coverage and rates come from the catalogue. A planning example does not establish that the requested records are held.

### Checking the published catalogue…

Coverage and prices are not substituted with example values. Review the catalogue before making a data request.

Check again[Explore this data family](https://rewalto.com/data/commerce)

FOLLOW THE QUESTION

## Useful next steps.

[### Product matching guide

Check comparability before treating a price difference as meaningful.

Explore](https://rewalto.com/guides/same-product-different-price-across-apps) [### Understand missing data

Keep an unchecked source separate from an empty result.

Explore](https://rewalto.com/guides/not-checked-is-not-empty) [### Report layouts

Inspect data-first layouts for supplied evidence.

Explore](https://rewalto.com/reports)

BEFORE YOU GET STARTED

## Questions worth asking.

Why keep missing values visible?

So a gap is not read as zero. Keep missing values distinct from zero, unavailable stock and a confirmed empty result, and state what was checked and what remains unknown.

Can another person check the report?

Yes. Each result carries its source and collection time, so a reader can see the data behind a conclusion and repeat the work.

Where do I start?

Define the comparable record first: the product, pack, source, location and period that make two values comparable.

Can I combine prices collected at different times?

You can examine them together if the dates stay visible and the comparison explains that timing differs. Do not describe them as a simultaneous price comparison.

Will the report studio perform my analysis?

The studio organises supported supplied content. Findings, charts and recommendations need to be supplied in its supported report document and checked by the author before sharing.

![](https://rewalto.com/brand/neo/assets/sample-basin-light.svg)![](https://rewalto.com/brand/neo/assets/sample-basin-dark.svg)

FROM A QUESTION TO USEFUL DATA

## Start with the question you need to answer.

[Browse datasets](https://rewalto.com/data)[Explore report layouts](https://rewalto.com/reports)

---

Canonical page: https://rewalto.com/use-cases/analysts
Last content change: 2026-10-28