Product feed errors: how to find and fix them step by step
A beginner-friendly guide to diagnosing rejected products, empty fields and wrong formats before you submit your catalog to each ad channel.
Julia Villegas

Product feed errors can keep items out of Google Shopping, Meta, TikTok, Pinterest and other commerce channels even when your online store works perfectly. The fastest way to fix them is to check the catalog in order: access, structure, required fields, price, stock and images. That keeps technical problems separate from advertising policy issues.
What product feed errors are
A product feed is a file, URL or export that contains the data a channel needs to understand your catalog. It usually includes fields such as product ID, title, description, price, availability, product link, image link, brand and category. Ad platforms and commerce channels use those fields to create product listings, catalog ads or dynamic campaigns.
When a platform reports product feed errors, it usually means one of three things: it cannot access the feed, it cannot read the file correctly, or it can read the file but some product data is missing, inconsistent or formatted in a way the channel does not accept.
Not every issue has the same impact:
- Blocking error: the feed or product cannot be processed.
- Warning: the product may remain eligible, but some recommended data is missing or weak.
- Data rejection: the value in the feed is empty, invalid or does not match the landing page.
- Policy restriction: the product, image, copy, destination or category violates a platform rule.
This guide focuses on technical and data errors: empty fields, wrong formats, product links, price, stock and images. Policy reviews are different. Each platform applies its own rules, and those rules should be checked separately.
Google’s product data specification is a useful reference for the core principle: product data should accurately describe the item and match what shoppers find on the landing page. The required attributes can vary by product type, country and destination, so do not assume that one generic feed will work everywhere without adaptation.
Why feed errors happen when your store looks fine
A store can sell products normally and still export a feed that fails in an ad channel. Your storefront, ecommerce platform, inventory system and advertising channels do not always use the same language.
For example, your product page may display “Ships today” as a merchandising message, while a channel expects a structured availability value. Your website may show a correct price, but the feed may export it without currency. Your product image may look fine in the store admin, but the URL sent to the channel may be blocked, redirected or inaccessible outside a logged-in session.
Feed errors also appear when data moves between systems: Shopify, BigCommerce, Tiendanube, an ERP, a PIM, a spreadsheet, a CSV file, an XML file or another feed source. Fields can be renamed, columns can shift, decimal separators can be misread, internal categories can fail to map to channel categories, and product variants can inherit the wrong image, price or availability.
That is why it helps to diagnose from the outside in. First, check whether the channel can reach the feed. Then check whether it can parse the file. Only after that should you inspect individual attributes product by product.
Product feed errors: the right diagnostic order
The most common mistake is to open a long error list and start fixing random products. That can waste hours. If the feed URL is private, it does not matter whether your titles are good. If a CSV column is shifted, hundreds of products may look like they have missing data even though the real issue is file structure.
Use this order instead.
1. Check whether the feed URL is accessible
Open the feed URL in a private or incognito browser window. If it asks for a login, returns an error, times out or downloads an empty file, the channel will probably have the same problem.
Check that:
- The URL is public and stable.
- It does not depend on an admin session.
- It is not expired.
- It does not block external crawlers or systems.
- It returns the actual feed, not an HTML error page.
- The file is not empty.
A frequent beginner mistake is copying an internal admin export URL instead of the public feed URL. Another is using a manual export file that later gets overwritten, moved or deleted.
If the platform cannot download the feed, solve that first. Do not spend time on individual products until the channel can reliably access the file.
2. Validate the file structure
Once the URL works, check whether the file itself is readable. A feed may be CSV, TSV, XML, JSON or another format depending on the destination. The file extension is not enough; the internal structure must also be valid.
For a CSV or TSV, review:
- Whether every row has the same number of columns.
- Whether the header row contains clear field names.
- Whether commas, tabs or semicolons are used consistently.
- Whether product titles or descriptions contain separators that break the row.
- Whether special characters are encoded correctly.
For XML, check:
- Whether tags open and close correctly.
- Whether each product has its own complete item block.
- Whether required fields are placed in the expected nodes.
- Whether special characters are escaped correctly.
Structure problems often create many apparent product errors at once. If a channel suddenly reports hundreds of missing titles, prices or links, the issue may not be that hundreds of products are incomplete. It may be that one column moved, one delimiter changed or one XML tag broke.
3. Review required fields first
Every channel defines its own required attributes. Some fields are common across most product feeds: ID, title, product link, image link, price and availability. Others depend on the product category, market or channel destination, such as brand, GTIN, condition, size, color, gender, age group or category.
For Meta catalogs, for example, Meta provides documentation on catalog fields and formats in its commerce catalog guidance. Google, TikTok, Pinterest and other channels each have their own specifications too.
Prioritize these fields:
- Stable ID: the product identifier should not change if the item is still the same product.
- Useful title: the title should clearly describe the item, not just repeat an internal code.
- Valid product link: the URL should open the correct public product page.
- Accessible image link: the channel should be able to download the image.
- Price and currency: the value should be coherent and formatted as expected.
- Availability: the feed should reflect whether the item can actually be purchased.
The goal is not to fill fields with any available text. A title like “Product 123” may pass a basic validation, but it does not help the channel or shopper understand the item. An ID that changes every week can break continuity for product-level reporting and catalog learning.
If you manage a large catalog, do not try to review everything manually. Start with active products, bestsellers, promoted categories or items that already receive media spend. A product feed manager can help you map, clean and segment catalog data before publishing it to each destination.
4. Compare price, currency and promotions
Price is one of the most common causes of feed rejection. Channels often compare the price in the feed with the price visible on the product landing page. If they do not match, the product may be rejected or flagged.
Review these cases carefully:
- Price is sent without currency.
- Decimal separators are inconsistent.
- The site shows tax-inclusive prices while the feed sends tax-exclusive prices, or the opposite.
- Sale price is sent as regular price.
- Expired promotions remain in the feed.
- Product variants inherit the parent product’s price incorrectly.
- Bundles, multipacks or subscriptions are represented differently in the feed and on the page.
This matters even more during seasonal periods, promotions and markdowns. If you update many prices at once, create rules for the promotion period and double-check both the feed and the landing page. If you are preparing holiday campaigns, the related guide on catalog ads for Christmas explains how feed and creative preparation connect during a seasonal push.
5. Align stock and availability
Stock can mean different things in your ecommerce platform, warehouse system and advertising feed. A warehouse may know exact inventory units. A merchandising team may use internal statuses. A channel usually only needs to know whether the product is available, out of stock, preorder or another accepted value.
Check that:
- Out-of-stock products are not sent as available.
- Discontinued products are excluded from active campaign sets.
- Variants do not inherit availability from the parent product incorrectly.
- Preorder or backorder items use values accepted by the destination.
- Availability in the feed matches the public product page.
TikTok, for example, documents catalog requirements and product attributes in its product catalog overview. The exact values and requirements can vary by destination, so always check the channel specification rather than relying only on internal labels.
One important limitation: the frequency at which you import, update or generate a feed is not the same as the frequency at which each channel downloads and processes it. Even if your feed is updated, the channel may reflect the change according to its own schedule. Do not promise instant synchronization unless the channel itself provides that behavior.
6. Verify product links and images
Images feel like a creative asset, but in a product feed they are also structured data. The image URL must be accessible, stable and related to the product. If the image is blocked, redirected, too small, unavailable or mismatched, the channel can flag the product.
Use a simple image check:
- Copy the image URL from a product with an error.
- Open it in a private browser window.
- Confirm that the image loads directly.
- Check that it shows the correct product.
- Review whether variants need their own images.
- Confirm that the image is not an admin-only asset.
Do the same with product links. A URL with broken parameters, chained redirects or a 404 page can stop a channel from validating the item. The landing page should show the same product, price and availability represented in the feed.
Quick table: cause, test and fix
| Issue reported | Simple test | Common correction |
|---|---|---|
| Channel cannot fetch the feed | Open the URL in a private browser window | Use a public, stable feed URL |
| Many fields appear empty | Check headers, columns and delimiters | Fix structure, separators or field mapping |
| Duplicate or changing IDs | Compare exports across several days | Keep a stable product identifier |
| Price rejected | Compare feed value with landing page | Normalize currency, decimals, tax and sale price |
| Stock does not match the site | Compare feed, store admin and public page | Map the correct availability field or filter items |
| Image is invalid | Open the image URL outside the admin | Send an accessible, product-specific image URL |
| Required attribute is blank | Filter products with empty values | Map the right source field or create a valid rule |
This table is not a replacement for each channel’s documentation. It is a practical way to find the likely source of the issue before you regenerate or resubmit the feed.
Hypothetical example: a store with rejected products
Imagine a fictional home decor store called North House. It sells lamps, rugs and tables, and it wants to advertise them across several channels. When the team uploads its catalog feed, the channel reports rejections related to price, image and availability.
The team starts by opening the feed URL in a private browser window. The file downloads correctly, so the feed is accessible. Then they inspect the CSV structure. The rows and columns are consistent, and the headers look correct. Access and basic structure are not the problem.
Next, they filter products with missing values. They find that some lamps have no brand, and several rug variants do not have their own image. Those products are grouped into a review set.
Then they compare price values in the feed with the public product pages. This reveals the main issue: the store displays tax-inclusive prices, but some feed values come from a promotional field with a different logic. The team also discovers that several sold-out tables are still marked as available because the feed uses an internal merchandising status instead of the real stock field.
The fix happens in three layers. First, they map the correct stock field. Second, they normalize the price sent to the channel. Third, they temporarily exclude products without valid images until the missing image data is completed.
The goal is not to “approve everything automatically.” Each channel still applies its own review. The goal is to make the feed readable, coherent and easier to diagnose.
How to fix product feed errors with AdMotion
If you manage multiple destinations, fixing each feed separately from scratch can become repetitive. With AdMotion, you can connect a store or product file, map catalog fields, normalize data with rules, create product sets and publish channel-specific feeds through Export Channels.
A practical workflow looks like this:
- Connect the catalog source. Use a supported ecommerce store or any product file or feed.
- Map the fields. Match your catalog fields to the attributes required by the destination: ID, title, price, availability, link, image and other relevant fields.
- Create cleaning rules. For example, normalize availability values, complete data from a reliable source or exclude products that do not meet minimum requirements.
- Filter product sets. Separate active items, specific categories, products without images, sold-out items or priority campaign groups.
- Create the channel feed. One catalog can feed several destinations, each with its own format and product set.
- Review errors and warnings. The feed analyzer checks the export against the channel specification so you can identify issues before using the feed.
- Copy the feed URL into the channel. The channel downloads and processes that URL according to its own system and schedule.
This does not guarantee approval, and it is not a universal API submission to every platform. It does reduce repeated manual work when you need separate feeds for Meta, Google, TikTok, Pinterest, Snapchat, Criteo, Microsoft Advertising and other destinations. If channel formats and feed validation are your main bottleneck, review feeds for every channel with a built-in analyzer.
Final check before you resubmit
Before requesting another review or waiting for the next channel fetch, test a representative sample. Include active products, discounted products, out-of-stock items, low-stock items, variants and different categories.
For each sample product, compare the feed with the public landing page:
- Is the ID stable and unique?
- Does the title describe the product clearly?
- Does the product link open the right page?
- Does the image load and match the item?
- Do price and currency match the landing page?
- Does availability reflect what shoppers can actually buy?
- Are the required fields for that channel complete?
If the sample fails, fix the underlying mapping or rule before resubmitting. If the sample passes, group the remaining issues by pattern: category, brand, variant type, promotion, source field or destination format.
What to do this week
- Group errors by type, not by product. Separate access, structure, missing fields, price, stock and image issues.
- Test the feed URL outside your admin. If the URL is not public and stable, fix that before reviewing attributes.
- Build a critical product sample. Include variants, discounted items, out-of-stock products and important categories.
- Separate technical errors from policies. A missing currency is a feed issue; a restricted product is a policy issue.
- Document the rules you change. This helps you reuse them across channels and avoid undoing fixes before the next campaign.
A clean product feed is not about sending more data for the sake of it. It is about sending the right data, in the format each channel expects, while staying consistent with your store. Once you diagnose errors in the right order, a long rejection list becomes a set of manageable fixes.
Frequently asked questions
What is the difference between a product feed error and a policy issue?
A product feed error is about data access, structure or consistency: for example, a broken URL, empty required field, wrong price format or inaccessible image. A policy issue depends on a platform’s rules about products, content, destination pages or regulated categories. They can appear together, but they require different fixes.
Do I need to fix every warning before publishing a feed?
Not always. Blocking errors should come first because they can prevent a product or the whole feed from being processed. Warnings often point to recommended fields or data quality improvements. Still, they are worth reviewing because better structured product data helps channels understand your catalog and can prevent future issues.
Why does the feed price not match my online store price?
Price mismatches can come from tax settings, currency, sale price logic, variant inheritance or update timing. They also happen when the feed uses an internal field that is different from the price shown on the public product page. Always compare products with and without promotions before resubmitting.
Sources
- Especificación de datos de producto de Google — Google
- Feed Manager de AdMotion — AdMotion
- Export Channels de AdMotion — AdMotion
Related posts

Product feed format: CSV, XML or Google Sheets?
Choosing between CSV, XML and Google Sheets is not just a technical preference. It depends on catalog size, update frequency, team workflow and the ad channels you need to feed.

Feed rules: how to clean titles, prices and descriptions without editing products one by one
Feed rules help you fix repetitive catalog data issues without editing every product manually. Learn how to remove HTML, normalize prices and improve titles with a safe, reviewable workflow.

Product titles: how to clarify variants without stuffing your feed
Product titles help Google Shopping, Meta and other channels understand what each catalog item is. Learn a simple brand/type/attribute pattern to describe variants clearly without artificial keyword stuffing.