Three social commerce supplier routes compared on responsibility, not feature counts

What to take away

No winner is namedthe routes were never installed, timed or tested side by side, so the output is a duty map, not a ranking.
Direct platform tooling leaves checkout, refunds and data duties with the retailer. A connector splits them between the shop dashboard and the seller centre.
Score each candidate as documented, demonstrated, observed or unverified before weighting it.
Compare cost only as dated line itemssubscription, transaction fee, connector build, support, admin hours, exit.
Re-run when checkout location, platform policy, connector support or data collection changes.

Route boundaries: checkout, refunds and data

Shopify connectors run through documented sales channels. Shopify documents catalogue and order synchronisation with TikTok Shop, and a shared Meta catalogue where the purchase completes on the online store.

WooCommerce connectors run through extensions. Its TikTok extension record sends orders back to the WooCommerce dashboard, and its Pinterest extension documents feed generation and product synchronisation.

Direct tooling uses the destination's own seller centre. TikTok publishes a UK seller registration policy on seller eligibility, and Pinterest documents retail catalogue feeds. Less connector work, more retailer-built handling.

If the destination is still open, compare the channels in this social commerce channel strategy before buying tooling.

Route boundaries

Checkout

Shopify connector: Online store contract; channel refers the sale
WooCommerce connector: Online store contract
Direct tooling: Platform checkout where enabled

Refunds and disputes

Shopify connector: Shop back office, with seller centre checks
WooCommerce connector: Orders return to the dashboard; test the refund path
Direct tooling: Seller centre disputes; retailer owns refunds policy

Data

Shopify connector: App, theme and platform pixels
WooCommerce connector: Plugin settings plus platform events
Direct tooling: Platform pixels and consent tooling

Build and admin

Shopify connector: Channel setup, feed rules, app support
WooCommerce connector: Licence, feed build, dashboard upkeep
Direct tooling: Seller centre setup, feed monitoring, rejection triage

The table is a duty map. Two routes can show the same order in a dashboard and still differ over who authorises a refund.

What each route costs, and the figures nobody publishes

No supplier publishes a comparable, dated price for a whole route; public schedules cover single fees, not the full journey. Ask all three for the same six charge lines, captured on one day.

What each route costs

Current fee schedule, saved with the date it was read.
Platform commission or transaction fee as a percentage of order value.
Connector or extension licence, plus build cost against a fixed scope.
Support tier, including who owns escalation of failed orders.
Weekly staff hours for feed monitoring, rejection triage and refunds.
Exit costexport, teardown and notice period.

Mixed units are how route comparisons drift. One dated quotation per route, same order volume, same scope.

Keep units apart. A platform fee on native checkout is not the same unit as a shop subscription that also runs the retailer's own site.

The England rules that shape the choice

Distance sellers in England work to the Consumer Rights Act 2015 and the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013 on cancellation and refunds.

The route's seller of record carries those duties, so test the refund promise alongside the order flow.

VAT follows the seller, not the tool. Register once taxable turnover passes the threshold; GOV.UK VAT registration sets out the obligations and record keeping.

On data, the ICO's guidance on storage and access technologies covers pixels, tags and similar tools, so compare default and optional collection separately.

Contract terms, delivery promises and refund wording belong in a commercial contract record kept next to the supplier file.

Score evidence before weighting

Set the scale firstdocumented, demonstrated, observed or unverified.
Ask every supplier to run the same five scenariosan ordinary item, a variant, an unavailable product, a rejected record and a reversed order.
Start the clock at the same source change and keep the logs.
Weight the criteria before the demonstrations, then apply the same weights to each route.

Documented means a dated page or binding schedule answers the question, and demonstrated means the supplier completes the agreed scenario. Observed is the retailer's own controlled proof, and a verbal answer stays unverified until recorded.

A deep help centre is not evidence of operational results, and a responsive salesperson earns nothing for a missing function.

Re-run the comparison when four things change

Checkout location moves, for example native selling opens or closes.
Platform policy or fee schedule changes.
Connector support, roadmap or pricing changes.
Data collection defaults change, including new pixels or consent settings.

Track the checkout location signals that would reopen the comparison. Name the unresolved condition, its owner and the deadline.

Common questions

Which route suits a small England-based retailer?

Catalogue volatility matters more than size. Direct tooling fits a narrow catalogue sold in one place; a connector fits a retailer already on Shopify or WooCommerce that wants orders in one dashboard.

Do I need my own VAT registration when selling through a connector?

If taxable turnover passes the threshold, yes, because registration follows the seller. Where a platform acts as marketplace, confirm who is the seller of record for VAT first.

What should I demand before signing?

A dated fee schedule, a fixed-scope build quote and a demonstration of the five scenarios. Answers given only in conversation stay unverified.

When does this comparison go stale?

When checkout location, platform policy, connector support or data collection changes. Keep the decision conditional until the named condition is resolved.