Marketplace seller software strategy: one merchant job, GOV.UK order duties, VAT records, product safety and security

A marketplace seller software strategy should settle one operational choice for one authorised seller. Should an England merchant keep its controlled manual process, change configuration around one marketplace account, or investigate a hosted tool? The answer depends on evidence about one job, not on a feature list.

That job is maintaining an approved product record, stock position and later order states between the seller's source system and the account. The operations and delivery guide shows how those states are run once a route is chosen.

What to take away

Record the parties and the job

Name the authorised seller legal entity, the marketplace operator, the account owner and the source system. Specify the product population, identifiers and territory. A trading name or public profile is not evidence of authority to sell.

Keep the parties' activities separate. The legal seller contracts with the consumer. The marketplace supplies the venue and acts under its own terms. A software supplier may transmit records. A managed provider might operate the account on the seller's behalf, so its authority needs its own record.

An order moves through placed, authorised, captured, accepted and fulfilled states. It then moves through cancelled, returned, refunded, disputed and settled states as applicable. Never use "sale" as a catch-all for these events. Stock and price follow their own events too.

What the order journey must show

Software that sends a product record also publishes the offer. The seller must therefore map what the customer sees before an order is placed. The GOV.UK distance selling page says a seller must provide the price including all taxes and how a customer can pay.

The same list covers delivery arrangements, costs and how long goods will take to arrive. A listing feed that drops one of those fields breaks the journey even if the transfer succeeds.

Two further duties belong in the test script. The customer must be told they can cancel up to 14 days after the order is delivered. Goods must be delivered within 30 days unless the seller has agreed otherwise with the customer.

The Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013 set the cancellation period for sales contracts, which ends 14 days after the goods come into the consumer's physical possession. A consumer-law reviewer decides the exact application to the seller's goods.

Check VAT records and product safety

For a VAT-registered business, the invoice must show the VAT number and display the VAT separately. The standard rate is currently 20 per cent on most goods and services.

VAT is normally calculated on a price decided without VAT, and the invoice shows the separate amounts. The detail sits in HMRC VAT Notice 700.

A seller should test how each route reproduces those fields, as the VAT-registered sellers article explains.

Product safety needs its own gate. OPSS monitors products offered through online selling platforms as well as other routes.

Product recalls cover specific unsafe products sold in the UK. Under regulation 5 of the General Product Safety Regulations 2005, no producer may place a product on the market unless it is a safe product.

A recall check therefore belongs in the baseline. Record who looks for an alert or recall that matches a listed product, and who can pull the listing.

Test access and security

A marketplace account holds product, price and customer records, so access is part of the strategy. The NCSC lightweight cloud approach works best for SaaS services, which usually focus on solving a single business problem. It asks four sets of questions.

Those four areas are data encryption, authentication and access control, security logging and incident management, and governance. Ask each supplier for evidence under all four before a route is tested. Use named accounts, least privilege and a controlled administrator route.

This is a minimum check, not certification. A privacy adviser should also map the data roles of each party.

Build the gate table

Set the gates before scoring any route. The table links each gate to the evidence a seller holds and the rule behind it.

A route that fails any row does not proceed, whatever it scores elsewhere. Consumer information, VAT records, safety, privacy and security are non-compensating.

Define buyer-owned objectives

An objective describes an observable decision, not a promised saving. For example, the seller may want to determine whether a route can reproduce an approved product change and reconcile specified later order states without losing a record.

Every measure needs a named owner and these blank fields: eligible population, numerator or unit, denominator, time window and timezone, source and query version, decision threshold, and guardrail with stop level.

Do not borrow a conversion rate or failure threshold from another merchant. Missing evidence is not a zero. The strategy framework sets out the problem statement behind it.

Compare delivery routes on one case

Assess the current manual method, a single-account configuration, a buyer-built integration, a hosted tool and a managed service against the same product and order-state script. Keep the workload unit constant.

Run the script on each candidate, whether that is Linnworks, Veeqo or StoreFeeder, and on each marketplace account, whether Amazon, eBay, Etsy or OnBuy.

Each route must show who changes a record, how authority is checked, what evidence returns, who handles an exception and how data can be exported.

Supplier statements stay labelled as such. The costs and budget guide covers how to price each route once it passes the gates.

Make rollback and exit part of the strategy

Before any production decision, prove that configuration can return to the accepted baseline. Record who disables writes, revokes credentials, restores approved product and stock records, reconciles in-flight orders and notifies affected parties.

Export tests should cover product data, mapping rules, order-state evidence and audit logs. See tool implementation for the rollback states.

The planning template holds the decision paper: problem, baseline, candidate routes, evidence, unknowns, gate results, whole-life cost method, rollback and recheck date. The seller stays on its safe current route while any hold is investigated.

Before you act

Common questions

What is the first operational choice a marketplace seller software strategy should settle?

The strategy should settle one operational choice for one authorised seller. Start by asking whether an England merchant keeps its controlled manual process, changes configuration around one marketplace account, or investigates a hosted tool.