⏱️ Time Range Comparison (Vendor)

Dashboard link: https://app.emax-digital.com/vendor-daily-time-range-comparison

Overview

The Time Range Comparison dashboard lets you place two arbitrary date ranges side by side and compare daily Vendor Central performance across them — without being locked into the standard "this month vs. last month" or "this year vs. last year" comparisons available elsewhere. Pick any current date range and any comparison date range, and the dashboard aligns the two periods day-by-day (day 1 vs. day 1, day 2 vs. day 2, etc.) so you can read like-for-like patterns even when the windows have different lengths or sit in unrelated parts of the calendar.

It is built for vendor managers who need to answer questions such as: How did this year's Prime Day week compare to last year's? How did the two weeks after a price change compare to the two weeks before? How is the launch month of a new product tracking against the launch month of its predecessor?

The page is organised in three blocks — Retail performance (Ordered Revenue, Glance Views, Conversion Rate), Advertising performance (Ad Spend, Ad Sales, ROAS), and an ASIN-level comparison table — with scorecards on top of each block and day-aligned daily trend charts below.

What You Can See on This Dashboard

Section 1 — Header Scorecards

A row of context scorecards at the top of the dashboard echoes the active filters back to you so the rest of the page can be read in context: the selected Marketplace, the current Timerange, the comparison Timerange (Timerange Compare), the selected Categories, and the active Tags.

These are reference values — they tell you what scope every other number on the page is computed against.

Section 2 — Retail Scorecards: Ordered Revenue, Glance Views, Conversion Rate

Three two-row scorecards giving the headline retail comparison.

Key metrics (each shown for current period and for comparison period):

• Ordered Revenue — total customer-order value (Manufacturing view of the daily Vendor Sales Report) across all in-scope ASINs, in the selected currency.

• Glance Views — total product detail page views across all in-scope ASINs (daily Vendor Traffic Report).

• Conversion Rate — Ordered Units ÷ Glance Views, computed across the full period.

Visualizations: Each scorecard shows the current-period total on the top row and the comparison-period total on the bottom row, so the relative difference is immediately visible.

Section 3 — Retail Daily Trends

Three day-by-day line charts, each plotting the current period and the comparison period as two series on the same axis.

• Ordered Revenue Daily Trend — current vs. comparison, aligned by day number.

• Glance Views Daily Trend — current vs. comparison, aligned by day number.

• Conversion Rate Daily Trend — current vs. comparison, aligned by day number.

How the day alignment works: Day 1 of the current range is plotted against day 1 of the comparison range regardless of the calendar dates — so a 14-day window starting on a Monday can be compared cleanly against another 14-day window starting on a Friday. If the ranges have different lengths, the longer range continues alone past the end of the shorter one (the unmatched days show only one series).

Section 4 — Advertising Scorecards: Ad Spend, Ad Sales, ROAS

Three two-row scorecards mirroring the retail block, this time for advertising performance.

Key metrics (each shown for current period and for comparison period):

• Ad Spend — total advertising spend across the selected ad types (Sponsored Products, Sponsored Brands, DSP — depending on the Ad Type filter), in the selected currency.

• Ad Sales — ad-attributed sales using a 14-day attribution window.

• ROAS (Return on Ad Spend) — Ad Sales ÷ Ad Spend. Higher is more efficient. Shown as blank if Ad Spend is zero in a period.

Section 5 — Advertising Daily Trends

Three day-aligned daily line charts for the advertising block, following the same day-1-vs-day-1 logic as the retail trends:

• Daily Ad Spend — current vs. comparison.

• Daily Ad-Attributed Sales — current vs. comparison (14-day attribution).

• Daily ROAS — current vs. comparison (null where ad spend is zero).

Section 6 — ASIN-Level Comparison Table

A full per-product breakdown that ties retail and advertising together in one table. One row per ASIN, with every key metric reported for both periods plus the absolute and percentage change.

Columns shown for each metric (Sales, Glance Views, CVR, Ad Spend, Ad Sales, ROAS):

• Current period value

• 🆚 Comparison period value

• △ Absolute change (current minus comparison)

• △% Percentage change

Plus identifying columns: product link, ASIN, Title, Product Title.

Notes:

• Sales = Ordered Revenue from the Manufacturing view of the daily Vendor Sales Report.

• CVR (Conversion Rate) = Ordered Units ÷ Glance Views — blank if Glance Views are zero.

• ROAS = Ad Sales ÷ Ad Spend — blank if Ad Spend is zero.

• Ad Sales use a 14-day attribution window.

Use this table when the headline scorecards show a movement and you need to know which products drove it.

Available Filters

Filter interaction notes

• Marketplace is required and is single-select — you compare two date ranges within one marketplace at a time. To compare marketplaces, run the dashboard once per marketplace.

• Subcategory depends on Category. Selecting categories narrows the subcategory dropdown to only the values that belong to those categories.

• Ad Type only affects the advertising block (Section 4, Section 5, and the advertising columns of the ASIN table). The retail scorecards and retail daily trends are unaffected.

