Comparing marketplace software pricing on the payable event and what sits outside the meter

Marketplace seller software pricing models can be compared only after the meter and included work are fixed. This comparison uses one fictional England seller, one authorised marketplace account and the same product, stock and later order-state exchange.

It names real suppliers and public list prices. Research closed on 6 September 2026.

What to take away

Compare pricing structures, not product labels

Do not compare a software fee with a managed-service total. One may exclude implementation and operating labour that the other includes. Where a supplier combines meters, model each component and its interaction.

The current manual route uses the same task, role, observed time and period as the software job; measure its total cash and economic cost as the buy-side benchmark, not as a software fee.

Put named routes on the same meter

Public price pages and typical enterprise quotes give the first normalisation. Use the same period, currency and tax basis. A list price is not a final quotation.

The named rows do not rank value. They show where the payable event sits and what the meter excludes. Apply the same buyer volumes to each row before any comparison.

Define the payable event

Order placed, seller acceptance, payment authorisation, capture and fulfilment are separate events. Settlement, cancellation, return, refund and dispute are also separate events. The contract must say which one is billable, when it is counted, how duplicates are removed and whether reversals receive a credit. Supplier terminology needs a mapping to the seller's evidence.

GOV.UK's online-selling page provides the consumer-journey context for ordering, correction and confirmation. It does not define a software charging unit. Commercial counsel must inspect the actual terms.

Normalise each price card to common factors

For every model, enter legal supplier, exact edition, UK eligibility and currency. Add VAT status, unit, billing period, minimum term and committed volume. Add overage, promotion, pass-through amount and refund treatment. Add source date and exclusions. Mark the row unknown if any factor prevents a common calculation.

HMRC's VAT-record guidance identifies records for supplies and adjustments. An accountant must decide the particular VAT and accounting treatment; the supplier's display is not the merchant's conclusion.

Add costs that sit outside the meter

Include product-data preparation, interface work, migration, assurance and staff access. Add reconciliation, support, failed-event handling, correction and security. Add accessibility and exit. OPSS product-safety guidance shows why product role and traceability work can be separate from software functionality. NCSC supplier-assurance guidance prompts investigation of continuity and secure exit.

Test volume and reversal exposure

Build a buyer-owned volume sheet for products, active users and each billable event. Record the observed source period and exclude staff tests and duplicates. Apply the contract's treatment of rejected updates, cancelled orders, refunds and disputes.

Worked example. A fictional England seller, Ridgeway Tools Ltd, sells 1,200 orders a month at an average order value of £40, giving £48,000 monthly gross merchandise value.

On Amazon Professional, using the top of the published typical referral range at 15%, the month costs £25 subscription plus £7,200 referral, total £7,225 ex VAT.

On eBay Business Seller, using the top of the published typical final value range at 12% plus £0.30 an order, the month costs £7.99 Shop subscription plus £5,760 final value fees plus £360 per-order charges, total £6,127.99 ex VAT.

Run the same low, central and high buyer scenarios for every structure. State which input changed and keep the resulting amount labelled as a scenario, not a quotation.

Use a blank common-period formula:

Comparable cost = fixed charges + metered charges + implementation + internal operation + assurance + exceptions + exit

Run sensitivity only after the buyer has evidenced each input. Consumer, safety, tax and privacy gates remain outside the cost ranking. Security, accessibility and exit gates also remain outside it. If routes cannot be normalised to the same job and period, report them as incomparable.

Break-even illustration

At the same £48,000 monthly gross merchandise value and the top of both published ranges, eBay's total equals Amazon's when average order value is about £9.88. Below that, eBay's £0.30 per-order charge makes it the more expensive route. Above it, eBay's lower percentage rate keeps it cheaper.

If Amazon's category rate sits at 7% instead, Amazon totals £3,385 and eBay totals £6,127.99 at the same 1,200 orders. The percentage range moves the total more than the subscription does.

This is a scenario, not a quotation. The buyer must replace each rate with the category rate that applies to the exact products.

Common questions

What must be fixed before marketplace software pricing can be compared?

The meter and the included work must be fixed first. The comparison uses one fictional England seller, one authorised marketplace account and the same product, stock and later order-state exchange. It names real suppliers and public list prices.

Why should a software fee not be compared with a managed-service total?

One may exclude implementation and operating labour that the other includes. The text says to compare structures, not labels, and to model each component and its interaction where a supplier combines meters. A like-for-like cost entry must cover subscription plus omitted work and exit.

What should happen if routes cannot be normalised to the same job and period?

Report them as incomparable. Run sensitivity only after the buyer has evidenced each input. Consumer, safety, tax and privacy gates remain outside the cost ranking. Security, accessibility and exit gates also remain outside it, and scenario amounts must not be labelled as quotations.