How to Bulk Translate Shopify Metafields

Metafields are where the interesting content on a modern Shopify store lives. Care instructions, materials, dimensions, lead times, size guides, ingredient lists, the three bullet points your theme renders under the add-to-cart button — all metafields, all rendered on the product page, and all routinely left in English on every localized storefront.

The result is a page that looks translated until you scroll. The title and description are in German, and then a specification block reads "Machine wash cold, tumble dry low."

Why metafields get missed

Three reasons, and they compound.

They are invisible in the product list. Nothing in the admin index tells you a product has eight metafields, so nobody counts them when scoping a translation project.

They are buried in the translation editor, below the fields everyone expects to see, often requiring scrolling past a long description to reach.

And they are defined by someone else — a developer or an agency set up the definitions when the theme was built, and the person doing the translating may not know they exist at all.

So the work is skipped, and the gap only surfaces when a customer in another market asks a question your product page already answers in English.

The spreadsheet approach

SheetSync exports one tab per enabled locale, named Product Data (<locale>), and every metafield you select becomes a column on each of those tabs. Which means:

You can see the whole translation surface at once. Row count times metafield count times locale count is your actual workload, visible as a number rather than discovered halfway through.

Gaps are a filter, not an audit. Filter any metafield column to blanks on the French tab and you have precisely what is missing. This is the single fastest way to answer "how translated are we, really?"

Repeated values translate once. Care instructions are rarely unique — a hundred cotton products share one string. Build a lookup of distinct source values, translate each one once, and map it back with VLOOKUP. A hundred rows of translation becomes four.

Translation vendors can work in the file. Share the tab, let them fill the column, sync when it comes back. No export-import round trip, no file format conversation, no copy-paste into an admin UI.

Structured values stay structured. A dimension metafield or a list stays in its own column with its own format, so a translator changing wording cannot accidentally reshape your data.

Step by step

1. Open Product Info Sync and create a product spreadsheet.
2. In the field selector, include the metafields you want — and only those. Metafields multiply across locales, so an unselected metafield is real cells saved.
3. Export. Each locale tab carries the same metafield columns.
4. Translate on the non-primary tabs, using a lookup table for repeated values.
5. Paste formula results as values.
6. Sync back and check the log.
7. Open a localized product page and confirm the rendered blocks, not just the admin fields.

Things to watch

• Not every metafield should be translated. A SKU reference, a supplier code, a numeric dimension or a boolean flag is data, not copy. Translating it either does nothing useful or breaks the template reading it.
• Keep the type intact. If a metafield holds a number or a list, the translated value has to remain a valid number or list. Rewriting 2.5 as 2,5 cm because the target locale writes decimals that way will not render the way you expect.
• Rich text keeps its markup. Translate the words, leave the tags. A translator who reflows the HTML can break a layout that renders fine in English.
• Mind the cell budget. Google caps a spreadsheet at 10 million cells across the whole grid. Twenty locales times ten thousand variants times a generous column count exceeds it — select the metafields you actually need rather than exporting all of them.
• Translations go stale when the source changes. Shopify ties a translation to the source text it was made from; edit the English and that field's translations are marked outdated. Translate after the source copy settles, and re-export periodically to pick up what has drifted.

Where to start if the backlog is large

Rank your metafields by whether a customer reads them on the page. Care instructions, materials, size guides and anything in the buy box are worth translating properly and probably worth a human. Internal references, codes and flags are worth nothing translated. A short triage at the start usually cuts the real workload by more than half, and the sheet makes that triage a two-minute job rather than a meeting.