Marketplace seller software review method: Linnworks, ChannelEngine and four more on hold

On 6 September 2026, a fictional England seller is deciding whether to connect one source system to one authorised marketplace account. The task is limited to preserving an approved product record and stock position, then reconciling later order states. Procurement is frozen unless a precisely identified service can be admitted and tested.

The seller draws a boundary around the job

The case begins with a narrow operating need, not a general automation claim. No named provider has passed the entry checks or undergone controlled testing, so the seller and reviewer first settle what the proposed connection is meant to do and what remains outside it.

At the outset, the seller's boundary is one authorised marketplace account and one source system. It needs to maintain an approved product record and stock position, then reconcile later order states between those systems. This keeps the decision tied to a defined operation rather than a broad promise of automation.

Listing publication, repricing, inventory control, order management and payment handling are distinct functions. Fulfilment, returns, customer service, advertising and accounting sit outside that core as well. A provider might bundle several, but every included or excluded boundary needs checking rather than an assumption that one connection performs the whole job.

The manual option stays in view: approved spreadsheets, marketplace controls and documented hand-offs are candidates too. The reviewer records what the existing process can perform, how hand-offs are evidenced and which activities the seller has deliberately excluded. Visual sophistication is not an admission criterion, and neither is a software label.

Published pages produce a six-name candidate file

The search returns six named services from published information alone; none has received a controlled test. That produces a candidate file, not a shortlist or endorsement. Since prices change and a supplier quote is not itself an offer, commercial comparison must wait for equivalent terms.

For any later price comparison, the reviewer needs the currency, VAT basis, charging unit, period and eligibility. A published tier page remains a claim until a dated quote is available. Even then, quoted prices are not comparable until the buyer has matched their underlying basis.

Admission fails before anyone connects an account

A route can enter comparison only after the reviewer can identify the legal supplier, relate it to the trading name and establish the exact service under consideration. The scenario finds no candidate meeting that admission standard, so no provider connection or controlled service test follows.

The Companies House guidance on searching the company register explains which public company details may be viewed. A register result supports only the particular facts it records; it does not establish service quality, marketplace permission, financial resilience or suitability. The reviewer still has to connect the trading name, legal supplier and exact service.

The evidence file calls for dated first-party material covering functions, edition, UK availability and supported account conditions. It also needs schemas, identifiers, error handling and support terms. Price evidence stays out unless it states currency, VAT basis, charging unit, period and eligibility; a dated supplier quote is still needed to confirm published tiers.

The record identifies the reviewer's role, competence and independence status, as well as the precise subject, legal entity, service name, edition and geography. It also stores the review date, source-access dates, expiry triggers, opened documents and versions, fixture actions, untested production actions, live data and customer journeys, funding, affiliate links, samples, conflicts, unresolved evidence, method limits and permitted verdicts.

The author and fact-checker remain unassigned. Qualified specialists must approve the consumer, safety, privacy, accessibility and security gates, while tax and contract checks need named sign-off too. Privacy and security material must address the actual arrangement, not offer generic assurance.

The ICO controller and processor contracts guidance is under review following the Data (Use and Access) Act changes. It supplies due-diligence questions rather than a conclusion. NCSC supplier-assurance questions cover governance, incident recovery, access, data protection and contractual subjects, but a questionnaire cannot show how a particular configuration behaves.

The file therefore distinguishes a supplier answer from observed behaviour and leaves any unsupported conclusion unresolved. A supplier response can inform the investigation, but it cannot replace evidence from the exact offer, account conditions and configuration that the seller would use.

The independent checks block a live demo

The reviewer treats each consumer, product, data, device, security, recovery, configuration, accessibility, support and commercial-exit check as an independent gate. A strong result in one area cannot compensate for a failed legal or operational requirement elsewhere.

Online-selling guidance identifies information, price, ordering, correction and confirmation matters. The CMA price-transparency material addresses mandatory fees, taxes and charges. A fixture can check whether configured fields are preserved, but only a qualified reviewer can assess the seller's legal position.

OPSS product-safety advice explains that duties depend on the product and the business role. Marketplace acceptance does not replace product-safety evidence. Accessibility needs a task-based check; the EHRC services code of practice applies in England, Scotland and Wales, and a specialist must define the tasks and acceptable evidence.

A common fixture is ready but not run

