Product feed management that fixes the data first.
You find out about disapprovals when Merchant Center turns red, not before. The feed is one price change behind because someone has to remember to re-export it. And you are paying $30 to $300 a month for a feed app that ships whatever it is given and has no idea the data is incomplete. Apimio runs your product feed management from the catalog itself (Advanced and Enterprise plans): it shows you which products Google, Meta, Pinterest, TikTok or Bing will reject before you publish, maps your categories to Google's taxonomy, hosts every feed at a stable URL that refreshes on schedule, and pulls the real rejections back from Merchant Center so you can see prediction and outcome side by side.
Product feed management by the numbers
Only figures that hold up in the product. No invented uplift percentages.
The feed problem is almost always a data problem
Ask anyone who has managed a Google Shopping feed for a Shopify store what goes wrong. It is rarely the XML. It is what went into it.
What running feeds looks like today
What Apimio does instead (Advanced and Enterprise plans)
You find out about disapprovals late
Forty products go dark because a GTIN is missing, a title runs past 150 characters or the landing-page price no longer matches the feed. Nobody knows until someone opens Merchant Center diagnostics, by which point the campaign has been spending against a shrinking product set for a day or more.
Predicted rejections before you publish
Pre-publish diagnostics run a capped set of the rules that actually cause rejections — required fields per channel, title length, availability vocabulary, image minimum dimensions, price and currency mismatch, GTIN presence — and list every affected product with a click-through to fix it. A stale-feed badge tells you when a feed has not refreshed on schedule.
The feed is one price change behind
The feed is an export somebody re-uploads when they remember. Prices moved on Tuesday for a sale; Google is still reading last week's file. Ads show one number, the product page shows another, and that mismatch is itself a disapproval reason.
A hosted URL that refreshes itself
Each feed lives at a stable, tenant-scoped URL that Merchant Center or Commerce Manager polls. It regenerates on the cadence you set, from the live catalog, so a price change in Apimio is in the feed at the next refresh without anyone exporting anything.
You pay a feed app to ship a mess
A standalone feed app costs $30 to $300 a month and does exactly what it says: it moves your data to the channel in the right shape. It has no opinion on whether the data is complete. Garbage in, disapproved products out, plus a second invoice.
One subscription for fixing and feeding
The catalog that holds and scores your product data also serves the feeds. You are not paying a PIM and a feed app to do two halves of one job, and the two never disagree because there is only one source.
Meta rejects the category you typed
Meta, Pinterest and TikTok require a product category from Google's taxonomy, not the free-text “Sofas” your Shopify collection uses. Free text fails validation, so someone hand-maps hundreds of categories in a spreadsheet, once per channel, and again every time the range changes.
Your categories mapped to Google's taxonomy
Map each of your categories to a google_product_category once. Every template that needs it — Meta, Pinterest, TikTok, Bing, Google itself — reads the same map, so the category rejections stop and the spreadsheet retires.
Wholesale pricing lives next to a public feed
When trade price, MOQ and case pack are ordinary fields on the product, every export is a chance for them to end up in a public XML file. It only has to happen once for a dealer to see it.
Wholesale fields structurally excluded
Trade price, MOQ, case pack and lead time are a separate internal attribute class in Apimio. They are excluded from every feed by architecture, not by a checkbox someone could untick.
What a product feed manager has to do — and how Apimio does each part
Six jobs. A feed app does the first and the fifth. Apimio does all six from the catalog (Advanced and Enterprise plans).
Channel templates on one engine
Google Shopping XML is the first-class format. Meta catalog feeds for Facebook and Instagram, Pinterest, TikTok and Bing Shopping are templates on the same engine, mapped from the same product record, so a title fix lands in every channel at once. Amazon and Walmart are produced as importable TSV files in each marketplace's layout — files you upload, not live API connections.
- Google Shopping XML, Meta, Pinterest, TikTok, Bing — five templates, one engine
- Amazon and Walmart as importable TSV files, not API syncs
- Price-comparison formats from the same catalog
- Every template reads one canonical record, so channels never disagree
Google product-category taxonomy mapping
Meta, Pinterest and TikTok validate the product category against Google's taxonomy and reject free text. Apimio lets you map your own categories to google_product_category values once, then every feed that needs the field inherits the mapping. It maps your categories; it does not guess a category for each product with AI.
- Your category → Google taxonomy value, mapped once
- Shared by every channel template that requires a category
- Stops the “invalid product category” rejection class at the source
- You stay in control of how products are classified
Pre-publish diagnostics
Before a feed goes live, a feed health panel lists which products the channel will reject and why: missing required fields for that channel, titles over the limit, availability values outside the accepted vocabulary, images under minimum dimensions, price or currency mismatches, missing GTINs. Each finding links to the product so you fix it there, not in the file. It is a capped set of the rules that actually cause rejections, not a re-implementation of the whole Google spec.
- Required fields per channel, title length, availability vocabulary
- Image minimum dimensions, price/currency mismatch, GTIN presence
- Clickable fix list — every finding opens the product
- Stale-feed badge when a refresh has not run on schedule
Real rejections pulled back, side by side
Connect Google Merchant Center or Meta Commerce Manager and Apimio pulls each item's actual rejection status back onto the product, next to the issue the diagnostics predicted. You see what you expected to fail, what did fail, and the gap between the two — which is where the rules you did not know about live. Retrieval is time-boxed per item and requires you to connect the account.
- Item-level rejection status from Merchant Center and Commerce Manager
- Shown next to the predicted issues on the same product
- Requires connecting the channel account; time-boxed per item
- Closes the loop between prediction and outcome
Per-feed product selection and cadence
Every feed carries its own product selection — filter by collection, vendor, tag, attribute value or quality score — and its own refresh schedule. Put the full range on Google, a curated set on Meta, and only Channel-Ready products on TikTok, from one catalog. Up to 25 feeds per organization.
- Filter by collection, vendor, tag, attribute or quality score
- Different ranges per channel from one catalog
- Independent refresh cadence per feed
- Up to 25 hosted feeds per organization
Wholesale fields structurally excluded
Wholesale price, MOQ, case pack and lead time are a separate internal attribute class. They cannot appear in a feed, a Shopify sync or any public surface, because the feed engine never reads that class. That is an architectural boundary, not a setting.
- Separate internal attribute class for trade data
- Excluded from every feed template by design
- No checkbox to untick, nothing to audit
- Same boundary protects Store Sync and the Trade Portal
Five steps from a messy catalog to a feed that stays approved
Set up once. After that the feed is a URL that keeps itself current, and the diagnostics tell you when something new needs attention.
Connect your Shopify store
Install Apimio from the Shopify App Store or start a trial at app.apimio.com. The account provisions itself, the catalog syncs, and Store Health scores every listing on arrival, so you can see the identifier, image and description gaps before you build a single feed.
Fix the data
Work the Quality Guard fix list — missing GTINs, empty product types, images under size, titles over length — with Bulk Edit or Apimio AI. Map your categories to Google's taxonomy once. Set a quality threshold if you want only products above a score to be eligible for feeds.
Build the feed
Choose the channel template, pick the product selection, set the refresh cadence. Run the pre-publish diagnostics and clear anything the panel flags. The feed is generated and hosted at a stable, tenant-scoped URL (Advanced and Enterprise plans).
Give the channel the URL
Paste the hosted URL into Google Merchant Center, Meta Commerce Manager, Pinterest, TikTok or Bing as a scheduled fetch. For Amazon or Walmart, download the TSV and upload it to the marketplace. That is the last time you handle a file.
Watch predicted vs actual rejections
The feed regenerates on schedule. Connect Merchant Center or Commerce Manager and Apimio pulls each item's real status back next to the predicted issue. When a new rejection reason appears, fix the product once and every channel inherits the fix at the next refresh.
Feed app vs spreadsheet export vs Apimio
Most Shopify teams have run feeds both of the other ways. Here is where each one stops.
| Fixes the data first Apimio | Standalone feed app | Manual export | |
|---|---|---|---|
| Hosted feed URL the channel polls | |||
| Refreshes without anyone touching it | |||
| Fixes the product data before feeding it | |||
| Predicts rejections before publish | |||
| Real rejections shown next to predicted issues | |||
| Category mapped to Google's taxonomy | |||
| Google, Meta, Pinterest, TikTok, Bing from one record | |||
| Amazon and Walmart | Importable TSV files | Manual TSV | |
| Holds incomplete products out of the feed | |||
| Wholesale fields structurally excluded | |||
| Multiple Shopify stores from one catalog | |||
| Feed shaped for AI shopping assistants | |||
| Live API sync to Google, Meta or Amazon | |||
| Cost | Included in Advanced PIM $399/mo and Enterprise PIM | $30–$300/mo on top of your other tools | Free, plus the hours |
What changes when the feed manager knows the data
Feed apps solve transport. Disapprovals come from the data. Solving both in one place changes the week of the person who owns the feed.
Disapprovals surface before the spend
The identifier, title, image and price problems that trigger Merchant Center rejections show up in the pre-publish panel, on your schedule, instead of in a diagnostics tab after a day of wasted budget.
One invoice, not two
The tool that holds and scores your product data is the tool that feeds it. Advanced PIM at $399 a month covers both, so the feed-app line item disappears (Advanced and Enterprise plans).
Nobody re-uploads anything
The export-and-upload ritual ends. A stale feed stops being a thing that can happen quietly, because the feed refreshes itself and a badge tells you if it did not.
Channels stop disagreeing
Google, Meta, Pinterest, TikTok and Bing read the same record and the same category map, so two channels cannot show two prices or two categories for one SKU.
Trade pricing stays internal
The wholesale attribute class never reaches the feed engine. The scenario where a dealer finds your trade price in a public Shopping listing is designed out.
The right range on each channel
Full catalog on Google, a curated set on Meta, only Channel-Ready products on TikTok — from one catalog, with one product selection per feed instead of one export per channel.
Feeds are the output of a clean catalog
Product feed management in Apimio is one surface of a catalog operations platform. These are the parts it leans on.
Product Feeds
The feature page: hosted feed URLs per channel, templates, scheduling, Shopify specifics and the full FAQ (Advanced and Enterprise plans).
See Product FeedsQuality Guard
Scores every product against 74 rules and surfaces the identifier and image gaps that cause channel disapprovals — before the feed is built.
See how Quality Guard scores your catalogCatalog Hub
The canonical record every feed is generated from, synced two-way with your Shopify stores, with the category map and the internal attribute class that keeps wholesale data out of feeds.
Explore Catalog HubRelated reading on feeds, channels and pricing
Go deeper on the Google spec, compare Apimio with a dedicated feed platform, or see what the plans include.
Optimize your Google Shopping feed
A practical guide to the fields, titles, identifiers and images that decide approval and performance in Merchant Center.
Read the guideApimio vs Feedonomics
An honest comparison with the largest feed platform: where Feedonomics is stronger, where a Shopify merchant is paying for headroom it will never use.
Read the comparisonChatGPT product feed
The agent-ready feed format: a catalog an AI shopping assistant can actually read, generated by the same feed engine (Advanced and Enterprise plans).
See the agent-ready feedPricing
Basic PIM $199, Advanced PIM $399 and Enterprise PIM from $999 a month. Product Feeds are on Advanced and Enterprise.
See plans and pricingProduct feed management — the common questions
A product feed manager is the tool, or the person, responsible for turning a catalog into the files each sales channel expects — Google Shopping, Meta, Pinterest, TikTok, Bing, marketplaces — keeping those files current, and dealing with whatever the channel rejects. Standalone feed managers take product data as given and reshape it per channel. Apimio is a product feed manager built into the catalog itself (Advanced and Enterprise plans): it fixes the data, maps categories to Google's taxonomy, predicts rejections before publish, hosts each feed at a URL that refreshes on schedule, and pulls the real rejections back from the channel so you can see prediction and outcome together.
Product feed management software generates channel-specific product files from your catalog, hosts or submits them, refreshes them on a schedule and reports what the channel accepted or rejected. Standalone products like Feedonomics, DataFeedWatch, Channable and GoDataFeed do this as a separate subscription on top of whatever holds your product data. Apimio includes product feed management inside the catalog platform (Advanced and Enterprise plans), so the same system that scores and fixes product data also builds the feeds — one subscription rather than two, and no gap between the data and the file.
As often as your prices, stock or content change, and at least once a day. Google Merchant Center can fetch a hosted feed on a daily schedule and Meta Commerce Manager can poll hourly, so a feed that is refreshed less often than your price changes will carry stale numbers and eventually trigger price-mismatch disapprovals. In Apimio each hosted feed has its own refresh cadence (Advanced and Enterprise plans), so you can refresh a fast-moving sale feed hourly and a stable catalog feed daily, and a stale-feed badge flags any feed that missed its schedule.
Because the product data does not meet a rule, not because the XML is malformed. The usual causes are a missing or invalid GTIN, a title over the character limit, an availability value that is not one of Google's accepted terms, an image below minimum dimensions, a price or currency in the feed that does not match the landing page, or a required field that is empty for that product type. Apimio's pre-publish diagnostics check exactly those families before the feed goes live and list every affected product with a link to fix it, and once you connect Merchant Center the real rejection status is pulled back next to the prediction so nothing gets missed.
Shopify's Google & YouTube sales channel can sync products to Merchant Center, and for a single store with simple products it is often enough. It does not tell you in advance which products will be rejected, it does not map your categories for other channels, and it does not carry Meta, Pinterest, TikTok or Bing from the same setup. Merchants running several stores, large variant matrices, or several channels usually add a feed tool. Apimio covers that case from the catalog (Advanced and Enterprise plans): one record, five channel templates, diagnostics before publish and real rejections pulled back afterwards.
For Google Shopping, Meta, Pinterest, TikTok and Bing, no — Apimio generates and hosts those feeds itself (Advanced and Enterprise plans), and produces Amazon and Walmart as importable TSV files. Where a dedicated feed app may still earn its place: you need a channel Apimio has no template for, you want live API submission to a marketplace rather than a file, or you run rule-heavy title rewriting per channel at a scale Feedonomics or Channable specialize in. We spell out the trade-off honestly at /compare/feedonomics. If data quality is part of your disapproval problem, one subscription that fixes and feeds beats two that do half each.
Advanced PIM at $399 a month and Enterprise PIM from $999 a month. Product Feeds are not part of Basic PIM at $199 a month, which covers a single store, 10,000 SKUs, Quality Guard, Bulk Edit, Line Sheets and the AI content assists. Advanced adds multi-store, 50,000 SKUs, Product Feeds, Scheduled Imports, Sale Scheduler, the Image Library, multi-language and the API. Apimio offers a 14-day free trial, and if a subscription lapses your feeds pause rather than delete — turn it back on and they resume. Full detail is at /pricing.
Two ways, and it matters to keep them apart. The feed itself is a hosted URL that Merchant Center or Commerce Manager fetches on its own schedule — that is not a live API sync, and Apimio does not claim one. Separately, you can connect your Merchant Center or Commerce Manager account so Apimio pulls each item's actual rejection status back onto the product and shows it next to the predicted issues (Advanced and Enterprise plans). Retrieval is time-boxed per item and only runs once you have connected the account.
Yes, if it reads one product record and writes several templates. In Apimio the Google Shopping XML, Meta, Pinterest, TikTok and Bing feeds are templates on the same engine (Advanced and Enterprise plans), each with its own product selection and refresh cadence, up to 25 feeds per organization. Because they share one record and one category map, a title fix or a price change lands in every channel at the next refresh, and two channels can never show two prices for the same SKU. Shopify remains the only channel Apimio syncs with live and two-way.
A capped set of the rules that cause most rejections, not the whole channel specification: required fields for that channel and product type, title length, availability values against the accepted vocabulary, image minimum dimensions, price and currency consistency, and GTIN presence. Each finding is a clickable row that opens the product so you fix it in the catalog, and a stale-feed badge shows when a feed has not refreshed on schedule. Apimio then pulls the channel's real verdict back after processing (Advanced and Enterprise plans), so the rules the check does not cover still show up — attached to the product, not buried in a diagnostics export.
Only if the feed is shaped for it. Channel feeds are full of channel-specific fields and abbreviated values that an LLM reads poorly. Apimio's agent-ready feed format is a template on the same engine (Advanced and Enterprise plans) that outputs complete attributes, resolved categories and plain-language descriptions, served as a hosted URL — the catalog an AI shopping assistant can actually read. It can be mapped to what the ChatGPT and OpenAI product-feed programs ask for; it is not an official OpenAI specification. Details are at /chatgpt-product-feed.
See which products Google would reject before Google tells you
Start a 14-day free trial, connect a store, and run the pre-publish diagnostics on your real catalog. Product Feeds are on Advanced PIM and Enterprise PIM.