> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# BigCommerce Webhook Setup Guide

> Configure BigCommerce to deliver events to StackOne.

## Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See [Getting Started](https://docs.stackone.com/connectors/bigcommerce.md#getting-started) on the BigCommerce connector page.

## How BigCommerce webhooks are set up

There is nothing to configure in BigCommerce and no URL to copy. BigCommerce has no webhook screen in the control panel — webhooks are an API-only feature — so StackOne registers one webhook per event you enable, pointing at its own receiver, and removes them again when the account is disconnected.

<ul>
  <li>No callback URL to paste, and no verification step to complete.</li>
  <li>Webhooks are registered against the store whose **Store Hash** this connection uses.</li>
  <li>Only the events you enable in StackOne are registered in BigCommerce and delivered.</li>
  <li>You can review the registered webhooks by calling **GET /v3/hooks** on the store.</li>
</ul>

## Before you connect

Check the API account can manage webhooks and read the data the events point at.

<ul>
  <li>Give the API account the **Webhooks** scope set to **modify**.</li>
  <li>Webhook payloads are deliberately minimal — they carry ids, not records — so give the token read access to the resources you care about (orders, products, customers) if you intend to fetch the full record after an event.</li>
  <li>A webhook subscription is deactivated by BigCommerce after 90 days with no deliveries.</li>
</ul>

## Available webhook events

The following BigCommerce events can be enabled. Only events selected in StackOne are registered in BigCommerce and delivered — BigCommerce will not send events you have not subscribed to.

**1. Cart events**

Events on shopping carts, their line items and cart metafields.

<ul>
  <li>**Cart Abandoned** (`store/cart/abandoned`) — Fires when a cart is abandoned. A cart is considered abandoned when no changes have been made for at least one hour after the last modified property. This webhook is available for all store plans, regardless of whether the Abandoned Cart Saver feature is enabled</li>
  <li>**Cart Converted** (`store/cart/converted`) — Fires when a cart is converted into an order, which is typically after the payment step of checkout on the storefront. At this point, the cart is no longer accessible and has been deleted. This hook returns both the cart ID and order ID for correlation purposes</li>
  <li>**Cart Coupon Applied** (`store/cart/couponApplied`) — Fires when a new coupon code is applied to a cart. The payload includes the ID of the coupon code</li>
  <li>**Cart Created** (`store/cart/created`) — Fires when a new cart is created, either when a storefront shopper adding their first item to the cart, or when a new cart is created by API. If it is from the storefront, then it fires when the first product is added to a new session; the cart did not exist before. For the API it means a POST</li>
  <li>**Cart Deleted** (`store/cart/deleted`) — Fires when a cart is deleted. This occurs either when all items have been removed from a cart and it is auto-deleted, or when the cart is explicitly removed by a DELETE request to an API. This ends the lifecycle of the cart. The store/cart/updated webhook also fires when the last item is removed</li>
  <li>**Cart Line Item Created** (`store/cart/lineItem/created`) — Fires when a new item is added to the cart</li>
  <li>**Cart Line Item Deleted** (`store/cart/lineItem/deleted`) — Fires when an item is deleted from the cart</li>
  <li>**Cart Line Item Updated** (`store/cart/lineItem/updated`) — Fires when an item’s quantity has changed or the product options change</li>
  <li>**Cart Metafield Created** (`store/cart/metafield/created`) — Fires on store/cart/metafield/created</li>
  <li>**Cart Metafield Deleted** (`store/cart/metafield/deleted`) — Fires on store/cart/metafield/deleted</li>
  <li>**Cart Metafield Updated** (`store/cart/metafield/updated`) — Fires on store/cart/metafield/updated</li>
  <li>**Cart Updated** (`store/cart/updated`) — Fires when a cart is modified through the changes in its line items. The payload includes the ID of the cart being updated. Qualifying events include a new item added to a cart, an existing item quantity updated, an existing item deleted, a cart created - the</li>
</ul>

**2. Catalog events**

Events on products, variants, SKUs, categories, brands, modifiers and options.

