BigCommerce as a Source

July 2, 2026

Summary

Connect a BigCommerce store as a source to pull its products, pricing and inventory into Flxpoint and, when configured, send orders back for fulfillment. Connect with the BigCommerce API App (OAuth2) if you own the store, or a Store-Level API Bearer Token for a vendor store.

What this integration does

Get Inventory (Primary)

Imports the full BigCommerce catalog – products, variants, images, categories, pricing and stock – as a full feed every run

Send Fulfillment Requests

Creates an order in your connected BigCommerce store from an approved Flxpoint Fulfillment Request

Get Shipments

Pulls tracking, carrier and partial-shipment updates from BigCommerce back onto your Fulfillment Requests

How to connect - credentials you need

Go to Sources → + Add Source, name it BigCommerce, then click New BigCommerce Connection and pick a connection type. Enter the values below, click Test Connection, then Save Connection.

Connection TypeSetting

Choose BigCommerce API App (OAuth2) – recommended if you own the store – or BigCommerce API Bearer Token for a vendor store or manual keys.

OAuth2 is simpler to maintain and doesn't require sharing long-lived tokens.

Store HashRequired

The alphanumeric segment after /stores/ in your BigCommerce API Path, found under Settings → Advanced → API (e.g. abc123xyz in .../stores/abc123xyz/v2/). Required for both connection types.

Copy it exactly.

Authorize the Flxpoint appRequired

For the OAuth2 method: after entering your Store Hash, click Save Connection – you'll be prompted to install/authorize the Flxpoint app in your BigCommerce store to complete OAuth2, then click Test Connection.

OAuth2 connections only.

Client IDRequired

For the Bearer Token method: the Client ID from a BigCommerce Store-Level API Account (Settings → Advanced → API → Store-Level API Accounts).

Bearer Token connections only.

Access TokenRequired

The Access Token generated with your Store-Level API Account. It is shown only once at creation, so copy it immediately.

Bearer Token connections only. Rotate the token if it is ever shared or compromised.

Not sure of your Store Hash? Open Settings → Advanced → API in BigCommerce and read it from the API Path (the value after /stores/). If OAuth authorization fails, confirm you are the store owner and re-run the app install. For a Bearer Token, confirm the Store-Level API Account has these permissions: Content, Information & Settings and Products set to Read-only, and Customers, Orders and Order Transactions set to Modify.

Important - read before configuring

OAuth2 is the recommended connection method – use Bearer Token only for vendor stores

If you own the store, use BigCommerce API App (OAuth2): enter your Store Hash, click Save Connection, and install the Flxpoint app in BigCommerce to authorize. It's simpler to maintain and avoids long-lived tokens. Use the Store-Level API Bearer Token method only when connecting a vendor's store or when you can't perform OAuth2 authorization yourself.

Get Inventory (Primary) runs as a full feed every time – there is no delta mode

Every GIP run pulls the complete BigCommerce catalog: all products, variants, images, categories and stock levels. There is no partial/delta option. For large catalogs, lower the Product Page Size Limit (250 is a good default) and run at off-peak hours to avoid API rate limits.

Inventory tracking must be enabled on BigCommerce variants for quantities to import

Flxpoint reads stock from the variants.inventory_level field. If inventory tracking is not enabled on a variant in BigCommerce, that variant's quantity imports as 0 regardless of what the store displays. Confirm inventory tracking is active on each variant before troubleshooting quantity sync issues in Flxpoint.

Send Fulfillment Requests requires a valid Billing Address – it cannot be empty

BigCommerce's v2 order API requires a Billing Address on every order. If the Billing Address fields in your Send FR mapping are unmapped or empty, order creation fails. Map at minimum First Name, Last Name, Email, Address Line 1, City, State (or State Code), Postal Code and Country. For two-letter state codes, add a custom form field named State Code in BigCommerce and map it.

Mapping - fields to know

Get Inventory (Primary) Send Fulfillment Requests Get Shipments

Flxpoint Field	Maps From BigCommerce – Notes
SKU	`variants.sku` – unique identifier for matching products (case-sensitive).
Title	`name` – for product display and identification.
Quantity	`variants.inventory_level` – controls available stock; requires inventory tracking enabled on the variant.
Brand	`brand_id` resolved to `brands.name` – ensures consistent brand labeling.
Categories	`categories[0–2]` – up to 3 category levels supported.
All Images	Direct Copy – `images[0].url` and any additional product images are copied directly, no per-field mapping needed.
Weight	`weight` – imported in metric (KGS); important for shipping calculations.
Dimensions	`width`, `height`, `depth` – imported in metric (cm).
Price / MSRP / Cost	`price`, `retail_price`, `cost_price` – pricing for listings and reporting, in the store's currency.

Builds reference lists via GET v3/catalog/brands and GET v3/catalog/categories, then pulls products with GET v3/catalog/products?include=variants,images. Set Do Not Import Hidden Product to Yes to skip unpublished products. Not supported: BigCommerce Custom Fields, multiple warehouses and client-specific pricing.

Creates an order in your BigCommerce store from an approved FR via the v2 /orders endpoint; the returned order_id is stored as the auto-acknowledgement (and later used by Get Shipments). Items are matched by the external listing ID saved during Get Inventory (Primary), with variant SKUs fetched at order time when needed. Choose an Order Customer ID option: create a new customer from the PO details if one doesn't already exist, or use an existing customer from the PO details and fail the order if it doesn't already exist. Optionally, Hold for X hours or Only send during business hours for a review window. Orders are created in Awaiting Fulfillment status. A valid Billing Address is required; Custom Fields and attachments are not sent.

