Marketplace Ops

Costs and pricing

Part of Building a marketplace software budget from verified prices and the cost of the current route

Assessing marketplace software return from an observed baseline and net contribution

Assess marketplace software return through observed baselines, causal evidence, net contribution, whole-life cost, uncertainty, risk and buyer scenarios.

Marketplace seller software return on investment cannot be calculated from gross marketplace revenue or a supplier dashboard. For one England seller, define the eligible product and order population, observe the current route, estimate causal incremental contribution and subtract reviewed whole-life economic cost.

No figures are supplied. Research closed on 6 September 2026. This is a blank method, not financial or tax advice and not a return promise.

Freeze the observed baseline

Choose a period, Europe/London timezone, authorised account and stable product population. Define each event and its source. Keep listing publication, stock update, order placement, seller acceptance, payment authorisation, capture, fulfilment, retention, cancellation, return, refund, dispute and settlement apart.

Record eligible events, missing or late data, duplicates, staff activity, reversals and corrections. Document staff work using actual time records and approved cost sources. A baseline with changed products, prices or fulfilment conditions may not be comparable.

Separate four kinds of evidence

Observed evidence is what the seller's reconciled systems recorded. Attribution assigns an event to a channel or tool under a stated rule. A buyer scenario combines explicit assumptions. Causal evidence estimates what changed because the intervention occurred.

The HM Treasury QPIE guidance is written for policy impact evaluation, not merchant software. Its relevant warning is that attribution requires an appropriate counterfactual and proportionate design. A qualified evaluator must set eligibility, allocation or comparison, exposure, outcome window, contamination, missingness, stopping rules and uncertainty.

Define benefit as contribution, not receipts

An additional order is not automatically a benefit. Start from cash settled for eligible retained orders, then deduct refunds, disputes, taxes on the reviewed basis, product cost, fulfilment, customer support and other variable costs. Keep this net contribution separate from accounting profit.

Possible avoided labour needs an observed task reduction and evidence that released capacity had another useful application. Prevented error or risk remains a scenario unless the event frequency, consequence, counterfactual and uncertainty are supported. Absence of a complaint or incident does not by itself show a saving.

Use blank equations:

Incremental contribution = [net contribution with intervention] minus [counterfactual net contribution]

Net return = [causal incremental contribution] + [supported avoided economic cost] minus [whole-life economic cost]

ROI ratio = [net return] divided by [whole-life economic cost]

Currency, VAT basis, population, period and uncertainty must accompany every input. Do not calculate when the denominator is zero, negative or unsupported.

Include the full cost and failed gates

Whole-life cost includes supplier charges, internal labour, implementation, product-data work, consumer and safety assurance, privacy and PECR review, security, accessibility, support, correction, incident recovery, migration and exit. The current process is an option, not a free benchmark.

HM Treasury's Green Book 2026 distinguishes appraisal from evaluation and considers business as usual, lifetime costs, risk and uncertainty. It is not a private investment rule. Here it provides a methodological check against counting sunk spending as a reason to continue.

Consumer, product-safety, tax, privacy, security, accessibility and exit failures are stop conditions. A positive model cannot buy its way past them.

Decide under uncertainty

Show buyer-owned low, central and high scenarios only after documenting each assumption. Vary one uncertain input at a time and state the value that would change the decision. Recheck when the service edition, meter, volume, product mix, marketplace interface, tax view or test validity changes.

The final record may support proceed, rework, hold or stop. If causal evidence is not proportionate, report cost and operational outcomes without an ROI claim.

More in Costs and pricing

Costs and pricing

Building a marketplace software budget from verified prices and the cost of the current route

Build an England marketplace software budget from verified price evidence, internal work, assurance, order-state costs, uncertainty and exit.

Costs and pricing

A blank marketplace software budget for one seller, with VAT review and exit built in

Use a blank marketplace software budget template for one England seller, with price evidence, VAT review, whole-life work, uncertainty, controls and exit.

Costs and pricing

Costing one England marketplace seller workflow, from price cards to exit

Cost one England marketplace seller workflow through verified price cards, internal labour, assurance, order exceptions, uncertainty and tested exit.

Costs and pricing

Seven marketplace software costs that usually go missing from the estimate

Find seven often-omitted marketplace software cost categories through a dated, non-ranked England method using authoritative boundaries and buyer evidence.