BigCommerce price monitoring across every variant

BigCommerce connects through an API account you create in your own control panel, scoped to exactly the access you want to give. Products and variants come in with SKU, UPC, MPN, brand, default price and sale price, so matching starts from real identifiers instead of product titles. Competitor prices, promotions and below-MAP listings flow back. Writing a price into BigCommerce is enabled per rule and never by default.

What connecting BigCommerce does

BigCommerce catalogues tend to be better populated with identifiers than most, because UPC, MPN and brand are first-class product fields rather than plugin add-ons. That is a real advantage for matching. Where a Shopify store often depends on one barcode field, a well-maintained BigCommerce catalogue gives matching three independent signals per item, which resolves more products automatically and leaves fewer for human review.

What data flows in each direction

How to connect a BigCommerce store

1. 1

   Create a store API account

   In your BigCommerce control panel, create an API account and grant read access to products. Leave everything else at none. The credentials are shown once, so save them before you close the dialog.

2. 2

   Paste the credentials

   Open Integrations in your account, choose BigCommerce and enter the credentials. The connection test runs straight away and tells you which access level it found, so a missing permission is obvious immediately.

3. 3

   Confirm your identifier fields

   Check that UPC and MPN are reading from the fields you expect. Some catalogues keep barcodes in a custom field instead. Point at the correct field here and matching uses it from the first run.

4. 4

   Import and review matches

   Import everything or filter by category, brand or product type. Matching runs and returns candidates with confidence scores. Confirm the strong ones in bulk and correct the weak ones once.

5. 5

   Decide where output goes

   Alerts to email or Slack, proposals into a review queue, scheduled CSV exports, or write-back to the store. Only the last one needs write access on the API account.

Which identifiers BigCommerce price monitoring matches on

Variants are matched individually, so a 10-pack and a 25-pack of the same filter are two monitored items with two competitor sets. Where pack sizes differ across retailers, comparison is on unit price rather than shelf price.

Price write-back and pricing complexity

Write-back updates the price on products or variants that already exist. It is enabled per rule, and every attempt is recorded with the old value, the new value, the rule and the response from the store. A rejected write is marked failed rather than counted as applied, because a rule that reports success for a price that never landed is worse than no automation at all.

If you run several storefronts from one catalogue, monitor each storefront as its own price context so a rule written for one market cannot move a price in another. Multiple BigCommerce stores connect with their own API accounts and roll into a single account, with no per-store fee. See pricing for what counts against a plan.

What the BigCommerce integration does not do

• It does not read orders, customers, carts or payment data.
• It does not create, delete or reorganise products, variants or categories.
• It does not manage inventory, shipping, tax or channel listings.
• It does not edit theme files or inject storefront scripts.
• It does not reprice your marketplace listings. Marketplace coverage is on the Amazon integration page.

Where a PIM or ERP owns price rather than the storefront, take a scheduled CSV over SFTP or pull changes through the REST API and import on your own cycle. The result is the same change history either way. For the wider workflow, see retail price monitoring.