Social commerce return on investment: designing the decision view

When does a reported sale support a decision?

Weak version: Treat the platform total as the result of the programme, then choose continuation or expansion from its dashboard. That view follows a declared attribution rule, but it cannot show what would have happened without the activity. The choice is being made before a comparison has been designed.

Better version: Name the decision first: continuation, expansion, supplier choice or creative allocation. Keep the attributed view, which follows the platform or analytics rule, distinct from the decision view, which asks what changed because of the activity. An attributed order is evidence of attribution, not proof of cause.

What would have happened without the activity?

Weak version: Set the comparison after results arrive, or treat a before-and-after change as proof that the programme caused it. Different stock, pricing, promotions, seasonality or other activity can make the groups unlike. These measurement mistakes are harder to correct once the decision view has been chosen.

Better version: Fix the counterfactual before seeing results. Choose a comparison design that is feasible at the programme's scale, and have an analytics or research specialist approve the method. Record the conditions that could make the compared groups differ, rather than relying on the result alone.

A comparison is only useful if its assumptions are visible. Keep the chosen design, its known limitations and the relevant operating conditions together in the decision record. If the design cannot support a confident causal estimate, report that limitation instead of presenting attributed sales as incremental sales.

How does the outcome become a return?

Weak version: Divide a platform revenue figure by programme spend and label the result ROI. That calculation can leave out cancellations, refunds, product and fulfilment costs, or internal work. When the numerator is revenue before product and fulfilment costs, the result is a return-on-spend ratio, not contribution-based ROI.

Better version: Calculate from settled outcomes and incremental contribution, using the finance-approved tax basis. In the table, incremental contribution is after programme costs have been deducted; dividing it by incremental programme cost expresses the net return relative to that cost and does not deduct the costs again. If working from contribution before programme costs instead, deduct incremental programme cost once, then divide the result by incremental programme cost. If cost is zero or unknown, do not publish a percentage; label a revenue-based ratio accurately.

Use the finance-approved tax basis. HMRC's VAT guide says VAT charged to a business on purchases is input tax; recoverability depends on the business and purchase circumstances, so a qualified tax reviewer should decide whether each input is gross or net of recoverable VAT. Supporting cost evidence sits in the cost guide.

Which orders belong in the decision window?

Weak version: Include every recent order immediately, even when its cancellation, return or settlement outcome is unresolved. A cohort with immature orders can make the decision view look stronger or weaker than its eventual contribution. Leaving the customer geography or checkout route unstated also makes the scope unclear.

Better version: Choose a cohort and maturity date suited to the products' actual cancellation, return and settlement cycle; label customer geography and checkout route. GOV.UK's returns and refunds guidance says that in some cases a refund must be offered if a customer changes their mind. Keep recent sales provisional until relevant states reconcile.

Record time for planning, creator briefing, approvals, live cover, catalogue repair, customer service, refund matching and analysis. Multiply hours by a finance-approved loaded rate. Count incremental supplier and control work too, including configuration, consent review, testing and rights handling when measurement introduces them.

What happens when the records disagree?

Weak version: Force platform, shop, payment and refund totals to match by spreading an unattributed balance across channels. A clean-looking total does not resolve duplicated, missing or conflicting records. A precise percentage built from weak attribution should not be allowed to outrank a cautious result grounded in evidence.

Better version: Deduplicate records using stable order identifiers where permitted. Reconcile platform, shop, payment and refund exports, and put unmatched, duplicated and conflicting rows in an exceptions table. Keep the exceptions visible; a result based on reconciled orders is more useful than an unexplained balancing adjustment.

How should uncertainty appear in the result?

Weak version: Present one precise percentage without showing how attribution, returns, product margin or staff time affect it.

A single figure can hide uncertain inputs, and averaging an early loss with a later gain can conceal the cash path. The result should not imply a probability that has not been established.

Better version: Mark inputs as observed, contracted, allocated or estimated, and give the result an evidence grade. Change one driver at a time, especially attribution, returns, product margin and staff time. Show low, central and high cases as decisions under stated assumptions, not probability claims unless a statistician has supplied that analysis.

Show payback as cumulative incremental cost divided by periodic incremental contribution. It is usable only when contribution is positive and reasonably stable; otherwise report that payback has not been demonstrated. Preserve the cash path rather than smoothing an early loss against a later gain. Attach source files, calculation version, reviewer, exclusions and unresolved exceptions, then recalculate when the cohort matures. The payback period is not a substitute for the contribution-based decision.