Translated B2B emails now depend on the new Buyer Portal
On November 16, BigCommerce posted a short changelog entry that matters to any B2B Edition store still on the legacy storefront experience. Transactional email translations in B2B Edition are now available only to stores that use the new Buyer Portal.
Stores that have not migrated keep the single-language template editor in the B2B Edition control panel, and every transactional email they send goes out from that one template. Stores already on the new Buyer Portal keep their translations. The entry gives no other dates or exceptions.
In our view this is a good prompt for distributors selling into more than one language market to schedule the move. Buyers in those markets will otherwise receive their B2B Edition emails in the template’s single language.
Moving off the legacy storefront experience
BigCommerce’s Buyer Portal migration guide describes the route. You ask Support to add the self-service migration tool to your live store and your sandbox store. Only users with the Owner or Admin role can use it. You also ask Support to sync historical B2C orders on migration day, so customers without Company accounts can still see their earlier orders.
The theme is where the work usually sits. The guide says your theme must not contain any code from the legacy storefront experience. Some Stencil themes, including Cornerstone, Vault and 22 Savile Row, support the Buyer Portal’s entry points and buttons natively. Customized and third-party themes may need development work. Storefront Wish Lists should be turned off, because Shopping Lists replace them.
Sandbox testing is optional in the guide, though strongly advised. It lists sign in, register, forgot password, the account link, the Add to Quote and Add to Shopping List buttons, quotes, shopping lists and invoice payment as things to check. It recommends testing checkout as a buyer with a Company account and using the Optimized One-Page B2B Checkout. The live switch is a button in the migration banner, with a matching button to disable the Buyer Portal if you need to roll back.
Quotes: server-side pricing, line notes and a uuid check
Three quote changes landed in the B2B GraphQL API over the last month. The November 12 roll-up makes price fields optional on quoteCreate. If a request sends none, BigCommerce prices each product from catalog pricing for the shopper’s customer group, channel and currency, including bulk pricing and tax, and returns the saved prices. Requests that send prices behave as before. Each product line can also carry a new optional notes string.
This helps custom quote forms and ERP-driven quote flows, which often fetch and recalculate prices before creating a quote. Leaving the price fields out hands that job to BigCommerce. A priceless request fails if the product list is empty or a product or variant is missing from the catalog, so validate SKUs first.
On October 30, quoteUpdate gained an optional uuid argument, according to the October 30 entry. When sent, the update only applies if store, quote ID and uuid all match. Otherwise it returns “Quote not exist” and changes nothing. userEmail became optional, and calls that omit the uuid work as before.
Shopping lists and company addresses change in the GraphQL API
Shopping list operations in the B2B Edition GraphQL API are rolling out structured errors over the coming weeks. Each error carries an extensions object with a code: 400 for invalid input, 403 for no permission or no company, 404 for a missing list, item or company, 429 for throttling and 500 for server errors. A quantity outside 0 to 1,000,000 comes back on the mutation with HTTP 200 and a path. Code that parses error message strings should switch to the code.
customerShoppingListsCreate now saves a list on the default channel when channelId is omitted, null or 0. On multi-storefront stores, an unknown or disabled channel ID creates a list with no channel and returns no error, which is easy to miss in testing.
On the Storefront GraphQL side, the November 9 entry adds a searchTerm filter to customer.activeCompany.addresses and deprecates searchQuery. It still works, no removal date is set, and BigCommerce says a separate entry will announce the removal. Company addresses also gained a nullable companyName field, though addAddress and updateAddress do not accept it yet.
What to check this month
If you are still on the legacy B2B storefront and send emails in more than one language, book the Buyer Portal migration and start with a theme audit in the sandbox. If you have already migrated, the work is on the developer side. Replace searchQuery with searchTerm, update shopping list error handling to read extensions.code and pass the quote uuid on updates. Before you remove your own price calculation, compare server-side quote prices with what your ERP expects for a few customer groups.