<ul>
  <li>**Brand Metafield Created** (`store/brand/metafield/created`) — Fires on store/brand/metafield/created</li>
  <li>**Brand Metafield Deleted** (`store/brand/metafield/deleted`) — Fires on store/brand/metafield/deleted</li>
  <li>**Brand Metafield Updated** (`store/brand/metafield/updated`) — Fires on store/brand/metafield/updated</li>
  <li>**Category Created** (`store/category/created`) — Fires when a category is created</li>
  <li>**Category Deleted** (`store/category/deleted`) — Fires when a category is deleted</li>
  <li>**Category Metafield Created** (`store/category/metafield/created`) — Fires on store/category/metafield/created</li>
  <li>**Category Metafield Deleted** (`store/category/metafield/deleted`) — Fires on store/category/metafield/deleted</li>
  <li>**Category Metafield Updated** (`store/category/metafield/updated`) — Fires on store/category/metafield/updated</li>
  <li>**Category Updated** (`store/category/updated`) — Fires when a category is updated</li>
  <li>**Modifier Updated** (`store/modifier/updated`) — Only fires when you edit attributes for a local or shared modifier in a context of a channel and locale. For information on updating overrides, see the International Enhancements for Multi-Storefront overview</li>
  <li>**Option Updated** (`store/option/updated`) — Fires when you customize display name and values for a local or shared variant option in a context of a channel and locale. For information on updating overrides, see the International Enhancements for Multi-Storefront overview</li>
  <li>**Product Created** (`store/product/created`) — Fires when a new product is created</li>
  <li>**Product Deleted** (`store/product/deleted`) — Fires when a product is deleted</li>
  <li>**Product Inventory Order Updated** (`store/product/inventory/order/updated`) — Fires when *base product* inventory levels change in response to the order-related events configured in Inventory settings. For example, stock levels can change when you either place or complete/ship an order. Stock levels can also change when an order status changes to `Cancelled` or `Refunded`,</li>
  <li>**Product Inventory Updated** (`store/product/inventory/updated`) — Fires when inventory levels change for a *base product*. For products without variants, the webhook fires regardless of how you track inventory. For products with variants, the webhook only fires when the product's inventory properties are configured to track by *product* and the *product-level*</li>
  <li>**Product Metafield Created** (`store/product/metafield/created`) — Fires on store/product/metafield/created</li>
  <li>**Product Metafield Deleted** (`store/product/metafield/deleted`) — Fires on store/product/metafield/deleted</li>
  <li>**Product Metafield Updated** (`store/product/metafield/updated`) — Fires on store/product/metafield/updated</li>
  <li>**Product Updated** (`store/product/updated`) — Fires when you edit product attributes globally or for a channel locale as an override. For a full list of product fields that trigger an updated event, see the product updated events that follow. The properties and context fields are present for only updates to overrides, not the global store</li>
  <li>**Product Variant Metafield Created** (`store/product/variant/metafield/created`) — Fires on store/product/variant/metafield/created</li>
  <li>**Product Variant Metafield Deleted** (`store/product/variant/metafield/deleted`) — Fires on store/product/variant/metafield/deleted</li>
  <li>**Product Variant Metafield Updated** (`store/product/variant/metafield/updated`) — Fires on store/product/variant/metafield/updated</li>
  <li>**Sku Created** (`store/sku/created`) — Fires when a new SKU is created</li>
  <li>**Sku Deleted** (`store/sku/deleted`) — Fires when a SKU is deleted</li>
  <li>**Sku Inventory Order Updated** (`store/sku/inventory/order/updated`) — Fires when *variant* inventory levels change in response to the order-related events configured in Inventory settings. For example, stock levels can change when you either place or complete/ship an order. Stock levels can also change when an order status changes to `Cancelled` or `Refunded`, but not</li>
  <li>**Sku Inventory Updated** (`store/sku/inventory/updated`) — Fires when inventory levels change for a *variant*. This webhook does not fire for products without variants. For products with variants, the webhook only fires when the product's inventory properties are configured to track by *variant* and the *variant-level* inventory changes. Inventory</li>
  <li>**Sku Updated** (`store/sku/updated`) — Fires when a SKU is updated</li>
</ul>

**3. Customer events**

Events on customers, their addresses, metafields and payment instruments.

<ul>
  <li>**Customer Address Created** (`store/customer/address/created`) — Fires when a customer address is created</li>
  <li>**Customer Address Deleted** (`store/customer/address/deleted`) — Fires when a customer address is deleted</li>
  <li>**Customer Address Updated** (`store/customer/address/updated`) — Fires when a customer address is updated</li>
  <li>**Customer Channel Login Access Updated** (`store/customer/channel/login/access/updated`) — Fires on update of any customer's login access. The corresponding endpoint is Update a customer</li>
  <li>**Customer Created** (`store/customer/created`) — Fires when a new customer is created</li>
  <li>**Customer Deleted** (`store/customer/deleted`) — Fires when a customer is deleted</li>
  <li>**Customer Metafield Created** (`store/customer/metafield/created`) — Fires on store/customer/metafield/created</li>
  <li>**Customer Metafield Deleted** (`store/customer/metafield/deleted`) — Fires on store/customer/metafield/deleted</li>
  <li>**Customer Metafield Updated** (`store/customer/metafield/updated`) — Fires on store/customer/metafield/updated</li>
  <li>**Customer Payment Instrument Default Updated** (`store/customer/payment/instrument/default/updated`) — Fires when a customer default payment instrument is updated</li>
  <li>**Customer Updated** (`store/customer/updated`) — Fires when a customer is updated. It does not currently track changes to the customer address. Tracks changes to customer attributes only if you make the changes through the control panel. This change triggers the same event type and payload as updating a customer; the payload does not include</li>
