Meta Commerce Manager CSV Export Basics
> A Meta Commerce Manager CSV is a structured product data file formatted to Meta's catalog data specification — exported by FeedBridge as a live feed format — that submits product identity, pricing, availability, and attribute data to Meta's Commerce Manager platform, enabling product listings across Facebook Shops, Instagram Shopping, and Meta's dynamic product surfaces.
---
What Is a Meta Commerce Manager CSV Feed?
A Meta Commerce Manager CSV feed is a tabular product data file that conforms to Meta's catalog feed specification. Each row represents one product; each column represents a product attribute. The file is uploaded to Meta Commerce Manager — Meta's centralised product catalog platform — where it is validated and used to power product listings on Facebook Shops, Instagram Shopping, and Meta's catalog-powered advertising surfaces.
Meta Commerce Manager is the required gateway for all product catalog activity across Meta's platforms. It ingests product feeds in several accepted formats including CSV, TSV, XML (RSS/ATOM), and Google Sheets, and distributes approved product data across Facebook and Instagram commerce surfaces. [web:56] For merchants who sell or advertise on Facebook or Instagram, a correctly structured and current Commerce Manager catalog is the foundational data infrastructure.
The CSV format is one of the most widely used submission methods because it is compact, straightforward to generate programmatically, and easily inspected and validated before submission. FeedBridge exports Meta Commerce Manager CSV as a live feed format, generated from the same normalised product catalog that powers the ACP JSON-LD feed, UCP Interactive Protocol, Google Merchant Center CSV, and Amazon Inventory File TSV outputs. This means that enrichment applied to the product record in FeedBridge — AI-enhanced titles, descriptions, category normalisation, and structured attributes — benefits the Meta CSV export at no additional effort.
---
Required Fields in the Meta Commerce Manager CSV
Meta's catalog data specification defines a set of required fields that every product record must include to be approved in Commerce Manager. Products missing required fields are rejected or disapproved and will not appear on any Meta shopping surface. [web:50][web:57]
For Facebook Shops, Instagram Shopping, and catalog-powered ads — the standard surfaces for most merchants — the required fields are:
| Attribute | Meta Field Name | Notes | |---|---|---| | Unique product identifier | `id` | Merchant-assigned; must be stable across feed updates | | Product name | `title` | Plain text; max 150 characters recommended | | Product description | `description` | Plain text; max 5,000 characters | | Availability | `availability` | `in stock`, `out of stock`, or `preorder` | | Condition | `condition` | `new`, `refurbished`, or `used` | | Product page URL | `link` | Direct URL to the product's landing page | | Primary image | `image_link` | URL of the main product image | | Price | `price` | Numeric with ISO 4217 currency code (e.g., `29.99 USD`) | | Brand, MPN, or GTIN | `brand` / `mpn` / `gtin` | At least one unique product identifier required |
For Facebook Marketplace and Page Shop use cases, two additional fields become required: `inventory` (current stock count) and `google_product_category` (Google's product taxonomy path, which Meta also uses for category classification). [web:54][web:57]
---
Recommended Fields That Improve Catalog Performance
Beyond the required fields, Meta's catalog specification includes optional attributes that meaningfully improve catalog quality for variant products, category-specific listings, and promotional pricing scenarios. [web:55][web:59]
| Attribute | Meta Field Name | Why It Matters | |---|---|---| | Item group ID | `item_group_id` | Links variant products; Meta maps this to `retailer_product_group_id` for dynamic ads | | Colour | `color` | Variant differentiator; used in dynamic ads and product filtering | | Size | `size` | Variant differentiator for apparel, footwear, and other sized products | | Sale price | `sale_price` | Communicates promotional pricing; requires `sale_price_effective_date` | | Sale price effective date | `sale_price_effective_date` | ISO 8601 date range bounding the promotional period | | Product category | `google_product_category` | Google taxonomy string or ID; used by Meta for category classification | | Product type | `product_type` | Retailer-defined category path for internal product set organisation | | Additional images | `additional_image_link` | Up to 20 comma-separated additional image URLs | | Material | `material` | Product material description (e.g., leather, cotton, denim) | | Pattern | `pattern` | Pattern or graphic print descriptor | | Gender | `gender` | `male`, `female`, or `unisex` | | Age group | `age_group` | `newborn`, `infant`, `toddler`, `kids`, or `adult` | | Custom labels | `custom_label_0` through `custom_label_4` | Retailer-defined labels for product set segmentation; max 100 characters each |
The `item_group_id` field is particularly important for merchants with variant products. Meta uses it to group all variants of a product under a single parent identifier — a t-shirt available in four colours and three sizes would have twelve rows in the feed, each with the same `item_group_id`. For dynamic catalog ads, Meta selects the most relevant variant to display based on buyer signals, using the `item_group_id` to understand which rows belong together. [web:55]
---
How FeedBridge Generates the Meta Commerce Manager CSV
FeedBridge generates the Meta Commerce Manager CSV from the normalised, enriched product record in the merchant's FeedBridge catalog. The generation process involves field mapping — aligning each FeedBridge internal field to the corresponding Meta attribute name and format — and format validation to ensure values conform to Meta's accepted field formats before export.
The following mapping shows how FeedBridge fields correspond to Meta Commerce Manager attribute names:
| FeedBridge Field | Meta Attribute | Notes | |---|---|---| | `item_id` | `id` | Direct mapping | | `title` (AI-enhanced) | `title` | AI-enhanced title maps to Meta title field | | `description` (AI-enhanced) | `description` | AI-enriched description maps to Meta description | | `product_url` | `link` | Direct mapping | | `image_url` | `image_link` | Primary image maps to Meta primary image | | `price` + `currency` | `price` | Combined per Meta format (e.g., `29.99 USD`) | | `availability` | `availability` | Mapped to Meta accepted values (`in stock` / `out of stock`) | | `brand` | `brand` | Direct mapping | | `gtin` | `gtin` | Direct mapping | | `mpn` | `mpn` | Direct mapping | | `sale_price` | `sale_price` | Direct mapping with currency | | `sale_price_start_date` + `sale_price_end_date` | `sale_price_effective_date` | Combined as ISO 8601 range per Meta format | | `category` (normalised) | `google_product_category` | FeedBridge taxonomy normalisation outputs Google Product Taxonomy-compatible paths used by Meta | | Variant attributes | `item_group_id`, `color`, `size` | Variant structure maps to Meta variant fields |
One formatting difference to note between Meta and Google Merchant Center CSVs: Meta uses `in stock` (with a space) rather than `in_stock` (with an underscore) for the availability field. FeedBridge's format normalisation handles this distinction automatically in the Meta-specific export, so the same source availability value in FeedBridge produces correctly formatted output for both GMC and Meta CSV.
---
Feed Hosting, Scheduling, and Delivery
FeedBridge hosts the Meta Commerce Manager CSV on CDN-backed URLs unique per brand, following the same hosted feed infrastructure that applies to all FeedBridge feed formats. This means the Commerce Manager account can be configured to fetch the feed from a stable, hosted URL on a scheduled basis — rather than requiring manual CSV file uploads each time the catalog changes.
Meta Commerce Manager supports scheduled feed fetches from a URL, allowing the merchant to register the FeedBridge-hosted feed URL in Commerce Manager once and have Commerce Manager pull updates automatically on the configured schedule. [web:50]
FeedBridge's feed scheduling feature supports configurable auto-refresh intervals, ensuring the Meta CSV stays current with catalog changes — price updates, availability changes, new products, and removed products. Feed health monitoring continuously checks for dead product URLs and validity issues, with feed alert preferences sending email notifications when stale feeds, dead URLs, or low-validity states are detected.
For Meta specifically, feed freshness matters because Commerce Manager has its own staleness detection — a feed that has not been updated within the expected refresh window will be flagged in Commerce Manager's feed health dashboard. Scheduled refresh from FeedBridge's hosted URL prevents this by keeping the feed current within the merchant's normal catalog change cycle.
---
Meta CSV vs Other FeedBridge Feed Formats
The Meta Commerce Manager CSV is one of five feed formats FeedBridge generates from the same product catalog. Understanding what it covers relative to the other formats clarifies its scope:
| Dimension | Meta CSV | GMC CSV | ACP JSON-LD | |---|---|---|---| | Channel | Facebook Shops, Instagram Shopping | Google Shopping, Google AI Mode | ChatGPT Shopping, ACP surfaces | | Format | CSV (tabular) | CSV (tabular) | JSON-LD (structured linked data) | | Unique identifier | At least one of brand, MPN, or GTIN | GTIN required for branded products | GTIN + MPN both supported | | Variant grouping | `item_group_id` | `item_group_id` | `variant_dict` mapping | | Sale pricing | `sale_price` + `sale_price_effective_date` | `sale_price` + `sale_price_effective_date` | `sale_price` + start/end date fields | | AI enrichment fields | Not in Meta spec | Not in GMC spec | Intent tags, Q&A, personas, use cases | | Trust signals | Not in Meta spec | Not in GMC spec | `accepts_returns`, `return_deadline_days`, `is_digital` | | Availability format | `in stock` (space) | `in_stock` (underscore) | `in_stock` (underscore) |
The Meta CSV and GMC CSV share similar structures because Meta's catalog specification was originally modelled closely after Google's product data specification. The most important practical difference for feed generation is the availability field format — `in stock` vs `in_stock` — which FeedBridge handles automatically per format. [web:57]
---
Custom Feed Templates for Meta
FeedBridge's Custom Feed Templates feature allows merchants to apply custom field mappings and filters to the Meta CSV export for specific Commerce Manager account configurations. This is useful in several scenarios:
- Custom label population: Merchants who use `custom_label_0` through `custom_label_4` for product set segmentation (e.g., margin tier, season, promotion eligibility) can configure custom label mappings from FeedBridge catalog fields or tags.
- Category override: Merchants whose products have specific Meta category requirements beyond the default taxonomy normalisation output can apply category mapping overrides via Custom Feed Templates.
- Product filtering: Merchants who want to exclude specific product categories, price ranges, or availability states from the Meta feed can apply feed-level filters in Custom Feed Templates without modifying the underlying product catalog.
Why It Matters for Merchants
Meta Commerce Manager is the required data gateway for product listings on Facebook and Instagram. A correctly structured, current, and complete Commerce Manager CSV feed is the prerequisite for any product visibility on Meta's commerce surfaces. Disapproved or incomplete products are excluded from all Meta shopping surfaces — regardless of the merchant's ad spend or account standing.
For merchants already investing in AI enrichment for their ACP or GMC feeds, FeedBridge's Meta CSV export means that enrichment work extends to Meta surfaces at no additional effort. AI-enhanced product titles and descriptions, normalised category paths, structured variant attributes, and current sale pricing fields all map into the Meta CSV export from the same underlying enriched product record. The result is a higher-quality Meta Commerce Manager feed than a basic product data export would produce — with better title and description quality, complete variant structure, and current promotional pricing.
The combination of CDN-hosted feed URLs, configurable scheduling, and feed health monitoring ensures that the Meta Commerce Manager CSV stays current and valid without requiring manual intervention in the merchant's day-to-day workflow.
---
FeedBridge Relevance
FeedBridge exports Meta Commerce Manager CSV as a live feed format, hosted on CDN-backed URLs with configurable scheduling and feed health monitoring. The export is generated from the normalised, AI-enriched product record — mapping FeedBridge fields to Meta Commerce Manager attribute requirements including title, description, price with currency, availability (formatted to Meta's `in stock` convention), brand, GTIN, MPN, sale pricing with date range, variant grouping via `item_group_id`, and Google Product Taxonomy-style category paths from FeedBridge's taxonomy normalisation pipeline.
Auto field mapping handles 13 common columns during catalog import, aligning source data to Meta field requirements from ingestion. Custom Feed Templates allow custom field mappings and filters for Meta-specific account configurations, including custom label population and product set filtering. Feed Alert Preferences and Feed Health Monitoring keep the Meta feed current and valid.
---
Frequently Asked Questions
Q: Do I need to upload the Meta CSV manually to Commerce Manager, or can FeedBridge deliver it automatically? A: FeedBridge hosts the Meta Commerce Manager CSV at a stable, CDN-backed URL per brand. You register that URL once in Meta Commerce Manager as a scheduled data source. Commerce Manager then fetches the feed from FeedBridge's hosted URL on your configured schedule — no manual file upload required after the initial URL registration.
Q: What is the difference between `brand`, `gtin`, and `mpn` in the Meta CSV — do I need all three? A: Meta requires at least one unique product identifier — `brand`, `gtin`, or `mpn` — per product. You do not need all three, though providing all that are available improves product identity accuracy. GTIN is the strongest identifier (a globally registered barcode), MPN is manufacturer-specific, and brand alone is the weakest. FeedBridge maps all three fields from the product record into the Meta CSV export wherever they are populated.
Q: Why does the Meta CSV use `in stock` with a space when Google uses `in_stock` with an underscore? A: Meta and Google use slightly different accepted values for the availability field — this is a specification difference between the two platforms' catalog formats. FeedBridge's format normalisation handles this automatically per format: the same `in_stock` availability value in the FeedBridge product record is exported as `in stock` in the Meta CSV and as `in_stock` in the Google Merchant Center CSV, with no manual adjustment required.
Q: How do I handle variant products in the Meta Commerce Manager CSV? A: Variant products are handled by assigning the same `item_group_id` value to all rows that are variants of the same base product, and populating variant-specific fields (`color`, `size`, etc.) differently for each row. FeedBridge maps its internal variant structure to `item_group_id` and the relevant variant attribute fields in the Meta CSV export. Meta uses the `item_group_id` grouping to understand which rows are variants and to select the most relevant variant for dynamic product surfaces.
Q: Are ACP enrichment fields like intent tags and Q&A included in the Meta CSV? A: No. ACP enrichment fields — intent tags, persona arrays, use cases, Q&A pairs, and voice snippets — are ACP-specific extensions not included in Meta's catalog specification. They are present in the ACP JSON-LD feed and UCP endpoint responses, which serve AI agent surfaces. The Meta CSV export maps to Meta's standard catalog attribute set. However, the underlying enrichment work improves the AI-enhanced title and description fields, which do map into the Meta CSV and directly affect catalog quality on Meta's surfaces.
---
Related Topics
Parent hub: Product Feeds and Commerce Data — Feed Formats
Related concepts:
- ACP Feed JSON-LD Explained
- Google Merchant Center CSV for AI Shopping Readiness
- Amazon Inventory TSV Export Basics
- Hosted Feed URLs Explained
- Product Attributes That Improve Discoverability
Breadcrumb:
---
Source Documentation
| Claim | Source | Source Class | Reference | |---|---|---|---| | Meta Commerce Manager CSV: live feed format in FeedBridge | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Hosted Feed URLs, Feed Scheduling, Feed Health Monitoring, Custom Feed Templates — live features | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Auto field mapping: 13 common columns including SKU, title, price, GTIN, MPN, images | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Required fields for Meta catalog: id, title, description, availability, condition, link, image_link, price, and at least one of brand/mpn/gtin | Meta Commerce Manager Product Data Specification | T2 – Meta | facebook.com/business/help/120325381656392 | | Marketplace/Page Shop additionally requires inventory and google_product_category | Meta Commerce Manager Product Data Specification | T2 – Meta | help.godatafeed.com/hc/en-us/articles/360048361091 | | item_group_id maps to retailer_product_group_id; Meta selects variant via pixel/app signals | Instagram Marketplace Product Feed Specifications | T2 – Meta | feedonomics.com/supported-channels/instagram-marketplace-feed-specifications | | Meta accepted formats: CSV, TSV, XML (RSS/ATOM), Excel (XLSX), Google Sheets | Facebook Product Feed Specifications 2026 | T2 – Meta Ecosystem | blog.adnabu.com/facebook/facebook-product-feed-specifications | | Meta and GMC required field overlap; Meta uses `in stock` (space); availability format difference | Product Feed Specs for Every Major Platform (Marpipe) | T2 – Ecosystem | marpipe.com/blog/product-feed-specs |