datawebotFacebook Shops data: catalogs, storefronts and product details
Separate Meta catalogs, dated Shops checkout guidance and Marketplace partner listings. Track each detail by surface, market and destination.
Commerce Manager catalogs are seller-managed product data
Meta Blueprint’s public product-catalog course, checked October 4, 2026, describes Commerce Manager catalogs as tools for organizing, managing, updating and promoting product details across Meta technologies. That supports the catalog’s role as seller-managed product data; the course is not a current API field specification, public feed, permission grant or guarantee that every catalog item appears on every surface.
Scroll to compare →
| Catalog context | Useful data to preserve when supplied | What it does not establish |
|---|---|---|
| Commerce Manager catalog | A seller-managed source of product information used across Meta technologies, as described by Meta Blueprint. | That a given item is published, eligible, visible, available or identical across surfaces. |
| Seller-provided item and variant data | Seller-native item identifier if supplied; product and variant/group relation if supplied; title, description, image or destination reference; stated price/currency, availability, category/brand, market and export time. | These are proposed data-model fields, not Meta API field names. Do not fill absent values or infer a full variant matrix. |
| Catalog-to-surface relationship | Record a relationship only when a seller export or an explicit surface reference supports it. | Use of catalogs across Meta technologies does not prove the same item is visible on Facebook Shops, Instagram or Marketplace. |
Facebook Shops checkout guidance is a dated platform statement
Meta Business Help was reviewed on September 27, 2026 and stated that Shops use website checkout as of September 2025. A direct recheck on October 4, 2026 redirected to a login/block page, so this page treats the statement as historical Meta guidance and does not claim that it verifies every current account, product, surface, market or checkout route.
Scroll to compare →
| Source context | What the dated statement says | How to record a separate observation |
|---|---|---|
| Meta Business Help · statement about changes as of September 2025 | The earlier review read the article as saying Shops use website checkout as of September 2025. | Attribute the timing to Meta Help; do not restate it as a newly confirmed universal route. |
| Access recheck · October 4, 2026 | The official Help article redirected to a login/block page during the current review. | When a separately authorized observation is made, record its surface, market, displayed purchase label, destination and date. |
| Checkout eligibility and destination | The accessible evidence does not establish current account- or market-specific eligibility. | Keep the observed action/destination attached to that observation; do not infer it from catalog presence. |
Record a Shop product detail as a surface-specific observation
A consumer-facing product detail is evidence about what was displayed on that surface at that time. It is not a substitute for the seller’s catalog or a guarantee that all options and stock are exposed.
Scroll to compare →
| Observed surface | Details worth retaining when visible | Limit of the observation |
|---|---|---|
| Facebook Shop product detail | Shop/Page reference; item URL; visible title and image; selected option; displayed amount and currency; stated availability; purchase label and destination; market/locale and observation time. | A selected option is not the full variant matrix; a label is not exact warehouse quantity, delivered price or seller-private SKU. |
| Instagram product tag or shoppable post | Post/Reel reference; product reference only if explicit; tagged option if shown; surface, market and observation time. | A tag does not establish publication in a Facebook Shop. Matching title or image alone is not a product join. |
| Catalog item supplied by seller | Seller’s own identifier and variant relation, plus fields present in the authorized file and its timestamp. | Do not treat seller-supplied data as a live observation of what a shopper can see. |
Join catalog, Shop and Instagram records only on explicit references
Synthetic example only; no live seller, product or collection is represented. Keep the seller’s input and each surface observation as separate records. The example labels below are placeholders, not Meta field names.
Scroll to compare →
| Synthetic record | Illustrative value | Join rule |
|---|---|---|
| Seller catalog row | Seller-provided item `SYNTH-ITEM-A`; optional variant group `SYNTH-GROUP-A` if the source supplies it. | Preserve the seller’s identifiers as given; an absent ID or relation stays unknown. |
| Facebook Shop detail observation | At synthetic time `T1`, a selected option and displayed purchase label/destination are recorded with the observed market. | Join to the catalog row only if an explicit reference supports that link; retain the surface and time. |
| Instagram product tag | At synthetic time `T2`, an explicit product reference may point to the same seller item. | If the tag does not provide an explicit reference, do not infer a join from name or image. |
| Historical checkout context | Meta Help previously stated website checkout as of September 2025; the article was login/block-gated on October 4, 2026. | Keep the dated statement separate from any observed destination, which must be recorded for its own authorized observation. |
Marketplace partner inventory is a separate listing path
Meta’s November 13, 2025 Marketplace update described eBay and Poshmark partner inventory in Marketplace. It said partner listings are marked, Marketplace detail pages show listing and seller information, and buyers continue to the partner site for checkout. This is a dated Marketplace partner path, not a Facebook Shop catalog or Shops checkout rule.
Scroll to compare →
| Marketplace record | Dated source context | Keep separate from |
|---|---|---|
| Marketplace listing from a partner | Meta’s November 2025 update names eBay and Poshmark inventory and says partner listings are marked in Marketplace. | A seller’s Commerce Manager catalog row or Facebook Shop product detail. |
| Marketplace detail and purchase path | The same announcement describes listing/seller details on Marketplace and partner-site checkout. | A claim that every Marketplace item, partner or market uses this route today. |
| Local Marketplace listing | A Marketplace listing with its own listing, seller, location and transaction context. | A Facebook Shop item; do not join by title or image alone. |
Use access guidance within its verified source limits
Meta’s accessible public explainer “How We Combat Scraping,” published April 15, 2021 and reopened October 4, 2026, says automated collection from Facebook without Meta’s permission violates its terms; public viewability alone does not authorize automated collection. This is an attributed statement from that older explainer, not a current review of the separate Automated Data Collection Terms.
Scroll to compare →
| Meta source | Review result | What this guide says |
|---|---|---|
| How We Combat Scraping · April 15, 2021 | Accessible on October 4, 2026; the article describes Meta’s position on unauthorized automated collection. | Date and attribute the warning to the explainer; do not present it as newly updated Terms text or legal advice. |
| Automated Data Collection Terms | The official Terms destination was login/block-gated on October 4, 2026. | Link the official page for direct review; do not claim current clauses were reviewed or paraphrase them. |
| Catalog exports and integrations | The accessible sources did not establish a public catalog feed or a current field-level API schema. | A seller-provided export or documented route still requires the seller’s authority and permission applicable to that use; it does not create access to other Meta surfaces. |
Questions about catalogs, Shops and Marketplace
These answers keep the three source models separate and attach each statement to its date and evidence.
Scroll to compare →
| Question | Answer | Record boundary |
|---|---|---|
| Is a Commerce Manager catalog the same thing as a Facebook Shop? | No. Meta Blueprint describes catalogs as seller tools for managing product details across Meta technologies; a Shop is a separate consumer-facing surface. | Catalog presence does not establish Shop publication or visibility. |
| What did Meta say about Shops checkout in September 2025? | The Help article previously reviewed September 27, 2026 said Shops use website checkout as of September 2025; it was login/block-gated in the October 4 recheck. | Treat the statement as historical and record a specific observed label/destination separately. |
| Are Marketplace partner listings Facebook Shop products? | No. Meta’s November 13, 2025 update describes Marketplace partner inventory and partner-site checkout as a separate listing path. | Keep Marketplace partner/listing identity and transaction context separate. |
| Does an Instagram product tag prove a Facebook Shop match? | No. Use an explicit product reference if one is shown; a similar name or image is not enough. | Keep unmatched records separate. |
| Does a public Shop URL by itself authorize automated collection? | Meta’s April 15, 2021 anti-scraping explainer says public visibility alone does not authorize automated collection without Meta’s permission. The current Terms page was inaccessible in the October 4 review. | Attribute the dated statement and do not imply current Terms clauses were reviewed. |
Related data concepts
These references explain adjacent surfaces, authorized-route distinctions and provenance; they do not assert a Meta integration or collection permission.
Scroll to compare →
| Topic | Reference | How it relates |
|---|---|---|
| Instagram Shop and tagged products | Instagram Shopping source guide | Keep tags separate from Facebook Shop details unless an explicit product reference connects them. |
| APIs and storefront observations | Web scraping versus official APIs | Choose only a currently documented route and authorization appropriate to the use. |
| Missing values and provenance | Data documentation | Keep source, surface, market and observation date with each value; retain unknowns. |
Content reviewed 2026-10-07.