Changelog

September 1, 2026

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.

September 1, 2026

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.

September 1, 2026

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.