RavenOSDiscuss Fit

Operator worksheet

Build an ecommerce data inventory before analysis

A blank report inventory helps founders see what evidence exists, what its figures mean and which gaps could change the next decision.

Start with a decision and an evidence owner

Before adding platforms, name the question the inventory supports. For example, a founder investigating weaker repeat purchase needs a different evidence set from a team checking a checkout incident.

Assign an owner who can explain each report. Access to a dashboard does not establish that its figures are complete, current or comparable.

Copy this blank inventory

Create one row for each report or export you already have. A source can remain listed even when access is unavailable; mark the gap explicitly.

FieldWhat to record
Source and reportPlatform, exact report name and owner
CoveragePeriod, cutoff, timezone and currency
Metric basisOrder date or payment date, gross or net, attribution window
FreshnessLast refresh and expected lag
ScopeIncluded products, channels, statuses and exclusions
AccessAvailable, permission needed or unavailable
Known gapsMissing costs, history, refunds or unresolved definitions

Reconcile definitions before totals

Two reports can both be accurate and answer different questions. Gross sales and net sales differ. Orders placed and payments collected differ. A platform-attributed conversion is not automatically a distinct order or evidence of incremental revenue.

Write the definitions next to the figures you plan to use. If the basis cannot be reconciled, keep the views separate and explain the difference rather than forcing a single total.

A synthetic reporting gap

Imagine an invented store has a completed seven-day order report, but its advertising export stops two days earlier. That inventory does not support a seven-day comparison of spend and revenue. The next action is to obtain matching coverage or narrow both reports to the same completed window.

If refunds post later, record which date basis each report uses. A change in net revenue might reflect refunds on older orders rather than fewer new purchases. The inventory should make that question visible before anyone diagnoses a channel.

Turn gaps into a work list

For each missing input, name the owner, the requested period and what decision depends on it. Rank the gaps by whether resolving them could change the next action. Collecting every available field is not the objective.

This worksheet describes an operator-led review. It does not mean every listed platform has a live RavenOS integration. Begin a conversation with the decision and the sources available, then agree scope and safe handling before sharing records.