Skip to content

Product feed management for agencies: a practical guide

A beginner-friendly workflow for separating clients, permissions, reusable rules and channel checks without sharing passwords or mixing brands.

J

Julia Villegas

· 9 min read · 272 views
Color-coded folders and product cards for agency product feed management

Product feed management for multiple agency clients should not rely on scattered spreadsheets, shared logins or last-minute manual edits. If every client has its own catalog, brand, channels and internal stakeholders, you need a repeatable workflow that separates projects, controls permissions and lets your team reuse feed rules safely.

What product feed management means for an agency

A product feed is a structured file or URL that contains catalog data: product ID, title, description, price, availability, image link, brand, category and other attributes required by advertising or commerce platforms. Meta, Google Shopping, TikTok, Pinterest and Microsoft Advertising do not all read catalogs in exactly the same way, so one source catalog often needs several adapted outputs.

For example, Google documents required and optional fields in its Merchant Center product data specification, while Meta explains how businesses use catalogs for ads and commerce surfaces. The principle is simple: platforms need clean, structured data before they can use products in catalog campaigns, dynamic ads or shopping placements.

In an agency, managing feeds does not just mean “uploading a file”. It usually includes:

  • Receiving product data from stores, files or existing feeds.
  • Mapping fields that have different names across clients.
  • Cleaning titles, categories, prices, availability or image links.
  • Creating different feed outputs for each channel.
  • Filtering product sets by campaign, market, stock, season or business rule.
  • Reviewing errors and warnings before the feed is used in a platform.
  • Coordinating responsibilities across account management, paid media, data and creative teams.

The challenge grows when this workflow repeats across several clients. One online store may have a simple catalog. Another may have thousands of variants. Another may sell in multiple countries. Another may update promotions every week. Without structure, a small catalog change can slow down campaign work or create confusion between accounts.

The safest operating model is to keep one project per client, with separate catalog data, brand assets, rules, product sets and feed URLs. Then the agency can apply a common way of working without mixing client-specific decisions.

Why product feed management matters for multi-client agencies

In catalog advertising, the feed sits at the intersection of several teams. The client owns the product information. The agency configures campaigns. The feed specialist prepares channel outputs. Creative teams may need product images, prices or branded templates. Someone must validate that the final feed is ready to be added to each platform.

When agencies do not define a process, the same problems appear repeatedly:

Problem What usually happens Risk for the agency
Shared passwords Several people use the same client login Poor traceability and operational risk
Mixed feeds Old files are reused without separating brands or markets Wrong data can end up in the wrong client workflow
Manual rules Each specialist fixes the feed in a different way Changes become hard to maintain or audit
Late validation Errors are found only after uploading the feed Campaign delays and rejected products
Single-person dependency Only one team member understands the setup Work stops when that person is unavailable

The answer is not simply to add more tools. The important part is to define a repeatable operating model: what data comes in, who can change it, which rules apply, how the output is checked and who approves the feed before it is used in campaigns.

Agencies should also separate two timing concepts that are often confused. One is how often the catalog is imported or updated in your feed management workflow. The other is how often each advertising or commerce platform downloads, processes or reviews the feed URL. You should not promise instant synchronization inside the channel, because each platform controls its own refresh, review and approval processes.

How to manage product feeds with projects, permissions and reusable rules

A practical agency workflow starts before anyone edits a title or filters a product. The key is to turn client onboarding into a checklist. That way, your team avoids unnecessary access requests, reduces back-and-forth and documents decisions before campaigns depend on them.

1. Create a separate project for every client

Each client should have its own workspace. That project should contain its data sources, brand settings, feed rules, product sets and output feeds.

This prevents common mistakes such as:

  1. Applying one client’s rule to another client’s catalog.
  2. Using the wrong brand treatment in product creatives.
  3. Confusing feed URLs between advertising accounts.

Separation matters even more when your agency works across verticals. A fashion retailer, a furniture store, a travel brand, a real estate advertiser and an automotive business may all use catalogs, but they do not need the same attributes, formats or validation checks.

2. Assign permissions by role, not by urgency

Agency work involves different profiles: account managers, paid media specialists, feed specialists, designers and project leads. They do not all need to edit the same parts of the workflow.

A simple permission model could look like this:

  • Account management: view status, coordinate with the client and confirm business decisions.
  • Feed specialist: connect sources, map fields, create rules, build product sets and validate outputs.
  • Paid media: review channel-specific feeds and use feed URLs in platforms.
  • Creative team: review brand consistency, product images and templates when relevant.
  • Leadership: get visibility without editing day-to-day settings.

