Skip to content
feedlab Request early access

Concept

Feed scheduling

Also called scheduled fetch, feed refresh, and feed cadence.

Feed scheduling is the arrangement where a sales channel fetches a feed from a fixed URL on a repeating timetable instead of the merchant uploading a file. It matters because the interval between regenerations is the window in which a channel can be wrong about a price or a stock level, and most mismatch disapprovals are caused by that window being too wide rather than by a bad mapping.

Frequently asked questions

How often should a product feed be regenerated?

Often enough that the feed is rarely wrong. If prices change weekly and stock is deep, daily is comfortable. If stock is shallow and moves quickly, or prices change through the day, daily guarantees windows where the feed contradicts the site and disapprovals follow.

What is the difference between regenerating a feed and the channel fetching it?

Two independent clocks. You control when the file is rebuilt from the catalogue; the channel controls when it reads the URL. Accuracy depends on both, and a feed regenerated just after the channel fetched it is stale for almost a full cycle.

How often do the major channels fetch a scheduled feed?

Google Merchant Center offers daily, weekly or monthly. Meta supports hourly, daily or weekly. Pinterest fetches once every 24 hours. Microsoft runs on a daily cadence. Meta is the only one of the four offering sub-daily scheduled fetches.

Why does feed cadence cause disapprovals?

Because channels crawl the landing page and compare it against the feed. Any gap between a change in the shop and the next regeneration is a window where the two disagree, and a crawl landing in that window produces a price or availability mismatch.

Related attributes

Related errors

Related concepts

Channels this applies to

Primary sources

Channel specifications change. These are the official documents this page is based on.

Last reviewed View as markdown