Operations
Plan shopping feeds operations before peak season
A practical guide to shopping feeds operations: ownership, image and crawl rules, service levels, cross-border data and delivery checks for UK sellers.
What to take away
- Name one accountable owner and a deputy for the catalogue that reaches every channel.
- Split the work into five jobsownership, data quality, images and crawl access, cross-border fields, and service levels.
- Most peak failures trace to four causesa broken image link, a crawl block, a stale price or an unchanged customs field.
- Check daily for price and stock, weekly for images and attributes, quarterly for structure.
- Budget the hours, not just the licence.
Output, owner and platform choice
The deliverable is a catalogue that is complete, valid and live on each channel by an agreed date. Before choosing software, write down who answers when a product fails to appear. That answer sets the checks, the rota and the cost.
Describe the promise simply: every active SKU live, priced correctly, with an image that loads. Feed management tools such as Channable, DataFeedWatch and Feedonomics do similar work, so operating discipline decides the result.
If you sell on Shopify, the product feed plugin choices for Shopify matter as much as the feed platform behind them.
Five jobs and their owners
| Job | Owner | Covers | Cadence |
|---|---|---|---|
| Catalogue | Merchandising | Master data and GTINs | Weekly |
| Channel | Marketplace manager | Error queues and appeals | Daily |
| Image | Studio or content | Asset library and URL health | Weekly |
| Compliance | Finance or legal | Duty, VAT and returns fields | Monthly |
| Service levels | Operations lead | Targets and reporting | Quarterly |
Small teams can merge catalogue and channel work. A blank row is the mistake that hurts.
Channel error queues are not interchangeable
Google Merchant Centre disapprovals happen when the price disagrees with the landing page, a GTIN is missing or mismatched, or the landing page fails to load.
Meta Commerce Manager rejects items when a required field such as price or availability is missing, or the product URL will not load. Amazon checks GTIN validity and category attributes, and Bing Shopping accepts feeds built close to Google's structure.
Keep a separate error log for each channel, because one combined queue hides the pattern. Fixing Google Merchant Centre disapprovals covers the common causes.
The morning check as a numbered routine
The morning check
- Open each channel's error report and list only new items.
- Compare a sample of live prices against the website.
- Confirm availability flags against warehouse stock.
- Test five image URLs for a 200 response.
- Escalate anything touching price or stock before the next upload.
Images and crawl access: the quiet failures
Images fail more often than data. A feed can pass validation and still show a placeholder because an image URL returns a 404.
Google supports extra images per item through the additional_image_link attribute, which shows packaging, scale and detail. Each extra image is another URL to keep alive, so run the link check with the feed check.
Image and crawl checks
- Every image URL returns a 200 response
- No redirect chains on image URLs
- File size and format accepted by channel
- robots.txt rules match expectations
- Re-test after any site migration
Crawl rules cause the other quiet failure. A line written to hide a staging folder can block the path holding your product images. For example, Disallow: /media/ blocks /media/large/ while leaving /images/ open, so the feed validates and the gallery stays empty.
The fix is to narrow the rule to the staging folder or add an Allow line for the catalogue path, because the more specific rule wins. Google's robots.txt specification explains the matching order.
Cross-border fields at listing, not at the order
Country of origin, commodity codes, duty treatment and the returns address must be right before a product goes live. Wrong data becomes a held parcel or a customs query.
GOV.UK's guidance on buying and selling outside Great Britain is the starting point before you add a country. Northern Ireland is the trap, because goods movement rules there differ from the rest of the UK.
Example: costing feed hours
Method: count people and hours a week, multiply by working weeks, then apply a loaded hourly rate that includes employer costs.
Costing feed hours
- People on feed work
- 2
- Hours per person each week
- 15
- Working weeks
- 40
- Hours a year
- 1,200
- Loaded hourly rate
- £20
- Labour cost a year
- £24,000
Substitute your own hours and rate. The figures are illustrative, not benchmarks.
Automation that removes four hours a week pays for itself against the labour line, not the licence. This comparison of UK Google Shopping CSS partners with fees and service levels shows what bought-in help costs.
Common questions
How often should a feed be checked?
Daily for price and availability, weekly for images and attributes, quarterly for structure.
Who should own shopping feeds operations?
One named person, usually in ecommerce operations or merchandising, plus a deputy. The owner is accountable for the catalogue being correct.
What causes most feed errors at peak season?
Broken image links and stale prices, because both change outside the feed team's control. Comparison against the website catches them.
In this guide
- Why a shopping feeds operating workflow beats firefightingHow to build a shopping feeds operating workflow with named owners, attribute checks, crawl budgets and a weekly release rhythm that survives peak trading.
- Nine checks that keep shopping feeds quality in shapeA shopping feeds quality checklist for catalogue teams: titles, identifiers, security, ownership and the audit trail that keeps multichannel orders flowing.
- Shopping feeds team roles explained for data and sourcesA practical look at shopping feeds team roles, covering who owns product data, source systems and compliance checks across catalogue operations.
- When to trust a shopping feeds launch review and its sourcesHow to read a shopping feeds launch review: what gets assessed, what vendor claims are worth, and which independent sources support a decision.
