BigCommerce Platform

Most BigCommerce merchants eventually need their catalog to show up correctly on channels beyond their own storefront, such as marketplaces, comparison shopping engines, or advertising platforms. Keeping product details, stock levels, and order status accurate across all of these destinations by hand quickly becomes unmanageable as a catalog grows.

• Save time by removing manual exports and spreadsheet edits every time a product, price, or stock level changes.
• Reduce errors that come from copying data between systems by hand.
• Keep listings current so stock and pricing shown elsewhere reflect what is actually in the BigCommerce catalog.
• Scale more easily as the number of products, variants, and sales channels grows.

Feedance connects directly to a merchant's BigCommerce store using an authorized, permissioned connection, the same approach BigCommerce itself recommends for any application that needs programmatic access to store data. No plugin needs to be installed on the storefront theme, and no manual file exports are required.

Once the connection is established, Feedance reads the relevant catalog, inventory, and order data on a scheduled basis and keeps it in sync, so the merchant does not need to trigger updates manually every time something changes in BigCommerce.

Feedance only works with three data entities on any platform it connects to. On BigCommerce, that means:

• Scoped, permissioned access: BigCommerce's API model is built around limiting each connected application to only the scopes it actually needs (for example, read-only access to products versus full read and write access). This is a good practice to keep in mind when reviewing what any connected app, including Feedance, is authorized to access.
• API request limits: BigCommerce enforces hourly and short-window rate limits on API calls, with higher allowances on higher-tier plans. This is a normal part of working with any BigCommerce integration and is one reason scheduled, incremental syncing works better than constant polling.
• Variants and options model: BigCommerce distinguishes between product options (like size or color) and the resulting variants, each of which can carry its own SKU, price, and stock level. Feed tools need to handle this structure correctly so that each sellable variant is represented accurately rather than only the parent product.
• Multi-storefront setups: Larger BigCommerce merchants sometimes run multiple storefronts or channels from a single catalog. It is worth confirming which store or channel a feed connection is pulling from when more than one is in use.

1. Create a Feedance account or log in to an existing one.
2. Choose BigCommerce as the platform when adding a new store connection.
3. Authorize Feedance to access the BigCommerce store when prompted, granting the permissions needed for products, inventory, and orders.
4. Wait for Feedance to complete the first sync, which pulls in the current catalog, stock levels, and order data.
5. Review the imported data, then configure and publish feeds to the desired destinations.

Feedance syncs BigCommerce data on a regular schedule rather than instantly with every single change, so that updates to products, stock, and orders are reflected without placing unnecessary load on the BigCommerce API. Exact sync frequency can depend on the plan and the volume of data involved; merchants with time-sensitive stock changes should confirm current sync timing for their account.

1. Write clear, descriptive product titles and descriptions in BigCommerce, since these often carry directly into external feeds.
2. Keep product images high-quality and correctly assigned to each variant where relevant.
3. Make sure stock levels are kept accurate in BigCommerce so feeds do not advertise items that are actually unavailable.
4. Organize products with consistent categories and attributes to make feed rules and mappings easier to maintain.
5. Periodically review which variants are active versus disabled so discontinued options do not linger in feeds.