How to assess marketplace seller software tools and providers

A. Continue with the manual workflow

Keep the seller's current manual process as a full candidate, not merely a baseline. Record how it moves approved product records and stock positions, returns later order states, handles exceptions and supports recovery. Compare its evidence with every alternative using the same job, fixture and exit question.

For this route, document the source of approved facts, the steps that move stock and order information, and the person who resolves conflicts. Test whether product records and open order states can be recovered while the current method resumes, rather than assuming that a familiar process is automatically dependable.

B. Use a marketplace-account feature

An existing marketplace-account feature qualifies only within the seller's actual permission to use it. Verify that permission inside the marketplace account and against current terms. A public integration directory does not establish authorisation, and the feature's presence alone is not evidence that it suits the bounded job.

Record the feature's inputs, outputs, exceptions and recovery behaviour. Test export, restore and access revocation with the shared fixture, and do not treat a directory listing as permission to connect. Keep the exact account, feature and configuration under review identifiable in the evidence record.

C. Specify the connection the buyer would build

Assess a buyer-built integration as an exact implementation, supported by evidence for data transformations, sequencing, retries and rejected updates. Identify which fields originate in the seller's own system, the marketplace or another party. Retain buyer-controlled test output from the same fixture used for every other route.

Inspect the schemas and the treatment of changes that are late, duplicated or rejected. Record which records and open order states remain recoverable without the connection, and test that recovery rather than treating buyer ownership of the build as proof of control or successful operation.

D. Name the hosted offer precisely

Admit only the exact legal supplier, service and edition that the seller can contract for and use in the intended UK context. A category label or feature list does not identify the offer, and no product or provider should be selected before the comparison boundary is fixed.

Date direct records, test the specified behaviours and mark unavailable details as unknown rather than inferring them. Confirm the precise service and configuration represented by each record, since a claim about one edition does not establish how another edition behaves.

E. Separate contracted work from software

A managed service adds a provider's operational work, but that work must remain distinct from a software licence. Record contracted duties, support boundaries and correction ownership separately. Test the service's behaviour and exit evidence on the same basis as every other route, using the precise managed-service model under consideration.

Record labour separately from software charges and identify which party performs each operational task. The provider's service description is not a substitute for observed behaviour, and the seller must retain access to records during transition and after the service ends.

One merchant case defines the perimeter

Use one bounded case: a fictional merchant established in England, its authorised seller legal entity and one marketplace account. Limit the job to moving an approved product record and stock position from the seller's source system, then returning later order states to that system. No product or provider is pre-selected.

Record the case boundaries:

Name the seller, marketplace operator, software supplier, managed provider, and any payment or fulfilment party. Record which legal entity controls the account, who may change a product record and who contracts with the consumer. These are separate roles, even where a service description appears to combine them.

HMRC's digital-platform seller guidance distinguishes an individual or entity seller from the platform operator. It also says platform reporting does not replace ordinary business records or tax calculations. For UK VAT questions, compare seller records with UK VAT record duties, without treating software as the decision-maker.

Software may transport a field without taking responsibility for its meaning. The merchant still needs qualified decisions about product evidence, consumer information, safety, privacy, accessibility and tax. Check marketplace permission in the actual account and current terms; a public integration directory does not establish authorisation.

Keep placed, accepted, authorised, captured, fulfilled, cancelled, returned, partially refunded, fully refunded, disputed and settled states distinct. If a supplier uses different terms, require a mapping that explains what creates each status, what can change it, whether updates may arrive late, and how duplicates or rejections are handled. A workflow diagram alone does not establish a schema contract; the state sequence provides a test boundary.

Evidence must match the exact offer

For every candidate, date the direct records and establish the exact supplier, service and edition. The evidence file must address functional behaviour, consumer information, product controls, data, security, accessibility, support, commercial terms and exit. A change to an identifier, price or stock unit without explanation is a stop issue.

Interface and observed behaviour

Collect input and output schemas, identifiers, validation rules, transformations, sequencing, retries, rejection handling, rate or volume limits, change notices and support boundaries. Identify which values come from the seller, marketplace or supplier. Test observed behaviour against the declared interface; unexplained changes to a product identifier, price or stock unit block progress.

Consumer information and goods

Trace product facts, total-price inputs, unavoidable charges and optional choices through to the consumer-facing record. The CMA price-transparency publication addresses mandatory fees, taxes and charges. GOV.UK online-selling guidance identifies product description, price, delivery, order correction and confirmation matters, and says online businesses need express consent for optional extras.

A consumer solicitor must examine the actual invitation to purchase, goods, offer and exceptions. For goods, retain model or batch identifiers, manufacturer or importer information, warnings, instructions, traceability and corrective-action routes where applicable. OPSS product-safety advice distinguishes Great Britain from Northern Ireland and notes that product-specific rules may apply. Supplier features and marketplace acceptance do not amount to product approval.

Personal data and device access

Map each purpose, personal-data field, source, recipient, location, retention period and deletion route. Decide controller and processor roles from the actual activity, not the contract heading; ICO controller and processor guidance explains that factual distinction. Keep data-protection checks tied to the particular service and configuration under review.

Record subprocessors, remote access, international transfers, rights assistance, incident help and end-of-contract handling. The ICO's detailed controller-processor contract guidance is marked under review following DUAA changes. Preserve that status with the evidence and obtain a publication-day privacy check before relying on the guidance.

