Changelog

September 22, 2026

Complete Checkout Settings reference

The REST Management API’s Checkout Settings reference now documents every field the API returns, up from seven. The store-level schema covers all 21 fields, and the channel-level schema covers the 18 fields a channel can override.

  • Checkout type and guest checkout — checkout_type, guest_checkout_type, and guest_checkout_for_existing_accounts, with their accepted values.
  • Policy consent and order terms — policy_consent, order_confirmation_contact_email, is_order_terms_and_conditions_enabled, order_terms_and_conditions_type, order_terms_and_conditions_link, and order_terms_and_conditions_textarea.
  • Custom checkout and styling — custom_checkout_supports_data_hydration, should_redirect_to_storefront_for_auth, checkout_style_override, and checkout_style_override_sri_hash.
  • B2B checkout — support_b2b_settings, returned for stores where B2B checkout settings are enabled.
  • Channel-level behavior — the channel endpoints now explain that null means a channel has no override and uses the store-level value, and each endpoint has request and response examples.

For details, see the Checkout Settings reference:

September 22, 2026

GraphQL Schema Updates

Storefront GraphQL company registration can now name the company’s primary address.

Storefront GraphQL

  • Address label on company registration: AddCompanyAddressInput, the type of the address field in RegisterCompanyInput, gains an optional label string, so a registerCompany request can name the company’s primary address (for example, “Headquarters”). The value is returned in the existing label field on CompanyAddress. Omit it to keep the previous behavior.

For schema details, see the Storefront GraphQL API reference:

September 22, 2026

Clearer connection steps on the MCP Server Overview

Thanks to user feedback, the MCP Server Overview now makes clear which steps happen in the BigCommerce control panel and which happen in your AI client. A reader following the Claude Desktop instructions went looking for a Settings → Developer menu in the control panel, because the page had just finished walking through the control panel’s Settings → Early access flow.

  • AI client lead-in — the How to connect section now opens by stating that every tab is configured in your AI client (Claude Desktop, Claude Code, Cursor, or Warp), not in BigCommerce
  • Application named in each step — the Claude Desktop, Claude Code, and Cursor instructions now name the application they apply to, matching the existing Warp step
  • Handoff sentence — the section intro now reads “Once you’ve enabled the MCP server in the control panel,” so the transition from BigCommerce to the client is explicit

For details, see the MCP Server Overview.