• Currency conversion uses the annual exchange rate for the year in which the selected date range begins. If your current and comparison ranges sit in different years, the two periods may be converted at different annual rates — see Limitations below.

• Tag and Auto Tag are independent filters that can be combined. Tag is your manually maintained labels; Auto Tag is system-generated.

Use Cases

1 — Year-over-year event comparison (e.g. Prime Day, Black Friday)

You want to know how this year's Prime Day week performed vs. last year's — but the two events fall on different calendar dates.

• Set Marketplace to the marketplace of interest.

• Set the current Timerange to this year's Prime Day window (e.g. the 7 days of the event).

• Set the comparison Timerange to last year's Prime Day window (the equivalent 7-day event period).

• Read the retail scorecards (Ordered Revenue, Glance Views, Conversion Rate) and the advertising scorecards (Ad Spend, Ad Sales, ROAS).

• Use the daily trend charts to see whether the lift came on day 1, day 2, or held throughout — and use the ASIN-Level Comparison Table sorted by △ Sales to identify the deal ASINs that drove the year-on-year change.

2 — Before / after a price or content change

You changed a price (or refreshed A+ content, or updated main images) two weeks ago and want to measure the impact.

• Set the current Timerange to the 14 days after the change.

• Set the comparison Timerange to the 14 days before the change.

• Focus on Conversion Rate (did shoppers convert better at the new price / with the new content?) and Glance Views (did the change affect traffic, e.g. through algorithmic ranking?).

• Drop into the ASIN table to confirm the effect on the specific ASINs you changed, rather than the portfolio overall.

3 — New-product launch vs. predecessor launch

You launched a new ASIN last month and want to benchmark it against the predecessor product's first month on the market.

• Filter Product to the new ASIN and set the current Timerange to its first 30 days of sales.

• Switch the Product filter to the predecessor ASIN and set the comparison Timerange to its first 30 days.

Note: the Product filter applies to both periods. To compare two different ASINs' launches, you may need to widen the filter to include both ASINs and then read the per-ASIN comparison in the table — see Limitations below.

4 — Campaign-flight comparison

You want to compare two advertising flights of different lengths — e.g. a 10-day burst campaign vs. a 21-day always-on period preceding it.

• Set the current Timerange to the 10-day flight, the comparison Timerange to the 21-day baseline.

• Set Ad Type to the relevant ad format(s).

• Read the Ad Spend / Ad Sales / ROAS scorecards and the Daily ROAS chart — the day-by-day alignment will show how performance ramped over each flight, independent of their total lengths.

5 — Category-level seasonality check

You want to know whether a category is over- or under-performing its same-period last year.

• Filter Category to the category of interest.

• Set current and comparison Timeranges to the same calendar weeks one year apart.

• Read the retail block to gauge organic demand, the advertising block to gauge media support, and the ASIN table to see which products inside the category are pulling the average up or down.

Limitations & Notes

• Day-by-day alignment, not calendar alignment. The daily trend charts and the ASIN-level table compare day 1 to day 1, day 2 to day 2, regardless of weekday or date. This is intentional — it allows ranges of different lengths or different calendar positions to be compared — but it means day-of-week effects are not aligned. Comparing a Mon-start range to a Fri-start range will mix weekday and weekend traffic patterns. Where possible, choose comparison ranges that start on the same weekday.

• Unequal-length ranges. If the current and comparison ranges have different lengths, the daily trend charts will plot a single series for the days that exist in only one of the two ranges (the other series is blank). The headline scorecards still sum the full range on each side — so a 10-day current period compared to a 20-day comparison period will naturally show a lower total on the current side, even if daily performance is better.

• Vendor Central only. This dashboard covers vendor (1P) data. Seller Central (3P) sales and advertising are not included.

• Manufacturing view only. Retail metrics (Ordered Revenue, Ordered Units) come from the Manufacturing distributor view of the daily Vendor Sales Report. There is no Sourcing view toggle on this dashboard.

• 14-day ad attribution window. Ad Sales and ROAS reflect purchases made within 14 days of an ad interaction. Very recent comparison windows (e.g. ending in the last few days) may show under-reported Ad Sales until the attribution window completes.

• Currency conversion uses a single annual rate per period. Each period is converted using the exchange rate for the year in which its start date falls. When current and comparison ranges sit in different calendar years, the two periods may use different annual rates — interpret cross-year monetary comparisons with this in mind. In-marketplace native-currency views are not affected.

• ROAS and Conversion Rate are blanked when the denominator is zero. A blank ROAS does not mean zero efficiency — it means there was no ad spend in the period. Likewise blank CVR means no glance views.

• **Filters apply to both periods identically.** Marketplace, Category, Subcategory, Product, Tag, Auto Tag and Ad Type all scope the current and comparison periods to the same ASIN set. There is no way to compare different product scopes between the two ranges in a single run — to do that, run the dashboard twice and compare results.

• Marketplace is single-select. The dashboard does not aggregate across marketplaces; run it once per marketplace.

Data Refresh

Data updates daily.