Comparisons Product feed vs API: how to send product data to channels
Product feed vs API: how to send product data to channels
Feed files versus APIs such as Google's Merchant API and eBay's Sell APIs: how fresh the data is, the limits, errors and feedback, and when each one fits.
- A feed file sends the whole catalog on a schedule; an API sends single changes when they happen.
- Google fetches scheduled files daily, weekly or monthly, while Merchant API changes apply as your integration sends them.
- APIs have quotas: Google allows product updates up to twice per day by default, and eBay allows each listing 250 revisions per calendar day.
- Google's Content API for Shopping reached its sunset on August 18, 2026; API work for Merchant Center now belongs on the Merchant API.
- Files suit catalogs that change slowly; APIs suit fast-moving prices and stock.
The difference in one table#
| Feed file | API | |
|---|---|---|
| What you send | The whole catalog, or a full snapshot, each time | Single products or small batches when something changes |
| How fresh | As fresh as the last fetch or upload | As fresh as your last request |
| Google Merchant Center | Scheduled fetch daily, weekly or monthly; manual fetch or upload in between | Merchant API; Google says API data sources update in real time when your integration sends requests |
| eBay | Sell Feed API: upload and download files, processed asynchronously | Sell Inventory API: create, update and publish listings, up to 25 items or offers per bulk call |
| Limits | File size, for example under 4 GB for a Google scheduled fetch | Request quotas and revision limits per day |
| Errors and feedback | A processing report or result file after the run | A status per item in the response, plus notifications |
| Setup | A file at a URL and a schedule | Developer work, authentication and quota handling |
| Fits | Catalogs that change slowly, small teams, channels that only accept files | Fast-moving prices and stock, large catalogs, many channels |
Freshness#
Files are only as current as the last fetch. Google's scheduled fetches run daily, weekly or monthly. To update more often, you trigger a fetch by hand, upload a new file or switch to the API. Microsoft's file feeds work the same way: a feed downloaded from a URL runs every 24 hours, and Microsoft says a feed expires after 30 days if you do not update it (Microsoft Advertising Help). OpenAI's product feed for ChatGPT accepts only full snapshots, by upload, hosted URL or SFTP (OpenAI).
APIs send a change when it happens. If Northpeak sells its last green tent at 10:00, an API call can mark it out of stock at 10:01; a daily file would show it in stock until the next fetch. Google's Merchant API also offers real-time notifications for product data changes, so you learn about status changes without polling.
Limits#
Both methods have limits, but of different kinds.
| Channel | File limits | API limits |
|---|---|---|
| Scheduled file under 4 GB | Product updates up to twice per day by default; the daily call quota is generally set to twice the account's offer quota; quotas reset at 12:00 UTC | |
| eBay | Uploads and downloads are processed asynchronously | Up to 25 items or offers per bulk call; each listing can be revised up to 250 times per calendar day |
Google adds that individual products can be updated more than twice as long as total daily calls stay within the account quota, and that only temporary quota increases are available, for example for a launch in a new market or a busy shopping season. Each request in an HTTP batch counts against the quota.
Errors and feedback#
With a file, you learn about problems after processing. eBay's Feed API gives each upload a task ID; you check its status and download a result file. Google and Microsoft show issues per product in Merchant Center after the file is processed.
With an API, each response reports per item. eBay's bulk publish call returns a result for each offer, with errors and warnings for the ones that failed; some offers in a call can succeed while others fail. Google reports exceeded quotas as API errors and in Merchant Center diagnostics.
A deadline for Google API users#
Google's Content API for Shopping reached its sunset on August 18, 2026. Since September 1, 2026, requests without an approved extension fail intermittently with HTTP 410 Gone, and Google plans to turn off all endpoints in early 2027, a date it says may change. Integrations still on the Content API need to move to the Merchant API.
When each one fits#
Choose a feed file when:
- your prices and stock change a few times a week or less;
- a channel accepts only files, as OpenAI's product feed does today;
- you want a setup without developer time.
Choose an API when:
- prices or stock change several times a day;
- you need per-product feedback right after each change;
- you manage large catalogs or many sellers and want changes in small batches.
You can also combine both. Google says the Merchant API complements file uploads, so a daily file can carry the full catalog while API calls send price and availability changes.
Where Central fits#
Central publishes to the channels you choose. Every value is backed by sources you can check; what the sources do not support is held back.
Questions
Can I combine a feed file and an API?
Yes. Google says the Merchant API complements other upload methods such as files and autofeed, so a daily file can carry the catalog while the API sends price and stock changes.
Is Google's Content API for Shopping still available?
It reached its sunset on August 18, 2026. Since September 1, 2026, requests without an approved extension fail intermittently with HTTP 410 Gone, and Google plans to turn off all endpoints in early 2027.
Sources
- Update your product data source on a schedule · Google Merchant Center Help checked 19 November 2026
- Quotas · Google Merchant API checked 19 November 2026
- Deprecation and sunset · Google Content API for Shopping checked 19 November 2026
- Feed API overview · eBay Developers Program checked 19 November 2026
- bulkPublishOffer · eBay Developers Program checked 19 November 2026