For each FR's BigCommerce order, polls GET /v2/orders/{orderId}/shipments and, when shipments exist, GET /v2/orders/{orderId}/products to associate shipped quantities to FR lines via product/variant IDs (mapped back to SKU). Attaches Tracking Number, Tracking Link, Carrier and Shipping Method, and moves the FR from Open → Partially Shipped → Shipped as shipments post. The FR Lookback Period (default ~90 days) limits which FRs are checked; invoices and custom fields are not imported.

Common issues

Zero quantities importing even though BigCommerce shows stock

The most common cause is that inventory tracking is not enabled on the variant in BigCommerce. Flxpoint reads variants.inventory_level – if BigCommerce isn't tracking inventory for that variant, the field returns 0. Open the product in BigCommerce, confirm inventory tracking is on with a quantity entered, then re-run Get Inventory (Primary).

Missing products after Get Inventory (Primary) completes

Check the Do Not Import Hidden Product setting first – if enabled, unpublished/hidden products won't import. Temporarily disable it and re-run GIP to confirm; if the products appear, publish them in BigCommerce. Also verify no Post-Mapping Workflow rules with Do Not Import conditions are filtering them out.

Import running slowly or hitting API rate limits

BigCommerce enforces rate limits on catalog endpoints, and GIP runs as a full feed. Lower the Product Page Size Limit (start at 250; try 100 for very large catalogs), run overnight/off-peak, and avoid running other BigCommerce operations at the same time. If rate-limit errors appear in the log, wait for the window to reset and re-run.

Send Fulfillment Request failing – address error or order not created

BigCommerce requires a complete Billing Address on every order. Confirm these are mapped and non-empty: First Name, Last Name, Email, Address Line 1, City, State (or State Code), Postal Code and Country. If the state is failing, map State Code (two-letter) instead of the state name – add a State Code custom form field in BigCommerce if needed.

"Couldn't match item" error on Send Fulfillment Requests

Send FR looks up each line by the external listing ID saved during GIP. If a product was deleted and recreated in BigCommerce (new IDs), or the FR SKU doesn't match the BigCommerce SKU exactly (case and spaces matter), the lookup fails. Re-run Get Inventory (Primary) to refresh the external listing IDs, then retry – SKU matching is case-sensitive.

Get Shipments not returning tracking for recent orders

First confirm the order has a shipment record in BigCommerce – Get Shipments only returns tracking after a shipment is created in BC by your fulfillment app or warehouse. If the shipment exists but isn't importing, confirm the FR is within the FR Lookback Period, that Tracking Number, Carrier and Shipping Method are mapped, and that the BC order ID was stored during the Send FR run.

FAQs

What permissions does the Store-Level API key need?▸

When creating a Store-Level API Account in BigCommerce (Settings → Advanced → API → Store-Level API Accounts), set Content, Information & Settings and Products to Read-only, and Customers, Orders and Order Transactions to Modify. After saving, copy the Client ID and Access Token immediately – they're shown only once – and enter them with your Store Hash into the BigCommerce API Bearer Token connection in Flxpoint.

Where do I find my BigCommerce Store Hash?▸

In BigCommerce, go to Settings → Advanced → API. The API Path looks like https://api.bigcommerce.com/stores/abc123xyz/v2/. The Store Hash is the alphanumeric segment after /stores/ – here, abc123xyz. Copy that value exactly into the Store Hash field in Flxpoint.

What product data does Get Inventory (Primary) import from BigCommerce?▸

GIP uses three v3 endpoints: GET v3/catalog/brands and GET v3/catalog/categories to build reference lists, then GET v3/catalog/products?include=variants,images for full product data. Per run it imports all variants with individual stock counts, standard pricing (Price, MSRP, Cost) in the store's currency, weights and dimensions in metric units (KGS/cm – convert to lbs/in as needed), up to 3 category levels, and product images. Custom Fields and multiple warehouses are not supported.

What does the "Do Not Import Hidden Product" setting do?▸

When enabled, Get Inventory (Primary) skips any product that is unpublished or hidden in BigCommerce – recommended so your Flxpoint catalog reflects only active, visible products. Disable it if you need to import draft or staged products. This toggle is the only published-status filter available on the BigCommerce source.

How does Send Fulfillment Requests match items from the FR to BigCommerce products?▸

Send FR uses the external listing ID saved during Get Inventory (Primary) to look up the product. For simple products the product ID is stored; for variant products Flxpoint fetches the product's variant SKUs at order time and selects the right variant. Orders are created via the v2 /orders endpoint, and the returned BigCommerce order ID is stored as the auto-acknowledgement and used later by Get Shipments to retrieve tracking.

Does BigCommerce as a Source support partial shipments in Get Shipments?▸

Yes. Get Shipments polls GET /v2/orders/{orderId}/shipments for each FR's BigCommerce order, then requests GET /v2/orders/{orderId}/products to match shipped quantities to FR lines via product and variant IDs. The FR status progresses from Open to Partially Shipped to Shipped as shipments are created in BigCommerce, and multiple tracking numbers are stored and visible on the FR.

What is the FR Lookback Period in Get Shipments?▸

The FR Lookback Period controls the maximum age of Fulfillment Requests that Get Shipments checks for tracking updates (default ~90 days). Older FRs are excluded to keep the job performant. If you have FRs older than the window that still need tracking, temporarily increase the period and re-run, then return it to the default to avoid unnecessary overhead.

Back to Platform-Based Sources