</ul>

**4. Order and shipment events**

Events on orders, their transactions, refunds, messages and shipments.

<ul>
  <li>**Order Archived** (`store/order/archived`) — Fires when an order is archived</li>
  <li>**Order Created** (`store/order/created`) — Fires when an order is created from the storefront, using the control panel, an app, or the API. It also fires for incomplete orders, including failed payment and payment not processed orders</li>
  <li>**Order Message Created** (`store/order/message/created`) — Fires if order message is created by a customer or in the control panel</li>
  <li>**Order Metafield Created** (`store/order/metafield/created`) — Fires on store/order/metafield/created</li>
  <li>**Order Metafield Deleted** (`store/order/metafield/deleted`) — Fires on store/order/metafield/deleted</li>
  <li>**Order Metafield Updated** (`store/order/metafield/updated`) — Fires on store/order/metafield/updated</li>
  <li>**Order Refund Created** (`store/order/refund/created`) — Fires if a refund has been submitted against an order</li>
  <li>**Order Status Updated** (`store/order/statusUpdated`) — Fires only if the order status has changed, such as Pending to Awaiting Payment</li>
  <li>**Order Transaction Created** (`store/order/transaction/created`) — Fires when a transaction record is created</li>
  <li>**Order Transaction Updated** (`store/order/transaction/updated`) — Fires when a transaction record is updated</li>
  <li>**Order Updated** (`store/order/updated`) — Fires when an already created order is updated. Any change to an existing order fires this webhook. Updates can include changing the status, updating a coupon, or changing an address</li>
  <li>**Shipment Created** (`store/shipment/created`) — Fires when a shipment is created</li>
  <li>**Shipment Deleted** (`store/shipment/deleted`) — Fires when a shipment is deleted</li>
  <li>**Shipment Updated** (`store/shipment/updated`) — Fires when a shipment is updated</li>
</ul>

**5. Price list events**

Events on price lists, their records and assignments.

<ul>
  <li>**Price List Activated** (`store/priceList/activated`) — Fires when a price list is activated</li>
  <li>**Price List Assignment Updated** (`store/priceList/assignment/updated`) — Fires when a price list assignment is assigned, reassigned, or unassigned. The corresponding endpoint is Create price list assignments. BigCommerce sends no record id for this event (data is an array or carries only a type), so the store id identifies the delivery</li>
  <li>**Price List Created** (`store/priceList/created`) — Fires when a price list is created</li>
  <li>**Price List Deactivated** (`store/priceList/deactivated`) — Fires when a price list is deactivated</li>
  <li>**Price List Record Created** (`store/priceList/record/created`) — Fires when a price list record is created</li>
  <li>**Price List Record Deleted** (`store/priceList/record/deleted`) — Fires when a price list record is deleted</li>
  <li>**Price List Record Updated** (`store/priceList/record/updated`) — Fires when an existing specific price list record is updated by variant and currency</li>
  <li>**Price List Records Created** (`store/priceList/records/created`) — Fires when price list records are created. BigCommerce sends no record id for this event (data is an array or carries only a type), so the store id identifies the delivery</li>
  <li>**Price List Records Deleted** (`store/priceList/records/deleted`) — Fires when price list records are deleted. BigCommerce sends no record id for this event (data is an array or carries only a type), so the store id identifies the delivery</li>
  <li>**Price List Records Updated** (`store/priceList/records/updated`) — Fires when you update one or more existing price list records using any batch call. BigCommerce sends no record id for this event (data is an array or carries only a type), so the store id identifies the delivery</li>
  <li>**Price List Updated** (`store/priceList/updated`) — Fires when a price list is updated</li>
  <li>**Price Lists Deleted** (`store/priceLists/deleted`) — Fires when one or more price lists are deleted. BigCommerce sends no record id for this event (data is an array or carries only a type), so the store id identifies the delivery</li>
</ul>

**6. Inventory and location events**

