# Commerce provider setup and selection

Choose which store supplies each commerce operation for your website and subsites.

*Release 3.3 · admin, developer*

**Settings › Commerce › Commerce Providers**

## What it is

**Commerce Providers** connects INSIDE to your store's products, customers and orders. You choose which tasks each provider supplies and where it applies. Different tasks can use different providers.

## Who uses it and why

Administrators with **Settings** choose stores, operations and subsite coverage. Users with **Developer** connect supported stores or a prepared custom integration. You need **Settings** with the relevant **AI** access, or **Developer**, to manage providers.

## Where to find it

Open **Settings › Commerce › Commerce Providers**. The list shows **Provider**, **Use for**, **Availability** and **Enabled**.

## How it works

For each requested operation, INSIDE considers enabled providers that supply that operation. Providers for the matching **Selected subsites** take priority over **Website default** providers. Within each group, the list order decides priority. Providers that cannot currently supply the operation are skipped during selection.

A Commerce function with an explicitly selected **Commerce Provider** uses that provider independently of automatic subsite routing. It cannot switch to another store if its selected provider is disabled or unavailable.

Use the list's **test** action to check currently available selected operations. A successful result names those operations. It can still report restrictions on other store access.

## Configure it

1. Select **New** and enter a unique **Name**.
2. Choose **Provider type** and complete its connection details.
3. Select at least one supported operation under **Use for**.
4. Set **Availability**. For **Selected subsites**, select at least one subsite belonging to this website.
5. If operators should use this catalogue, enable **Replace the standard Products panel** and choose any **Product filters**.
6. Save, then use **test**. Use **move up** and **move down** to change priority.

For a new selection, the editor initially selects supported operations other than **Customer search** and **Order search**. Review these choices before saving.

Turn **Enabled** off to remove a provider from selection while keeping its configuration. Deleting a native store provider also removes its saved connection credentials.

### Settings

| Setting | Where | Applies to | Default | Who can change it | What it does |
|---|---|---|---|---|---|
| Enabled | Settings › Commerce › Commerce Providers | website | On for a new provider | Settings role, Developer role | Makes the provider eligible for its selected operations and availability. |
| Use for | Settings › Commerce › Commerce Providers | website | Supported operations except Customer search and Order search | Settings role, Developer role | Selects the product, customer and order operations this provider may supply. At least one is required. |
| Availability | Settings › Commerce › Commerce Providers | website | Website default | Settings role, Developer role | Applies the provider across the website or only to selected subsites. |
| Replace the standard Products panel | Settings › Commerce › Commerce Providers | website | Off | Settings role, Developer role | Uses commerce product search and product cards in the operator Products panel when this provider is selected. |
| Product filters | Settings › Commerce › Commerce Providers | website | Not set | Settings role, Developer role | Chooses which provider filters operators see. An empty selection gives a search-only panel. |

### Fields

| Field | Where | Required | What it is for |
|---|---|---|---|
| Name | Settings › Commerce › Commerce Providers | Yes | Identifies the provider in INSIDE. Use a unique name within the website, up to 200 characters. |
| Provider type | Settings › Commerce › Commerce Providers | Yes | Chooses the store integration, UCP connection or custom script and its connection fields. |

### Permissions

| Permission | Lets you |
|---|---|
| Settings | Manage Commerce Providers, subject to the AI permission and View Only restriction. |
| AI | Allows a Settings role to use commerce administration when its Settings permissions are restricted. |
| Developer | Access commerce provider administration. |
| View Only | Restricts the Settings role to viewing configuration. |

## Limits and good to know

- Selecting an operation does not grant the required store permissions. The connection must have access too.
- The Products panel replacement requires **Product search**. Filters also require **Product facets**.
- You can select up to 50 distinct product filters.
- An existing website-specific product search customisation takes priority over the commerce Products panel replacement.
- Visitor access to private records requires separate verification. Enabling customer or order operations alone does not grant visitors access.

## Depends on and works with

### This feature uses

- **Configured in** [Roles and permissions](ADM-008.md): Roles and permissions control commerce administration.
- **Configured in** [AI functions and required inputs](AI-016.md): A Commerce function can select a fixed provider instead of automatic routing.
- **Configured in** [Customer and order access](COM-012.md): Customer and order access options control visitor verification separately from operator reads.
- **Works better with** [Subsites](ADM-003.md): Subsites let providers serve selected brands, regions or country sites within the website.
- **Works better with** [Shopify commerce connection](COM-002.md): Supplies the Shopify provider option.
- **Works better with** [Salesforce B2C Commerce connection](COM-003.md): Supplies the Salesforce B2C Commerce provider option.
- **Works better with** [BigCommerce store connection](COM-004.md): Supplies the BigCommerce provider option.
- **Works better with** [UCP product catalogue connection](COM-005.md): Supplies the UCP Connection provider option.
- **Works better with** [Custom commerce integrations](COM-006.md): Supplies website-specific Custom Script providers.

### Used by

- **Required by** [Shopify commerce connection](COM-002.md): Shopify must be saved and enabled as a Commerce Provider with selected operations.
- **Required by** [Salesforce B2C Commerce connection](COM-003.md): Connection operations and availability are selected in Commerce Providers.
- **Required by** [BigCommerce store connection](COM-004.md): BigCommerce is configured as a provider with selected operations and availability.
- **Required by** [UCP product catalogue connection](COM-005.md): The connection must be selected in an enabled Commerce Provider with the required operations.
- **Required by** [Custom commerce integrations](COM-006.md): Custom providers use the shared enabled operations, availability and routing rules.
- **Required by** [Product search and filters](COM-007.md): An enabled provider must supply Product search; provider settings choose panel filters.
- **Required by** [Store product selection for chat](COM-009.md): The commerce Products panel needs an enabled provider with Product search and panel replacement selected.
- **Required by** [Store customer matches and orders](COM-010.md): The CRM panel needs an enabled provider with customer lookup or order listing available for the visitor.
- **Required by** [AI customer and order search](COM-011.md): Private search needs a fixed enabled provider with the requested operations selected.
- **Required by** [Customer and order access](COM-012.md): Visitor access uses an enabled provider with authorisation support.
- **Required by** [Store order details and history](COM-013.md): The provider must support and enable the requested customer or order operation.
- **Required by** [AI commerce functions and access limits](COM-029.md): A provider must support and enable the requested operation.
- **Configures** [Product options and variant selection](COM-008.md): Product lookup for incomplete cards is enabled on the selected Commerce Provider.
- **Enhances** [Product recommendations and purchase tracking](COM-017.md): An available provider supplies authoritative product information for matching suggestions.

## FAQ and troubleshooting

### Why is a different provider used on one subsite?

A matching **Selected subsites** provider takes priority over a **Website default** provider for the requested operation. Check its enabled operations and list order.

### Why does the test succeed when order access fails?

Success means at least one selected operation is currently available. Read the result's operation list and any connection warnings, then check the store's customer and order permissions.

### Why does an AI function ignore the provider order?

Check **Commerce Provider** in **Settings › AI › Functions**. An explicit selection fixes that function to one provider.

### Why can I see the screen but not save?

Check **View Only** and the **AI** permission for your **Settings** role. Role permissions are managed through Roles and permissions.