Seven ownership areas in a marketplace seller workflow, with no staffing prescription

Marketplace seller software team roles should follow accountable decisions, not a standard organisation chart. One person may hold several categories, or a specialist may be external. The hand-offs must still identify who owns the evidence and who can stop a release.

Method: Roles were included when the bounded product, stock and order-state workflow needs a distinct decision owner supported by a current official boundary. Research date: 6 September 2026.

England scope: One fictional merchant established in England and one authorised marketplace account. UK and Great Britain sources retain their stated territory. Inclusions: Operational and specialist decision categories. Exclusions: Universal titles, headcount, reporting lines, salaries and supplier staffing.

Ranking: Non-ranked because the gates are non-compensating. Conflicts: No funding, recruitment interest, affiliate link or private staffing evidence.

1. Seller and account authority owner

This owner verifies the legal seller, marketplace account authority, permitted interface and production access. They approve account changes and remove obsolete privilege. HMRC distinguishes sellers from digital-platform operators, so a marketplace label cannot settle the merchant's identity or record duties.

2. Catalogue and consumer-journey owner

This role controls product identifiers, descriptions, claims, total price inputs, delivery and confirmation evidence. It accepts or returns changes rather than editing source facts silently. GOV.UK's online-selling guidance identifies the customer information and ordering subjects that require qualified consumer review.

3. Product-safety owner

For goods, the owner records supply-chain role, traceability, warnings, applicable regime, incidents and corrective action. OPSS product-safety advice separates Great Britain and Northern Ireland treatment. The named specialist, not the software operator, decides the actual product boundary.

4. Order, fulfilment and support owner

This owner preserves placed, accepted, fulfilled, cancelled, returned and refunded states, then routes customer exceptions without overwriting history. The current returns and refunds page shows why later remedy states need evidence and qualified review. It does not supply a universal workflow.

5. Payment, settlement and tax-record owner

Payment authorisation, capture, dispute and settlement stay separate from order status. The owner reconciles marketplace, payment and seller records and sends unresolved tax questions to the named adviser. HMRC's VAT records guidance covers supplies, adjustments and documents without deciding this seller's treatment.

6. Privacy, security and access owners

The privacy owner maps purposes, roles, storage or access operations, rights and deletion. The security owner controls privileges, logging, incidents and recovery. These may be separate people. ICO controller and processor guidance and NCSC online-service guidance establish different decision boundaries.

7. Accessibility, advertising and release owner

Accessibility review covers customer and staff tasks. Advertising review keeps paid placement and commercial claims identifiable. The release owner gathers both decisions, but cannot override them. The government service-provider guide gives the Great Britain accessibility context, while CAP recognition rules address identifiable marketing communications.

Build a RACI or similar record only after these decisions are mapped. A staffing shortage leaves the affected gate unresolved; it does not transfer authority to the nearest available person.