# BigCommerce store connection

Connect BigCommerce products, customers and orders to INSIDE and support eligible additions to the shopper's basket.

*Release 3.3 · admin, developer, operator, visitor*

**Settings › Commerce › Commerce Providers**

## What it is

**BigCommerce** supplies products, customer matches and orders to INSIDE. Operators can use this information in conversations. Eligible product cards can also add a selected variant to the visitor's own shopping basket.

## Who uses it and why

Administrators with **Settings** or **Developer** connect the store and grant its API permissions. Operators find products and private records. Visitors choose supported product variants and access verified order information.

## Where to find it

Open **Settings › Commerce › Commerce Providers** and choose **BigCommerce** as **Provider type**. Connection administration needs **Settings** with the relevant **AI** access, or **Developer**.

## How it works

INSIDE validates the store connection and checks which product, customer and order reads are available. Catalogue search uses the store's available filters. Dynamic Storefront filters use an explicit Storefront token or a private token generated from the Management API credentials.

Exact customer and guest-order email matches are checked against returned records. Related private order information is read only after the applicable ownership check. An order header can remain visible even when line items cannot be loaded.

Before offering a native basket action, product detail loads variants and checks modifiers. Required or unchecked modifiers prevent that action. The shopper can use the product page instead.

## Configure it

Create the provider, enter **Store hash** and **Management API access token**, and optionally supply **Client ID** and **Storefront URL**. Use a Management API account with read-only access to Information & Settings, Products, Customers and Orders. Dynamic filters also need Modify access to Storefront API Tokens for automatic token generation.

Normally, leave **Storefront API token override** blank. Supply it only when an explicit override is needed. **Remove the saved Storefront API token** removes a previous override.

Select **Use for** operations, set **Availability**, save and use **test**. Configure product panel replacement and visitor access separately. Store sign-in requires an app-level Current Customer integration; the store-level Management API token cannot identify a shopper.

### Fields

| Field | Where | Required | What it is for |
|---|---|---|---|
| Store hash | Settings › Commerce › Commerce Providers | Yes | Identifies the BigCommerce store. Use letters and numbers only. |
| Client ID | Settings › Commerce › Commerce Providers | No | Optionally identifies the Management API account. Its client secret is not used here. |
| Storefront URL | Settings › Commerce › Commerce Providers | No | Supplies the public HTTPS shopping address for product links. Store information can fill it automatically. |
| Management API access token | Settings › Commerce › Commerce Providers | No | Authenticates store reads. Required for a new store; leave blank to keep the token for the same store. |
| Storefront API token override | Settings › Commerce › Commerce Providers | No | Optionally supplies a Storefront token instead of automatic private token generation. |
| Remove the saved Storefront API token | Settings › Commerce › Commerce Providers | No | Removes the explicit Storefront token override so automatic token generation can be used. |

### Permissions

| Permission | Lets you |
|---|---|
| Settings | Configure BigCommerce, subject to AI access and View Only. |
| AI | Allows commerce administration for a restricted Settings role. |
| Developer | Configure the BigCommerce commerce provider. |

## Limits and good to know

- Product and private search pages contain up to 50 results. The operator Products panel requests 20 products at a time.
- Missing Storefront token permissions can reduce the filters available. Basic catalogue filters can remain usable.
- Basic category and brand filter choices can be cached for six hours.
- Products with required modifiers cannot use the native basket action.
- Pre-order and explicit availability information take priority over stock-count estimates.
- Commerce reads do not change orders or issue refunds. Adding to a basket is a separate action in the shopper's browser.

## Depends on and works with

### This feature uses

- **Requires** [Commerce provider setup and selection](COM-001.md): BigCommerce is configured as a provider with selected operations and availability.
- **Configured in** [Roles and permissions](ADM-008.md): Roles control connection administration.
- **Configured in** [Customer and order access](COM-012.md): Visitor order matching and Current Customer sign-in require separate access configuration.
- **Works better with** [Product search and filters](COM-007.md): Supplies product search and available catalogue filters.
- **Works better with** [Product options and variant selection](COM-008.md): Supplies variants and checks required product modifiers before basket actions.
- **Works better with** [Store customer matches and orders](COM-010.md): Supplies customer and order information in CRM.
- **Works better with** [AI customer and order search](COM-011.md): Supports private customer and order searches.
- **Works better with** [Store order details and history](COM-013.md): Supplies authorised order details and history.
- **Works better with** [Add to cart from product cards](COM-016.md): Eligible products can be added to the shopper's own storefront basket.

### Used by

- **Enhances** [Commerce provider setup and selection](COM-001.md): Supplies the BigCommerce provider option.
- **Enhances** [Product search and filters](COM-007.md): BigCommerce supplies catalogue search and available store filters.
- **Enhances** [Product options and variant selection](COM-008.md): BigCommerce supplies variants and checks modifiers before native basket actions.
- **Enhances** [Store customer matches and orders](COM-010.md): BigCommerce can supply store customer records and orders.
- **Enhances** [AI customer and order search](COM-011.md): BigCommerce supplies customer name search and order search by exact order number or email.
- **Enhances** [Customer and order access](COM-012.md): BigCommerce supports guest matching and customer sign-in through an app integration.
- **Enhances** [Store order details and history](COM-013.md): Supplies BigCommerce order information.
- **Enhances** [Add to cart from product cards](COM-016.md): BigCommerce supports finding or creating the shopper's basket and adding a line.

## FAQ and troubleshooting

### Why do products work but dynamic filters do not?

Check the Management API account's Storefront API Tokens permission, or the explicit **Storefront API token override**. Some basic filters may remain available without dynamic Storefront filtering.

### Why is a token required again after changing Store hash?

A different store needs its own Management API credentials. INSIDE does not reuse the previous store's token.

### Why does a product have no basket action?

It may have required modifiers, incomplete options or no available variant. Open its product page to complete the store's purchase choices.

### Why can I see an order total but no products?

The order header can load even if the store's related line-item read fails. Refresh the customer information and check the connection's order permissions.