Arabic and French product descriptions: keep the facts consistent

Writing in two languages means more than pasting machine translation below an original. Each shopper should understand the same offer: what it is, whether it fits, what arrives and its limitations. Style and explanation order can differ, but dimensions, price, contents and service promises should not. Build one factual reference, write natural versions and inspect them on a phone as customers do rather than only inside a translation spreadsheet.

Establish facts before persuasive copy

Record the internal name, reference, materials, dimensions, relevant weight, contents, compatibility, care and limits. Identify the source: your sample measurement, supplier documentation or an unverified statement. An attractive phrase must not turn an assumption into a technical property. Separate appearance from guaranteed performance. If water resistance is unknown, do not add it simply because it improves a translation’s sales tone.

Include who the product does not suit, such as a holder incompatible with a textured surface or a bag too small for a particular computer. Clear limits save customer and staff time. When supplier or dimensions change, update the fact sheet first so that an old French description does not remain beside a corrected Arabic one.

Build a small terminology list

Agree recurring terms for materials, sizes, contents, warranty and delivery. Familiar wording can still be precise. Do not translate a model or internal reference into another identifier. A bundle should not mean two items in one language and one item in another. Keep measurements and codes stable in the source record.

Fact	Arabic	French
Dimensions	30 × 20 × 10 سم	30 × 20 × 10 cm
Contents	حقيبة واحدة	Un sac
Exclusion	الأدوات الظاهرة غير مرفقة	Accessoires présentés non inclus
Reference	BAG-302010	BAG-302010

This is a fictional working table, not a compulsory translation standard. State length, width and height order when ambiguity matters. A row of numbers can be linguistically correct yet leave customers unable to decide whether an item fits.

Answer first, then support comparison

Open with product identity and primary use, followed by a benefit tied to a fact. Replace best bag for everything with actual dimensions and a pocket that exists. Organise remaining information into use, specifications, contents and limits. Avoid repeating keywords mechanically or translating sentence structures so literally that the result sounds unnatural.

You can organise product information and images with Matjri using available fields. Changing the administration language does not establish automatic translation of all product content. If both texts share a page, separate them clearly. If separate language pages exist, inspect each with the same options and prices.

Keep one price and one commitment

A fictional bag priced at 59 TND with 8 TND shipping totals 67 TND for one unit in both languages. Omitting delivery from one explanation should not create a conflicting offer. If an extra strap is excluded, say so in both. An estimated courier time must not become guaranteed delivery tomorrow in the translated version.

For planning only, allow twenty minutes collecting facts, twenty writing Arabic, twenty writing French and fifteen reviewing together, totalling seventy-five minutes. This is not an ideal time for every product. Technical goods and safety instructions may need longer and qualified review rather than shortening the process to match an arbitrary schedule.

Treat machine translation as an assistant

Give the tool the fact sheet and instruct it not to add specifications. Then compare every number, unit, negative and exception. Not included, incompatible and may vary can disappear in smoother rewriting. Do not supply customer data or accept invented certificates and product experiences.

Ask someone who understands the language to answer five questions from the text: what is sold, its dimensions, its contents, the main limitation and delivery. Different answers between languages require correction. Compare translated facts directly with the source rather than expecting a second automated translation to expose every problem.

Separate translation from search configuration

For genuinely separate pages, Google’s localised-version guidance explains language signals. Two paragraphs do not automatically create two pages or guarantee ranking. For feeds, review the Merchant Center product specification. Consistency between page and feed language is a separate check, not merely a translated button.

Should Arabic be formal or Tunisian conversational language?

Choose wording your customers understand while retaining precise terminology and units. A conversational opening can accompany clear specifications. Friendly phrasing should not hide conditions or turn technical facts into guesses.

Should the price be repeated everywhere?

Usually not. Multiple manually copied figures increase the chance of an outdated value. Use actual price fields and review any offer example when conditions change.

How can future differences be prevented?

Include facts, both texts, images and instructions in each product update. Record the reviewer and date. Start today with one item and a comparison table, then expand the glossary after correcting what that exercise reveals.