Facebook Product Catalog Feed
A Meta Product Catalog feed is an XML file that lists your WooCommerce products (id, title, price, stock, image, link, etc.). Meta fetches it on a schedule to keep your catalog always in sync, so you can run:
- Dynamic Product Ads (DPA) / catalog remarketing
- Catalog Sales campaigns
- Meta Shop / product sets / retargeting audiences
How to upload it to Meta (high level):
- Create / open your Catalog in Meta Commerce Manager.
- Go to Data sources → Add items → Data feed.
- Choose Scheduled feed, paste the feed URL generated by the plugin (or upload manually if you prefer).
- Set a schedule (daily/hourly) that matches how often you regenerate the feed.
- After the first fetch, check Diagnostics for missing fields, disapprovals, or image/link issues.
Feed setup screen (everything in your screenshot)
Basic
- Feed name
Internal label. Only for you. - Feed type (Facebook Product Catalog)
Selects the correct format/fields for Meta catalogs. - Feed file name
Becomes the exported feed file name (and usually the URL path). Keep it simple and stable (don’t rename it later unless you also update Meta). - Regeneration frequency + start time
Controls when the plugin rebuilds the feed file.
Tip: set it a bit before Meta’s scheduled fetch time, so Meta always pulls fresh data.
Multicurrency
If your store uses a currency switcher, this section helps the plugin export correct prices/currency in the feed.
- You’ll see a list of supported multicurrency plugins and whether they’re detected.
- Use it so Meta receives consistent prices (and you don’t end up with mixed currencies in the catalog).
ID settings (very important)
- ID (the product identifier used in the feed)
Pick what Meta will treat as the product “id” (commonly product ID or SKU). - Prefix / suffix
Adds text before/after the ID (useful when you run multiple shops/countries and need globally unique IDs).
Why it matters: Meta matches catalog items to events using IDs (ex: your pixel’s content_ids). If IDs don’t match, DPA/remarketing won’t work correctly.
Prices & tax
Controls what price Meta receives.
- Which price to export (regular vs sale)
- Tax handling (include/exclude tax depending on how you want prices represented)
- Any extra price-related rules shown there (ex: using Woo tax settings)
Tip: keep it consistent with what users see on the product page to avoid disapprovals or confused reporting.
Inventory + backorders
- Inventory / availability rules
Controls how products show as in stock / out of stock. - Backorders behavior
Decide how backorder items should be exported (for Meta, availability values must be valid and consistent).
Filters (control what goes into the feed)
Use these to keep the catalog clean and compliant.
Common uses:
- Include only specific categories
- Exclude certain product types
- Exclude out of stock
- Exclude products without required data (ex: no image)
Buttons like Select Product Categories / Select Product Types help you build the feed scope fast.
Smart tags
Adds extra tagging/logic to help with segmentation. Typical use:
- Mark items for promo sets, seasonal groups, special labels, etc.
Product titles
Options that control how the title is built (and how much detail is included).
Typical choices:
- Keep titles clean (avoid excessive variation noise)
- Optionally add useful identifiers (like size/color) when needed
Product descriptions
Choose what text becomes the catalog description (short description, full description, etc.).
Tip: keep descriptions readable and avoid heavy formatting—catalog platforms often truncate.
Product images
Controls which images Meta receives:
- Use featured image vs variation image
- Include extra gallery images (when available)
- Fallback behavior (if a product is missing an image)
Tip: image quality is a top reason for catalog issues—make sure every included product has a valid image URL.
Product condition
Sets the exported condition (new/used/refurbished).
Most WooCommerce stores should use New.
Google taxonomy + product type
Even on a Meta feed, taxonomy/product_type settings help platforms categorize items.
- Google taxonomy: choose a taxonomy path (global or per-product rules).
- Product type: often mapped from your WooCommerce categories or a custom value.
Brand / GTIN / MPN / Identifier exists
These fields improve matching and approval rates across platforms (and are required in some scenarios).
- Brand: define where it comes from (custom brand field, Woo brands taxonomy, autodetect, fallback value).
- GTIN: optional for many stores; required for many standard retail products.
- MPN: manufacturer part number (often SKU/ID if that’s what you have).
- Identifier exists: use “no” for custom-made items without GTIN/MPN/brand identifiers.
Custom labels (0–4)
These are for segmentation in campaigns/product sets (Meta + other platforms).
Examples:
custom_label_0: “high_margin”custom_label_1: “sale”custom_label_2: “top_seller”custom_label_3: “season_summer”custom_label_4: “price_50_100”
In the UI you map each label to an attribute/category/custom field/value rule.
UTM parameters (track catalog traffic)
- Enable UTM for this feed
Adds UTMs to product links so clicks from catalog ads show up cleanly in GA4/analytics.
You can usually pick:
- a template (recommended)
- or define a custom set of UTMs
Tip: keep UTMs consistent with your ad platform naming, and don’t double-append UTMs if your ads already add them.
Metadata for this feed
Extra feed-level metadata fields/options. Use this only if you know your platform expects/benefits from it (otherwise leave defaults).