For AI agents: a documentation index is available at the root level at /llms.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
LogoLogo
Dev Portal
DocsAPI ReferenceLearnCommunityChangelog
DocsAPI ReferenceLearnCommunityChangelog
Dev Portal
On this page
  • September 9, 2026
  • GraphQL Schema Updates
  • September 8, 2026
  • Stencil CLI 10.0.0
  • September 7, 2026
  • Translate transactional email templates
  • September 4, 2026
  • Cart option labels follow the cart's locale on Stencil storefronts
  • September 2, 2026
  • Checkout theme files are now documented for headless channels
  • September 1, 2026
  • Backorder messaging is now generally available
  • Sorting for customer orders in the GraphQL Storefront API
  • Orphaned catalog trees and category data are cleaned up on deletion
  • August 31, 2026
  • Catalyst 1.10.1
  • Catalyst 1.11.0

Changelog


September 9, 2026
September 9, 2026

September 8, 2026
September 8, 2026

September 7, 2026
September 7, 2026

September 4, 2026
September 4, 2026

September 2, 2026
September 2, 2026

September 1, 2026
September 1, 2026

September 1, 2026
September 1, 2026

September 1, 2026
September 1, 2026

August 31, 2026
August 31, 2026

August 31, 2026
August 31, 2026
Older posts
Next
Built with

GraphQL Schema Updates

Inventory and backorder capabilities expand across the Storefront and Admin GraphQL schemas.

Storefront GraphQL

  • Inventory and backorder fields: the inventory and order types now expose inventory and backorder details.
    • Product inventory: availableOnHand, unlimitedBackorder, and availableForBackorder on both the Aggregated and AggregatedInventory types.
    • Inventory settings: showQuantityOnBackorder, showQuantityOnHand, showBackorderMessage, showBackorderAvailabilityPrompt, backorderAvailabilityPrompt, showDefaultShippingExpectationPrompt, and defaultShippingExpectationPrompt on InventorySettings, plus backorderMessage on InventoryByLocations.
    • Cart items: stockPosition on CartDigitalItem and CartPhysicalItem.
    • Orders: backorderShippingExpectationMessage on the BaseOrder interface (and therefore on Order and OrderWithPayments), plus backorderedQuantity and backorderMessage on OrderPhysicalLineItem.

Admin GraphQL

  • Backorder message management: a new inventory field on the Store and Mutation types exposes backorder messages.
    • Query: Store.inventory.backorderMessages returns the store’s backorder messages, filterable by ID or name through GetBackorderMessagesFiltersInput.
    • Mutations: Mutation.inventory provides createBackorderMessages, updateBackorderMessages, and deleteBackorderMessages.
    • Type: the new BackorderMessage type exposes id, name, message, isDefault, createdAt, and updatedAt.
  • Product backorder inventory fields: new backorderLimit and qtyBackordered fields on the AggregatedProductInventory and AggregatedProductVariantInventory types.
  • New currency code: the CurrencyCode enum adds XCG (Caribbean guilder).

Account GraphQL

  • New currency code: the CurrencyCode enum adds XCG (Caribbean guilder).

For schema details, browse the Storefront GraphQL API reference, Admin GraphQL API reference, and Account GraphQL API reference.

Stencil CLI 10.0.0

Stencil CLI 10.0.0 raises the minimum supported Node.js version to Node 24 and drops support for Node 20 and Node 22.

  • Node 24 required — Stencil CLI now requires Node 24 or later to run. Node 20 and Node 22 are no longer supported.
  • Breaking change — this is a major version release. Update your local and CI environments to Node 24 before upgrading Stencil CLI.

For installation instructions, see Installing Stencil CLI.

Translate transactional email templates

B2B Edition merchants can now translate every transactional email template — company approvals, invoices, quotes, and more — directly from the control panel, so each recipient gets the email in their own language.

  • Per-locale translations — edit each template’s text for any locale enabled on the storefront, using the new Phrases tab.
  • Shared layout — the Code tab’s HTML and subject line stay the same across all languages; only the translated text changes per locale.
  • Preview and test — preview a template in each language before sending, or send yourself a test email.
  • Reset to system defaults — revert a customized template, and all its translations, back to BigCommerce’s original wording.

For details, see Transactional Emails.

Cart option labels follow the cart’s locale on Stencil storefronts

On multi-language Stencil storefronts, product option and modifier labels on the cart page and the cart Quick View modal now render in the cart’s stored locale, matching the option values and product name on the same line item. This fixes a bug that affected carts created through the REST Carts API (POST /v3/carts).

  • What was wrong — Labels were read live from the catalog in the language of the current request, while the values came from the cart itself. When a cart’s locale differed from the request’s locale, the label fell back to the store’s default language while the value stayed translated, for example Color: Bleu instead of Couleur: Bleu.
  • Who was affected — Carts created with the REST Carts API Create a Cart endpoint (POST /v3/carts) using an explicit locale, then opened through a redirect_urls link that resolves to a different storefront language.
  • What changed — The name of each entry in the cart object’s items[].options[] array now comes from the cart’s own snapshot of the selected options, the same source the checkout page uses.
  • Action required — None. Themes that render {{name}} for cart item options, as Cornerstone does, pick up the fix automatically. Single-language stores and carts viewed in the language they were created in are unaffected.

