Changelog

Guest contact fields stay editable on duplicated quotes

We are beginning to roll out a fix so that the guest contact fields on a duplicated quote stay editable in B2B Edition. You will see both fields stay available over the coming weeks.

• Duplicated quotes - after you duplicate a quote, replace its contact, and continue as a guest, the Name and Email fields both stay editable. Before this fix, entering one locked the other and left it blank, so the only way to finish the guest contact was to save the quote as a draft first.
• Unchanged - new quotes and drafts behave as before, and the contact fields of a sent quote stay locked when you view it.

Archive a B2B quote: response body documented

Thanks to integration feedback, the Update a Quote reference now documents the response returned when a request archives a quote, along with the rules that apply to the status field.

• Archive response: a request with "status": "archived" returns the full quote object, with status set to 6 (Archived) and the quote identified by quoteNumber rather than quoteId.
• Why the response differs: archiving closes the quote to further activity. Archived quotes are left out of list responses unless you filter for status 6, and they can’t be checked out or ordered, so the archive response returns the resulting quote object for confirmation.
• Standard update response: requests that omit status, or send any value other than "archived", return quoteId and quoteUrl.
• One archive per request: an archive request ignores the other fields in the body, so update the quote first and archive it separately.
• Only "archived" is writable: any other status value is ignored and the request is processed as a standard update.

For details, see Update a Quote.

Clearer payment method name for Braintree ACH orders

The paymentMethodName field on Storefront GraphQL order payments now returns “US Bank Account” for orders paid with ACH through Braintree. It used to return the same name as Braintree card payments, so the two could not be told apart.

• Braintree ACH payments: paymentMethodName returns “US Bank Account” instead of the same name as Braintree card payments.

The paymentMethodId value does not change. Card payments through Braintree are not affected.

Customer password reset link behavior is now documented

Thanks to developer feedback, the new customer password reset guide explains how reset links expire, when they stop working, and what a shopper or a headless storefront sees when a link is no longer valid.

• 12-hour link lifetime: a reset link is valid for 12 hours from the time the email is sent.
• One use per link: a successful reset invalidates the token, so the link cannot be used again.
• Only the newest link works: requesting another reset email invalidates earlier links, even if they have not expired.
• Other password changes leave the link valid: changing the password in the control panel, through the Customers API, or in storefront account settings does not invalidate an outstanding reset link.
• Expired link experience: on a Stencil storefront, the Set New Password page shows the invalid link message above the form when the page loads, and submitting the form returns the shopper to the Request New Password page with the same message.
• GraphQL Storefront API errors: there is no separate token validation query, so resetPassword returns a CustomerPasswordError with the message Invalid password reset token or customerEntityId. for an expired or invalid link, and the mutation returns HTTP 200.

For details, see Customer password reset.

Customers Learn more link opens the Modern Customer Management article

The Learn more link in the new View Customers and Edit Customer banners now opens the Modern Customer Management article in the Help Center. Before, it opened the older Customer Account Management article.

• Both pages: the banner’s Learn more link now points to the modern customer management guidance.
• No behavior change: customer records, fields, permissions, and API responses are unchanged.

For details, see Modern Customer Management in the BigCommerce Help Center.

Storefront GraphQL adds semanticSearchEnabled to site.settings.search

The Storefront GraphQL API now includes a read-only semanticSearchEnabled boolean on site.settings.search, so headless storefronts can tell whether conversational (semantic) search is turned on for a store.

• When it is true: Conversational Search is turned on for the store.
• Store level only: The value reflects store configuration. It does not describe whether an individual request is served semantic results.
• No action required: The field is additive. Existing fields are unchanged, and search results do not change.

GraphQL Storefront API: manage Company users

The GraphQL Storefront API now covers B2B Edition Company user management natively, under the authenticated customer’s activeCompany context. Company Admins can list, create, update, and delete the users of the Company they are acting for, and look up the roles they can assign. Every Company user can read the user extra fields the store has configured and update their own extra field values.

• Queries: customer.activeCompany.users, customer.activeCompany.companyRoles, customer.activeCompany.currentUser, and site.settings.b2b.extraFields.user.
• Mutations: company.createUser, company.updateUser, company.deleteUser, and company.updateCurrentUser.
• Permissions: access follows the caller’s Company role. Admins manage users; every Company user can read roles and maintain their own extra fields.

The new Company user management guide covers each operation with example requests and responses and the role permission matrix. For schema details, browse the Storefront GraphQL API reference.

Migrated orders documentation now covers inventory behavior

The Orders API and order migration docs now explain that orders created with external_source set to M-MIG don’t deduct inventory, so you can import historical orders from another platform without changing your current stock levels.

• Create Order: the endpoint note and the external_source field description now cover inventory behavior for M-MIG orders.
• Orders overview and order migration guides: the M-MIG guidance now mentions inventory, and the migration FAQ has a new entry about it.
• Later edits: editing the products on a migrated order later does change stock levels.

For details, see Order Migration.

B2B Edition shopping list queries return totals and full item details

The shoppingLists and customerShoppingLists queries in the B2B Edition GraphQL API can now return the same totals and item details as shoppingList and customerShoppingList, so you can load a page of shopping lists in a single request.

• List totals. grandTotal, totalDiscount, and totalTax are now available on each list returned by shoppingLists and customerShoppingLists.
• List item details. Items returned by these queries now include baseSku, variantSku, basePrice, discount, tax, enteredInclusive, productUrl, primaryImage, productName, and sortOrder.
• Product SKU on single lists. Items returned by shoppingList and customerShoppingList now include productSku.
• Pricing across several lists. When one query prices several shopping lists, each item is now priced against its own list. Previously, item prices could come back as 0 for aliased queries that requested more than one list.

Prices and product details are only calculated for the fields you request, so existing queries run as before and do not get slower. Requesting totals or item prices for many lists in one query takes longer, because each list is priced separately.

Catalog Enrichment is live for eligible stores

Catalog Enrichment is out of beta and live now for eligible stores. It is a paid AI tool in the control panel that reads your existing product data and generates content optimized for search engines and answer engines, such as ChatGPT and Google’s AI results.

• What it generates — content for seven product fields: product name, description, SEO meta description, and SEO page title, plus AI snippet, intent Q&A, and conversational Q&A custom fields for answer engines
• Why it matters — richer, product-specific content gives search engines and answer engines more to read and cite, which can improve how often your products appear in search results and AI responses, without writing content for every product by hand
• You stay in control — guide the voice with brand guidelines and additional context, check quality scores, and review results before you apply them

Your store is eligible if it meets all of the following:

• Latest Add/Edit Product experience — the store uses the latest Add/Edit Product experience (v3 catalog)
• Latest product list — the store uses the latest product list; to migrate to it, contact BigCommerce support
• US English catalog — the catalog content is in US English

For details, see What is Catalog Enrichment?.