How Much Does It Cost to Translate an Ecommerce Store?
What Are You Actually Paying For?
You are paying for characters of text sent to a translation service, once per language. That is the whole unit of cost, and understanding it makes the arithmetic straightforward.
Start with your catalogue. A product with a title and a short description is maybe four hundred characters. Two hundred products is around eighty thousand characters. Add your pages, policies and blog posts and a small store lands somewhere between one and three hundred thousand characters in total.
Multiply that by each language you offer. Two languages is twice the text, not twice the products.
At typical machine translation prices, that total is small: a few dollars per language on an inexpensive model, more on a premium one. The reason it feels uncertain to merchants is that the price is quoted per character or per million tokens, which is not a unit anyone thinks in. Converting it to "my catalogue, once" makes it concrete. For most OpoShop stores it is a smaller number than the monthly cost of most apps.
Why Does Caching Change the Bill So Much?
Caching changes the bill because it decides whether you pay per sentence or per page view, and the difference between those two is the difference between a fixed cost and an open-ended one.
Imagine a product description of six hundred characters. If it is translated once and stored, you pay for six hundred characters, ever. If it is translated when a shopper loads the page, you pay for six hundred characters every time anyone views that product.
A thousand views of one product is the difference between six hundred characters and six hundred thousand. Your best sales day becomes your most expensive day, which is exactly backwards.
This is why the single most useful question to ask about any translation tool is whether translations are stored. A cached setup also loads faster, because the page is serving text from a database instead of waiting on an external service. Speed and cost point the same direction here, which is unusual and worth taking advantage of on an OpoShop storefront.
What Are the Real Cost Drivers?
Four things move your bill, and only one of them is the price list.
- How much text you have: Long, detailed descriptions cost more than short ones. This is the biggest single factor.
- How many languages: Cost is roughly linear. Four languages is four times one language.
- How often your copy changes: Only changed text needs re-translating, so a stable catalogue costs almost nothing after the first run.
- Which model or service you choose: The gap between a cheap model and a premium one is large, and on descriptive product copy the quality gap is much smaller than the price gap.
That third point is the one merchants underestimate in a good way. If translations are keyed to the text itself, editing one sentence in one product re-translates that one sentence. Everything else is already done and stays done.
It means the cost curve is front-loaded. Your first run is the expensive one, and every month after that costs a fraction of it unless you are adding products constantly. Merchants who expect a recurring bill the size of the first month are usually pleasantly surprised.
How Do You Estimate Your Own Cost?
You estimate it by measuring your own text rather than trusting a general figure, and it takes about ten minutes.
1. Measure, do not guess
Merchants routinely overestimate how much text their store contains. Two hundred products sounds like a lot of words and usually is not, because most product descriptions are a few sentences.
Ten minutes with a character counter gives you a real number, and the real number is nearly always lower than the anxious one. Do it before you shop for an app on OpoShop, so you can judge pricing against your own catalogue.
2. Remember policy pages
The text people forget is not product copy, it is the long pages: shipping, returns, terms, about, FAQ. These are often the longest documents on a store and they matter enormously to international buyers.
Include them in your estimate. They are also a one-time cost, since a returns policy rarely changes, which makes them some of the best value text on the whole store.
3. Set the limit before you turn anything on
An estimate tells you what you expect. A limit tells you what is possible. Set a monthly character cap that you would be comfortable seeing on a bill, and let the tool stop there.
The best behaviour is that reaching the cap pauses new translation and tells you, rather than quietly continuing. Anything already translated should keep working, so your OpoShop storefront never regresses because a limit was reached.
How Do the Pricing Models Compare?
There are three ways translation gets billed, and they behave very differently as a store grows.
| Model | How it scales | Typical shape | Risk |
|---|---|---|---|
| Per character, cached | With your catalogue size | A larger first month, then very small | Low. Your bill is predictable and capped |
| Per character, uncached | With your traffic | Grows every time you get more visitors | High. A viral day is an expensive day |
| Per word, human | With your catalogue, per batch | A real invoice per language, repeated as you add products | Low surprise, high absolute cost |
The first row is what you want for a small store. The second is the one to check for, because it is not always disclosed and the failure only shows up once you are successful.
The third is not a bad option, it is simply a different order of magnitude, and it makes sense when your words are the product rather than a description of it.
There is a fourth model worth mentioning: apps that charge a flat monthly subscription and include translation. That can be fine, but check what happens when you exceed the included volume, because that is where the surprise usually lives. It is a fair question to ask of anything you install on OpoShop.
What About Bring-Your-Own-Key Pricing?
Bring-your-own-key means you supply your own translation account and pay that provider directly, rather than paying an app a marked-up rate. For most merchants it is the cheapest and most transparent arrangement.
The advantages are concrete. You see the real cost on your own provider bill rather than a number an app chose. You are not paying a margin on top. And if you stop using the app, your provider account is still yours.
The trade-off is one extra setup step: creating an account with a translation provider and pasting a key. That is a five-minute job, and it is the price of removing a middleman from your bill.
There are two things worth checking about how an app handles that key. It should be encrypted when stored, and there should be no way to read it back out of the app afterwards, including by the people who built it. And it should let you set a hard spending limit, because a key that can be used without a ceiling is a key that can surprise you. Any app you add to OpoShop that asks for a provider key should be able to answer both plainly.
Best answer: Translating a small store with machine translation typically costs a few dollars per language for the whole catalogue, because the unit is characters and a small catalogue is a few hundred thousand of them. Human translation costs orders of magnitude more. What really decides your bill is caching: a tool that stores translations charges you once per sentence, while one that translates on demand charges you again for every visitor. Estimate your own text, then set a hard monthly limit so the estimate becomes a guarantee.
What Are the Hidden Costs?
The hidden costs are rarely the translation itself. They are the things around it that no price list mentions.
- Your own review time: Reading your key pages in each language, once. An afternoon, not a project, but it is real.
- Maintenance as your catalogue grows: New products need translating. If your tool does it on a schedule, this is close to free. If it needs prompting, it is a recurring task.
- Re-translation you did not need: A tool that re-translates unchanged text is charging you for nothing. Keyed-to-the-text caching prevents this entirely.
- The cost of getting it wrong: A mistranslated size chart or a mangled returns policy generates support messages and returns, which cost more than the translation did.
That last one is the argument for protecting the things that are not language. Prices, sizes, SKUs and order numbers should be excluded from translation structurally, because an error there is expensive in a way a slightly awkward sentence is not.
None of these are large for a small store, but they are worth knowing so that the number you plan around is the real one rather than the sticker price. On a typical OpoShop store the honest total is still small.
Is It Worth It at That Price?
At machine translation prices, the question is usually not whether it is worth it but whether you have the international traffic for it to matter.
The cost of translating a small catalogue into one language is comparable to a couple of coffees. The cost of a shopper leaving because they could not read your product page is one order. If translating brings back a single sale, most stores are ahead.
That maths is why the more useful question is about traffic rather than price. If a meaningful share of your visitors already use another language, the return is likely. If almost nobody international visits you, you are paying a small amount for something nobody will see, and your money is better spent getting traffic first.
The good news is that the experiment is cheap enough to simply run. Translate one language, watch that segment for a month, and you will have an answer specific to your own store rather than an average from someone else's. That is a better basis for the decision than any general figure, including this one.
FAQs
Is there a free way to translate my store?
Browsers can offer to translate a page for some visitors, which costs you nothing but gives you no control over wording, no protection for your brand names, and no guarantee a shopper ever sees the prompt. It is better than nothing and considerably worse than a translation you control.
Do I pay again every month?
Only for text that is new or changed. If translations are stored against the text itself, an unchanged product is never translated twice, so a stable catalogue costs very little after the first run. Stores that add products constantly will see a small ongoing cost.
What happens if I hit my monthly limit?
Everything already translated keeps serving normally and new translation pauses until the next month or until you raise the limit. That is the behaviour to expect. A tool that continues spending past a limit you set has ignored the setting.
Is a premium model worth the extra cost?
For descriptive product copy, usually not. Materials, dimensions and care instructions translate well on inexpensive models. If your store's value lives in carefully written brand copy, spend the difference on your five most important pages rather than on your whole catalogue.
How much does adding another language cost?
Roughly the same as the first one, since it is the same text translated again. The exception is that your second language is faster to set up because you have already found and fixed the gaps in your content.
Can I try it without committing?
Yes, and you should. Translate one language, set a low monthly limit, and watch that traffic segment for a month. If it does nothing for your store, you have spent very little and learned something specific to your own business.
Work out your own character count before you decide, because the real number is almost always smaller than the one you are imagining.