For the cart object properties, see the Stencil object reference.

Checkout theme files are now documented for headless channels

Checkout renders from BigCommerce even when your storefront does not, so its text and styling come from the theme attached to your channel. New documentation covers how to reach those files on a headless channel.

  • New page: Accessing Checkout Theme Files gives the URL that opens My Themes for a specific channel, explains how to find your channel ID, and covers what to do when a read-only marketplace theme blocks file editing.

For details, see Accessing Checkout Theme Files.

Backorder messaging is now generally available

Backorder messaging — shopper-facing backorder availability, quantity, and shipping-expectation prompts across the product detail page, cart, checkout, and order confirmation — is now generally available.

  • V3 Settings API: seven new backorder display settings on GET/PUT /v3/settings/inventory (show_quantity_on_backorder, show_backorder_message, show_backorder_availability_prompt, backorder_availability_prompt, show_default_shipping_expectation_prompt, default_shipping_expectation_prompt, show_quantity_on_hand).
  • V3 Inventory API: backorder_limit, backorder_message, and qty_backordered on item and location inventory data, including backorder_limit as a writable field on inventory settings updates.
  • V2 Orders API: quantity_backordered on order line items.
  • Storefront Cart and Checkout REST APIs: a stockPosition object (quantityOnHand, quantityBackordered, quantityOutOfStock, backorderMessage) on physical and digital line items.
  • Storefront GraphQL: backorder display settings, product and variant inventory fields, cart line item stock position, and order backorder fields.
  • Stencil and Catalyst: documented context variables and reference file pointers for theme and headless storefront developers.

For details, see the Backorders guide.

Sorting for customer orders in the GraphQL Storefront API

BigCommerce is rolling out sorting for a customer’s order history in the GraphQL Storefront API, giving you control over the order in which customer.orders results are returned.

  • New sortBy argument. The customer.orders field now accepts an optional sortBy argument that takes a CustomerOrdersSortInput enum value.
  • Supported sort options. CREATED_AT_NEWEST returns orders by creation date, newest first; CREATED_AT_OLDEST returns orders by creation date, oldest first; and ID_DESCENDING returns orders by order ID in descending order.

For details, see GraphQL Storefront API: Orders.

Orphaned catalog trees and category data are cleaned up on deletion

We’re rolling out a fix so that terminating a channel no longer leaves orphaned catalog trees behind, and deleting a category no longer leaves orphaned customer group and context data behind.

  • Channel termination — trees that were assigned only to the terminated channel are now deleted along with their categories, URLs, and images, instead of remaining in the catalog with no channel assignment. Trees shared with other channels are unaffected.
  • Category deletion — deleting a category, individually or in bulk, now also removes its associated customer group restrictions and translation/override values, instead of leaving those rows behind.

You may notice changes in this area over the coming weeks as the fix rolls out. For details, see the Delete Categories reference.

Catalyst 1.10.1

Catalyst v1.10.1 is a patch release covering a Next.js security upgrade, a localization fix, and promotion callout styling.

  • Next.js security release — Next.js is upgraded from 16.2.6 to 16.2.11 to pick up the July 2026 security release.
  • Localized content after ISR revalidation — product, category, and brand content no longer falls back to the default language after revalidation. generateMetadata fetched page data before calling setRequestLocale, so during background regeneration next-intl could not resolve the locale and the default-locale response poisoned the memoized cache for the whole render.
  • Promotion callout styling — promotion callouts now use Storefront Kit’s built-in warning variant instead of custom Tailwind classes, bumping storefront-kit to ^0.32.3 so its stylesheet imports cleanly under Turbopack.

See the full 1.10.1 release notes for details and release tags.

Catalyst 1.11.0

Catalyst v1.11.0 is now available.

  • Runtime locale subfolders — merchant-configured locale subfolders such as /fr-fr and /es-es are now read from BigCommerce at runtime and cached in KV, instead of being baked into build-config.json at build time. Incomplete locale data at build time no longer 404s every localized URL until the next deploy.
  • Breaking: redirect and permanentRedirect moved — import them from ~/i18n/navigation-server instead of ~/i18n/routing, and await them. i18n/locales.ts is removed.
  • Wallet payment buttons on the cart — the cart page now renders wallet payment buttons, such as PayPal, when payment wallets are configured, initialized through the BigCommerce Checkout SDK.
  • Inventory accuracy — the PDP disables Add to Cart and shows an error when the requested quantity exceeds available-to-sell, and the cart’s “ready to ship” message now appears only when part of the line item is backordered.
  • Session, consent, and SEO fixes — session cookies are now actually deleted on logout, consent-gated cookies work on stores with cookie consent disabled, the product og:image no longer emits an unfetchable placeholder URL, and Account Registration hides State/Province for countries that have none.
  • Cache behavior — entries in the in-memory KV layer now expire after 60 seconds and its capacity rises from 500 to 4096, so processes pick up values the shared store already holds instead of each refetching from the origin.

See the full 1.11.0 release notes for migration details and release tags.