Should I write an English brief when I want a French product description?

Brief language and publish language are separate choices

Input language, output language and immutable terms serve different purposes. Translating the briefing notes first can introduce a second opportunity for numeric or naming errors. Conversely, leaving every marketing phrase untranslated produces mixed-language copy. Define which material should change and which should remain exact.

Choose the language using the actual tool’s documented behavior. Shopify currently says generated descriptions match the prompt language and recommends writing the prompt in the desired description language. For French copy in that workflow, use a French prompt and retain protected brand/model terms and verified facts. In another tool with a separate output-language control, confirm that setting rather than assuming English instructions work identically everywhere. Language changes do not authorize invented prices, services, measurements or product facts.

Lock names and facts before translating the draft

Prepare three blocks: verified facts, the requested language and audience, and exact terms not to translate. Give approved spellings where available. Review the draft line by line for names, numbers and units, then have an appropriate target-language reviewer check meaning and naturalness before applying it to imagery or the store.

Separate instructions about tone from the facts to preserve. Provide the reviewer a source sentence and its proposed output side by side. Ask whether quantities, limitations and use conditions survived, not merely whether the translation sounds natural.

1. Preserve meaning and quantities: authoritative product notes.
2. State both explicitly: language and audience.
3. Check exact spelling: brand and model codes.
4. Compare against original facts: target-language draft.

An English fact record for a French listing

Fictional exercise: a verified English fact record describes a pouch, and the operator prepares a French prompt for the documented Shopify workflow. “Luma-P2” remains the exact product code, while the benefit sentence is translated. The reviewer compares the French draft with the fact block rather than guessing from the photograph. No language setting certifies the result as error-free.

For the same fictional French listing, the verified English fact block says the pouch has a removable component and includes a limited set. The French draft must preserve both meanings, with Luma-P2 unchanged. Reject a fluent sentence that invents sterilization or expands the included set. This is an editorial comparison example, not evidence that any tool generated an approved French result.

Check meaning rather than surface fluency

Stop if an untranslated term has no approved interpretation or if the target-language reviewer cannot confirm a claim. Keep the ambiguity visible instead of silently resolving it with AI.

Record the approved terms for the next revision. If the product changes, revisit those facts instead of treating the prior translation as a permanent specification. CartVisual can help draft requested-language copy from confirmed inputs. It does not establish regional policy, translate packaging facts automatically or replace a qualified language review.

Fact source to human review: decision worksheet

Use this matrix as a manual review record and add your own real evidence. Its conditions are not completed test results.

Download this question’s review worksheet (CSV)