Facebook Shops Integration

A Shop is only as good as the catalog behind it. Manually adding items in Commerce Manager works for a handful of SKUs, but any store with a real inventory — sizes, colors, prices that move, stock that runs out — needs an automated feed so the storefront reflects reality without someone re-uploading a spreadsheet every day.

1. Catalogs can hold up to 10 million items, far beyond what manual entry can sustain.
2. A feed keeps availability, price, and stock status current, which matters directly to buyers browsing the Shop tab, not just to ad performance.
3. The same feed doubles as the source for Instagram product tagging and dynamic ads, so one well-structured feed does the work of three separate integrations.
4. A feed lets you apply Shops-specific fields — like size and quantity_to_sell_on_facebook — consistently across thousands of items instead of one product at a time.

Facebook Shops, Advantage+ (dynamic) catalog ads, and Instagram/Facebook product tagging all read from the same underlying Commerce Manager catalog, but they are not the same feature, and this is where the Shops integration diverges from a generic Meta catalog/ads setup:

1. Shops is the always-on storefront itself — a dedicated Shop tab and collection of product detail pages that a shopper can browse organically, independent of any ad spend.
2. Dynamic (Advantage+) catalog ads are paid placements that pull individual items from the same catalog to retarget or prospect users, shown as ads rather than as a persistent storefront.
3. Product tagging lets a business tag catalog items directly inside organic posts, Stories, and Reels, linking that specific piece of content to a product detail page in the Shop.

The mechanic that used to separate Shops most sharply from the other two — completing an entire purchase without leaving Facebook or Instagram via native checkout — has been discontinued. Meta phased native checkout out starting June 2025, with most U.S. merchants transitioned off it by August 2025. Practically, that means the link field in your feed (the checkout URL) now carries more weight for Shops specifically than it does for a standalone dynamic-ads catalog: it's the field that actually completes the sale, since the buyer is handed off to your own website's checkout rather than paying inside the app.

Shops draws from the same catalog ingestion pipeline as the rest of Commerce Manager, so it accepts the standard Meta catalog feed formats:

1. CSV or TSV (spreadsheet-style, one row per item)
2. XML in RSS 2.0 or Atom 1.0 format
3. A Google Sheets link, which Meta re-fetches on a schedule you set

You add the feed as a scheduled data source (a URL Meta re-fetches automatically) or upload it directly, and for programmatic or near-real-time updates Meta also exposes a Catalog Batch API. Whichever format you use, Meta requires at least one valid category per item — via Google Product Category or Facebook Product Category — and notes this becomes mandatory once onsite/checkout-linked selling is enabled for the catalog.

Shops inherits Meta's core catalog field set, plus a couple of attributes that only matter once items are sold through a Shop rather than shown in a generic ad. The table below reflects Meta's own catalog field reference.

Feedance maps your store's product data into the field structure Meta's Commerce Manager expects for Shops, rather than a generic ads-only catalog, and keeps it synced automatically.

1. Connect your store or PIM as the data source inside Feedance.
2. Select the Facebook/Meta Shops template — it prefills the required fields (id, title, description, availability, condition, price, link, image_link) and the Universal ID trio (brand, gtin, mpn).
3. Fill in the Shops-specific fields that a plain ads feed can skip: size for apparel/footwear categories and quantity_to_sell_on_facebook for stock-aware checkout eligibility.
4. Point the link field at your live, checkout-capable product URL on your own domain — this is the field that now closes the sale, since Meta hands the buyer off to your site rather than processing payment in-app.
5. Publish the generated feed URL (CSV, TSV, or XML) and register it as a scheduled data source in Commerce Manager, or connect it directly to your existing catalog.
6. Monitor the Catalog Health Dashboard / Issues tab in Commerce Manager, and let Feedance re-validate and re-push corrected items on the same schedule.

Commerce Manager lets you set a fetch frequency for a scheduled feed — hourly, daily, or weekly — at which Meta re-pulls your feed URL and refreshes the catalog behind your Shop. Meta's general guidance is to schedule at least once daily, and to move to hourly if prices or stock change frequently enough that a stale listing could show the wrong price or a sold-out item as available. For updates that need to reflect immediately — a price change or an item selling out mid-day — Meta's Catalog Batch API allows pushing changes in near real time instead of waiting for the next scheduled fetch. Feedance can run on either model: scheduled feed regeneration on a cadence you choose, or more frequent syncs for fast-moving inventory.

Most Shop-visibility problems trace back to a handful of well-documented issues in Meta's own catalog tooling:

1. Missing Universal ID. If an item has no brand, mpn, or gtin value at all, Meta will not approve it — at least one of the three is required.
2. Item not approved / policy violation. Items are disapproved when they're missing required fields or when they run afoul of Meta's commerce policies; Meta's review can take up to 48 hours, and merchants can request a second review if they believe an item was flagged incorrectly.
3. Catalog-wide disapprovals. These usually point to either an account-level policy issue or a structural problem with the feed itself, rather than a single bad row.
4. Stale or missing checkout link. Since native in-app checkout was phased out, an item whose link doesn't resolve to a working, domain-matched checkout page on your own site is a direct path to a broken buying experience — worth checking specifically during and after the transition.

Commerce Manager's Catalog Health Dashboard and Issues tab surface these problems item-by-item, which is the fastest place to check before assuming a feed-mapping bug.

1. Fill in brand, gtin, and mpn wherever you have them — even though only one is strictly required, having all three reduces disapproval risk and improves matching.
2. Use the most specific google_product_category level available; category depth affects both discoverability and, per Meta, becomes mandatory once a catalog is used for onsite/checkout-linked selling.
3. Set size correctly for every apparel and footwear item — it's a Shops-only requirement that a generic dynamic-ads feed can otherwise skip.
4. Keep quantity_to_sell_on_facebook and availability in sync with real stock; a mismatch is what causes sold-out items to still appear purchasable in the Shop.
5. Point link at a fast, mobile-friendly checkout page on your verified domain — since the buyer now completes the purchase there rather than in-app, that landing page is effectively your Shop's final conversion step.
6. Use full 500x500px+ images and, where possible, additional_image_link for secondary angles — Shops product detail pages show more imagery real estate than a single ad unit.

1. Is Facebook Shops the same thing as the Meta Ads catalog integration? No. They share one underlying Commerce Manager catalog, but Shops is the always-on storefront (Shop tab, product detail pages, tagging), while Meta Ads/dynamic catalog ads are paid placements pulling from that same catalog.
2. Can a customer still complete a purchase without leaving Instagram or Facebook? Not anymore for most merchants. Meta phased out native in-app checkout starting June 2025, with the transition largely complete for U.S. merchants by August 2025; buyers are now redirected to the merchant's own website checkout via the product's link field.
3. How many products can a Shop's catalog contain? Between 1 and 10 million items, per Meta's catalog eligibility requirements.
4. Can I use the same catalog for Shops and for dynamic ads? Yes — that's the intended setup — but a given catalog can only be attached to one Shop at a time.
5. Does Feedance handle the Universal ID and size requirements automatically? Feedance maps your source data (brand, GTIN/UPC/EAN, MPN, size/variant attributes) into Meta's expected field names and flags items missing all three Universal ID fields before they reach Commerce Manager.