Skip to content

Main content

SKU Unit Pack Revenue Crosswalk

Extend pack sales into unit quantity and revenue under an explicit per-unit price, excluding discounts, returns and taxes.

Loading tool…

Description

Extend supplied pack sales to units and unit-price revenue.

Business metrics depend on event definitions, time windows, revenue and cost bases, and reporting scope. Observed sales during stockout do not by themselves verify latent demand, while a return contribution depends on which costs were already recognized. Local flags and signed balances are not a complete profitability or causal analysis.

Extend supplied pack sales to units and unit-price revenue.

When to use this tool

Use SKU Unit Pack Revenue Crosswalk when you already have packsSold, unitsPerPack, pricePerUnit and need to extend supplied pack sales to units and unit-price revenue.

How to use the tool and how it works

  1. Enter packsSold, unitsPerPack, pricePerUnit. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read unitsSold, revenue. Use the output convention below.

Require packs nonnegative safe, units/pack positive safe and price/unit>=0; units=packs*unitsPerPack, revenue=units*price.1

Input fieldMeaning and unitsAccepted input
packsSoldPacks SoldRequired. Safe integer; minimum 0.
unitsPerPackUnits Per PackRequired. Safe integer; minimum 1.
pricePerUnitPrice Per UnitRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
unitsSoldpacksSold*unitsPerPack; unsafe integer outputs are rejected.Required. Safe integer.
revenueRevenueRequired. Finite number.
json
{
  "input": {
    "packsSold": 12,
    "unitsPerPack": 6,
    "pricePerUnit": 2.5
  },
  "output": {
    "unitsSold": 72,
    "revenue": 180
  }
}

Limitations and assumptions

  • Unsafe unit counts are rejected. Pack definitions, currency, actual sales, returns, tax and realized revenue are not verified.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Reconcile source transactions, inventory and cohort records with the full metric definitions. Use complete forecasts, accounting and study designs where needed; individual contributions and supplied scenarios do not establish performance or causal effects.

References

  1. Calculation and input contract: business-analytics/sku-unit-pack-revenue-crosswalk — tool.io

Similar or alternative tools