BigCommerce product feed for Meta & Google (2026)

Here is the fact that quietly trips up most BigCommerce product feed setups: BigCommerce's native Google Shopping channel does not hand you a copyable feed URL. You connect it in the Channel Manager, it generates the feed internally, and it submits that feed to Merchant Center on roughly a 24-hour sync. There is nothing to copy and paste. So if you came looking for "my BigCommerce product feed URL" (to point an ad catalog, a price-comparison engine, or an enhancement tool at it), the native channel is not where you find it. Once you know which of the four paths you are actually on, the setup stops being confusing. This walks through each one, the BigCommerce-specific gaps that get feeds rejected, and where an enhancement layer fits.

The ways a BigCommerce store gets a Meta or Google feed

Every BigCommerce store reaches Google and Meta through one of the paths below, and only some of them give you a feed URL you control. This one table is the whole mental model:

The honest headline: the modern native channel app is the lowest-friction path, and for a store that just needs a standard catalog in one Google or Meta account it is genuinely enough. But it is also the path that gives you no feed URL. The moment you need a portable URL, you move to a third-party feed app (or, if your store still has it, the legacy export). This is the same native-channel-versus-feed-URL split that Shopify stores hit, described in the Shopify product feed setup guide.

Channel by channel: what BigCommerce actually connects

Each native connection is a sync into the destination platform, not a copyable URL. Here is the mechanism and the timing for each, plus the feed-URL alternative when you need one.

Google Shopping connects through the native channel app in the Channel Manager: you complete domain verification and account linking, and from then on BigCommerce generates a product feed from your catalog and submits it to Merchant Center, syncing every 24 hours by default. There is no feed URL in this path. The Emberfeed-relevant alternative, when you want a feed URL into Google (a scheduled-fetch URL in Merchant Center), is to get that URL from a feed app or the legacy export, not from the native channel app.

Facebook & Instagram by Meta connects as a free integration that syncs your BigCommerce catalog into Meta so products can sell on Facebook and Instagram, managed from the BigCommerce control panel. In Commerce Manager this shows up as a partner-platform connection that imports and auto-syncs your catalog on a regular basis, not a scheduled-fetch feed URL. When you instead want a feed URL into Meta (create the catalog manually and add a data feed on a scheduled fetch), that URL again has to come from a feed app or an Emberfeed-served URL. Meta advises not connecting a partner platform at the same time as a manual feed, to avoid double-management.

Feedonomics Surface: the BigCommerce-owned self-serve option

Because BigCommerce owns Feedonomics, it now sells a feed manager directly inside the Channel Manager. There are two tiers, and they are very different products.

Feedonomics Surface (self-serve)

Surface is the self-serve product, sold through BigCommerce and accessed from the Channel Manager. It launched on October 14, 2025 as a self-service feed management solution that lets merchants create, manage, and synchronize feeds without deep technical knowledge. The current product page lists channels Google, Meta, Microsoft, TikTok, and Pinterest (the launch announcement named Google and Meta only, so read it as a launch that has since expanded), with published pricing tiers:

• Basic: free for up to 100,000 SKUs with 2 connections.
• 29 USD/mo: up to 1K SKUs and 2 connections.
• 49 USD/mo: up to 10K SKUs and 4 connections.
• 89 USD/mo: up to 30K SKUs and 8 connections.
• 199 USD/mo: up to 100K SKUs and 20 connections.
• Managed Service: custom pricing, unlimited SKUs and channels.

Managed Feedonomics (enterprise)

The managed service is the original Feedonomics: enterprise, fully custom-priced by SKU count, channel type, and service level, with a free feed audit as the lead magnet. BigCommerce acquired Feedonomics in July 2021, so this is the BigCommerce-owned heavyweight rather than a neutral third party. The DataFeedWatch alternatives comparison covers the Feedonomics ownership and the managed-versus-Surface split in more depth.

Third-party feed apps (when you need a portable URL)

These are the path that yields a feed URL you can paste anywhere. Each reads your BigCommerce catalog and hosts a feed file. The capabilities below are from each vendor's own listing; for monthly prices, check the app listing or ask the vendor, since they are not quoted here.

• DataFeedWatch connects in a few clicks, generates TXT, CSV, and XML feeds, and provides a link to connect your inventory to sales channels. That feed URL points at Google Merchant Center (Shopping plus dynamic product ads) and the Facebook Product Catalog (dynamic ads, FB Shop, Instagram Shopping), across Google, Facebook, and 2,000+ channels.
• ShoppingFeeder connects a BigCommerce store to 1,000+ channels, including Google Shopping, Facebook and Instagram Shop, Amazon, TikTok Shop, Pinterest, and Bing, plus regional marketplaces and price-comparison sites.
• FeedGeni, Facebook & Google Shopping Feed by Socialhead, and Google Shopping Feed by Expert Ecommerce are other feed-generator apps in the BigCommerce marketplace that produce a feed file for the major channels.

The required fields each channel needs

Whichever path produces the feed, the destination spec is the same. For the full per-attribute reference, the build-a-Google-feed-by-hand walkthrough goes attribute by attribute. The short version:

• Google Merchant requires 7 on every product: id, title, description, link, image_link, availability, price. Brand, GTIN, and MPN are conditional on identifier logic; google_product_category is optional (auto-classified). Missing identifiers trigger a limited-visibility warning, not an outright rejection.
• Meta catalog needs id, title, description, availability, condition, price, link, image_link, plus brand, GTIN, or MPN. The apparel attributes (color, size, gender, age_group) are a Google rule, not a Meta one.

