Synthetic worked example
A Sample Ecommerce Operator Brief
This example uses entirely invented data. It is not a client case, product output from a connected store, forecast, or evidence that RavenOS improves performance. Its purpose is to show what a useful operating question and a transparent readout can look like.
The question: sales grew, so why did contribution fall?
An imaginary store compares two complete 28-day periods. Its order count is unchanged, but promotion activity and paid-media spending changed. The founder is considering increasing acquisition spend. Before doing so, the team wants to understand the economics of the growth already reported.
For this example, net sales means sales after discounts and returns, excluding taxes and shipping collected. Product and variable fulfillment costs are assumed to be 45% of net sales in both periods. That simplification is an explicit assumption, not a general ecommerce benchmark.
| Metric | Period A | Period B |
|---|---|---|
| Orders | 1,000 | 1,000 |
| Sales before discounts and returns | $120,000 | $135,000 |
| Discounts and returns | $20,000 | $30,000 |
| Net sales | $100,000 | $105,000 |
| Assumed variable costs, 45% | $45,000 | $47,250 |
| Paid-media spend | $20,000 | $25,000 |
| Contribution after those costs | $35,000 | $32,750 |
What the numbers establish
Net sales rose 5%, from $100,000 to $105,000. The contribution defined in this table fell by $2,250, or approximately 6.4%. It is calculated as net sales less the assumed variable costs and paid-media spend. The arithmetic does not include fixed overhead, salaries or every possible operating cost. It is not full profit or cash flow.
The extra $5,000 of net sales produced $2,750 after the assumed 45% variable costs. Paid-media spending increased by $5,000. Under these assumptions, the additional contribution before media did not cover the additional media expense.
This aggregate comparison cannot tell us which campaign caused the change. It also does not tell us whether different products, new customers, repeat customers, refunds or a reporting difference explain it. The next investigation matters more than a confident story about one channel.
What we would check before changing the budget
First reconcile the periods: are returns recognized on the same basis, are orders complete, and did inventory or prices change? Then replace the flat cost assumption with the actual cost basis where available. A change in product mix can alter the conclusion.
Next examine the composition of the sales: orders and realized prices by product, promotion exposure, customer type and acquisition source. If customer quality is the concern, compare groups with enough follow-up time rather than treating a recent group as a mature one.
Do not add together platform-attributed revenue as if each platform had exclusive credit. Do not multiply every failed payment event by average order value and call it lost sales. Both shortcuts can overstate the apparent opportunity.
- Confirm the revenue and cost definitions.
- Reconcile product and promotion mix.
- Inspect new and returning customers separately.
- Record which questions remain unanswered.
A bounded next action
The initial recommendation in this synthetic situation is to complete the reconciliation before making a material budget increase. The acquisition owner prepares source-level spending, the commerce owner checks discounts and returns, and the finance owner supplies the appropriate cost inputs.
That is a proposal, not a claim that pausing or increasing spend is always correct. An urgent operational issue, a committed promotion, or strong contrary evidence could change the decision. A short review should name when it will conclude and which finding would change the action.
A subsequent test needs its own comparison and decision criterion. A later improvement in sales would not by itself prove that this diagnosis caused it.
How to use this example
Use the structure to ask better questions of the reports you already have. It does not estimate your store’s opportunity or promise recovered revenue. The working relationship, scope and implementation owners should be clear before any real analysis begins.
RavenOS is private software supporting Joshua’s operator-led work. If this is the kind of decision your business is facing, begin with the business question. Keep confidential data out of a general contact message.