Step 1
Gather the approved source copy per field, the target language and market, the glossary with locked terms such as model codes, brand names and SKU identifiers, and the local formatting conventions for units, dates and numerals.
A new market is opening and the catalog must appear in its language, but no glossary or unit convention is agreed. In this case, the immediate task is to translate product information for a specified market. The workflow should produce localized copy shown beside the source, with a terminology list and every count or unit traceable to the merchant's records.
First replace every [bracketed] placeholder with real store scope and constraints, then add any actual records or data you have, and paste it into your preferred AI assistant or Spark agent. Spark will follow this page's workflow to produce structured output and verification steps.
Act as a Shopify operations specialist.
Help me translate product information for a specified market.
My store context is [describe the business, products and target audience].
My scope is [specify the affected products, pages, customers or reporting period]. Use these inputs: [approved source copy per field, the target language and market, the glossary of locked terms, and local formatting conventions for units, dates and numerals].
Translate the requested fields while keeping locked terms, specifications and countable facts character-identical to the source, applying local unit and numeral formatting only where the convention does not change the recorded value.
Return localized copy beside the source with a terminology review list for the specified task.
Show the relevant evidence or before-and-after examples and explain how I can verify the result.
If essential data is missing, ask for it and mark unsupported conclusions as unknown.
Do not invent metrics, product claims or customer facts.
For any publication, message, account or store change, use only connected tools within my explicitly authorized scope and report success only after verification; otherwise provide the draft or proposed steps.Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
Gather the approved source copy per field, the target language and market, the glossary with locked terms such as model codes, brand names and SKU identifiers, and the local formatting conventions for units, dates and numerals.
Translate the requested fields while keeping locked terms, specifications and countable facts character-identical to the source, applying local unit and numeral formatting only where the convention does not change the recorded value.
Deliver localized copy shown beside the source with a terminology review list of every ambiguous term, then verify field by field that locked terms are unchanged and that each count, unit and measurement traces to the merchant's record.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
They are copied character by character rather than transliterated or adapted, and the field-level check compares each one against the glossary after translation; a locked term that differs even in case is treated as an error.
Only through a convention that preserves the recorded value, and the original unit stays visible in the terminology list; converting a measurement without merchant-approved conversion rules would quietly change the product fact.
Every source term with more than one plausible reading, the chosen literal reading, and the reason; the list is the merchant's chance to catch an interpretation before the localized page goes live.
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
Ciwi Spark builds Shopify-native AI tools and agents around the workflows merchants actually run: research, ads, translation, and customer support. Stop rewriting the same prompts by hand.