Performance review template for Ecommerce
Free download as CSV and Markdown. Nothing sits in front of the file: no form, no account, no email address.
The files
What it is
The performance review with the columns a store needs: every line reviewed by catalogue segment, results read on kept orders rather than orders, and causes that include the three things a platform's reporting cannot see — stock, margin and returns.
Everything else is the general review, unchanged. Planned from the plan, variance separated from cause, cause held to evidence, one decision with one owner and a date.
When to use it
Run it at the end of every season and every promotion, and weekly during a flight. A store's periods are short and lumpy, so a monthly rhythm reviews an average of two weeks that behaved completely differently.
Run it also once the returns from a period have landed, which is usually several weeks after the spend.
| Type | How to fill it | |
|---|---|---|
| Period | Text | The window being reviewed, with its dates and the promotion window it sits inside. A store's periods are lumpy, and a review that does not say whether a sale was in the window is not comparable to anything. |
| Line reviewed | Text | The catalogue segment being reviewed, matching the plan. A campaign's average across best sellers and the long tail describes neither, and the decision taken on it is wrong for both. |
| Planned spend | Integer | What the plan said this segment would spend, in minor units, taken from the plan rather than recalculated. Retail plans are revised often, so the figure has to come from the version that was approved. |
| Actual spend | Integer | The spend that actually happened, in the same units and the same currency. In a store the gap is frequently about pacing within the period rather than the total, which is why the flight plan is read beside this. |
| Planned result | Text | The primary metric and its target from the plan, with the segment's margin beside it. Two segments hitting the same cost per order have not produced the same contribution. |
| Actual result | Text | What it produced, on the same metric, read on kept orders where returns are material. The source is the store's own system, not the platform's reported revenue, and the two will not agree. |
| Variance | Text | The difference on spend and on result, stated plainly. Where the result is still provisional because returns have not landed, say so here rather than presenting it as final. |
| Cause | Text | Why, as far as the evidence supports, and in a store the three causes reporting cannot see come first: a stock event, a returns effect, a delivery cut-off. Any of them looks like fatigue and none of them is. |
| Evidence | Text | The export and the window the cause rests on, plus the stock and returns records where they are part of it. A cause naming a sell-out needs the date the stock ran out. |
| Decision | Text | Continue, change the weight, change the segment split, or investigate. A store has a fourth common decision — hold for the promotion — and it should be written as change with the window named. |
| Owner | Text | Who carries the decision, by name. Segment-split decisions usually belong with the trading manager rather than the media buyer, and assigning them in the room is what makes them happen. |
| Next review | Date (YYYY-MM-DD) | When this row is looked at again, which for anything read on orders means after the returns from this cohort have landed. That second date is the one that decides what the period actually produced. |
| Notes | Text | What the next reader needs: the line that sold out, the promotion that pulled demand forward, the delivery cut-off, the competitor sale that moved the auction for a fortnight. |
Review the segment, because the campaign is an average
A store's campaigns usually span more of the range than their names suggest, and the average across a campaign hides the only thing worth knowing.
The same prospecting campaign can carry a strong result on best sellers and a poor one on the long tail, and the blend will look acceptable. A decision taken on the blend — more budget, less budget, new creative — is then wrong for both halves at once.
So the unit of review is the catalogue segment, matching the unit in the plan. Where the account is not structured that way, the review is still written that way, from whatever breakdown the reporting can produce. The structural change usually follows the first review that shows the gap.
Read on kept orders where returns matter
An order that comes back cost money and produced nothing, and in several categories the proportion that comes back is large enough to change every conclusion.
Where that is true, the primary result column reads kept orders rather than orders, and the review has to wait for the returns to land. That means two reviews rather than one: a fast review during and just after the flight, on orders, to make operational decisions; and a slower one several weeks later, on kept orders, that decides what the period actually produced.
Keeping them separate is important. The fast review is for changing weight this week. The slow one is what informs the next plan, and it is the one that occasionally reverses the conclusion of the first.
Margin sits beside the result
Two segments hitting the same cost per order have not produced the same outcome.
So the review carries the margin for every segment being judged on a cost per order, taken from the plan. It is what turns a comparison between segments into a comparison of contribution, and it stops the review approving whichever part of the range is easiest to sell.
Where a segment's margin was blank in the plan, it is blank here too, and the decision for that row is usually investigate: find the margin before the next flight, because without it the segment cannot be judged at all.
Stock, returns and the causes reporting cannot see
Three causes are specific to this category and none of them is visible in a platform's report.
Stock. A line that lost its best-selling variant on day nine was interrupted, not outperformed. A campaign pointed at a collection where several items went out of stock has been quietly narrowed. Both look like performance decline.
Returns. A creative or an offer that raises expectations will lift orders and lift returns further, and the effect arrives weeks later against a cohort nobody is still watching.
Delivery cut-offs. Traffic sent after the last date an order can arrive in time converts worse for reasons that have nothing to do with the ad, and the drop is sharp enough to be mistaken for fatigue.
Record all three as events with dates in the notes, and name them in the cause column where they apply.
Promotions distort everything they touch
A period containing a promotion cannot be compared with one that does not, and the weeks either side of a promotion are not ordinary weeks either.
Demand is pulled forward into a sale and taken out of the weeks after it. Auction costs move. The mix of buyers changes. A review that compares a promotional fortnight with the fortnight before it is measuring the offer, not the work.
So the period column carries the promotion window, the notes record where the edges fell, and comparisons are made like for like: this promotion against the same promotion last year, full-price weeks against full-price weeks.
The decisions a store actually makes
Four decisions cover most rows, and naming them makes the review faster.
Change the weight — usually the response to a pacing variance where the cause is understood. Change the segment split — the response to a margin-adjusted comparison rather than a cost-per-order one. Change the creative — the response to a fatigue signal that survives the stock and delivery checks. And investigate — the response to any row where the cause is not known and the money involved justifies finding out.
Anything vaguer than those four is not a decision.
Keep the reviews, by segment and by season
The accumulated reviews answer questions no single one can.
What each segment has actually cost to sell, across seasons. Which promotions have ever paid for themselves once returns are counted. How much demand a peak pulls forward from the weeks after it. Which creative themes have worked on which parts of the range.
Those are the four questions every store's planning meeting tries to answer from memory. A shelf of consistent reviews answers them from evidence, and it is the only asset in this process that compounds.
Before you close the review
Seven checks. Every row is reviewed at segment level, matching the plan. Results are read on kept orders wherever returns are material, with a second review scheduled once they land. Margin is stated beside every cost-per-order comparison. Stock events, returns and delivery cut-offs are recorded as dated events. Promotional periods are compared like for like. Every decision is one of four, with an owner and a date. And the finished reviews are kept by segment and by season.
The general template, and other industries
Performance review template
A free performance review template as a CSV and a Markdown file: one row per line, with planned against actual, the cause, and a decision with an owner.
Performance review template for B2B SaaS
A free performance review template for B2B SaaS as a CSV and a Markdown file, reviewed by segment and stage, with the cycle lag written into the comparison.
Performance review template for Fintech
A free performance review template for fintech as a CSV and a Markdown file, read on funded accounts, with approval rate and review changes among the causes.
Performance review template for Healthcare
A free performance review template for healthcare as a CSV and a Markdown file, read on attended appointments, with capacity and handling among the causes.
Performance review template for Real estate
A free performance review template for real estate as a CSV and a Markdown file, read per listing and per stage, with the guide and the market as causes.
Templates that go with it
Budget allocator template
A free budget allocator template as a CSV and a Markdown file: one row per destination, with floors, ceilings, the basis for each share and a move rule.
Phase plan template
A free phase plan template as a CSV and a Markdown file: one row per area per phase, with limits, what still needs approval, and the evidence to advance.
Test plan template
A free test plan template as a CSV and a Markdown file: one row per test, with the hypothesis, the single variable, the read date and the decision rule.
Related reading
Questions
Put frontier AI to work on every ad account you run.
Tempio connects your ad accounts into one workspace and hands your own AI the numbers and the tools. Every change it writes is a draft until you approve it, or until a rule you wrote does.
Request early access- Read and draft by default. Approve is a separate permission you grant.