The Storefront GraphQL API now exposes how a cart was created and its associated B2B company.
source and companyId fields on the Cart type.
source returns the new CartSource enum, indicating how the cart was created: B2B, B2B_INVOICE, B2B_QUOTE, or BUY_NOW.companyId returns the B2B company ID associated with the cart.For schema details, browse the Storefront GraphQL API reference.
catalyst upgrade now carries @bigcommerce/catalyst* dependency version bumps through its merge automatically, the same as any other package.json change.
workspace:^ get an opt-in migration prompt after the merge, offering to swap to the published version so future upgrades can keep it current the normal way.For details, see Upgrading and the Catalyst CLI reference.
Thanks to user feedback, the Delete Products reference now explains how to clear an entire catalog.
For details, see Delete Products.
Beginning September 26, 2026, breadcrumb links on Stencil wishlist details pages will use absolute URLs instead of storefront-relative paths.
{{breadcrumbs}} will return a url that includes the storefront scheme and domain. For example, a wishlist URL will change from /wishlist.php to https://www.example.com/wishlist.php.{{url}} as-is. Themes that already render {{url}} directly, including the default Cornerstone breadcrumbs component, require no changes.For the breadcrumb properties, see the Stencil object reference.
Breadcrumb links on the Stencil order status and order details pages now use absolute URLs instead of relative paths.
page_type account_orderstatus), each item in {{breadcrumbs}} returns a url that includes the storefront scheme and domain, for example https://www.example.com/account.php?action=order_status rather than /account.php?action=order_status.templates/pages/account/orders/details.html), for example https://www.example.com/account.php?action=view_order&order_id=1000000 rather than /account.php?action=view_order&order_id=1000000.{{url}} directly, as the default Cornerstone breadcrumbs component does. If your theme prefixes {{url}} with a domain or base path of its own, remove that prefix.For the breadcrumb properties, see the Stencil object reference.
When a storefront request carries a customer ID, the platform now uses it while determining the tax zone that governs tax display. This can change whether product prices appear including tax, excluding tax, or with both values.
For how tax zones and their price display settings work, see Tax settings and Tax rates and zones.
Thanks to user feedback, the B2B Edition webhooks reference now shows the correct data object for quote events.
quote_id and quote_uuid. The previous example listed type and id, which quote webhooks do not return.For details, see B2B Edition Webhooks.
Thanks to user feedback, the GraphQL Storefront API docs now explain when and how an authenticated customer shapes a request.
X-Bc-Customer-Access-Token header). It includes a reference table of known operations that require customer context, and holds the customer access token instructions previously kept on the Authentication page.registerCompany.For details, see Customer context in the GraphQL Storefront API.
The Storefront GraphQL schema adds a way to list a store’s enabled payment methods and a display-friendly shipping provider name. These fields are alpha and marked deprecated in the schema: do not use them in production yet.
paymentMethods connection on the Site type lists the payment methods enabled for the current store and channel, returned as the new PaymentMethod type (with entityId and name).OrderShipment type adds shippingProviderDisplayName, a human-readable version of the existing shippingProviderName.companyUser query, the updateCompanyUser mutation, and the search filter on CompanyOrdersFiltersInput have been removed from the schema.For schema details, browse the Storefront GraphQL API reference.
Authenticated customers can now delete a stored payment instrument through the Storefront GraphQL API. This mutation is an alpha release: the schema marks it deprecated with the reason “Alpha version. Do not use in production.”
deleteStoredPaymentInstrument mutation on the CustomerMutations type deletes a stored payment instrument for the authenticated customer.
DeleteStoredPaymentInstrumentInput takes the token of the stored payment instrument to delete.DeleteStoredPaymentInstrumentResult returns an errors list of DeleteStoredPaymentInstrumentError; an empty list indicates success.See the Customers guide for an example mutation, or browse the Storefront GraphQL API reference for schema details.