Skip to navigation

Changelog

October 30, 2026

B2B GraphQL: quoteUpdate accepts a quote uuid

The B2B GraphQL quoteUpdate mutation now accepts an optional uuid argument, which the mutation checks against the quote before it updates. You will see this change in all stores over the coming week.

  • uuid argument: when you send it, the mutation matches the quote by store, quote id and uuid. A uuid that is malformed or does not match the quote returns Quote not exist, and the quote is left unchanged.
  • userEmail is now optional: on a guest quote, the message author is the contact name stored on the quote, and an email in the request does not change it.
  • Existing calls: a request that omits uuid behaves as it does today.
  • B2B and B2C quotes: the existing owner checks still apply, and the uuid does not replace them.

For details, see the quoteUpdate mutation in the B2B GraphQL API reference.

October 30, 2026

Braintree local payment methods: fix for a false error after payment

BigCommerce is rolling out a fix for a false error at checkout after a shopper paid with a Braintree local payment method, such as Alipay.

  • No false error at checkout: when Braintree confirmed the payment and the shopper returned to the store at nearly the same time, the second request was rejected. With the fix, the shopper sees the order confirmation.
  • Captured payments stay captured: the rejected request could report the captured payment as failed, so the order’s payment could show as declined. The fix reports it as captured.
  • No change to your setup: the fix needs no action from store owners or developers, and no API fields, values, or endpoints change.

Your shoppers will see the order confirmation instead of the error over the coming weeks as the fix reaches every store.

October 30, 2026

Shared modifiers no longer appear in translations

The Translations Admin GraphQL API no longer returns shared modifiers or shared modifier values, because shared modifiers do not support translations.

  • PRODUCT_MODIFIERS queries — shared modifiers are no longer included in translations results. Modifiers that belong to a single product are returned as before.
  • PRODUCT_MODIFIER_VALUES queries — values of shared modifiers are no longer included in results.
  • Page sizes — a page can contain fewer results than the first argument you requested. Continue with the returned cursor as usual.
  • Rollout — you will see this change in your store over the coming weeks. Updates and deletions for shared modifiers and their values were already rejected.
October 30, 2026

Shopping Agent shows a Beta tag in the control panel

We are beginning to roll out a BETA tag on Shopping Agent in the control panel, to show that the feature is in open beta.

  • Navigation: the tag appears beside Shopping Agent in the Agents menu.
  • Page headers: the tag appears beside the title on each Shopping Agent page, including Dashboard, Behavior, Knowledge, Settings, and Packages and billing.
  • All merchants: the tag appears whether or not a store has activated Shopping Agent or purchased conversations.

You will notice this change in the control panel over the coming weeks.

October 30, 2026

Shopping Agent shows plain error messages in the control panel

The Shopping Agent pages in the control panel no longer show raw technical error text, such as “Request failed: 502” followed by an internal request path, when a request fails.

  • Purchase history — under Packages and billing, a failed load now says “Purchase history could not be loaded. Try again in a few minutes.”
  • Other errors — failed loads and actions on the Shopping Agent pages, such as buying a package or uploading a document, now say “Something went wrong. Please try again in a few minutes.”
  • Unchanged — error messages that explain what to fix, such as a rejected agent name, still appear as before
October 30, 2026

Shopping Agent shows a friendly message when a request fails

When a request to the Shopping Agent fails, the chat widget on your storefront no longer shows shoppers raw technical text, such as “Server error 503” followed by a proxy error. Shoppers now get a short, plain reply from the agent, with a way to try again.

  • Failed requests — connection failures, timeouts, and server errors now show “Sorry, something went wrong on our end. Please try again.” as a regular agent message, without the red warning style
  • Try again — a Try again button resends the shopper’s message in one click, without repeating it in the conversation
  • Too many requests — when the agent is busy, shoppers see a separate message asking them to wait a moment
  • Technical details — the raw error text is written to the browser console for debugging and is no longer shown in the chat