Five marketplace routes on one seller job, and why the winner is withheld

Marketplace seller software channel strategy means choosing how one seller job is delivered, not choosing where to advertise. This comparison uses one England merchant, authorised seller entity and marketplace account. The job is to carry an approved product record and stock position from the seller's source, then return distinct order and later-state evidence.

No provider or marketplace is named. Exact access, service and contract records would be required before one could enter the comparison.

Hold the case and unit constant

Each route receives the same synthetic product, identifiers, price correction, stock conflict, placed order, cancellation, refund, dispute, late event and duplicate. The unit is one eligible state transition with its acknowledgement, exception or reconciliation evidence. Buyer-set thresholds remain blank.

Route	Control and work	Evidence returned	Dependency and exit
Current manual	Authorised staff enter and reconcile records	Versioned source, marketplace response and signed exception log	Staff capacity; retain procedure and files
Single-account configuration	Buyer configures existing account functions	Configuration version, event log and exported state	Marketplace terms and account features; restore prior setup
Buyer-built integration	Merchant owns mapping and code	Source commit, test record, message and error log	Interface change and internal support; disable writes and restore build
Hosted tool	Contracted service transforms or transmits records	Supplier and buyer logs, configuration and export	Exact edition, subprocessors and service continuity; tested export
Managed service	Provider operates an agreed process	Work record, approval trail, exception and hand-back pack	People, system and contract dependency; credential removal and handover

These are delivery categories, not claims that every route exists for a particular account. The current method stays in the table even if it is labour-intensive.

Apply the same seller gates

The legal seller owns its customer and product decisions. GOV.UK online-selling guidance sets out information and ordering matters that can shape the test script. It does not say that a technical route assumes seller responsibility.

Every category must preserve approved product and traceability evidence, total-price and optional-choice decisions, accessible customer tasks and correction or withdrawal. OPSS product-safety material shows why product role and category need review. A transmitted listing is not proof that the product is safe.

Keep order placed, payment authorised, captured, fulfilled, cancelled, returned, refunded, disputed and settled as separate values. HMRC's VAT record page distinguishes transaction and adjustment records. An accountant decides how the seller reconciles them.

Examine access, data and evidence

Ask who may change catalogue, stock and price, who can see orders, and how privileged actions are logged. NCSC's SaaS security guidance recommends least privilege, monitoring and recovery planning. Apply those tests to every category, including the manual route.

Map controller and processor roles from actual decisions. Record tracking technologies separately and have a PECR specialist check them. Test export, access removal, rollback and deletion with synthetic records.

Measure every route in the same reporting window and Europe/London timezone. Define the eligible state transition, numerator, denominator, missing and duplicate treatment, source query and evidence owner. A marketplace response received after the window stays late; it is not silently moved into a favourable period. Costs also use one buyer-defined unit and whole-life boundary.

Withhold the winner

Choose only after all routes have comparable evidence, whole-life cost and named specialist decisions. Consumer, safety, privacy, security, accessibility, VAT and exit failures cannot be outweighed by convenience. This desk comparison has no winner because no merchant dossier, controlled test or buyer threshold exists.

If a route cannot expose its transformation, error or export evidence, record the field as unknown and hold it. Do not reward a polished supplier description for evidence that the current manual method can actually produce.