Skip to content
NagentNagent
Log inSign upHire your AI Growth Team
NagentNagent
Log inSign up

Why is my Meta catalog out of sync with my store inventory?

8 Minutes read
Published:
A Meta catalog drifts from store stock when the feed updates less often than stock changes, uploads fail, IDs do not match, or an integration has stopped. Here is how to find which one it is and fix it, with Meta's own limits.
PB
Pratap BeheraNov 14, 2026·8 min read
Why is my Meta catalog out of sync with my store inventory?

A Meta catalog falls out of sync with store inventory for a handful of reasons: the feed updates less often than your stock changes, uploads fail and Meta rejects the items with errors, product IDs differ between store and catalog, variants are grouped inconsistently, or the app or integration feeding the catalog has stopped. Find which data source feeds the catalog, check its last upload and its errors, compare a sample of products, and then fix the cause rather than editing items by hand.

How does a Meta catalog get its inventory data?

Every catalog has one or more data sources. Which one you use decides how fresh your stock data can be.

  • A platform integration. Shopify's Facebook and Instagram by Meta channel syncs products you make available to Meta. Shopify says changes to product details sync automatically and usually display after a few minutes (Shopify Help Center).

  • A scheduled data feed. A file at a URL that Meta fetches on a schedule. Meta's documentation says scheduled feeds do not support uploads more often than once per hour (Meta for Developers).

  • The API. Your developer or a feed tool pushes changes directly. Meta's Catalog Batch API creates, updates and deletes many items in one request (Meta for Developers).

  • Manual entry. Fine for a handful of products, and the first to drift.

If you have two sources writing to the same catalog, for example an old feed and a newer app, they can overwrite each other. That alone explains many "random" mismatches. Note also that campaign tools, including Nagent's performance marketing lead NIA, read and change campaigns, not feeds, so the fix almost always sits in the data source.

What are the most common causes of a catalog falling out of sync?

  1. The feed updates less often than your stock changes. A daily feed cannot reflect a product that sold out at 11 a.m. Even the fastest scheduled feed is hourly.

  2. Uploads fail. Meta rejects any product marked with an error from your catalog (Meta for Developers). If the error is on the availability or price field, the old value can stay live.

  3. IDs do not match. Meta's id field should be a unique content ID, ideally the SKU, and must appear only once (Meta catalog reference). If your store changes SKUs or your feed tool generates its own IDs, updates land on new items while old ones linger.

  4. Variants are grouped inconsistently. Meta asks that variants share the same item_group_id and that availability and inventory fields are provided for every variant in the group.

  5. The integration stopped. An expired token, a disconnected app, a removed permission or a changed business owner stops updates silently. Meta's feed guide notes the error "Cannot access an object not managed by the business owning this app" when an app no longer belongs to the business (Meta Feed API guide).

  6. Products fail the platform's own rules. Shopify lists products that will not sync: digital products, products without a return policy, products missing an image, a Google product category or variant details, and free products.

  7. A replace feed removed items, or an update feed did not. In a replace feed, items missing from the new file are deleted. In an update feed, Meta creates and updates items but does not delete those missing from the file (Meta Feed API guide). Teams that switch modes without knowing this see products vanish or stick around.

  8. An old API endpoint stopped working. Meta says the older /{catalog_id}/batch endpoint is deprecated and unavailable from API v27, and integrations should move to /items_batch. A custom integration still on the old endpoint will stop updating after an upgrade.

How do you find which cause you have?

Work through these checks in order. Most teams find the cause by step four.

  1. List the data sources. In Commerce Manager, open the catalog's data sources. Note each source, its type and its last successful update.

  2. Pick ten products. Choose some that changed stock or price today, some best sellers and some recently added. Compare store and catalog for availability, price, sale price and ID.

  3. Read the upload errors. For feeds, Meta's API lists errors per upload session, and a full error report can be generated. A fatal error means the item cannot be ingested; on a warning, Meta drops the bad field and keeps the rest (Meta Feed API guide).

  4. Check the integration's own status. On Shopify, the channel's overview page shows product status, and the product list's Issues column names publishing errors.

  5. Check the timing. If store and catalog differ only for products changed in the last hour or day, your update frequency is the cause, not an error.

  6. Check for a second writer. If a product's values flip between two versions, two sources are writing to it.

  7. Check the pixel. If ads show the right products but sales do not attribute, compare the content IDs your pixel or Conversions API sends with catalog IDs.

How do you fix each cause?

  • Slow updates: move from a daily to an hourly schedule, or push stock changes through the API as they happen. For fast-moving stock, an update-only feed with just id and changed fields is quicker to process than a full file.

  • Upload errors: fix the source data, not the catalog item. Errors come back on the next upload if the store data is still wrong. Meta's advice is to fix all upload errors.

  • ID mismatch: choose one ID scheme, usually the SKU, and use it in the store, feed, pixel and Conversions API. Then remove the orphaned items once.

  • Variant grouping: give every variant the parent's item_group_id, and send availability for every variant, including sold-out ones.

  • Broken integration: reconnect the app, confirm it belongs to the business that owns the catalog, and renew any expired tokens. Set a reminder to check monthly.

  • Platform rules: fix the listed issues in your store's product editor and save; the product syncs again on the next run.

  • Feed mode confusion: use a replace feed for the full daily file and an update feed for intraday stock and price changes, and document which is which.

  • Old endpoint: ask your developer to move to /items_batch before upgrading the API version.

