BigCommerce as a Channel
June 28, 2026
Summary
BigCommerce is a fully supported sales channel in Flxpoint. Connect over OAuth (recommended) or an API Account, then import and publish listings, sync price and quantity, and pull orders with tracking write-back. Set Inventory Tracking to variant in BigCommerce or quantity updates are silently discarded.
What this integration does
Import Listings
Pulls existing BigCommerce products and variants into Flxpoint. Manual-only (no scheduling) and reads fields directly – no mapping template.
Sync & Link Listings
Links Flxpoint listings to existing BigCommerce products (SKU first, then UPC/GTIN/MPN as fallbacks) and syncs price, quantity, visibility, and mapped metafields on demand or on a schedule.
Publish Listings
Creates or updates BigCommerce products from your Flxpoint listings – parent and variant fields, images, categories/brands, and metafields.
Get Orders
Imports BigCommerce orders into Flxpoint (billing/shipping, line items, totals, notes), processing up to 50 orders per page.
Sync Orders
Writes tracking and shipment status back to BigCommerce via POST /v2/orders/{order_id}/shipments, with automatic carrier detection on retry.
How to connect - credentials you need
In Flxpoint go to Sales Channels → +, choose BigCommerce, name the channel and pick your processes, then on the Connect step choose a method and enter the values below. Click Continue / Authorize (OAuth) or Save (API Account), and use Test Connection to confirm.
Connection MethodSetting
Choose OAuth (recommended, no keys to manage) or API Account (Client ID / Client Secret / Access Token). Use API Account only if your organization can't approve OAuth app installs.
OAuth is the preferred, token-free setup.
Store HashRequired
Identifies your BigCommerce store. It appears as
Needed for both methods. Staging and production stores have different hashes – confirm you're using the right one.
store-XXXXXX in your Admin URL, or after /stores/ in an API Account's API Path.OAuth AuthorizeRequired
For the OAuth method: enter your Store Hash, click Continue / Authorize, log in if prompted, and approve the requested permissions. You return to Flxpoint with the connection shown as Connected.
Must be approved by the store owner or staff with app-install permission in BigCommerce.
Client IDOptional
API Account method only. Create or select an API Account in BigCommerce Admin under Advanced Settings → API Accounts and copy the Client ID.
Part of the API Account fallback (skip if using OAuth).
Client SecretOptional
API Account method only. Copied when you create the API Account in BigCommerce Admin.
Store credentials securely and rotate tokens when personnel or policies change.
Access TokenOptional
API Account method only. The bearer token issued alongside your API Account.
Part of the API Account fallback (skip if using OAuth).
API ScopesSetting
For API Accounts set minimum scopes: Products (Read/Write), Orders (Read/Write), Customers (Read), Content (Read), Information & Settings (Read).
Insufficient scopes return an 'invalid credentials' or permission error even when the token and Store Hash are correct.
Seeing "invalid credentials" or "insufficient scope"? Recheck the token, scopes, and Store Hash, and confirm you're authorizing the correct store (staging and production differ). OAuth installs must be approved by the store owner or staff with app-install permission. Upgrading V2 → V3 requires a new API Account – existing V2 tokens can't be upgraded in place.
Important - read before configuring
Set Inventory Tracking to "variant" before syncing quantities
BigCommerce does not persist per-variant quantity when Inventory Tracking is set to product or none – Flxpoint's sync appears to succeed but quantities never update on the storefront. Set Inventory Tracking to variant on all products, either manually in BigCommerce or by mapping it as a static value in your Publish Listings template.
Quantity must be mapped in the Get Orders template
Leaving Quantity unmapped in Get Orders causes a NullPointerException that blocks all order import – no orders come through. Go to Templates → Get Orders → Field Mapping, map Quantity → Line Quantity, save, and re-run.
Product images must be under 8 MB
BigCommerce rejects images larger than 8 MB on Publish Listings. Publish appears to succeed but the listing fails or shows no image on the storefront. Compress product images below 8 MB (prefer JPG or WEBP) before running Publish.
Staging and production are separate connections
Staging environments have a different Store Hash from production and separate product/order databases. If you configured the integration against a staging store it will not sync to your live store. Confirm the correct Store Hash – found in your BigCommerce Admin URL after /stores/ – for the environment you intend to connect.
Mapping - fields to know
| BigCommerce Field | Imported As – Notes |
|---|---|
| Name | → Product title. Shown on the parent product. |
| SKU | → Primary identifier. Used for later linking/matching. |
| Description | → Description. Long/HTML description, sanitized to supported HTML. |
| Price | → Price. Imported for reference only; not sent back by this job. |
| Images | → Images. Product image URLs; keep each under 8 MB if you plan to publish later. |
| Categories | → Categories. Multi-level category paths are preserved. |
| Brand | → Brand. Imported if set on the product. |
| Weight / Dimensions | → Physical attributes. Imported if present on product/variant. |
| Variant SKU | → Child identifier. Critical for later linking. |
| Inventory Level | → Quantity. Per-variant stock, when managed per variant. |
| UPC / Barcode | → Global identifier. Useful as a secondary match key. |
| Options (name/value) | → Options. Option label & value (e.g. Color: Blue). No mapping template is used for Import. |
Import options (Product & Listing Management)
This required setting controls what each run is allowed to create and update. All four options are available on BigCommerce.
| Option | What it does | When to use it |
|---|---|---|
| Change feed (recommended) | Creates new products and listings and updates existing ones. Each run only fetches what changed on BigCommerce since the last successful run, so runs stay fast. | Your everyday default. |
| New products and listings | Creates new products and new listings only. Existing Flxpoint records are left untouched. | When you have curated data in Flxpoint that BigCommerce should not overwrite. |
| New listings | Creates new listings only. No products are created in your catalog, and existing records are not updated. | When your catalog is built from your sources and BigCommerce should only contribute listings. |
| Catalog refresh (not recommended) | Creates new products and listings and updates all existing ones, re-reading your entire BigCommerce catalog. | One-off recovery after a bulk edit on the BigCommerce side. Expect a long-running job. |
Pricing and quantity are not updated by Import Listings. Price and quantity come in when a listing is first created, but no option updates them afterward, including Catalog refresh. They are aggregate fields owned by your Pricing & Quantity Strategies, which would overwrite any imported value on the next sync. Titles, descriptions, brands, categories, images and attributes do update on the options that update existing records.
Upgrading from the previous options? Existing configurations were migrated for you. Create and update products & listings now runs as Change feed, and Create products & listings only now runs as New products and listings. Create new products only was retired and now runs as Change feed, which also updates existing records, so switch to New products and listings if you need existing records left alone.
| Flxpoint Field | BigCommerce Field – Notes |
|---|---|
| Quantity | → Inventory Level. Required. Updates variant stock – only persists when Inventory Tracking = variant. |
| List Price | → Price. Recommended. Apply markup/rounding rules as needed. |
| Sale Price | → Sale Price. Optional. Leave blank if you don't run sales in BigCommerce. |
| MSRP | → Retail Price (MSRP). Optional. Reference / compare-at price. |
| SKU | → SKU. Recommended. Primary match key for Linking Priority (keep SKU ↔ SKU as your first row). |
| Availability Description | → Availability Description. Optional. Customer-facing availability note. |
| Metafields | → Metafields. Optional. Creates missing and updates mapped metafields; unmapped metafields are preserved (not deleted). |
| Flxpoint Field | BigCommerce Field – Notes |
|---|---|
| Title | → Name. Required. ≤ 250 chars; use the truncation setting if needed. |
| Type | → Type. Required. physical / digital. |
| Price | → Price. Required. Base product price. |
| Weight | → Weight. Required for physical items – needed for shipping rates (kg). |
| Brand | → Brand. Optional. Created if missing. |
| Category 1–3 | → Categories. Optional. Up to 3 levels, created if missing; no duplicate or multi-parent categories (can return a 409 Conflict). |
| Description (HTML) | → Description. Optional. Sanitize HTML if copied from external sources. |
| Images (URLs) | → Images. Optional. Each ≤ 8 MB; controlled by "Parent Images Direct Copy." |
| SKU | → Variant SKU. Recommended. Primary identifier for updates. |
| List / Sale / MSRP | → Price / Sale Price / Retail Price. Variant pricing; use rules for markups/rounding. |
| UPC / GTIN / MPN | → UPC / GTIN / MPN. Optional. Helpful for marketplace feeds and audits. |
| Option Name/Value | → Options. Optional. Each value ≤ 250 chars. Up to 250 variants per product. |
| Inventory Tracking | → static value variant. Recommended so per-variant quantity syncs actually persist on the storefront. |
| Metafields | → Metafields. Optional. Created on publish and updated on re-publish, at parent and variant level. |
| BigCommerce Field | Maps To – Notes |
|---|---|
| SKU | → Line - SKU. Required. Orders/lines without a SKU won't import. |
| Quantity | → Line - Quantity. Required. Unmapped quantity triggers a NullPointerException that blocks all order import. |
| Date Created | → Order - Created. Required. Creation date. |
| State Code (Billing / Shipping) | → State Code. Recommended. Prefer the two-letter code (e.g. CA) for downstream tax/shipping rules. |
| Shipping Method | → Shipping - Method. Map each method to a Flxpoint shipping policy; unmapped methods put orders On Hold. |
| Order ID / Status / Totals | → Order fields. Optional. Identifier, BC status, and subtotal/tax/total context. |
| Staff / Customer Notes | → Order - Notes. Optional. Communication captured on the order. |
| Gift Certificate (no SKU) | Uses a generated SKU: name-orderItemId, or type-orderItemId for duplicate names. Digital items import as type digital. |
| FFL Details | Optional. Enable Import FFL Details to read FFL info from Order Comments when present. |
| Flxpoint Field | BigCommerce Shipment Field – Notes |
|---|---|
| Tracking Number | → tracking_number. Required. Unmapped tracking prevents shipment creation. |
| Tracking Link | → tracking_url. Optional. Direct tracking URL. |
| Tracking Carrier / Shipping Provider | → carrier. Optional. Use a BigCommerce-accepted value, or map empty if it isn't recognized. |
| Shipping Method | → shipping_method. Optional. Service/method label. |
| Merchant Shipping Cost | → shipping_cost. Optional. Merchant cost. |
| Date Created | → shipped_at. Optional. Shipment timestamp. |
| Comments | → comment. Optional. Note included on the shipment. Shipments post via POST /v2/orders/{order_id}/shipments; order status becomes Partially Shipped until all lines ship. |
Common issues
Get Orders failing –
NullPointerException on QuantityFull error: "Cannot invoke java.lang.Integer.intValue() because the return value of BigCommerceProductDto.getQuantity() is null." Quantity isn't mapped in the Get Orders template – this is the most common BigCommerce order-import failure. Go to Sales Channels → BigCommerce → Templates → Get Orders → Field Mapping, map Quantity → Line Quantity, save, and re-run.
Orders not importing from BigCommerce
Three common causes: (1) the Order status filter doesn't include the statuses you expect – widen it to include Incomplete, Pending, or Awaiting Payment. (2) A line item is missing a SKU – orders without a SKU won't import (fix in BigCommerce, or use generated SKU logic for gift certificates only). (3) The Time Frame is too narrow – widen the date range.
Inventory quantities not updating on the BigCommerce storefront after sync
Inventory Tracking on the affected products is set to product or none, so BigCommerce silently discards variant-level quantity (Flxpoint shows no error). Open each product in BigCommerce Admin, change Inventory Tracking → variant, and re-run Sync & Link Listings. To prevent it going forward, add Inventory Tracking as a static
variant value in your Publish Listings template.Sync Orders completing but shipments not updating in BigCommerce
Two causes: (1) Tracking Number not mapped – required; without it BigCommerce rejects the shipment call (check Templates → Sync Orders → Field Mapping). (2) Invalid carrier value – Flxpoint attempts automatic normalization on retry, but if it still fails, map the carrier field to empty so shipments post without a carrier label. Reference the accepted carrier values CSV.
Publish fails – "name: The product name is a duplicate"
The parent and variant title can be the same – that alone does not cause this error. It usually appears when the same title already exists under a different parent or as a variant elsewhere on the channel. It can also happen when a parent has two variants sharing the same title: one variant publishes successfully, while the second throws this error for the duplicate title.
Connection fails – "Invalid store hash" or "Invalid credentials"
Check three things: (1) Store Hash matches the target store exactly – staging and production differ; find it after
/stores/ in the Admin URL. (2) API scopes – for an API Account, enable Products, Orders, Customers, Content, and Information & Settings; missing scopes return a credentials error even when the token is valid. (3) Account permissions – OAuth approval requires the store owner or staff with app-install permission.FAQs
What's the difference between OAuth and API Account connection – which should I use?▸
OAuth is recommended – a secure, token-free setup that authorizes Flxpoint via BigCommerce's app-install flow without exposing API keys. Use API Account (Client ID, Client Secret, Access Token) only if your organization can't approve OAuth app installs. With an API Account, ensure minimum scopes: Products (Read/Write), Orders (Read/Write), Customers (Read), Content (Read), Information & Settings (Read).
Where do I find my BigCommerce Store Hash?▸
Your Store Hash appears in the BigCommerce Admin URL as
store-XXXXXX, or after /stores/ in the API Path when creating an API Account. It's a short alphanumeric string (e.g. abc123def). If you have multiple stores, confirm you're using the hash for the correct one – staging and production stores have different hashes.Quantities sync successfully in Flxpoint but aren't updating on my BigCommerce storefront – why?▸
BigCommerce doesn't retain per-variant inventory when a product's Inventory Tracking is set to product or none. Flxpoint's API call succeeds (no error) but BigCommerce discards the variant-level quantity. Fix: change Inventory Tracking to variant on the affected products, then re-run Sync & Link Listings to backfill correct quantities. To prevent this on future publishes, add Inventory Tracking → static value
variant to your Publish Listings template.Does Sync & Link Listings update product content like titles, descriptions, and images?▸
No – Sync & Link Listings updates price, quantity, and visibility only (plus mapped metafields). For content updates (titles, descriptions, images, categories), use Publish Listings with the Overwrite setting enabled. Running only Sync means content edits made in Flxpoint never reach BigCommerce.
How do I set up the new BigCommerce API V3 OAuth scopes correctly?▸
When creating an API Account (Advanced Settings → API Accounts → Create API Account), set minimum scopes: Products (Read/Write), Orders (Read/Write), Customers (Read), Content (Read), Information & Settings (Read). Insufficient scopes cause "invalid credentials" or permission errors even when the Store Hash and token are correct. Upgrading from V2 to V3 requires a new API Account – existing V2 tokens can't be upgraded in place.
Can I map shipping methods from BigCommerce to Flxpoint shipping policies?▸
Yes – and it's required for orders to route correctly. Go to Sales Channels → BigCommerce → Shipping/Carrier Mappings and map each BigCommerce shipping method name (exactly as it appears on orders, e.g. "Standard Shipping", "Free Shipping") to a Flxpoint shipping policy. Unmapped shipping methods put orders On Hold. Wildcard or pattern matching is not currently supported – each method text must be mapped individually.