Events on inventory levels and inventory locations.

<ul>
  <li>**Channel Inventory Product Low\_stock\_reached** (`store/channel/*/inventory/product/low_stock_reached`) — Fires when a product or variant stock level is lower or equal to the low-stock value at a location. Stock levels must change through an order</li>
  <li>**Channel Inventory Product Out\_of\_stock\_reached** (`store/channel/*/inventory/product/out_of_stock_reached`) — Fires when a product or variant stock level is zero at a location. Stock levels must change through an order</li>
  <li>**Channel Inventory Product Settings\_changed** (`store/channel/*/inventory/product/settings_changed`) — Fires when a product's safety stock, is\_in\_stock flag, or warning level changes at a location. A product or variant's inventory settings apply to all storefront channels. Changing a product or variant's inventory settings triggers one webhook event. The corresponding endpoint is Update inventory</li>
  <li>**Channel Inventory Product Stock\_changed** (`store/channel/*/inventory/product/stock_changed`) — Fires when a product or variant stock level changes at a location. For example, stock levels can change by manual merchant adjustments in the control panel or API. The corresponding endpoint is Absolute adjustment</li>
  <li>**Inventory Location Created** (`store/inventory/location/created`) — Fires when a location is created. The corresponding endpoint is Create locations</li>
  <li>**Inventory Location Deleted** (`store/inventory/location/deleted`) — Fires when a location is deleted. The corresponding endpoint is Delete locations</li>
  <li>**Inventory Location Metafield Created** (`store/inventory/location/metafield/created`) — Fires on store/inventory/location/metafield/created</li>
  <li>**Inventory Location Metafield Deleted** (`store/inventory/location/metafield/deleted`) — Fires on store/inventory/location/metafield/deleted</li>
  <li>**Inventory Location Metafield Updated** (`store/inventory/location/metafield/updated`) — Fires on store/inventory/location/metafield/updated</li>
  <li>**Inventory Location Updated** (`store/inventory/location/updated`) — Fires when a location is updated, including enabling or disabling a location. The corresponding endpoint is Update locations</li>
</ul>

**7. Store, channel and subscriber events**

Events on store settings, channels, metafields, redirects and subscribers.

<ul>
  <li>**App Uninstalled** (`store/app/uninstalled`) — Fires when a client store is canceled and uninstalled from the platform</li>
  <li>**Channel Created** (`store/channel/created`) — Fires when a channel is created using the control panel or the API. The corresponding endpoint is Create a channel</li>
  <li>**Channel Metafield Deleted** (`store/channel/metafield/deleted`) — Fires when any channel metafield is deleted. The corresponding endpoint is Delete a channel metafield</li>
  <li>**Channel Metafield Updated** (`store/channel/metafield/updated`) — Fires when any channel metafield is updated. The corresponding endpoint is Update a channel metafield</li>
  <li>**Channel Updated** (`store/channel/updated`) — Fires when a channel is updated using the control panel or the API. The corresponding endpoint is Update a channel</li>
  <li>**Information Updated** (`store/information/updated`) — Fires when changes are made to store settings. For a full list of fields that can trigger this event, consult the following section on store information updated events. BigCommerce sends no record id for this event (data is an array or carries only a type), so the store id identifies the delivery</li>
  <li>**Metafield Created** (`store/metafield/created`) — Fires on store/metafield/created</li>
  <li>**Metafield Deleted** (`store/metafield/deleted`) — Fires on store/metafield/deleted</li>
  <li>**Metafield Updated** (`store/metafield/updated`) — Fires on store/metafield/updated</li>
  <li>**Redirects Updated** (`store/redirects/updated`) — Fires when redirects are created or updated. One event covers every redirect in the request. The corresponding endpoint is Upsert redirects. Deleting redirects doesn't fire this event. BigCommerce sends no record id for this event (data is an array or carries only a type), so the store id identifies the delivery</li>
  <li>**Store Metafield Created** (`store/store/metafield/created`) — Fires on store/store/metafield/created</li>
  <li>**Store Metafield Deleted** (`store/store/metafield/deleted`) — Fires on store/store/metafield/deleted</li>
  <li>**Store Metafield Updated** (`store/store/metafield/updated`) — Fires on store/store/metafield/updated</li>
  <li>**Subscriber Created** (`store/subscriber/created`) — Fires when a subscriber is created</li>
  <li>**Subscriber Deleted** (`store/subscriber/deleted`) — Fires when a subscriber is deleted</li>
  <li>**Subscriber Updated** (`store/subscriber/updated`) — Fires when a subscriber is updated</li>
</ul>

## Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.