Tools and providers
Part of How to assess marketplace seller software tools and providers
Five marketplace seller routes compared on one England job without changing the question
Compare manual, configured, built, hosted and managed marketplace seller routes on one England job, shared evidence units and non-compensating gates.
A useful marketplace seller software supplier comparison puts every route through the same job and evidence test. This one compares five marketplace seller routes for a fictional England merchant that moves one approved product record, stock position and later order states between its source system and one authorised marketplace account.
The five routes are manual spreadsheet uploads, configured account apps, buyer-built integration, hosted platforms and managed services. Named tools appear in the table. They include Amazon Seller Central, eBay Seller Hub and Shopify Marketplace Connect. ChannelEngine, Amazon SP-API, Linnworks and Pattern follow.
No winner is declared. Research closed on 6 September 2026. Commercial amounts, weights, thresholds and service levels stay blank, because no exact offer or controlled result was supplied.
What to take away
- Compare five named routesmanual flat files, configured apps, buyer-built code, hosted platforms, managed services.
- Run all five through one identical fixture, then export and restore each one.
- Manual examplesAmazon Seller Central and eBay Seller Hub. Configured apps: Shopify Marketplace Connect and ChannelEngine.
- Built workAmazon SP-API and eBay Sell APIs. Hosted: Linnworks, ChannelAdvisor and Veeqo. Managed: Pattern and Netrush.
- Consumer and product safety gates sit outside the score and can stop a route.
- Do not compare a licence price with a managed-service total.
- No winner is declared in this comparison.
- If no route passes every gate, keep the current process or stop.
Use one comparison unit
The unit is one complete execution of the predeclared fictional fixture, followed by export and isolated restore. Product population, identifiers, state vocabulary, evidence date and test environment must be identical for every route.
Fixture contents:
- Product changesapproved, rejected, corrected total price, unselected optional extra.
- Eventsconflicting stock, duplicate, late, rejected.
- Post-salecancellation, partial refund, dispute, suppression, refused tracking.
- Accessrevoked privileged access, accessible staff and customer tasks, rollback.
- Export and restore.
- No public listing, real order, payment or customer message.
Compare five routes without changing the question
Each route can be delivered by real tools. Manual work runs on Amazon Seller Central flat files and eBay Seller Hub File Exchange. Configured apps include Shopify Marketplace Connect and ChannelEngine. Buyer-built work uses Amazon SP-API or eBay Sell APIs. Hosted platforms include Linnworks, ChannelAdvisor and Veeqo. Managed services include Pattern and Netrush.
Compare five routes
Evidence the buyer must obtain
- Manual process: Amazon Seller Central templates, eBay Seller Hub File Exchange
- Current steps, owners, source records and error history; Amazon and eBay upload file limits
- Configured account apps: Shopify Marketplace Connect, ChannelEngine
- Exact account feature, permission, schema, limits and change record; app listing and plan terms
- Buyer-built integration: Amazon SP-API, eBay Sell APIs, Shopify Admin API
- Code owner, interface contract, tests, deployment and maintenance evidence; SP-API app review and eBay OAuth keysets
- Hosted platform: Linnworks, ChannelAdvisor, Sellercloud, Veeqo
- Exact supplier, service, edition, contract, subprocessors and support; quoted plan and order-volume band
- Managed service: Pattern, Netrush, Marketplace Valet
- Supplier plus named operating role, authority, process and access records; retainer basis and revenue share
Main exposure to investigate
- Manual process: Amazon Seller Central templates, eBay Seller Hub File Exchange
- Human hand-offs, account permissions and reconciliation
- Configured account apps: Shopify Marketplace Connect, ChannelEngine
- Marketplace dependency and constrained configuration
- Buyer-built integration: Amazon SP-API, eBay Sell APIs, Shopify Admin API
- Buyer capacity, interface change and privileged access; eBay's default 5,000 calls a day per app
- Hosted platform: Linnworks, ChannelAdvisor, Sellercloud, Veeqo
- Supplier change, data handling, access and portability
- Managed service: Pattern, Netrush, Marketplace Valet
- Human intervention, subcontracting, accountability and continuity
Exit proof
- Manual process: Amazon Seller Central templates, eBay Seller Hub File Exchange
- Demonstrate that the documented process can resume
- Configured account apps: Shopify Marketplace Connect, ChannelEngine
- Export available records and restore the prior setting
- Buyer-built integration: Amazon SP-API, eBay Sell APIs, Shopify Admin API
- Rebuild from controlled source and retained code
- Hosted platform: Linnworks, ChannelAdvisor, Sellercloud, Veeqo
- Export, revoke, delete and restore independently
- Managed service: Pattern, Netrush, Marketplace Valet
- Remove access and return the task with complete evidence
This is a route comparison, not a claim that every marketplace offers the relevant interface. Permission must be proved for the named account from its current first-party terms and configuration.
Keep consumer and safety gates outside the score
Each route must preserve product facts, traceability, price, optional choice and later correction. GOV.UK's online-selling guidance identifies description, price, delivery, ordering and confirmation fields. Mandatory fees, taxes and charges are among the subjects of the CMA's price-transparency guidance. Those records define questions for consumer counsel; they do not approve a route.
For goods, OPSS product-safety advice requires attention to actual supply-chain roles, territory and product-specific rules. A route stops if it drops a required identifier, warning, traceability field or withdrawal instruction.
Compare data and security evidence consistently
Use the same fields for purposes, and for controller and processor facts. Add subprocessors, transfers, retention and rights help. Cover deletion and device storage or access. The ICO's controller-processor contract page remains under DUAA review, so its status and publication-day check belong in every dossier.
Security evidence covers authentication and minimum privilege. Add logs, support access and incidents. Include protected copies and recovery. NCSC's SaaS security guidance is useful for the hosted route but is not certification. Apply equivalent buyer questions to the other routes.
Record money and decision status
Public list prices and quoted ranges give a starting point, as of 2026. Manual work carries no licence fee: Amazon referral fees typically take 7% to 15% of the sale price, and eBay final value fees typically land near 10% to 13% plus a fixed charge.
Configured apps such as Shopify Marketplace Connect and ChannelEngine typically cost from nothing to about £150 a month. Buyer-built integration avoids licence fees but consumes developer time, typically £400 to £700 a day in the UK.
Hosted platforms such as Linnworks and Sellercloud typically quote about £200 to £800 a month at low order volume, rising with marketplace count. ChannelAdvisor-style enterprise contracts are typically quoted above £1,000 a month.
Managed services such as Pattern, Netrush and Marketplace Valet typically charge a retainer of about £2,000 to £10,000 a month, or 10% to 20% of marketplace revenue. Category, volume and service scope drive the range.
For each candidate, enter currency and VAT basis. Add the charging unit, period and term. Then limits, internal labour and pass-through costs. Finish with correction, migration and exit. Do not compare a licence price with a managed-service total. HMRC's VAT records page supports the evidence categories, while an accountant decides the actual treatment.
The prices above are labelled market ranges, not quotes from a controlled trial. The final record shows observed fixture outputs, missing evidence and separate gate outcomes. A buyer may choose only among routes that pass every required gate. If none does, retain the current process or stop the project rather than manufacture a winner.
Before you act
- Fix the fixture, identifiers and evidence date before comparing.
- Obtain the exact evidence listed for each of the five routes.
- Prove account permission from current first-party terms and configuration.
- Check consumer, price and product safety gates separately.
- Record money, VAT basis, labour and exit costs per candidate.
- Choose only among routes that pass every required gate.
Common questions
What does the comparison unit cover?
It is one complete execution of the predeclared fictional fixture, followed by export and isolated restore. Product population, identifiers, state vocabulary, evidence date and test environment must be identical for every route.
The fixture covers approved and rejected product changes, plus conflicting stock. It adds duplicate, late and rejected events. It also covers cancellation, partial refund, dispute, suppression and refused tracking. Revoked privileged access, accessible staff and customer tasks, rollback, export and restore close the run.
Why are consumer and safety gates kept outside the score?
Each route must keep product facts, traceability, price, optional choice and later correction. GOV.UK guidance names description, price, delivery, ordering and confirmation fields. OPSS advice covers supply-chain roles, territory and product-specific rules.
Those records set questions for consumer counsel; they do not approve a route. A route stops if it drops a required identifier, warning, traceability field or withdrawal instruction.
What happens if no route passes every gate?
The final record shows observed fixture outputs, missing evidence and separate gate outcomes. A buyer may choose only among routes that pass every required gate. If none does, retain the current process or stop the project rather than manufacture a winner. No winner is declared, and research closed on 6 September 2026.