How often should a Meta catalog update?

Match the update frequency to how fast your stock changes.

  • Stable catalog, few sell-outs: a daily replace feed is usually enough.

  • Active D2C store: hourly scheduled updates, the fastest a scheduled feed supports.

  • Flash sales, drops or limited stock: push changes through the API as they happen, because hourly is too slow when a product sells out in twenty minutes.

Madgicx suggests daily feed updates at minimum for active stores and hourly for high-volume stores (Madgicx). That is a sensible floor, but your own sell-out speed is the real guide.

What does an out-of-sync catalog cost?

Meta's catalog reference says out-of-stock items show as sold out in a shop and do not appear in ads. So the expensive case is the reverse: a product the catalog still thinks is in stock.

  • Wasted clicks. People click an ad for something they cannot buy. Every one of those clicks is paid for.

  • Lost trust. A shopper who lands on "sold out" twice may not come back.

  • Wrong prices. An ad showing last week's price can cause complaints or a mismatch with the landing page.

  • Worse optimisation. When catalog IDs and pixel events disagree, Meta has less signal to match products to people.

How do you stop it happening again?

  • One source of truth per catalog, written down.

  • A daily check of the data source's last update time, with an alert if it is older than your schedule.

  • A weekly ten-product spot check against the store.

  • Stock thresholds: pause catalog ads, or exclude a product set, when key products fall low.

  • An owner for the integration who renews access before it expires.

Where does Nagent fit?

We make Nagent. Nagent is multiplayer AI for growth: people and AI agents in one shared context, delivering the number. NIA, the AI performance marketing lead on the MIRA-led Marketing team, works Meta ads (Beta) at campaign level today.

To be clear about the limit: NIA does not manage your Meta catalog, product feed or Commerce Manager, and she does not edit ad sets, audiences or creative. What she can do on Meta is read your campaigns, report how they did over the last 1 to 30 days, and propose pausing a campaign or lowering its budget, for example while a catalog problem is being fixed. Each change waits for a person to approve, and anything that commits more money must fit the ad account's hard spend cap. For catalog fixes, the steps above are the work. See what NIA covers.

Frequently Asked Questions

Why are my Meta ads showing out-of-stock products?

Usually because the catalog has not received the stock change yet. Check when the data source last updated, look for upload errors on the availability field, and confirm the product's ID matches between store and catalog.

How long does a Shopify to Meta catalog sync take?

Shopify says product changes usually display on Facebook a few minutes after they sync. Products with publishing errors do not sync until the errors are fixed.

Why is my catalog match rate low?

Most often because the product IDs sent by your pixel or Conversions API do not match catalog IDs, or the ViewContent event is not firing with product parameters. Align the ID scheme across store, feed and events.

What is the difference between a replace feed and an update feed?

A replace feed is the full list: items missing from it are deleted. An update feed only creates and updates the items it contains and deletes nothing, which makes it suited to frequent stock and price changes.

Want a second pair of eyes on your Meta setup? Book a demo.

AI agents for E-commerce & D2C

Continue learning

Related agents

Agents that match this read.

Browse all 200+ agents
Select Category
Creative

How to make a video ad with AI from product photos

Start from a clean, well-lit product photo, write the script first, animate each shot from the photo rather than from a text prompt, add text and logo as layers, then check the label at full size. Here is the step-by-step method, the tools and the checks.

Marketing AI

AI Agents for Localized Store Marketing

AI agents for localized store marketing close the gap between central teams and hundreds of locations: store-specific campaigns drafted from local signals, with a person approving what goes live.

Marketing

Gen AI Catalog Management Software: What It Does

What gen AI catalog management software does for product catalogs, from attributes and descriptions to taxonomy, images, feeds and review, what to look for, and where Nagent fits.

Performance Marketing

How do I set up NIA to optimise Google Ads and Meta ads campaigns?

Install the Marketing team, connect Google Ads through Google's consent screen and sync, connect your Meta ad account and set its daily and monthly hard spend cap, confirm conversion tracking, then run a diagnosis and approve NIA's proposals on Actions. Step by step.

Performance Marketing

What is a good ROAS for Meta ads?

A good ROAS for Meta ads is one above your break-even ROAS plus the profit you need, not a universal number. A product keeping half its price after costs breaks even at 2.0. Here is how to calculate yours, what published benchmarks say and why Meta and your store disagree.

Performance Marketing

Does AI creative testing work with Meta Ads Manager, Google Ads and Shopify data?

Mostly yes for Meta, partly for Google Ads, and usually indirectly for Shopify. Creative tools read ad-level results from the ad platforms; Shopify sales reach them through the platforms' conversion tracking or an attribution tool.