No candidate reaches admission in this scenario, so provider testing stops before it begins. The seller nevertheless records the shared fictional fixture that every admitted route and the manual baseline would receive, with production publication disabled throughout any proposed run.

The planned sequence contains these events:

The test record names its configuration, scripts, expected states and reviewer. The same synthetic fixture is intended for the admitted service and manual baseline. A passing action proves only the specified behaviour in that setup; it does not establish marketplace coverage, continuous availability, lawful processing or accessibility for every user.

Product safety, financial correctness and commercial effect remain outside this fixture. A changed edition, interface or permission triggers another check. The fictional fixture is a controlled examination of named behaviour, not proof that untested production journeys work.

The evidence grid keeps unknowns visible

For every route that is eventually admitted, the seller records the same fields in the same units, including the manual route if it meets the entry standard. Missing evidence is marked UNKNOWN. Scoring waits until the buyer has defined weights and thresholds, and cannot override an independent failed gate.

Every requirement, source document, test step, observation and specialist decision receives an ID, which the comparison record can cite. The reviewer retains original first-party pages or contract versions, access dates and later corrections. When a supplier changes a claim, both states stay on file with the version used for the verdict identified.

If something fails, the record attributes it where possible to the candidate, marketplace response, buyer configuration, fixture or an unresolved interaction. An unexplained failure is not a product conclusion and must not be erased. The affected field remains UNRESOLVED, with the next evidence needed recorded beside it.

Claim labels expose why the verdict is limited

The reviewer keeps supplier statements, register facts, contract terms, customer reviews and observed results in separate evidence classes. Each can support only what it actually establishes, and none should silently stand in for a different kind of evidence.

A company-register entry remains a register fact. Contract wording records what identified parties agreed, subject to legal review. Customer reviews bring their own authenticity, selection and recency problems. A star rating does not show that a service handles this seller's product or order states, so no sentiment score or unverifiable testimonial is manufactured.

The CMA collection on reviews and social media endorsements points businesses to current fake-review guidance. Its current fake-reviews publication reinforces the need to keep review material separate from controlled evidence. Review claims cannot fill gaps in tests, account permission or the exact service configuration.

An agency receives the same scrutiny: its legal entity, defined service and actual dossier must be verifiable. Without a specific agency record available for examination, the reviewed set stays empty. An agency dossier exists for this purpose only when evidence concerns the exact supplier and service, not merely a named provider.

HOLD is the only supported decision

The verdict follows the available evidence rather than editorial enthusiasm. UNTESTED applies when a dossier exists but controlled actions have not taken place. Admission status, test results, gate outcomes and unresolved matters stay visible, and a weighted score cannot hide a failed independent gate.

Published evidence makes Linnworks and ChannelEngine appear closest to the defined task: both publish marketplace connectors, inventory handling and order states. Veeqo and Sellbrite cover narrower slices. ChannelAdvisor and Mirakl target larger buyers through quote-led contracts. Every named provider remains on HOLD.

No provider reached the admission and test standard, so the case produces no shortlist, ranking or winner. The decision record cites the candidate dossier, requirement version, fixture and gate results. It also records unknowns, the conflict statement and evidence expiry date, and names who can pause procurement and what proof permits reconsideration.

The record publishes the search date, sources considered and exclusion reasons. Before any later recommendation, the exact edition must be tested with the approved fixture. If required records cannot be exported or access cannot be revoked, the review remains on hold. Publication itself stays paused until real reviewers are named and every source is reopened on publication day.

The verdict changes when the legal entity, service edition, marketplace permission or contract changes. A changed data arrangement, accessibility evidence or recovery route also triggers revision. Reconsideration depends on current evidence for the changed subject, not on a previous edition or permission set.

Rules to reuse after this case

The case leaves a practical rule set: define the seller's task before searching, admit only an identifiable supplier and exact service, and limit each test conclusion to the configuration that produced it. Keep the manual process eligible for comparison and leave unsupported claims unresolved.

Keep unknowns explicit, keep independent gates outside a score and make the decision reproducible. The record should say who reviewed the evidence, which controlled actions ran, what remains untested and how the verdict follows. A register entry, supplier page, questionnaire or customer rating cannot establish facts beyond its own evidence scope.

Any new edition, interface or permission calls for another check before the decision changes. The reviewer should retain the documents, test observations and specialist decisions behind the conclusion, while procurement remains paused until the evidence supports reconsideration.