How to Choose Which Products to Translate First: A Revenue-Based Prioritization Framework for Shopify Merchants
Most merchants who start translating their Shopify store make the same mistake: they translate everything alphabetically, or they start with whichever product page they happened to have open. That approach wastes your translation budget on low-traffic SKUs while your top earners sit in English for customers who shop in French, German, or Japanese.
Knowing which products to translate on Shopify first — based on actual revenue data rather than gut feel — is one of the highest-leverage decisions you can make when expanding internationally. This guide gives you a concrete framework to make that call fast.
Why Translation Order Matters More Than You Think
Translation has a word count. StoreLingo's free plan is a one-time allowance; paid plans are a monthly budget. Either way it is finite. Spending it on a product that generates 0.3% of your revenue before you've touched your bestsellers is a real cost — not just an opportunity cost.
There's also an indexing argument. Google indexes translated content separately per hreflang. The sooner your high-converting product pages are live in a target language, the sooner they can rank organically in that market. Waiting three months to get to your bestsellers means three months of lost compounding SEO value.
Step 1: Pull Your Revenue-by-Product Report
Before you open any translation tool, open Shopify Analytics.
Go to Analytics → Reports → Sales by product. Set the date range to the last 90 days and sort by Total sales (descending). Export the CSV.
You now have a ranked list of every product by revenue. This is your starting point — not your product catalog, not your collections page.
What to look for
- The top 20% of products by revenue typically account for 60–80% of total sales (the classic Pareto distribution holds up well in e-commerce).
- Flag any product with a high order count but low revenue — it might be a low-margin filler that's not worth prioritizing.
- Note products with high revenue but low order count: these are high-AOV items. International buyers who are hesitant about a large purchase are especially sensitive to language barriers. Translate these early.
Step 2: Layer in International Traffic Data
Revenue data alone tells you what's selling to your current audience — mostly English speakers. You also need to know where your potential international audience is coming from.
In Google Analytics 4, go to Reports → User → User attributes → Audiences, then filter by country and language. Look for:
- Countries with meaningful session volume but conversion rates well below your store average
- Languages other than English appearing in browser language data
A product page with 400 monthly visits from Germany and a 0.4% conversion rate (versus your 2.5% store average) is a signal: the demand is there, but the language gap is killing conversions. That page should be near the top of your translation queue regardless of its current revenue rank.
Once you have translated pages live, you can track exactly how traffic, conversions, and revenue break down by language to validate your prioritization decisions over time.
Step 3: Score Each Product on Four Dimensions
Create a simple scoring table. Rate each product 1–3 on these four dimensions, then add up the score. Products with the highest totals get translated first.
| Dimension | 1 (Low) | 2 (Medium) | 3 (High) |
|---|---|---|---|
| Revenue rank | Bottom third | Middle third | Top third |
| International traffic | Minimal | Some | Strong |
| AOV | Under $30 | $30–$100 | Over $100 |
| Content complexity | Simple (few variants) | Moderate | Complex (many variants, rich descriptions) |
Content complexity scores inversely here: a simple product costs fewer words to translate and delivers faster ROI per word spent. A product scoring 11–12 total is your first batch. Products scoring 4–6 can wait.
Step 4: Group by Collection to Maximize Coherence
Once you have your priority list, group products by collection before translating. There are two reasons for this.
First, navigation coherence: if a German shopper lands on your "Running Shoes" collection page but half the products are in English, the experience is jarring and trust drops. Translating whole collections together — even if some products in that collection rank lower — creates a consistent in-language experience.
Second, word count efficiency: collection descriptions, product type labels, and shared attributes (like size or color names) repeat across products. Translating them in one pass is more efficient. This matters if you're working within a monthly word limit.
If you have bundles or subscription products sitting inside a priority collection, make sure those are covered too — the considerations for those content types are different enough to deserve their own approach.
Step 5: Don't Neglect the Supporting Content Around Your Priority Products
A translated product page doesn't exist in isolation. If a shopper reads your French product description but then hits an English size chart, English checkout fields, or English error messages, you've lost them at the finish line.
Before you call a priority product "done," check that the surrounding experience is also translated:
- Size and measurement content — especially important for apparel and footwear. See how to handle size charts and unit conversions across markets.
- Product reviews — social proof is one of the highest-converting elements on a product page. Translating reviews for your top products can meaningfully lift conversion in new markets.
- Navigation and filters — if shoppers can't find your priority products through translated menus and collection filters, the product translation itself won't help much. Translated navigation and faceted search closes that gap.
- Checkout — this is where intent becomes revenue. Untranslated checkout fields and validation messages create friction right at the point of purchase. Translating checkout fields and error messages is a high-ROI step once your top products are live.
Step 6: Automate Re-Translation for Your Priority Products
Your top-selling products are also the ones most likely to have copy updates — price changes, new variant descriptions, updated features. If you translate them once and forget them, you'll end up with stale translations that undermine trust.
Set up auto-translate rules specifically for your priority products so that any content change triggers a re-translation automatically. StoreLingo detects changed content and only re-translates what has actually changed, so you're not burning word budget on unedited fields. For large catalogs, bulk translation handles the initial pass efficiently, while auto-translate keeps everything current going forward.
Putting It Together: A Practical Starting Point
If you want a quick-start rule of thumb before you've built the full scoring table:
- Start with your top 10 products by revenue — no analysis needed, just sort and go.
- Add any product with strong international traffic but below-average conversion — these are your hidden opportunities.
- Complete the collections those products belong to — don't leave gaps.
- Translate the supporting experience — size charts, reviews, navigation, checkout.
- Enable auto-translate for all priority products so changes stay current.
Add StoreLingo on the Shopify App Store →
FAQ
How many products should I translate first if I'm on a limited word budget? Focus on your top 10–15 products by revenue and traffic rather than trying to cover your whole catalog. A fully translated experience for 15 key products will consistently outperform a half-translated experience across 100 products — prioritize depth over breadth until your budget scales.
Should I translate products differently for different target markets? The core translation should be accurate for each language, but market-specific adjustments — like units of measurement, sizing conventions, or promotional framing — do matter. Use a glossary to keep brand terms consistent, and review translated content for your highest-priority markets before publishing.
What if my international traffic is too low to analyze meaningfully? If you don't yet have enough data, use your revenue rank as the sole prioritization signal and start with the top 20% of products. Once translated pages are live, you'll generate language-specific traffic data within a few weeks that lets you refine your approach using the full framework above.
Choose from 47 languages
StoreLingo translates products, collections, pages and articles with AI — review and approve by default. On paid plans from Starter, auto-translate is off by default and publishes new or updated products automatically. Keep your brand terms consistent.
Add to Shopify →