Skip to navigation

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.


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.


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.