The goal is not to block the team. It is to reduce accidental changes and avoid shared passwords. Whenever possible, every team member should use their own user access with the permission level required for their work.

3. Document where the catalog comes from

Before cleaning or transforming product data, the agency needs to know where that data starts. A client might connect an ecommerce store, send a CSV file, share an XML feed or provide an existing feed already used in another platform.

During onboarding, document at least:

  • Catalog source: store, file or feed.
  • Client-side owner of the product data.
  • Available fields and required fields by channel.
  • Expected update frequency.
  • Markets, languages and currencies.
  • Business rules: excluded products, priority categories, sensitive brands, seasonal ranges.
  • Planned channels: Meta, Google Shopping, TikTok, Pinterest, Criteo, Microsoft Advertising or others.

This document does not need to be complex. It just needs to help any authorized team member understand how the project is fed and which decisions have already been made.

4. Map fields before creating rules

Mapping means matching fields from the source catalog to the fields used in the working feed or final channel feed. One client may call the product identifier sku, another may call it item_id. One may use sale_price, another may use discounted_price.

If mapping is weak, every rule built on top of it becomes fragile. Before filtering or transforming data, make sure these base fields are clear:

  • Unique product ID.
  • Product title.
  • Description.
  • Price and sale price, if available.
  • Availability or stock.
  • Product URL.
  • Image URL.
  • Brand.
  • Category.
  • Relevant variants such as size, color or material.

Once mapping is organized, your agency can build safer reusable rules: exclude products without images, normalize availability, split categories by campaign, or create seasonal product sets.

5. Reuse rules, but validate them client by client

A reusable rule is an instruction that can be copied and adapted across projects. For example:

  • If a product has no image, exclude it from the campaign set.
  • If stock equals zero, mark the product as unavailable.
  • If the category contains “outlet”, send it to a specific feed.
  • If the brand is missing, use a client-approved fallback value.

Reusable rules save time, but they should not become blind copy-paste. Two clients may use similar category names with different meanings. One client’s “outlet” might be always-on clearance; another’s might be a seasonal campaign. Always review rules inside the client project before activating them.

In AdMotion, agencies can work with projects and permissions, connect stores or files, map fields, normalize data with rules, filter product sets and generate feed URLs. Copyable rules help transfer learnings across clients while keeping catalogs and brands separate. If your team manages several accounts, the agency solution is the most relevant place to start.

Fictional example: three clients, three channel setups

Imagine an agency with three ecommerce clients:

Element Client A Client B Client C
Business type Fashion store Home decor retailer Electronics brand
Source Shopify CSV file XML feed
Main sets Sale, new arrivals, outlet Sofas, lighting, textiles High stock, launch, accessories
Channels Meta and Google Google and Pinterest Meta, Google and Microsoft
Main validation focus Promotions and sizes Images and variants Stock and price

The agency uses the same operating model, but it does not mix data. It creates a separate project for each client, assigns permissions by responsibility and documents who validates each output.

For Client A, the feed specialist creates a rule that separates discounted products into a sale set. For Client B, the team prioritizes products with valid main images, because visual quality matters for discovery placements. Pinterest, for example, provides guidance for retailers using catalogs and data sources. For Client C, products without available stock are filtered before the agency prepares channel feeds.

The agency is not using one rigid template for every client. It is using a common process with client-specific decisions. That difference is what makes the workflow scalable.

How to set this up with AdMotion

The following workflow shows how an agency can manage catalog work in a structured way without relying on shared files as the source of truth.

  1. Connect the catalog source. Use the client’s store, a product file or an existing feed. The data belongs to the relevant client project.
  2. Map the fields. Match source fields to the working catalog fields: title, price, availability, image, brand, category and other attributes.
  3. Normalize data with rules. Clean values, transform fields and correct inconsistencies. In the Feed Manager, rules can also be written in natural language and reviewed before being applied.
  4. Create product sets. Filter subsets for campaigns, channels, seasons or business conditions: sale products, in-stock products, priority categories or gift ranges.
  5. Generate channel feeds. One catalog can feed several outputs, each with its own format and product set. With Export Channels, feeds can be prepared for Meta, Google Shopping, TikTok, Pinterest, Snapchat, Criteo, Microsoft Advertising, Thribee, ChatGPT or a custom channel.
  6. Review errors and warnings. The analyzer checks the feed against the channel specification. This helps catch issues before the URL is added to the platform, but it does not guarantee final approval by that platform.
  7. Copy the URL into the channel. The feed URL is registered in the relevant advertising or commerce platform. Remember that the feed URL and the platform’s processing schedule are not the same thing.

