
Tools and providers
Part of Before you sign a shopping feed contract, check these tools and providers
How to score shopping feeds software for catalogue teams
Plan shopping feeds software selection for catalogue teams: scoping, channel and attribute fit, data quality checks, integration, pricing models and scoring.
What to take away
- Feed platforms have moved from bulk upload tools to workflow products, so selection now turns on data quality controls.
- Newer ad surfaces such as TikTok catalogues and YouTube video campaigns change what a feed must carry, including video assets and localised product data.
- Score vendors against your own catalogue before you see a demo, and check data protection claims against the ICO checklist.
- Pricing differs sharply, from per SKU to per channel or per order, so model cost at your realistic SKU count.
Define the job before you shortlist
Start with the tasks your team performs weekly. For example, a retailer with 2,000 SKUs across three channels needs different tooling from one running 40,000 listings.
Define feed outputs and owners
- List weekly team tasks
- Name required outputsGoogle, TikTok, Meta
- Record missing attributes causing disapprovals
- Assign owner per output
- Require separate roles and approval step
Write down the outputs you need: a Google Merchant Centre feed, a TikTok catalogue, a Meta catalogue, and possibly a price comparison file. Missing attributes cause disapprovals that cost revenue quietly.
Record who owns each output. If merchandising owns titles and marketing owns images, the tool must support separate roles and an approval step.
Channel fit and attribute coverage
Channel coverage is the first filter. Check that the vendor supports the destinations you actually sell on.
Channel fit and attribute coverage
- Confirm vendor supports your exact destinations
- TikTokproduct identifiers and frequent availability
- Video placementslanding page URLs match ads
- Map category taxonomy to Google product categories
- Flag gaps that create recurring manual work
TikTok catalogues need product identifiers and availability data that refresh often, since how to create a catalogue in TikTok Ads Manager sets out the structure advertisers must populate. Stale feed data drags performance down.
Video-led placements add another requirement. Understanding video ad formats on YouTube helps you judge whether a vendor can supply the product data those campaigns need, including landing page URLS that match the ad.
Ask each vendor to map your category taxonomy to their supported Google product categories. Gaps create recurring manual work.
Questions to ask on data quality
How does the tool detect and fix missing GTINs, invalid prices or broken image links? Request a report, not a promise.
Questions to ask on integration
Which commerce platforms and PIM systems does it connect to natively, and what happens when a sync fails overnight?
Integration, workflow and compliance
Integration depth decides how much manual work remains. A native connector to your ecommerce platform beats a scheduled CSV import, because it narrows the gap between a price change and a feed update.
Check the failure path. If a sync breaks at 2am, who is alerted, and can the previous feed version be restored? Ask for support hours in writing, including bank holidays.
If you run email or SMS alongside feeds, the data you hold must meet consent rules. The ICO direct marketing checklist is a sensible reference when reviewing how a vendor handles opt-in records.
For a wider view of the market before you commit, the tools and supplier guide for 2027 sets out the categories of vendor you will encounter.
Pricing models and total cost
Vendors price per SKU, per channel, per order or by monthly tier. A per-SKU model punishes long catalogues with low sales; a per-order model punishes growth.
For example, a team paying £400 a month on a tier covering 10,000 SKUs should ask what the same tier costs at 25,000 SKUs, in writing.
Add implementation fees, feed template build, and any charge for extra channels. These often exceed the first year of subscription.
Scoring and comparison
Score vendors on a fixed scale before demos, and keep the scores. The table below shows a workable structure with illustrative weightings.
Weight
- Channel coverage
- 20%
- Data quality tools
- 20%
- Integration
- 15%
- Workflow and roles
- 15%
- Pricing at scale
- 15%
- Support
- 15%
What to check
- Channel coverage
- Your exact destinations
- Data quality tools
- Validation, error reporting, auto-fixes
- Integration
- Native connectors, sync frequency, failure alerts
- Workflow and roles
- Approvals, audit trail, permissions
- Pricing at scale
- Cost at 2x and 5x SKU count
- Support
- Hours, response times, named contact
Run a scored trial with your own data. A vendor that performs well on a clean sample file may struggle with your real catalogue, which holds duplicates and incomplete attributes.
Before signing, confirm ownership and exit terms. The vendor due diligence checklist covers contract traps worth reviewing first.
Common questions
How long should a selection project take?
For a catalogue under 10,000 SKUs, plan for four to six weeks: two weeks scoping, two weeks trials, then scoring and negotiation. Larger catalogues need longer for integration testing.
Should we choose one tool for all channels?
Usually yes, because a single source of truth reduces reconciliation work. Split only when a channel has unique data needs no single vendor handles well.
What is the biggest selection mistake?
Choosing on demo polish. Demos use clean data. Insist on a trial with your own feed export, including your worst-performing category.



