A number that looks simple almost never is.

Reports and systems lose trust when they disagree about the same number. Every new integration is one more chance for them to disagree. I enforced the rules and made them visible.

Average

Averaged across what?
Can two stores be added up?

order

Does an exchange make a second one?
Does a zero dollar order count?
Does a discounted order count?

value

Do returns come out of this?
Which register sent it?

The five data sets the company runs on.

Each one has its own vocabulary.

Hover any definition. Click to pin it open.

And each one arrives from more than one place.

I define the rules, enforce them in the data warehouse, then show them in the registry.

The Data Warehouse

orderitemrevenue_takenorders_paid10482Boot 10.5148.001

The Metrics Registry.

Anyone can open it and see how a number is made.

Number	Definition	Grain	What it excludes	Last promoted by
Average order value	Money taken per order, once returns are out	order	Returns, and orders taking no money	Priya
Returns arrive as their own zero-value line and are out of the numerator, not netted against it. An exchange keeps the original order. The denominator counts distinct orders with money taken above zero.
Gross	Everything rung up before returns	day, store	Nothing. Returns are still in it	Priya

Open a row. That is the definition every other tool is required to use.

This is an executable contract that every dashboard, query and system reads from. Anyone can audit it here. If it's in the data warehouse, it's here.

All shown