How to Connect BigCommerce to Facebook

Three ways to connect BigCommerce to Facebook

1. BigCommerce's own channels and apps

BigCommerce's free Meta for BigCommerce channel, added from Channel Manager, syncs your catalog to Meta for Facebook and Instagram shopping and ads and installs the Meta Pixel. It covers Facebook and Instagram only.

2. Export a file yourself

BigCommerce can export your products to a CSV (Products > Export), but the file uses BigCommerce's own template and columns - not the field names and formats Facebook expects - and it's a snapshot, so it's out of date as soon as a price or stock level changes. If you go this way, start from our free Facebook Catalog CSV Template Generator so at least the columns are right.

3. A store catalog connector

A connector reads your BigCommerce catalog through BigCommerce's REST API, using a read-only API account you create in your control panel, and builds the Facebook feed for you. BigCommerce can notify a connector through webhooks when a product, price, or stock level changes, so updates arrive within moments - and only the products that changed need to be read again. The connector hosts the feed at a URL that Facebook reads on a schedule, and one connection can usually feed several platforms at once.

What Facebook needs

• A Meta business portfolio with access to Commerce Manager, where your catalog lives.
• Nine fields per product: id, title, description, availability (in stock or out of stock), condition, price, link, image_link, and brand.
• Images in JPEG or PNG, at least 500 x 500 pixels and up to 8 MB.
• A data feed - a file you upload, or a URL that Commerce Manager fetches hourly, daily, or weekly.

How your BigCommerce fields map to Facebook

The table above shows where each Facebook field comes from in your BigCommerce catalog. A few BigCommerce details need extra care:

• Variants: each combination of options (Navy / M, Navy / L...) should become its own listing with its own price, stock, SKU, and image, grouped under the product with a shared item_group_id. Name your options Color and Size so they're read as color and size, and leave out variants with purchasing disabled.
• Product type: BigCommerce categories are what you map to a Google product category. Stores often reuse a name under different parents (Men > Shirts, Women > Shirts), so map by the full path, and skip shopping groups like "Sale" or "New".
• Identifiers and condition: BigCommerce has Brand, GTIN, UPC, MPN, and Condition fields - fill them in and they come straight across. Products without a brand need a default, usually your store's name.
• Clothing details: BigCommerce has no gender or age group fields, and Google and Facebook require them - with a color and a size - on clothing and shoes. Add them as custom fields, or set them by product name if your tool supports it.
• Prices and tax: if your store enters prices with tax included, check what Facebook expects for each country - US listings, for example, are shown without tax.

Step by step

1. Get your Facebook account ready - see "What Facebook needs" above.
2. Create a read-only API account. In your BigCommerce control panel, go to Settings > Store-level API accounts and click Create API account. Set Products and Information & settings to Read-only, leave the rest at None, and save. Copy the API path, access token, and client secret - BigCommerce shows them only once.
3. Map your product types to Google product categories. Facebook needs to know what each product is. Map each of your BigCommerce categories (shown as full paths like "Men > Shirts") to one category from the Google product category list once, and every product with that value is categorized from then on.
4. Add the data feed in Commerce Manager. Open your catalog, go to Data sources, add items with a data feed, choose a URL, and paste your feed URL with its login. Pick a daily schedule.
5. Check the first import. Review the errors Facebook reports and fix them in BigCommerce, not in the feed - your store stays the single source of truth.

Common BigCommerce to Facebook problems

• Hidden, disabled, and price-hidden products. Only visible products a shopper can buy at a shown price belong in the feed - hide a product, turn off purchasing, or hide its price in BigCommerce and it should drop out.
• Digital products and headless storefronts. Digital products aren't sold through shopping catalogs. If shoppers buy on a separate headless storefront, product links must point there, not to your BigCommerce store address.
• Items rejected for a missing brand. Facebook requires brand on every item - set a default if your store doesn't record one.
• Backorders. Facebook has no "preorder" value, so backordered items need to be sent as in stock or out of stock. Facebook Catalog Feed Errors, Fixed covers the rest.

Related guides

For more on Facebook itself, see How to Create a Facebook Catalog Without Shopify. On a different store platform? WooCommerce to Facebook, PrestaShop to Facebook, Wix to Facebook, Square to Facebook, Squarespace to Facebook, and Webflow to Facebook cover the same setup for those stores.