Marketplace Ops

Measurement

Part of Measuring marketplace seller software by reconciled commerce states rather than assumptions

Marketplace seller metrics defined by commerce state, eligible record and evidence lineage

Define marketplace seller software metrics through exact commerce states, eligible records, evidence lineage and blank buyer-owned thresholds.

Marketplace seller software key metrics should show whether a bounded commerce state can support a specific decision. They are not external benchmarks. For the fictional England seller used here, every threshold stays blank until an accountable buyer sets it from reviewed evidence.

Research closed on 6 September 2026. The taxonomy is non-ranked and contains no measured performance.

Use one definition card

Each measure needs: decision; exact event; eligible population; numerator and denominator, or another unit; clock start and stop in Europe/London; source, query, schema and definition version; duplicate rule; late and missing treatment; exclusions; correction status; owner; retention; uncertainty; threshold source; and failure response.

The Government Data Quality Framework asks public bodies to treat quality as fitness for purpose and manage it through the lifecycle. Its framework and dimensions are used here only as methodological prompts, not as a private-sector standard.

A non-ranked metric taxonomy

Product transmission integrity

Decision: investigate or pause a feed. Event: an approved source change receives a versioned response. Eligible population: in-scope product attempts during the stated clock. A possible proportion is accepted responses divided by eligible attempts, but retries and corrected resubmissions need declared treatment. Inspection of the customer-visible offer remains separate.

Rendered offer agreement

Decision: release, correct or withdraw an offer. Compare inspected description, total price, optional choices and seller identity with approved evidence. GOV.UK's online-selling guidance identifies information, price, ordering and confirmation subjects. A numerical match does not establish legal sufficiency.

Stock-state agreement

Decision: contain conflicting availability. Define source stock, marketplace acknowledgement, reservation and event time. Count unresolved conflicts or divide resolved matches by eligible product-location states. Do not call an acknowledgement a customer-visible stock fact.

Order-state reconciliation

Decision: route exceptions. Keep placement, acceptance, payment authorisation, capture, fulfilment, cancellation, return, refund, dispute and settlement distinct. The denominator may be orders accepted within the reporting window; later states need their own maturity cutoff. HMRC's digital-platform seller guidance notes that platform reporting does not replace a seller's ordinary responsibilities.

Safety-action control

Decision: suppress, investigate or escalate an affected product. Record eligible product identifiers, safety instruction, action state and evidence owner. OPSS business product-safety guidance explains that obligations depend on product and business role. This is a stop gate, not a score to average with sales activity.

Privacy-choice integrity

Decision: stop unexplained device access or correct processing. The population is eligible user-equipment interactions under the documented purpose. Compare recorded choice with observed storage or access; do not infer consent or lawfulness from a tracking event. The ICO's storage and access technologies guidance supplies the current PECR context.

Settlement reconciliation

Decision: investigate money differences, not estimate profit. Reconcile captured amounts, refunds, disputes and settlement to the reviewed accounting basis. HMRC's VAT records guidance identifies relevant record categories for VAT-registered businesses. An accountant must approve the tax and accounting treatment.

Set the decision before the number

Write the action, evidence owner and rollback route first. A metric remains UNRESOLVED if its denominator, state meaning or correction status cannot be reproduced. No favourable result can override a consumer, safety, privacy, accessibility, security or tax hold. Recheck definitions after any schema, account, product, payment or marketplace-rule change.

More in Measurement

Measurement

Measuring marketplace seller software by reconciled commerce states rather than assumptions

Build marketplace seller software measurement around exact commerce states, reconciled evidence, decision owners and honest limits on attribution.

Measurement

Comparing marketplace attribution methods on one population and one window

Compare marketplace software attribution methods on one population and window, exposing assumptions and reserving causal language for credible designs.

Measurement

Screening marketplace software benchmarks before any of them reach the report

Screen marketplace software benchmarks for comparable function, population, denominator and uncertainty, and publish the evidence gap honestly.

Measurement

Six ways marketplace measurement goes wrong before the numbers reach a seller

Find marketplace software measurement errors that corrupt state, denominator, reconciliation and causal claims before they shape seller decisions.