Manual, buyer-built, hosted or managed marketplace operations, compared by failure mode

Four marketplace seller software business models can solve the same job in different ways: retain a manual process, build a buyer-owned connection, buy a hosted tool or contract a managed service. There is no winner without evidence from the merchant's catalogue, account permissions, order volume, failure history and exit needs.

This comparison uses one unit throughout: one accepted cycle in which an England merchant changes an authorised product record, updates stock, receives an order, reconciles a refund and exports the history.

Common case and evidence fields

The seller owns the commercial decision and the marketplace account. One catalogue is in scope. Record product identifier, evidence source, listing version, available quantity, order identifier, payment state, cancellation, return, refund, dispute and settlement. The outcome is a correctly reconciled cycle with an auditable exception route, not revenue or faster growth.

GOV.UK's online-selling guidance sets out information and ordering controls for online sellers. OPSS product-safety guidance directs businesses to obligations tied to their role and product. Those gates apply to all four routes. A successful data transfer cannot substantiate a product or cure missing seller information.

Like-for-like comparison

Route	Who performs the work	Main dependency	Evidence to obtain	Exit test
Current manual process	Authorised merchant staff	Documented hand-offs and marketplace interface	Timestamped change, second-person check and exception log	Reproduce the complete record outside personal files
Buyer-built connection	Merchant developers or contracted build team	Marketplace interface and buyer-maintained code	Versioned mapping, test results, access register and maintenance owner	Disable credentials and restore from buyer-held export
Hosted service	Contracted software supplier	Exact service edition, integration and supplier operations	Contract, data flow, support scope, change notice and export format	Import a complete export into a controlled destination
Managed service	External operator using agreed systems	People, approvals, account access and service contract	Named approvers, activity log, escalation route and continuity plan	Revoke access and transfer work without losing history

The comparison leaves charges blank. A supplier fee, developer labour and merchant review time use different units. The buyer should record currency, VAT basis, period, quantity, term and exclusions before calculating whole-life cost.

Responsibilities do not move as a block

HMRC's collection on goods sold through online marketplaces shows that VAT treatment can depend on seller status, customer, goods and location. A managed operator cannot decide those facts by reading a settlement file. The accountant and VAT adviser own the mapping.

Customer and staff data require a separate route. The ICO's final storage and access guidance addresses device storage and access technologies. The merchant must still document purposes, parties and configuration. The contract should state who can access what, but legal wording is not proof of actual control.

NCSC secure-service guidance supports checking identity, logging, monitoring and incident response. Apply the same synthetic access-removal and recovery test to every route. Do not award a compensating score if credentials cannot be revoked or a full history cannot be exported.

Choose by failure mode

Keep the manual route if the catalogue is stable, the cycle is reliable and its evidence cost is acceptable. Consider a buyer build where unusual mappings matter and maintenance ownership is funded. Investigate hosted software where repeated standard work dominates. Consider managed delivery when judgement and exception handling matter more than automation.

Before approval, run the defined cycle with synthetic or specifically authorised data. Stop if price, safety, privacy, security, accessibility, VAT or export evidence fails. The route that passes every gate at an acceptable verified whole-life cost is eligible for procurement. That is a buyer decision, not a market ranking.

There is no universal winner across these routes.