List cookies, pixels, SDKs and other device storage or access separately. The ICO's storage and access technologies guidance sets out the current PECR position. Marketplace or payment permission does not answer the PECR question for unrelated tracking, so examine and document that activity separately.

Security, recovery and configuration

Require evidence of the authentication model, privileged roles, logs, support access, security contacts, incident process, protected copies, recovery and deletion methods. NCSC supplier-assurance questions cover governance, access, data protection, incidents, independent testing and contract exit. They prompt investigation; they do not endorse a supplier.

Examine buyer configuration as well as supplier controls. NCSC SaaS security guidance says customers retain responsibility for configuration specific to their use. Test least privilege, account removal, monitoring and recovery directly rather than relying on a trust-page badge or supplier statement alone.

Accessibility and support

Define staff and customer tasks that must remain usable: editing product evidence, resolving a rejected event, checking price, making an optional choice, cancelling, requesting a refund and reaching support. The government's Equality Act service-provider guide describes the Great Britain service context and notes that Northern Ireland has separate legislation. An accessibility lawyer and practitioner should assess the actual service.

Ask for an accessibility statement or test evidence, then inspect its edition, scope, technology and date. An automated scan does not show that an end-to-end task works. Record support channels, accessible alternatives, escalation, change notice and correction ownership without inventing a service level.

Commercial terms and exit

Capture the contracted entity, service, currency, VAT basis, charging unit, period, minimum term, limits, pass-through amounts, renewal, suspension, support, liability and insurance evidence. Leave every amount blank until a current record exists for the precise offer. HMRC VAT-record guidance identifies record categories, but does not decide treatment for this merchant or contract.

Exit evidence should cover export fields and formats, open-order handling, correction access, transition help, account revocation, retention, deletion and an isolated restore. A low subscription charge cannot compensate for blocked export or an unresolved consumer, safety or privacy gate. Include exit terms in contract review, not only in a sales discussion.

Apply one synthetic fixture to all routes

Write the fictional fixture before testing so results cannot be tailored to a preferred option. Use fictional products and people, a non-production account where authorised, and no live listing, order, payment or customer message. This fixes the test boundary without creating a real marketplace transaction.

Apply the same fixture, product population, state vocabulary, evidence window and exit question to the manual process and each alternative. Include an approved and a rejected product change, conflicting stock, a corrected total price, an unselected optional extra, duplicate and late events, a rejected update, cancellation, partial refund, dispute, listing suppression and refused tracking.

Also test revoked privileged access, an accessible staff task, an accessible customer task, rollback, export and restore in isolation. For each case, record expected input, expected output, observed output, timestamp, log reference, reviewer and result. A pass establishes only the specified behaviour in that configuration, not broader compatibility or compliance.

It does not establish marketplace-wide compatibility, legal compliance, accuracy on other data, performance at scale or durability after a release. Keep those limits beside the result so a successful fixture is not presented as evidence for a different population, configuration or later software version.

Keep hard gates outside the comparison score

Compare the manual process, existing account configuration, buyer-built connection, hosted tool and managed service using identical fields. Do not blend a managed provider's labour with a software licence, or describe supplier pricing as merchant revenue. Set buyer-owned weights and thresholds only after non-compensating gates have passed.

Consumer information, safety, tax, privacy and PECR, security, accessibility and exit cannot be traded against convenience. Record three evidence classes: a first-party supplier statement, independently inspectable evidence and buyer-controlled test output. Anything outside those classes remains unknown until evidence supports it.

Companies House register-search guidance warns that filed information is not verified by Companies House. A register result can support a narrow identity fact, but not operational capability. Keep that distinction in the dossier, and use the fictional fixture to test behaviour rather than treating an identity record as a performance result.

Make any release recoverable

Begin with discovery and an approved baseline, then complete the role map, interface specification, assurance dossier and synthetic fixture. Configure a restricted environment, run tests, close evidence gaps and obtain each required specialist decision. Keep production access disabled throughout these stages.

For each gate, record pass, rework, hold or stop. Only a named authorised owner may approve a limited release after every required gate passes. Define monitoring for rejected or late events, state conflicts, access changes, product corrections and customer-affecting exceptions, alongside rollback, evidence preservation and restart authority.

Rehearse export, isolated restore and return to the current process before commitment. If the buyer cannot recover product records and open order states without the candidate, the exit claim remains unproved. The operations state model can frame the event sequence, but it does not replace tests of the chosen configuration.

Bound the recorded decision

The procurement pack should identify the buyer's problem, alternatives considered, exact candidate, evidence dates, unknowns, fixture results, independent reviews, commercial assumptions and final authority. Re-open supplier and regulator records before publication and contracting because editions, interfaces, terms and guidance can change.

This method helps an England merchant investigate a bounded decision. It does not certify a supplier, marketplace connection, service or legal outcome. Use the selection stop rules alongside specialist decisions, and retain the evidence supporting every pass, hold, rework or stop result.

The scope includes goods, consumer contracts, consumer protection, personal data, accessibility, online selling, VAT and product description. Preserve the distinctions between those subjects when recording a decision; a positive result for one area does not settle another, and no single score replaces the relevant evidence or specialist judgement.