Skip to content
Ospivia StudioITEN
Back to the studioSynthetic data

PulseReport · Python · HTML

Create a weekly report from CSV exports

Turn two exports into a weekly report with metrics, comparisons and anomalies. Counts and amounts are reconciled before delivery.

WEEKLY COMPARISON · SYNTHETIC DATA

The numbers, with their sources.

2026-08-31 — 2026-09-06

€859.00gross sales in the sample
8accepted orders
€107.38average order value
Daily gross sales · EUR
€114.80
€59.70
€150.00
€120.00
€99.50
€240.00
€75.00

Accepted rows only: quantity × unit price in EUR. Discounts, refunds, taxes and costs are not modelled. The source export’s completeness is not established by this demonstration.

Inspect the evidence.

A comparison of consecutive weeks in EUR. The report identifies excluded data; scheduled runs and source connections need to be configured separately.

How to make two exports comparable

  1. Consistent scope

    Define the dates, currency and meaning of one row. This example compares adjacent seven-day weeks in EUR, with one product per order. Incomplete exports or different rules make a comparison less reliable.

  2. Agreed metrics

    The report shows gross sales, orders, units and average order value. Gross sales and average value use accepted orders only; taxes, margins and refunds need additional rules.

  3. Anomalies before totals

    Check duplicates, dates and amounts before aggregating. Excluded rows should remain visible with a reason, so a precise-looking metric does not hide missing data.

  4. Reproducible comparisons

    Compare periods of equal duration and reconcile daily and product totals. Where there is no valid baseline, mark the percentage change as unavailable instead of inventing one.

Inside the example report

The two exports contain 22 rows: 16 accepted, 1 duplicate and 5 quarantined. Gross sales from accepted rows move from EUR 569.10 to EUR 859.00, with 8 accepted orders in each week. The report exposes daily details and anomalies. These are synthetic data and partial KPIs: internal reconciliation does not prove the source export is complete.

When a dedicated workflow is useful

A spreadsheet may be enough for occasional exports and frequently changing rules. A dedicated report is useful when you rebuild the same calculations and checks repeatedly. The demo generates a document from files; scheduling, automatic export retrieval and delivery to recipients need to be defined and configured in the project.

What to include in your enquiry

Describe the export source, required frequency, metrics and recipients. Include a synthetic example and explain how cancellations, refunds and missing data should be handled.

Scope, price and acceptance terms

From the example to your workflow: scope and acceptance

Want something like this?

Describe your process