NewProduct Score, 4T Segmentation, Price War and Broken Size are live.See what's new
Feedance
Facebook Shops logoFacebook ShopsChannel · Marketplaces and apps
Meta integration

Send Meta the products
worth showing

Feedance builds your Facebook Shops feed and adds product-level labels for score, 4T segment, price position and broken sizes, so every product carries its own performance signal.

Facebook Shops product feed
Generated by Feedance
XML, CSV or JSON exportUpdated on every sync
<item>
  <id>TS-1042</id>
  <title>Crew neck T-shirt</title>
  <price>49.90 USD</price>
  <availability>in stock</availability>
  <custom_label_0>score_86</custom_label_0>
  <custom_label_1>top</custom_label_1>
  <custom_label_2>best_price</custom_label_2>
  <custom_label_3>size_ok</custom_label_3>
</item>
Feedance labels, written as custom labels
What Feedance sends to Meta

A catalog with a performance signal on every product

Meta reads your products from the feed. Feedance sends a complete, valid feed plus the signals Meta does not have on its own.

Product Scorecustom_label_0A 0 to 100 score from views, add to carts and purchases over 1, 7 and 30 days.
4T segmentcustom_label_1Top, Tolerable, Tranquil or Toxic, from each product's own traffic and return.
Price Warcustom_label_2Best, same or more expensive than named competitors.
Broken Sizecustom_label_3Flags styles whose size run is mostly out of stock.
Creativesimage_linkBranded images from Creative Suite, with price and campaign details from the feed.
How you use it: split campaigns, product groups or product sets by these labels, for example only Top products, or everything except Toxic and broken size runs. Label slots are configurable. Feedance does not change your bids or budgets.

What is Facebook Shops?

Facebook Shops is Meta's native storefront feature, built and managed inside Commerce Manager, that lets a business publish a browsable product catalog directly on its Facebook Page, Instagram profile, and Messenger. One product catalog powers the storefront across all three surfaces at once — the same catalog can simultaneously drive the Shop tab, Instagram product tags, and Meta's dynamic ad placements. Shops are restricted to physical goods: Meta's own catalog eligibility rules explicitly block selecting a catalog built for other verticals such as hotels, flights, vehicles, destinations, or home listings as a Shop's source catalog.

A Shop also has to be exclusive — you cannot point two different Shops at the same catalog in Commerce Manager — and the connected Business Manager account must own the catalog and hold permission to manage it.

One thing has materially changed since Shops launched: Meta began phasing out true in-app payment ("native checkout") on Facebook and Instagram in June 2025, with the transition largely complete for U.S. merchants by August 2025. Today, Shops function primarily as a discovery and storefront layer — product listings, collections, tags, and detail pages — while the actual purchase is completed on the merchant's own website through the product's checkout link, rather than inside the Facebook or Instagram app itself.

Why connect your product feed to Facebook Shops?

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.

Shops vs. Dynamic Ads vs. product tagging — same catalog, different jobs

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.

What feed format does Facebook Shops require?

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.

Which product attributes does Facebook Shops require?

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.

FieldRequired forWhat it controls
idAll itemsUnique content ID (ideally your SKU); must match pixel content IDs used for dynamic ads.
titleAll itemsProduct name, max 200 characters (Meta recommends keeping it near 65 for readability in the Shop).
descriptionAll itemsUp to 9,999 characters; should call out specific, unique features like material or color.
availabilityAll items"in stock" or "out of stock" — out-of-stock items are shown as sold out on the storefront.
conditionAll items"new", "refurbished", or "used".
priceAll itemsNumeric value plus a 3-letter ISO 4217 currency code, e.g. "9.99 USD".
linkAll itemsThe product/checkout URL; must start with http(s):// and sit on your business's own verified domain. This is the field that now carries the buyer to checkout, since native in-app checkout has been retired.
image_linkAll itemsJPEG or PNG, at least 500x500px.
brand, gtin, mpnAll items (at least one of the three)Meta treats this trio as a "Universal ID" set; missing all three is a common cause of item disapproval.
sizeShops only, specific categoriesRequired specifically for selling in Shops for categories such as clothing and shoes — not required for a plain ads catalog.
quantity_to_sell_on_facebookShops checkout eligibilityWhole-number stock count; an item needs a value of at least 1 plus "in stock" availability to be eligible for checkout in a Shop, and Meta auto-decrements it as orders complete.

How to connect your feed to Facebook Shops with Feedance

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.

How often should the feed update?

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.

Common Facebook Shops feed and listing errors

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.

Optimization tips for Facebook Shops listings

  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.

Facebook Shops FAQ

  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.

About Facebook Shops

Facebook Shops is Meta's storefront feature for businesses, introduced in 2020 and managed in Commerce Manager. It lets a brand publish a browsable product catalog on its Facebook Page and Instagram profile, so shoppers can discover products, open product detail pages and explore collections without searching for the brand's website first.

A single product catalog powers the Shop, product tags in Instagram and Facebook posts, and Meta's catalog-based ads. Shops are meant for physical goods, and the catalog must be owned by the Business Manager account that runs the Shop.

The way purchases work has changed. Meta began phasing out native checkout on Facebook and Instagram in June 2025, so shoppers who want to buy are now sent to the merchant's own website to complete the order. Shops remain a discovery and browsing surface, while payment, order management and returns happen on the retailer's site.

For merchants, the catalog behind the Shop is the whole experience. A store with sizes, colors, changing prices and limited stock needs an automated product feed that keeps titles, images, prices, availability and links in sync. Outdated prices or sold-out items in the Shop lead to disappointed shoppers and wasted clicks, and the same feed quality also affects tagged posts and catalog ads that read from the same catalog.

See which
products earn.

Connect your feed and GA4. We show Product Score, 4T, Price War and Broken Size on your own catalog.