Foundations
Part of Shopping feeds basics: the fields, channels and marketplace fees behind a UK catalogue
How to choose a shopping feeds business model for UK retailers
Managed agency, self-managed software, marketplace-native and revenue-share shopping feeds business models weighed on cost, control, risk and contract terms.
What to take away
Shopping feeds business models describe who builds, pays for and maintains the product data a retailer sends to Google Shopping, Amazon, eBay, Meta and other marketplaces and search platforms.
- Most UK retailers choose between managed agency support, self-managed software, marketplace-native tools and revenue-share deals.
- Each shifts cost, control and risk between retailer and supplier.
- Catalogue size, data skills and channel count decide which one fits.
- Compare total cost per SKU per month, not headline fees alone.
Why the model matters more than the tool
A feed tool is one part of the deal: the model decides who fixes a rejected product, who pays for extra channels and who owns the data when the contract ends. A cheap quote can become expensive.
Feed accuracy affects trade, because online selling runs through UK businesses. Read the wider UK market guide before comparing models, as your channel mix shapes the right one.
Managed agency model
An agency builds and maintains the feed. You supply product data; it handles mapping, category rules and error fixes. Fees are usually a monthly retainer plus setup. A team paying £600 a month for a 2,000-SKU catalogue pays about 30p per SKU monthly.
Managed agency cost example
- £600monthly retainer
- 2,000SKUs in catalogue
- 30pcost per SKU monthly
The attraction is speed and specialist help. The drawback is dependence on the agency for every change; response times vary. Ask for a named contact and a written service level for feed errors.
Self-managed software model
You licence product feed software and run the feed yourself. Costs fall per SKU at scale, but your team carries the workload. It suits retailers with clean product data and someone who understands taxonomy and attributes.
Google Merchant Center can update some product information automatically, as its guidance on automatic product information updates explains. That cuts manual work but does not replace data governance. Budget for training and a weekly feed check.
Marketplace-native and revenue-share models
Some channels, Amazon and eBay among them, offer free feed tools and take commission on sales instead, which lowers fixed cost and suits retailers testing a new marketplace. The trade-off is weaker control over presentation and limited support when listings underperform.
Revenue-share deals make cross-channel comparison difficult, because the true cost appears only after sales. Track commission, payment fees and returns separately, then test the blended figure against a software licence.
The four models side by side
| Model | Who runs the feed | Cost shape | Control | Main risk |
|---|---|---|---|---|
| Managed agency | An agency, working from your product data | Retainer plus setup | Shared; the agency holds the detail | Dependence on one supplier |
| Self-managed software | Your team, on licensed software | Licence plus team time | Yours | Skills and workload |
| Marketplace-native | The channel's own tools | Free tooling, commission on sales | Limited; the channel sets the rules | Weaker control over presentation and support |
| Revenue-share | The supplier, paid out of sales | Rises with sales | Shared, weighted to the supplier | Blended cost is hard to compare |
Read the table down the columns. The model that looks cheapest on fixed cost rarely leads on control or on exit terms.
What to check before choosing
Use this checklist to choose between shopping feeds business models. It applies to UK-based retailers selling into UK and overseas channels.
- Total monthly cost per SKU, including setup, licence or retainer fees and channel add-ons.
- Who owns the feed data, and whether you can export it on exit.
- Named support contact and guaranteed response time for feed errors.
- Coverage of the channels you actually useGoogle Shopping, Amazon, eBay, Meta and anything else on your roadmap.
- Attribute validation and image checks built into the workflow.
- Contract length, notice period and price review clauses.
- Reporting on impressions, clicks and conversion by channel.
Weigh the criteria before you score
A comparison is only as good as the criteria behind it. List what matters to your business — data control, speed to launch, total monthly cost per SKU, channel coverage, support response and exit terms — then give each one a weight that reflects what a failure would cost you.
Score each of the four models against every criterion, multiply each score by its weight and add the totals. Run it once before you ask for quotes, with the agency example above standing in for the managed model and the licence and commission shapes from the table for the rest, then rerun it with real setup fees, licence tiers, commission terms and notice periods.
If a model wins only on price, check what you have given up in control and exit terms before you sign.
Where the growth is
Model choice affects how quickly you add channels: agencies launch marketplaces in weeks; self-managed setups take longer but cost less at volume.
ONS statistics on internet sales and ecommerce adoption show how widely online selling is embedded among UK businesses, so build the channel list in any comparison from the channels your customers actually use. Retailers planning to expand should weigh the commercial opportunities for UK retailers against the operational cost of each model.
Common questions
Which model suits a small catalogue under 500 SKUs?
Marketplace-native tools or a low-cost software licence usually work best; agency retainers spread poorly across few products. Keep the arrangement flexible so you can move to a managed service if volume grows.
Can I mix models across channels?
Yes. Many retailers run a self-managed feed for their main website and a managed service for complex marketplaces. The risk is duplicated data, so agree one source of truth.
How long should a contract run?
Three to twelve months is common. Shorter terms cost more per month but let you change supplier if feed quality disappoints. Avoid auto-renewal clauses without a clear notice window.
What is the biggest hidden cost?
Data cleanup. Poor titles, missing attributes and wrong categories cause rejected products regardless of model. Budget time for fixing source data before comparing quotes.
