Whose job is the product feed? Owning it when five people touch it

The product feed should have one owner who is accountable for it as a whole, usually whoever runs ecommerce or the online store, even when other people supply parts of it. Product data comes from whoever manages the catalog, prices and stock from operations, campaign fields such as custom labels from whoever runs ads, and the connection itself from a developer or an app. Without a named owner, feed problems sit in Merchant Center until sales drop.

What this comes down to

  • Name one person accountable for the feed as a whole, even if several people supply its data.
  • Each kind of data has a natural owner: catalog data, prices and stock, campaign fields, and the technical connection.
  • Feed problems without an owner go unnoticed, because Merchant Center flags them in a tab nobody is responsible for reading.
  • In a small store one person holds several roles; the point is to write them down, not to hire for them.

SellerSort Team · Updated

Who supplies what

Who owns each part of the product feed
Part of the feedNatural ownerExamples
Product dataWhoever manages the catalogTitles, descriptions, images, identifiers, categories
Commercial dataOperations or whoever sets pricesPrice, sale price, availability, shipping
Campaign fieldsWhoever runs Google AdsCustom labels, and how product groups use categories
The connectionA developer, or the app that syncs the storeFetch schedule, file format, errors on upload
The feed as a wholeOne named personReading Merchant Center issues and routing each one
A feed with five contributors and no owner is a feed nobody is watching.

Why one person has to own the whole

Each contributor can do their part perfectly and the feed can still fail. The PPC manager sees disapprovals but cannot change prices. Operations changes a price on the site but does not know the feed only refreshes weekly. Google’s help page for mismatched prices says such a product may be disapproved, and nobody is watching the tab where that shows up.

The owner’s job is not to fix everything. It is to read the Needs attention tab in Merchant Center on a schedule, send each issue to the person who owns that data, and check that it was fixed.

In a small store

If you are a team of one or two, every row of the table is you. That is fine. Writing it down still helps, because the risk in a small store is not confusion between people; it is the feed being nobody’s task this week. Put a fifteen-minute Merchant Center check in your calendar and treat it like invoicing.

With an agency or freelancer

Agencies often run the ads and sometimes a supplemental feed. That makes the boundary important: if the agency changes categories or titles in a supplemental source, and your team changes the same fields in the store, the two copies drift. Agree in writing which fields each side owns.

The guide on where to keep categories covers the two-copies problem in detail, and the hiring guide helps if you are deciding whether to bring someone in.

A one-page ownership note

  1. Name the feed owner, and a backup for holidays.
  2. For each row of the table above, write who supplies that data.
  3. Make sure the owner has access to Merchant Center and receives its notifications.
  4. Set a weekly time to read the Needs attention tab.
  5. Record where categories live and who changes them; the Bulk Mapper output makes a good backup of that data.

Questions

Who is responsible for the product feed in an ecommerce business?

One named person should be accountable for the feed as a whole, usually whoever runs the online store. Catalog, pricing, advertising and technical staff each supply parts of it.

Should the PPC agency manage our product feed?

An agency can own campaign fields and even a supplemental feed, but agree in writing which fields they change and which your team changes, so the store and the feed do not drift apart.

How often should someone check Merchant Center?

Weekly is a sensible minimum for the Needs attention tab. Google also marks products as needing an update 30 days after their last update, so a feed that stops refreshing shows up there.