Screening marketplace software benchmarks before any of them reach the report

No directly comparable authoritative England or UK marketplace-seller-software benchmark was found in the official sources checked on 6 September 2026. That evidence gap should remain visible. Broad retail, business or tax records cannot be converted into a product-feed, stock, order-state or reconciliation threshold.

This article supplies a screening protocol, not an industry average or target.

Reject broad proxies

The ONS Retail Sales Index internet-sales dataset measures internet retailing within its stated statistical scope. It does not identify marketplace-software users, software functions, account configurations or eligible event denominators.

The ONS UK business activity dataset covers VAT and/or PAYE based businesses and local units, with published geography and classification. It cannot establish seller-software adoption or performance. HMRC's digital-platform seller guidance describes reporting and seller responsibilities, not a benchmark population.

These datasets may frame a separately worded question. They are non-additive and inadmissible as denominators for this niche measure.

Build an admissibility record

For every proposed benchmark, capture:

• exact software function and decision;
• event and state definition, including whether the record is transmitted, rendered, accepted, authorised, captured, fulfilled, retained, refunded, disputed or settled;
• population, sampling frame and recruitment or collection route;
• England, UK or other geography and the rule used to assign it;
• numerator, denominator or other unit;
• period, timezone, maturity window and publication date;
• duplicate, retry, bot, staff, missing, late and correction treatment;
• product, marketplace, channel and seller-mix exclusions;
• weighting and adjustment method;
• uncertainty, disclosure control and revision status;
• funding, conflicts and possible publication bias.

The Office for Statistics Regulation's Code of Practice for Statistics governs official statistics, not private marketplace reporting. Its quality, value and trustworthiness framework can inform questions about transparent methods, but it does not approve a commercial benchmark.

Test comparability before calculating

Place the seller's local definition beside the candidate record. Mark each field SAME, MATERIALLY DIFFERENT or UNKNOWN. A comparison is inadmissible if the function, event, population, denominator or later-state window differs materially. Unknown weighting, correction or funding can also justify HOLD when it could change the decision.

Do not average incompatible figures or select the most favourable one. A rate based on marketplace acknowledgements cannot be compared with inspected rendered offers. Orders placed cannot stand in for orders retained after the declared refund and dispute window. Captured value is not settlement, taxable profit or causal contribution.

The Government Data Quality Framework presents fitness for purpose, lifecycle management and communicated limitations for government data. Use those ideas as prompts to document the screening, while retaining their public-sector scope.

Use an internal reference carefully

The seller may compare the same stable definition across its own declared periods. Record schema and query versions, product and channel mix, operational changes, missingness and correction status. Call the result an internal historical reference, not an England norm. If a marketplace interface or accounting rule changes, break the series or provide an approved bridge rather than pretending continuity.

Publish a defensible finding

The research output should list databases searched, dates, candidate records, rejection reasons and unresolved fields. For this review, the finding remains: no admissible authoritative England or UK niche benchmark identified. The buyer's threshold therefore stays blank and must come from its risk, evidence and decision authority, subject to statistical and specialist review.