Before you begin
To connect your BigCommerce store, you need a Store-Level API Account created from inside your BigCommerce control panel. Unlike Amazon and Shopify (which use OAuth consent screens), BigCommerce requires you to generate API credentials and paste them into Repricing.app.
Here's what you need:
- Store Hash. A short alphanumeric identifier that uniquely identifies your BigCommerce store (for example,
gfx3br7qpc). Find it in the URL of your BigCommerce control panel:https://store-{store-hash}.mybigcommerce.com/. - Access Token. The permanent API token paired with your API account. This is shown only once when you create the API account, so save it somewhere safe.
- Client ID. The client identifier paired with the access token.
Creating the Store-Level API account
- Open your BigCommerce control panel and go to Settings > API > Store-level API accounts.
- Click Create API Account, choose V2/V3 API Token, and give it a descriptive name (for example, "Repricing.app").
- Grant the required scopes (listed below).
- Click Save. BigCommerce shows the credentials once: copy the Access Token, Client ID, and Store Hash. You will not be able to see the Access Token again, so store it somewhere safe.
Required scopes
Grant each of the following scopes. Each one enables a specific part of the integration:
- Products: read and write. Needed to sync your catalog (titles, prices, variants, cost) and to submit price updates back to BigCommerce.
- Information & Settings: read. Needed to verify your store, detect the default currency, and read store-level configuration during the initial connection.
- Orders: read. Needed to power the Sales Report and Units Sold Report.
- Channel Settings: read. Needed to discover storefronts on multi-storefront stores so each one becomes its own channel region.
If any scope is missing, the connection either fails outright or features that depend on the missing scope will silently stop working until you grant it.
Step-by-step connection process
Step 1: Open the connection dialog
Go to Channels in the sidebar, then click the BigCommerce card. A connection dialog opens automatically with the required credential fields.
Step 2: Enter your credentials
Fill in the three required fields:
- Store Hash. Paste your store hash exactly as it appears in your BigCommerce control panel URL.
- Access Token. Paste the access token from your Store-Level API account. It's stored securely and never exposed in the application.
- Client ID. Paste the client ID from the same API account.
Step 3: Connect
Click the Connect button. Repricing.app validates your credentials by making a test call to the BigCommerce API and discovering your active storefronts. If everything checks out, your account is connected and the initial sync begins. A label is generated automatically based on your store name. You can rename it later from the Channels page.
What happens after connecting
Once connected, Repricing.app starts syncing your BigCommerce data:
- Storefront discovery. Repricing.app calls the BigCommerce Channels API to discover every active storefront on your store. Each storefront becomes its own channel region inside Repricing.app, with the currency assigned to it on BigCommerce.
- Catalog sync. All your products are pulled in, including titles, images, BigCommerce product IDs, variant IDs, SKUs, brand, category, condition, UPC, inventory level, and current prices. This usually takes a few minutes for small catalogs and longer for larger ones (thousands of products). Products with variants are imported as one listing per variant.
- Cost data. If you have cost-per-item filled in on BigCommerce (the Cost field under each product's pricing settings), that value is synced too. Otherwise, you can add costs from the listings grid or through the Import module.
- Orders sync. Your recent orders are pulled in to power the Sales Report and Units Sold Report.
- Pricing sync. Your current prices and sale prices are synced. From this point on, when the repricer calculates a new target price for a listing, it is submitted back to BigCommerce during the next pricing cycle.
You can monitor progress on the Channel Sync Status page.
BigCommerce terminology in Repricing.app
BigCommerce has a few concepts that map specifically inside Repricing.app:
- Product. The catalog entry on BigCommerce. A product can have zero, one, or many variants.
- Variant. A specific buyable option of a product (for example, a size or color). In BigCommerce, every product has at least one default variant under the hood.
- Listing. Inside Repricing.app, each variant becomes one listing. If a product has 5 variants, you'll see 5 listings on the Listings page.
- Channel Product ID. The identifier shown in the Listings grid combines the BigCommerce product ID and variant ID, separated by a colon (for example,
1234:5678). This makes it easy to spot which listings belong to the same product. - Storefront. BigCommerce's term for a sales channel (a website, a B2B portal, a mobile app, an Instagram shop, etc.). Each active storefront on your store becomes a separate channel region in Repricing.app.
Multi-storefront support
BigCommerce Enterprise plans support multiple storefronts under a single store (for example, a primary website storefront, a B2B storefront, and a mobile app storefront). Repricing.app handles this automatically: each active storefront is created as its own channel region, with its own listing catalog, currency, and pricing.
If you are on a Basic, Plus, or Pro plan, you'll have a single storefront (the default Web channel). Multi-storefront accounts will see one region per storefront on the Channels page. You can enable or disable specific storefronts from your region settings.
Strategies are per-region, so you can run different pricing strategies on different storefronts (for example, more aggressive pricing on your B2B storefront and standard cost-plus on your main retail storefront).
Price, sale price, and compare-at
BigCommerce products have multiple price fields. Repricing.app uses them as follows:
- Sale Price. The price customers pay. Repricing.app reads and updates this field on every reprice. This is the price that appears in the Listings grid under "Price."
- Price (Retail). The full, undiscounted reference price. If your strategy uses compare-at price automation, Repricing.app sets this field so that customers see a strikethrough above the sale price.
- Cost Price. Your unit cost on BigCommerce. Synced into the listing's Cost field on Repricing.app. Used for ROI, Profit Margin, and Fixed Profit calculations.
How BigCommerce differs from marketplaces
BigCommerce is a direct-to-consumer channel, which means there's no Buy Box, no native competitor data, and no marketplace fees. This changes how repricing works:
- Two pricing approaches in the strategy wizard. BigCommerce strategies let you choose between Competitor-based pricing (the recommended default) and Cost-based pricing. You pick one in the Pricing step.
- Competitor-based pricing. Price relative to the lowest of the competitor URLs you've added on each listing. Sub-modes are Beat lowest competitor (recommended), Match lowest competitor, or Stay above lowest competitor, by a fixed amount or percentage. Requires at least one active competitor URL per listing. See Tracking External Competitors.
- Cost-based pricing. Calculate prices from your cost data using one of three metrics: ROI (Return on Investment), Profit Margin, or Fixed Profit. For example, a $10 cost with 30% ROI gives you a $13.00 price; with a 30% profit margin it's $14.29; with $3 fixed profit it's $13.00. See Pricing Settings.
- No native Competitors data from BigCommerce. BigCommerce is your own store, so there are no per-seller offers, Buy Box status, or marketplace fee estimation. When the listing's strategy uses Competitor-based pricing, the Competitors tab on the listing detail page lets you add competitor URLs manually so the repricer can monitor specific products on other sites. When the strategy uses Cost-based pricing, the tab is hidden since URLs aren't used. See Tracking External Competitors.
- Compare-at price automation. Configure compare-at (strikethrough) prices directly from your strategy with four modes: Disabled, Auto (uses the previous price), Markup (always a set amount above the selling price), and Set manually. See Compare Price.
- No Price Floor step in the wizard. BigCommerce strategies skip the Price Floor step. Instead, each listing's Min Price field acts as the floor: the repricer never sets a price below it, no matter which approach (competitor-based or cost-based) you've chosen. You set Min Price per listing in the grid, on the listing detail page, or via the Import module.
B2B Edition
BigCommerce B2B Edition (available on Enterprise plans) adds customer-group price lists and bulk-pricing tiers to your store. Repricing.app reprices the base sale price on your products. Customer-specific B2B price lists and quantity-based price breaks defined inside B2B Edition are not modified by the repricer; they continue to work as you configured them in BigCommerce, layered on top of the sale price that Repricing.app maintains.
Re-authentication
Store-Level API tokens do not expire on a fixed schedule, but they can be revoked at any time from your BigCommerce control panel (for example, if you delete the API account or rotate its credentials for security). If that happens, syncing and price updates pause and you'll see a re-authentication notice on the Channels page. Click the reconnect button and enter a new Access Token and Client ID. Your Store Hash stays the same since it's already on file. Your listings, strategies, costs, min/max prices, competitor URLs, and pricing history are preserved.
Troubleshooting
- "Invalid credentials" error. Double-check that you copied the full Access Token and Client ID with no extra spaces or line breaks. Make sure the API account still exists in your BigCommerce control panel under Settings > API > Store-level API accounts and that it has not been disabled.
- "Store not found" error. Verify your Store Hash is correct. It's the short alphanumeric segment in your BigCommerce control panel URL:
store-{store-hash}.mybigcommerce.com. The Store Hash is case-sensitive. - "Insufficient permissions" error. Open your API account in BigCommerce and confirm all required scopes are granted (Products read/write, Information & Settings read, Orders read, Channel Settings read). Add any missing scopes, save the account, and reconnect.
- Sync not starting. The first sync can take a few minutes to begin. Larger catalogs (thousands of products) may take longer to fully sync. If nothing happens after 10 minutes, try disconnecting and reconnecting the account.
- Products not showing. Only products marked as Visible in BigCommerce are synced. Hidden products and products in draft status are skipped. If a product is missing, check that it is visible and that it has at least one variant set up.
- Variants missing. Each variant of a product becomes its own listing. If a variant is disabled or out of stock with no purchase availability, it may not appear. Re-enabling the variant on BigCommerce makes it sync on the next cycle.
- Storefronts missing. Only active storefronts are discovered. If a storefront is disabled or deleted in BigCommerce, it won't appear in Repricing.app. Re-enable it on BigCommerce and reconnect to pick it up.
- Wrong price showing. Make sure you are looking at the Sale Price on BigCommerce, not the Retail Price. Repricing.app updates the sale price field. The retail price is only modified when your strategy uses compare-at price automation.
For general channel management, see Managing Channel Accounts.