spec sheet · cms & commerce

BigCommerce and Transglot, turn catalog copy into locale files.

Choose BigCommerce in your project’s CMS settings, add your credentials, and select the content and languages to sync. Translate and review in one project, then publish to your mapped target languages.

Import into Transglot

Direction: Import into Transglot
Plan: Starter and up
Scope: catalog products: name and description
Authentication: a store API account token and your store hash
Get started: Connect from your project’s CMS settings.

Create your project Setup

cms & commerce

the workflow

Connect your content. Review every language.

Connect once, choose your content and languages, then translate and review in the same project. The steps below show how it works in your tool.

Connect BigCommerce
Choose BigCommerce in the project’s CMS settings. Add a store API account token and your store hash.
connect
Choose the content and locale mapping
Select the types and fields you want to localize. The connector reads catalog products: name and description. Map the source and target locales to your project.
map
Sync and review the translations
Start Sync from CMS to bring the selected source into your project. Translate and review the resulting keys alongside the rest of your project content.
review
Deliver through your project
Pull the translated locale files through the API or CLI, or use the project’s CDN bundle. BigCommerce remains an import-only source.
deliver

Read translated locale files through the Transglot API, CLI or CDN. Publishing changes back to BigCommerce is not part of this connector.

what moves

What you can translate and deliver.

Catalog product name and description come in from the stable v3 API. It stays one way because BigCommerce's product translation write path is still in beta, is limited to Catalyst storefronts and writes only non default channel locales, which is not something to point at a live store yet.

What you can translate and deliver.
Surface	What to expect
Source and scope	catalog products: name and description
Translated output	Read translated locale files through the Transglot API, CLI or CDN. Publishing changes back to BigCommerce is not part of this connector.
Keep in mind	Import only. Your original BigCommerce content is read, and this connector does not write translations back.

get connected

A few steps to your first connection.

Follow your tool’s setup below: add the connection, choose what to sync, and try it with a small set of content. Your team can keep working in the tools they already use.

What you need

a store API account token and your store hash.

A Transglot project with its source and target locales configured.
Save credentials in the connection settings so your team can work without copying secrets between files.
Hosted API access requires a paid Transglot plan. AI translation uses your workspace’s word allowance.

Create your project

Create a Transglot project with the source and target locales you need.
Open the project’s CMS settings and choose BigCommerce.
Provide a store API account token and your store hash.
Save the connection, select the supported content, map locales, then run Sync from CMS.

same project, more possibilities