Choose the workflow before editing
Imagine a US store selling an illustrative 12 fl oz mug. Updating its English description is a product data task. Adding a Russian description as another storefront language is a translation task. Placing Russian text in an extra product CSV column does not create a published translation.
| File | Main purpose | Preserve |
|---|---|---|
| Product CSV | Product descriptions and supported product fields | Handles, variant relationships and export headers |
| Translation CSV | Translated fields for existing resources | Resource identity, field and locale information |
Use exports from your own store as the working structures. Do not relabel a supplier spreadsheet as a Shopify translation file. Check Shopify's current translation instructions because the admin workflow and supported columns can change.
Prepare the product update
- Export the relevant products and save the original.
- Review source facts such as material, capacity and care instructions.
- Confirm that Content's Shopify format and English US workflow are available in your account before processing.
- Review the returned text, preserve identifiers and import a small test batch yourself.
- Check the default language product page after import.
Add another language separately
Export the translation file for the required language from Shopify. Preserve its resource identifiers and field structure, add the translations and use the translation import workflow. Review the translated storefront URL and the default language page separately.
For Content's documented Ukrainian/Russian route, Ukrainian uses the product CSV and Russian requires the separate translation file step. Do not infer that a standard CSV carries both languages together or that any target language is supported by Content.
Verify the result before continuing
Check the mug's default description, translated description, selected variant, price and images. Look for untranslated fallback text and accidental overwrites. Keep a copy of each file with its purpose so another editor can tell which import produced a change.
Content does not publish through a Shopify app or API. You review and import the result. If the account does not expose the requested language workflow, confirm availability before buying or processing a larger batch.
Next step
Check Content capabilities and current pricing and the Shopify file workflows. Start with a representative batch and review the result before expanding. Shopify and English US processing are gated capabilities; confirm availability in your account before processing. A supported format does not establish enablement for every store.
Sources and verification
Checked November 4, 2026. Platform documentation describes platform rules, not StoreNex capabilities. StoreNex claims were checked against the November 3 compatibility matrix. Product examples are illustrative.
- A Shopify product CSV updates product data, while a translation CSV supplies language specific content for existing resources.
FAQ
Check headers, identifiers, quoting and Shopify’s import report. A product CSV and translation CSV use different structures. Keep their workflows separate and repeat a small test after correcting the file.
Export the required products from Shopify’s Products area and keep an untouched copy. Translation exports are a separate workflow in language settings. Use the current instructions for the type of content you intend to update.
Product CSV files update product fields, while translation CSV files identify resources, fields and locales. Do not add language columns to an ordinary product export and assume they create translations. Export and import each file through its matching Shopify workflow.
Titles, descriptions and SEO fields in bulk, as a file to import into Shopify, Horoshop, Prom or OpenCart.