Pilot checklist for an England merchant trying marketplace seller software

Set a narrow test boundary

Keep the pilot narrow: test one operational job, not a collection of features. Define one England merchant, one owned system, and one named marketplace account; the bounded task is keeping an authorised catalogue, stock record, and later order states aligned.

For a concrete example, choose an Amazon Seller Central account and verify the proposed Veeqo or Linnworks connection against that account. Those names are examples, not recommendations. Begin with synthetic or specifically authorised records, and keep live use on hold until specialist reviewers clear it.

Establish who can approve the connection

Require evidence of the seller's identity, account ownership and authority to approve an integration. Record the legal and trading names, establishment evidence and contractual role. Distinguish the marketplace operator, seller, software provider, payment service, fulfilment party and managed operator before the trial begins.

HMRC's guide for sellers on digital platforms explains information platforms may collect. It also says platform reports do not replace business records or tax calculations. Use that material to frame identity checks, not to choose the merchant's tax treatment; keep applicable company, UTR, VAT and EORI details distinct.

Preserve the offer that was approved

Make each marketplace listing traceable to an approved product record, image rights and claim evidence. Name who can change price, stock, charges, delivery details and product copy, then preserve the version and timestamp actually sent, including any rejection or override.

GOV.UK's online and distance selling guidance covers business and order information. Give corrections and withdrawals an owner, evidence trail and completion check. CMA price-transparency guidance addresses mandatory fees, taxes and problematic price presentation; assess the Consumer Rights Act 2015 and Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013 against the actual goods, offer and journey with a consumer lawyer.

Make product withdrawal testable

Before a product enters the pilot, establish the merchant's role for each product class and keep required technical, warning and traceability evidence outside the marketplace listing. Test suspension, recall communication and withdrawal with a synthetic item so the exercise does not depend on live customer or product records.

OPSS product-safety advice makes clear obligations depend on the product and business role. For relevant goods in Great Britain, check the General Product Safety Regulations 2005 alongside product-specific rules. Software validation is not a safety assessment. Stop if the merchant cannot trace or withdraw an affected item.

Follow each order through settlement

Represent each order as separate states: received, accepted, payment authorised, captured, dispatched and settled. Join cancellation, return and refund and dispute records to the original order without overwriting history. This is necessary to distinguish transaction history from the final settlement.

Reconcile marketplace deductions and cash separately from sales, VAT and profit. HMRC's online-marketplace VAT collection guidance shows treatment can vary with goods, seller, customer and location. Require an accountant and VAT adviser; do not let the connector classify an unresolved transaction. Check applicable VAT record duties with the relevant adviser.

Restrict data and account access

Map every customer data, staff and device field, its purpose, recipient, retention period and deletion route. Separate service messages from direct marketing and audience advertising. This map lets reviewers assess the proposed data flows and contact practices before any live records enter the integration.

Grant only the minimum account and API permissions needed for the bounded task, and list every credential with its owner. Log configuration, permission and bulk-change events without storing secrets in logs. The ICO's storage and access technologies guidance covers cookies, tags, pixels and related technologies; apply the UK GDPR, Data Protection Act 2018 and Privacy and Electronic Communications Regulations 2003 (PECR) where relevant.

NCSC online-service guidance addresses access, logging, monitoring and incident handling. Keep privacy and security approval independent, and hold the pilot if either review is incomplete. A connection that works technically does not itself establish approval for the data, permissions or customer contact involved.

Rehearse support and reversal

Test staff tasks and customer communications using accessible methods, and assign an owner to exceptions when a marketplace or API changes. Name the person responsible for each test and hand-off, so a failed task or connection change cannot disappear between the seller and supplier during the pilot.

The government service-provider guide provides Great Britain context for anticipating barriers and reasonable adjustments. England is within Great Britain, but that guide does not replace checking requirements for the merchant's service. Export catalogue, mappings, orders, adjustments and audit history in usable form, then revoke access and restore the export.

Run the pilot in four weeks, with a go or no-go rule

This article covers a merchant entering a pilot with a supplier, not a supplier entering the market. The sequence and thresholds below are suggested; agree your own in writing before week one, with a named owner for each.

Take the go or no-go decision at the end of week 4. Go only if every pass test is met, privacy and security approvals are signed, and the merchant can continue without the supplier. Any miss is a no-go until it is fixed and retested. A partial pass does not extend the pilot silently; record a new decision date instead.

Use a written pilot plan to record evidence, sign-off and the reversal test. Run the bounded workflow without the supplier and confirm the merchant can continue it. Hold entry until every applicable gate has evidence, named approval and a tested route back; convenience or cost cannot compensate for a failed gate.