Your Google Shopping feed is a URL now. It updates itself.
Product Feeds generates a hosted, always-current feed for every channel you sell through — Google Shopping, Meta, Bing, Pinterest — from the same catalog Apimio already keeps clean. You give Merchant Center a URL once. It polls that URL on its own schedule and always finds current prices, current stock and complete product data. No manual export, no re-upload someone has to remember, no feed that is one price change behind.
What a hosted feed changes
The difference between a feed you maintain and a feed that maintains itself.
The feed problem is a data problem
Merchant Center rejections are rarely about the feed file. They are about what went into it.
What happens today
What Product Feeds does
Disapprovals you find out about late
Google rejects 40 products for a missing GTIN, a mismatched price or a description that trips a policy check. Nobody notices until someone opens Merchant Center diagnostics and sees the red count.
Quality scoring sits upstream
Products are scored against 74 rules before they are eligible for a feed. The gaps that cause disapprovals — missing identifiers, empty fields, absent images — surface as a fix list, not as a Merchant Center rejection.
The feed is always one change behind
The feed is an export somebody re-uploads when they remember. Prices changed on Tuesday; the feed still carries last week's. Ads run against numbers that are no longer true.
The feed refreshes itself
Feeds regenerate on a schedule from the live catalog. A price change in Apimio is in the feed at the next refresh, without anyone exporting anything.
You pay a feed app to syndicate a mess
A standalone feed app costs $30–$300 a month and knows nothing about whether your data is complete. Garbage in, disapproved products out, plus a second subscription.
One subscription, not two
The catalog that holds your data also serves your feeds. You are not paying a PIM and a feed app to do two halves of one job.
Wholesale pricing near a public feed
If wholesale prices live as ordinary fields on the product, every export is a chance for them to end up somewhere public.
Wholesale fields are structurally excluded
Wholesale price, MOQ and case pack are a separate internal attribute class. They are excluded from every feed, every Shopify sync path and every public surface by design, not by a setting someone could switch off.
Every channel, from one catalog
Each feed is generated from the same product records, so the data behind them never diverges.
Google Shopping
Google Shopping XML is the first-class format, validated against the Merchant Center product data specification. Give Merchant Center the hosted URL and it polls on its own schedule.
- Google Shopping XML validated against the Merchant Center spec
- Hosted at a stable, tenant-scoped URL
- Scheduled refresh — no manual re-upload
- Identifier fields (GTIN, MPN, brand) surfaced as quality rules upstream
Meta, Bing and Pinterest
Templates cover Meta catalog feeds, Bing Shopping, Pinterest and price-comparison formats, each mapped from the same canonical product record.
- Meta catalog feed for Facebook and Instagram shopping
- Bing Shopping and Pinterest formats
- Price-comparison engine templates
- One data source, so channels never disagree
Amazon and Walmart as files
Amazon and Walmart are supported as importable TSV files in each marketplace's expected layout. These are files you upload to the marketplace, not a live API connection — we would rather be exact about that.
- Marketplace-formatted TSV export
- Generated from the same canonical record
- Not a live API sync — Shopify is the only live two-way sync
Scheduled refresh
Each feed carries its own refresh schedule. Set a cadence that matches how often the channel polls and how often your prices move.
- Per-feed refresh schedule
- Up to 25 hosted feeds per organization
- Feeds pause rather than break if a subscription lapses
Feed-level product selection
Each feed carries its own product selection, so a channel gets exactly the range you sell there — filtered by collection, vendor, tag, attribute or quality score.
- Per-feed product filters
- Exclude products below your quality threshold
- Different ranges per channel from one catalog
Clean data by construction
Because the feed is generated from the same catalog Quality Guard scores, the products entering a channel have already cleared your completeness bar.
- 74 quality rules across 4 outcome areas
- Publish Gate holds below-bar products as drafts
- Fix lists show what to correct before it costs you a disapproval
Four steps to a self-updating feed
Set up once. After that the feed is a URL that stays current on its own.
Fix the data first
Quality Guard scores the catalog and shows what is missing — identifiers, images, categories, descriptions. Clear the fix list, or set a quality threshold so only products above it are eligible for the feed.
Build the feed
Pick the channel format, choose the product selection, map your category field, and set the refresh schedule. The feed is generated and hosted at a stable URL.
Give the channel the URL
Paste the hosted URL into Merchant Center, Meta Commerce Manager or the channel of your choice. That is the last time you touch the file.
It stays current
The feed regenerates on schedule from the live catalog. Price changes, stock changes and content edits flow through automatically. The channel polls and always finds current data.
Why this beats a standalone feed app
Feed apps solve the transport problem. The disapprovals come from the data problem.
Fewer disapprovals at the source
The identifier and completeness gaps that trigger Merchant Center rejections surface as a fix list in Apimio, before they reach the channel.
One subscription instead of two
The catalog and the feed are the same product. You are not paying separately for the tool that holds your data and the tool that ships it.
Nobody re-uploads anything
The manual export ritual disappears. A feed being stale stops being possible, because nobody has to remember to refresh it.
Channels never disagree
Every feed reads the same canonical record, so Google and Meta cannot end up showing different prices for the same SKU.
Wholesale pricing stays internal
Wholesale fields are structurally excluded from feeds. The nightmare of trade pricing appearing on a public channel is designed out.
Different ranges per channel
Sell a subset on Meta and the full range on Google without maintaining two catalogs or two exports.
Manual export vs feed app vs Product Feeds
Most Shopify teams have tried the first two.
Manual CSV export | Standalone feed app | Quality upstream Apimio Product Feeds | |
|---|---|---|---|
| Hosted URL the channel polls | |||
| Refreshes without anyone touching it | |||
| Fixes the product data before feeding it | |||
| Blocks incomplete products from the feed | |||
| Wholesale fields structurally excluded | |||
| Separate subscription | |||
| Multiple Shopify stores from one catalog | |||
| Live API sync to the marketplace | |||
Feeds are the output of a clean catalog
The quality work and the feed are the same system, which is the whole point.
Quality Guard
Scores every product and surfaces the identifier and completeness 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 in real time.
Explore Catalog HubBulk Edit
Fill the fields your feeds need — identifiers, product types, descriptions, images — across hundreds of products at once.
See Bulk EditProduct feeds on Shopify — the common questions
In Apimio you build the feed from your catalog rather than exporting a file. Choose the Google Shopping format, select which products belong in it, map your category field, set a refresh schedule, and Apimio hosts the feed at a stable URL. You paste that URL into Google Merchant Center once. Merchant Center then polls it on its own schedule and always finds current data, so there is no export to repeat and no upload to forget.
Most disapprovals trace back to the product data rather than the feed file — a missing GTIN or MPN, a price in the feed that no longer matches the landing page, an absent image, or a description that trips a policy check. That is why Apimio scores products against 74 quality rules before they are eligible for a feed, and why you can set a quality threshold so below-bar products are simply excluded. Fixing the data upstream removes the cause instead of resubmitting the symptom.
No, and it is worth being exact about this. Apimio generates hosted feed files and URLs that those channels read on their own schedule, plus marketplace-formatted TSV files for Amazon and Walmart that you upload. That is not a live API connection. Shopify is the only channel Apimio syncs with live and two-way. If a vendor tells you a hosted feed is the same as an API integration, they are blurring something that matters.
A feed app solves transport: it takes the data you already have and ships it to a channel in the right shape. It has no view on whether that data is complete, so incomplete products become disapproved products. Apimio scores and fixes the data first and then feeds it, from the same catalog that syncs to your stores. Honest limit: if your product data is already clean and a feed is genuinely all you need, a dedicated feed app is cheaper. Apimio wins when data quality is part of the problem.
Yes. Each feed carries its own product selection, filtered by collection, vendor, tag, attribute value or quality score. You can put your full range on Google Shopping and a curated subset on Meta without maintaining two catalogs or two exports.
No. Wholesale price, MOQ, case pack and lead time are a separate internal attribute class in Apimio, not ordinary product fields. They are excluded from every feed, every Shopify sync path and every public surface by construction — not by a setting somebody could switch off by accident.
Not automatically. The feed uses the category field you maintain in Apimio, so you keep control of how products are classified rather than accepting a mapping you did not choose. Apimio AI can suggest product types to fill that field in bulk, and you review the suggestions before they save.
Advanced PIM and Enterprise PIM. Product Feeds is not part of Basic PIM — along with Scheduled Imports, Sale Scheduler, the Image Library, multi-language and the public API, it sits on Advanced and above. Basic PIM includes the catalog, Quality Guard, Bulk Edit, Line Sheets and the AI content assists.
Fix the data once. Every channel inherits it.
Install Apimio from the Shopify App Store, let it score your catalog, and see which products would be disapproved before a channel tells you.