Operations
Part of Operating marketplace seller software as a state machine, not a status label
Marketplace seller software service standards: a framework
Use marketplace seller software service standards to define events, evidence, customer-harm gates and failure handling without inventing unsupported targets.
Marketplace seller software service standards are useful only when they define an event, eligible population, unit, clock, evidence and response to failure. This guide offers a framework, not universal availability, accuracy or response targets; thresholds should follow the buyer's risk, capacity and reviewed contracts. For example, apply it to an order-sync service in seller platforms such as Linnworks or ChannelEngine connected to Amazon or eBay; these are examples, not endorsements or measured suppliers.
No supplier service, marketplace connection or live order was measured; the guidance below is a definition framework, not a supplier review.
What to take away
- A standard is useful only when it defines an event, population, unit, clock, evidence and failure response.
- Do not present a buyer standard, contractual commitment, supplier claim, observation or regulatory requirement as another class.
- Product safety gates cannot be averaged into catalogue quality and cannot be postponed by an operational target.
- Every threshold needs an owner who can pause the affected state and a record of what continues during containment.
- If clocks or populations differ, mark the standard unresolved rather than manufacture a common percentage.
Label the kind of standard
Buyer standard states the merchant's requirements. Contractual commitment is wording accepted by identified parties for an exact service and term, and a supplier claim is an attributed statement awaiting verification.
An observation is a measured result for a named version and period, and a regulatory requirement comes from the applicable authority and trigger. Never present one class as another.
NCSC supplier-assurance questions prompt buyers to examine incident management, remote access, continuity, reporting and contract exit. They provide questions, not an SLA or certification.
Complete the definition card
For each proposed service standard, record these definition-card fields:
- Event and state
- Eligible population
- Measure and unit
- Clock
- Evidence
- Threshold
- Failure response
- Recheck trigger
| Field | Buyer entry |
|---|
Standard definition card fields
- Event and state
- Eligible population
- Measure
- Clock
- Evidence
- Threshold blank until approved
- Failure response
- Recheck trigger
An event described as "order complete" is too vague. Separate placement, acceptance, authorisation, capture, fulfilment, cancellation, return, refund, dispute and settlement. State whether duplicates, retries, staff tests and unresolved records enter the denominator. For example, a buyer could define an order as reconciled only when a matching destination record exists, with missing or duplicate records surfaced as exceptions; this sets a test without prescribing a numerical target.
Choose standards around customer harm
For listing and price feeds, define the inspected version and evidence owner. The Competition and Markets Authority (CMA) is a relevant UK consumer authority; GOV.UK online-selling guidance identifies description, price, ordering, correction and confirmation subjects. Relevant legal context includes the Consumer Rights Act 2015 and Digital Markets, Competition and Consumers Act 2024; applicable duties depend on the transaction and the seller's role. A service failure response may withdraw an affected offer while open orders move to a customer-support queue.
For goods, product-safety gates cannot be averaged into catalogue quality. The Office for Product Safety and Standards (OPSS) notification guidance addresses business reports about unsafe or non-compliant products. The relevant authority and response depend on the product and circumstances; an operational target cannot postpone any applicable reporting or containment.
Define evidence and recovery standards
Service data standards specify permitted source, completeness rule, missingness, lateness, duplicate handling and correction history. Privacy permission is a separate gate. A faster event is not acceptable if a refused storage or access choice is ignored.
Security standards cover privileged access review, log availability, detection, containment and recovery evidence. NCSC secure online-service guidance distinguishes logging, security monitoring, transaction monitoring and incident management. Create separate measures rather than one security score.
Accessibility standards describe the user task, method, assistive setup where relevant, defect evidence, owner and retest. They must cover staff exception work and customer correction, refund and support journeys, not merely page rendering.
Make failure actionable
Every threshold needs an owner who can pause the affected state. The record must say what continues during containment, how customers and open orders are handled, what evidence permits restart and when rollback is required. Supplier escalation does not remove the seller's responsibility to preserve its records and routes.
Keep consumer, safety, tax, privacy, the Privacy and Electronic Communications (EC Directive) Regulations 2003 (PECR), security, accessibility and exit as separate gates for the software workflow, not measures that can compensate for one another. If the contract, system evidence and buyer definition use different clocks or populations, mark the standard UNRESOLVED. Do not manufacture a common percentage or choose the most favourable figure.
Before you act
- Label the kind of standard before using it.
- Complete the definition card for each proposed standard.
- Separate order events such as placement, acceptance and fulfilment.
- Define evidence source, query, version, owner and retention.
- Make failure response actionable with containment and restart rules.
- Keep consumer, safety, tax, privacy and security as non-compensating gates.
Common questions
What fields must a definition card record for each proposed standard?
The card records event and state, eligible population, measure, clock, evidence, threshold, failure response and recheck. The threshold stays blank until buyer-approved evidence exists. The recheck is triggered by contract, interface, volume or risk.
Why is order complete too vague as an event?
Because it fails to separate placement, acceptance, authorisation, capture, fulfilment, cancellation, return, refund, dispute and settlement. The text says to state whether duplicates, retries, staff tests and unresolved records enter the denominator.
When should a standard be marked unresolved?
When the contract, system evidence and buyer definition use different clocks or populations. The text says do not manufacture a common percentage or choose the most favourable figure. Instead, mark the standard unresolved.
