BigCommerce v3

BigCommerce v3

Connect your BigCommerce store via Channel Automation and sync orders, tracking, and inventory

BigCommerce v3 is the BigCommerce channel in ShipEdge Core that uses the BigCommerce REST API (OAuth-style API account credentials). You add it under Channel Automation in Preferences, same pattern as other selling channels loaded from the channel list (see Setting Up Integrations).

Quick Start

My Account → Preferences → Channel Automation → open BigCommerce v3 → Insert new store’s name → Add new store.

---

Create an API Account (Store Admin)

You can watch the video below—it walks through these steps.

1. Open API Accounts

   In the BigCommerce store admin, go to Advanced Settings → API Accounts → Create API Account.

2. Name the account

   Enter an internal name for the API account.

3. Set OAuth scopes

   Under OAuth Scopes, choose at least what your integration needs. The shipped help example lists Orders: modify, Products: modify, and Webhooks: modify as examples—enable the scopes your operations require.

4. Save

   Click Save and copy the Access Token, Client ID, and store details into ShipEdge.

---

Add a BigCommerce v3 Store

1. Open Channel Automation

   Open My Account → Preferences → Channel Automation.

2. Find BigCommerce v3 in the list

   In the Channels column, click BigCommerce v3 to expand the row if it is collapsed.

3. Name the store

   In Insert new store’s name, type a name you will recognize (for example your storefront name).

4. Create the store

   Click Add new store. Confirm the prompt if the browser asks. The app creates the store and links a configuration record.

5. Enter API credentials

   Fill in the fields exactly as labeled (names come from the channel definition):

   Field	Purpose
   Access Token	OAuth API access token from your BigCommerce API account
   Client ID	Client ID for that API account
   Store Hash	Store hash from your API base path
   Order status	Comma separated list of order statuses to be imported

6. Save configuration

   Click Save configuration. If required fields are empty, the screen shows Complete the fields required.

Store hash

Your BigCommerce API base path looks like https://api.bigcommerce.com/stores/123456/. The Store Hash is the numeric segment (for example 123456).

---

Orders, Tracking, and Inventory

Each block appears as a Method row.

1. Orders

   Enable the Orders checkbox when you want that behavior. After you save, you can click Get orders! to queue a manual pull. The confirmation asks you to expect about 2 minutes.

2. Update Tracking Number

   Enable Update Tracking Number when you want tracking updates sent for shipped orders according to your integration rules.

3. Update Inventory

   Enable Sync SKUs and/or Sync Synsets as needed. After Sync Synsets, click Update to run an inventory push. Update opens a confirmation that starts with Warning!! and states that inventory quantities in the channel may be substitued for the quantities in this system.

---

Why Use BigCommerce v3?

REST API credentials

Store configuration uses Access Token, Client ID, and Store Hash, plus an Order status list for which BigCommerce order statuses to import.

Orders, tracking, inventory

Enable Orders, Update Tracking Number, and Update Inventory (with Sync SKUs and Sync Synsets checkboxes) when your account supports those services.

In-app help

Use Get Help next to the channel to open the ShipEdge help center search for BigCommerce v3.

Best Practices

Test with real orders in mind

The Channel Automation screen recommends having orders ready to import before you rely on the configuration, and to recheck credentials if nothing imports.

PII access

The same screen reminds you that the integration needs access to personally identifiable information (PII) if addresses and phone numbers should transfer correctly.

SKU alignment

Keep BigCommerce SKUs aligned with ShipEdge SKUs (or your approved alias rules) so order lines import cleanly.

---

Troubleshooting

Problem	What to try
Channel row missing	Your account may be restricted for that enterprise, or the channel may be off for the deployment—confirm with support.
Cannot save	Complete required fields; look for Complete the fields required.
Get orders! seems delayed	The confirmation mentions ~2 minutes; the post-submit alert allows 2 to 15 minutes. Wait, then use View api logs (under API Parameters) or System Messages if your role has access.
Need official BigCommerce steps	Use BigCommerce’s current Admin paths (Advanced Settings → API Accounts) or watch the video above.

---

Related Links

Next steps: Setting Up Integrations · Integrations Overview · Order Rules