The BigCommerce gaps that get feeds rejected

These come specifically from how BigCommerce models product data. Fix them at the source and most feed surgery disappears.

• Native identifier fields exist but sit empty. BigCommerce has dedicated product-editor fields for Brand, UPC/EAN, GTIN, and MPN in the Product Identifiers section, plus SKU. Many merchants leave them blank, and an empty identifier is what flags the product downstream.
• Brand maps from manufacturer or vendor. The feed brand reads from the BigCommerce brand field, but values originally entered as manufacturer or vendor are what become the brand in practice. If brand is blank, set a static value or rename from the manufacturer field.
• GTIN maps from the UPC field. BigCommerce stores the GTIN in the field labelled UPC (or barcode), so the mapping is gtin from upc. If that field is empty for a variant, the identifier is missing.
• Variants become one feed item each. BigCommerce models variants through Options and SKUs, and the Google channel submits each variant as its own item. id maps from variant_id (auto-generated, always populated), and each variant should carry its own SKU, price, image, and a GTIN matching that specific variation.
• Variant images must be set at SKU level. A common failure: variant images do not sync because they only live on the option-level swatch, not the SKU-level image field. Set the image at the SKU level so every item row carries its own picture.
• Custom fields are the home for color, size, and material. BigCommerce supports custom fields on products to store feed attributes like material, pattern, age_group, and gender. But mapping them is manual, and the native channel app has limited custom-attribute mapping, so apparel attributes do not flow on their own.
• The MyBigCommerce-subdomain link trap. A product link can default to the *.mybigcommerce.com subdomain instead of your claimed domain, which causes a Merchant Center URL mismatch. It needs a domain-replace rule to point the link at the real store domain.
• google_product_category is not auto-mapped. There is no native BigCommerce mapping to google_product_category, so you either set it manually or let Google guess (it auto-classifies when the attribute is omitted).
• The image gap (the structural one). Every path here copies the product-photo URL into image_link and moves on. None of them brand, overlay, resize for policy, or composite a designed catalog image. And the channels pull in opposite directions: Meta dynamic and Advantage+ ads benefit from richer creative delivered through additional_image_link, while Google forbids promotional overlays and text on the primary image_link and will strip an overlay it detects. That asymmetry is the one gap no feed tool fills.

How a BigCommerce store gets a genuinely clean feed

Put together, the workflow that avoids disapprovals looks like this:

• 1. Fill the native identifier fields first. Set Brand, the UPC field (GTIN), and MPN in the Product Identifiers section, set images at the SKU level for every variant, and add custom fields for any apparel attributes. A cleaner source means far less downstream surgery.
• 2. Pick the lightest path that yields what you need. A standard catalog into one Google or Meta account: the native channel app, no URL required. A feed URL (for an ad catalog, a comparison engine, or an enhancement tool): one third-party feed app that emits a URL, or the legacy export if your store still has it.
• 3. Enhance the one URL, do not stack apps. Point a single tool at the feed URL to add images, rules, and validation, with the Google-versus-Meta rule front of mind: branded creative goes in additional_image_link and the Meta catalog, never on the Google primary image.
• 4. Validate before you submit. Check required fields per platform, identifier completeness, image specs, and title length locally, before the feed reaches a review queue that can take a day or two to clear.

Where Emberfeed fits

Emberfeed sits at step 3, after a feed URL exists, not instead of your BigCommerce connection. You give it the feed URL that a third-party app or the legacy export already produces, and it enhances it. It cannot read the native channel app's hidden internal feed, it does notreplace BigCommerce's native channel connection, it does not generate a feed from a store with no feed URL, and it is not self-hosted: it imports your URL and serves a new one.

What it adds on top of the feed you already have:

• Rendered images. Design one per-product template, and every image_link in the served feed becomes a rendered image, framed for Meta catalog ads and additional_image_link slots (keeping the Google primary image clean).
• Field rules. Patch brand (fallback from manufacturer), GTIN and identifier_exists, composite titles, custom labels, or the MyBigCommerce-subdomain link at the feed layer, without editing hundreds of BigCommerce products.
• Per-feed validation. Check the output against the live platform spec before you submit it.
• A new served URL that stays current on an hourly refresh, which you paste into Merchant Center or Commerce Manager.

For setup specifics on the BigCommerce side, the BigCommerce integration page walks through importing a feed URL. The WooCommerce product feed guide covers the same enhance-the-URL pattern on the plugin side.

FAQ

Does the native Google channel give me a feed URL?

No. The native Google Shopping channel app generates the feed inside BigCommerce and submits it to Merchant Center on a 24-hour sync, with nothing to copy. For a feed URL, use a third-party feed app or, if your store still exposes it, the legacy Marketing to Google Shopping Feed export.

Is Feedonomics Surface free?

The Basic tier is free for up to 100,000 SKUs with 2 connections. Paid tiers run 29, 49, 89, and 199 USD per month by SKU count and connection count, and the managed service is custom-priced.

Do I still need a feed app if I use Emberfeed?

Emberfeed imports an existing feed URL. On BigCommerce that URL comes from a third-party feed app or the legacy export, since the native channel app does not expose one. They do different jobs: the app produces the URL, Emberfeed enhances it.

Can I put a sale badge on my Google image?

Only on an additional_image_link, never on the primary image_link. Google forbids promotional overlays on the primary image and will strip them. On Meta, badges and lifestyle frames are allowed and tend to help.