Connect BigCommerce: pull orders in, push fulfillment out

Copy your Store hash and Access Token from BigCommerce Settings → API, paste them into Integration, test, map, activate — orders flow in and fulfillment flows back.

The BigCommerce connector pulls orders from your BigCommerce store into OMS, and pushes fulfillment back to BigCommerce. It can also push product and inventory updates out, so orders, shipping, and stock stay in sync on both sides.

Prerequisites#

• A BigCommerce store, with access to Settings → API in that store.
• Permission to create an API account in BigCommerce → Settings → API.
• The API account must be given the Orders, Products, and Inventory scopes — without them the connector cannot pull orders or push product and inventory updates.

Get your credentials#

1. In BigCommerce, go to Settings → API and create an API account.
2. When you create the account, make sure the Orders, Products, and Inventory scopes are included — the connector needs all three.
3. Copy the Access Token for that API account and keep it somewhere safe — you will paste it into Integration in the next step.
4. Find the Store hash in the API path of that API account. The path looks like https://api.bigcommerce.com/stores/abc123def/v3 — the part after /stores/ is the Store hash, in this example abc123def. Copy only that part.

Fill it into Integration#

1. Open Integration → Connector Marketplace → BigCommerce → New connection.
2. Store hash: paste only the store hash from the API path, for example abc123def. Do not paste the full URL — this field takes the hash on its own, and it identifies which store the connection belongs to.
3. Access token: paste the Access Token you copied from the API account in BigCommerce → Settings → API. Both fields are required. The token is encrypted at rest and never echoed back.

Test the connection#

Click Test connection. The test uses the Store hash and Access Token you filled in to reach your BigCommerce store and check that the credentials work. A pass means the store was found and the token was accepted. If it fails, note the error and check the FAQ below before changing anything else.

Mapping / pick a template#

Pick the BigCommerce standard template. It maps order number, line SKUs, quantities, ship-to address, and fulfillment status between BigCommerce and the standard order. Check the mapping preview before activating, especially that each BigCommerce SKU is paired to the right OMS product.

Activate#

After activation, Integration pulls new BigCommerce orders on the schedule you set, pushes fulfillment with tracking numbers back to BigCommerce, and pushes product and inventory updates out. Watch the first few orders in Runs / Logs before trusting it unattended.

FAQ#

Test fails: the token is not accepted

The Access Token in the connection is wrong or no longer valid — for example it was copied incompletely, or the API account it came from is no longer the one in use. BigCommerce cannot accept a token it does not recognize, so every request fails at the door.

Go to BigCommerce → Settings → API, open your API account, copy the Access Token again in full, and paste it into the Access token field in the connection. Save and test again.

Sync is blocked: the API account is missing a scope

The credentials reach the store, but the API account was not given all the scopes the connector needs. Without the Orders scope orders cannot be pulled; without Products or Inventory, product and inventory updates cannot be pushed.

Go to BigCommerce → Settings → API and check the API account: make sure Orders, Products, and Inventory are all included. If you create a new API account with the right scopes, copy its Access Token into the connection as well. Save and test again.

Test cannot find the store

The Store hash field holds the wrong value. The most common cause is pasting the full API path or the full URL into the field instead of the hash alone, or using the hash of a different store — either way, the connection points at a store BigCommerce cannot match to your token.

Go to BigCommerce → Settings → API, open your API account, and look at its API path: copy only the part after /stores/ — for example abc123def from https://api.bigcommerce.com/stores/abc123def/v3. Replace the Store hash in the connection with that value, save, and test again.

Connected but no orders come in

The connection itself is fine — testing passes — but your BigCommerce store has no new orders yet, so there is nothing to pull.

Place an order in your BigCommerce store (or wait for the next customer order), then run a manual pull and check Runs / Logs. New orders appear once the store has issued them.