If a client also needs product-level creatives, you can connect the catalog to the Templates Editor to generate images using catalog fields such as product photo, title, price and brand in 1:1, 4:5, 9:16 and 16:9 formats.

For a seasonal application of the same logic, see the related guide on catalog ads for Christmas, which applies product sets, pricing and creative preparation to a specific retail moment.

Onboarding checklist to avoid shared passwords

Before activating the first feed for a client, use a simple checklist. You can adapt this structure to your agency’s workflow:

  1. Client basics

    • Project name.
    • Client-side catalog owner.
    • Agency campaign owner.
    • Markets and languages.
  2. Catalog source

    • Connection type: store, file or feed.
    • Available fields.
    • Expected update frequency.
    • Person who validates product changes.
  3. Channels and goals

    • Planned platforms.
    • Product sets needed by campaign.
    • Required fields by channel.
    • Target activation date.
  4. Internal permissions

    • Who can edit rules.
    • Who can review feeds.
    • Who validates with the client.
    • Who copies the URL into each platform.
  5. Final validation

    • Products have usable images.
    • Prices are coherent.
    • Availability is correct.
    • Categories have been reviewed.
    • Errors and warnings are documented.

This checklist reduces repeated conversations and keeps the agency from depending on improvised access. It also helps explain to the client what is needed and why.

Common mistakes in multi-client feed management

The first mistake is using one file as the “template” for every client. It may look efficient, but it increases the risk of carrying over fields, filters or rules that belong to another account.

The second mistake is validating only at the end. If the team waits until the feed is uploaded to discover missing images, broken categories or inconsistent availability, there is less time to fix the issue. Review from the mapping stage, then check the final output again.

The third mistake is mixing brand and catalog logic. In catalog campaigns, data and creative are connected. A wrong price, outdated availability or incorrect brand treatment can create client-facing problems even if the campaign is technically active.

The fourth mistake is promising more than the agency or tool controls. A feed management platform can generate feeds, check outputs and provide updated URLs. The channel still controls its own download, processing, review and approval flow.

Finally, avoid keeping all knowledge in one person’s head. If each client project is documented, any authorized team member can understand what was done, what rules exist and what still needs approval.

What to do this week

  1. Audit your active clients. List each catalog source, the channels it feeds and the person responsible for every step.
  2. Separate projects and permissions. Check that every client has its own workspace and that the team is not using shared access for convenience.
  3. Choose three reusable rules. Start with simple rules such as excluding products without images, filtering out-of-stock items and creating a promotion set.
  4. Review one channel output. Pick a Meta, Google or Pinterest feed and check required fields, images, prices and availability before touching campaigns.
  5. Update your onboarding checklist. Add catalog source, validation, permissions and the person responsible for adding the feed URL to each platform.

Managing product feeds in an agency becomes easier when every client has a separate project, clear permissions and documented rules. Build the process during onboarding, and each catalog can keep its own logic, brand and channel outputs without creating unnecessary friction.

Frequently asked questions

What is a product feed in an agency context?

A product feed is a file or URL containing a client’s catalog data, such as titles, prices, images, availability, brand and categories. Agencies adapt that data for advertising and commerce channels. Good feed management includes mapping fields, cleaning data, creating product sets, checking errors and keeping each client’s workflow separate.

Why should an agency create one project per client?

One project per client keeps catalogs, brand assets, rules, product sets and feed URLs separate. This reduces the risk of applying the wrong rule, mixing outputs or using another client’s creative logic. It also makes permissions easier to manage and helps the team document decisions for each account.

Does a feed URL update instantly inside every channel?

Not necessarily. A feed management system can generate an updated URL when the feed is downloaded, but each platform has its own schedule for reading, processing and reviewing that data. Agencies should distinguish between updating the catalog source and the moment when a channel applies those changes.

Sources

  1. AdMotion para agencias — AdMotion
  2. Feed Manager de AdMotion — AdMotion
  3. Export Channels de AdMotion — AdMotion
Share:
J

Written by

Julia Villegas

Performance Marketing

Julia Villegas works in performance marketing at AdMotion.

Related posts