Blog

Team reviewing localization vendor proposal with quality and security icons
Translationary's checklist: what to look for before you sign with a vendor
Share this blog
Localization
Transcription & Buyer Education

How to Choose a Localization Vendor: A 10-Point Checklist

Choosing a localization vendor wrong rarely shows up as an obvious mistake on day one. It shows up three months later, as inconsistent terminology across markets, a missed launch date, or a brand voice that reads flat in every language except the original. By then, switching vendors mid-project costs more — in time, money, and rework — than getting the choice right the first time would have.

This guide breaks choosing a localization vendor down into ten concrete questions to ask, grouped into three categories: whether a vendor can actually do the work well, whether their process and technology hold up at scale, and whether they’re a partner you can actually work with for years, not just for one project.

At a Glance: The 10-Point Checklist
1. Native-speaker linguists with subject-matter expertise
2. A real, multi-stage quality assurance process
3. Relevant industry certifications
4. Sample work or references in your specific industry
5. Translation memory and terminology management
6. Realistic turnaround time and scalability
7. Technology and workflow integration
8. Transparent, itemized pricing
9. Confidentiality and data security practices
10. Communication style and project management
Checklist and quality icons representing choosing a localization vendor

All ten points matter, but weigh them differently depending on your project. A one-off document translation leans heavily on points 1 through 4 — the vendor’s raw capability and quality control. An ongoing multilingual content program, publishing regularly across several markets, leans just as heavily on points 5 through 7 and point 10 — the systems and relationship that hold up over years, not just a single deliverable.

Capability and Quality

1

Native-Speaker Linguists With Subject-Matter Expertise

Fluency alone isn’t the bar. A native speaker translating a medical device manual needs medical terminology fluency too, not just general language fluency, and the same holds for legal, financial, or technical content. Ask a prospective vendor how they match linguists to subject matter — do they maintain specialist pools by industry, or assign whoever is available that week? Also ask whether the same translator stays assigned to your account over time. Consistency across a long relationship matters as much as raw skill on a single project, since a translator who knows your brand voice and product history catches nuances a first-time translator simply won’t.

2

A Real, Multi-Stage Quality Assurance Process

A single translator producing a single draft, with no second set of eyes, is not a quality process — it’s a first draft with extra steps and a higher price tag. Look for a defined workflow: translation by one linguist, independent editing by a second linguist, and a final proofreading pass before delivery. Ask what happens when a reviewer disagrees with the original translator’s choices, since that answer reveals whether quality control is a genuine editorial process or just a formality added for the sales pitch. Also ask how errors get tracked over time — a vendor who can show you a defect rate trending downward over the life of your account is managing quality actively, not just promising it upfront.

3

Relevant Industry Certifications

Certifications aren’t everything, but their absence is a signal worth noting, especially for regulated industries. ISO 17100 covers translation service quality specifically — linguist qualifications, revision requirements, and project management standards. ISO 9001 covers general quality management across the business. For medical, legal, pharmaceutical, or government work, ask directly which certifications apply to your specific content type, and ask to see documentation rather than taking a logo on a website at face value. A vendor confident in their process will have this answer ready immediately, without needing to check with someone else first.

4

Sample Work or References in Your Specific Industry

A vendor that translates beautifully for e-commerce brands may struggle with dense legal contracts, and the reverse holds just as true — different content types demand genuinely different skills, not just different vocabulary. Ask for a sample translation in your subject area, or better, ask to speak directly with a current client in your industry rather than reading a testimonial on a website. General experience translating “a lot of content” says far less than specific experience translating content like yours, so push past the general pitch and ask for the specific proof.

Gears and magnifying glass representing localization vendor process evaluation

Process and Technology When Choosing a Localization Vendor

5

Translation Memory and Terminology Management

A translation memory stores every sentence a vendor has ever translated for you, so repeated or similar content doesn’t get retranslated — and re-billed — from scratch every time it appears. A termbase keeps your product names, brand terms, and industry vocabulary consistent across every project and every translator who ever touches your account, even years later when the original translator has moved on. Ask whether you own this data outright if you ever switch vendors. You should, and a vendor who hesitates on that answer is quietly building in a reason for you to stay regardless of quality.

6

Realistic Turnaround Time and Scalability

A quote that promises twenty thousand words translated overnight with no quality trade-off should raise questions, not confidence. Ask how the vendor scales for large projects: do they bring on more qualified linguists, or push existing ones to work faster and longer? The honest answer affects quality directly, and a vendor who’s transparent about the trade-off is more trustworthy than one who promises everything with no caveats. Also ask how they handle a sudden urgent request that falls outside your normal volume, since that’s usually when a vendor relationship gets tested most — and when the gap between marketing promises and operational reality shows up clearly.

7

Technology and Workflow Integration

If your content lives in a CMS, a code repository, or a design tool, manually exporting and re-importing files for translation adds friction and introduces errors at every handoff point. A vendor with API access or existing plugins for platforms like WordPress can pull content directly and push translations back automatically, without anyone manually copying text between systems. This is a meaningful difference if you’re publishing regularly rather than translating a single one-off document, and it compounds over time — the friction saved on file handoffs adds up across dozens of projects a year. Our software localization checklist covers the engineering side of this same handoff in more depth, including how to prepare your codebase before a vendor ever touches it.

Business and Partnership Factors in Choosing a Localization Vendor

8

Transparent, Itemized Pricing

Per-word pricing is the industry standard, but the per-word rate alone doesn’t tell the whole story. Ask whether that rate includes editing and proofreading, or whether those steps get billed as separate line items you’ll only discover later. Ask specifically how translation memory discounts work — repeated or highly similar content should cost meaningfully less than new content, not close to the same price every time it reappears. A vendor who can break down their pricing clearly and specifically in a first conversation will be far easier to budget against later than one who speaks only in vague ranges.

9

Confidentiality and Data Security Practices

Contracts, financial reports, product roadmaps, and medical records all pass through a vendor’s systems before they pass through yours again, translated and ready to use. Ask about their NDA policy, where files get stored and for how long, who inside the vendor’s organization has access, and whether linguists work with your content locally on their own machines or only through a secured, access-controlled platform. This matters even more if you’re operating under regulations like GDPR or HIPAA, since your vendor effectively becomes part of your compliance chain the moment they touch regulated content — not a separate concern outside of it.

10

Communication Style and Project Management

You’ll likely work with this vendor for years, not weeks, so pay attention to how they communicate well before you sign anything. Notice how they handle questions during the sales process: do they answer directly, or deflect with vague reassurance that sounds good but says little? Ask specifically who your actual point of contact will be day to day, since “you’ll work with our team” often quietly means nobody in particular owns your account when something goes wrong. A dedicated project manager who knows your account history, your brand terminology, and your past problem spots is worth more in practice than it sounds like on a features list.

Red Flags Worth Walking Away From

A handful of warning signs tend to matter more than any single item on the checklist above, because they usually point to a deeper problem rather than a single weak spot:

  • Pricing that’s dramatically below every other quote you’ve received. Someone absorbs that gap somewhere in the process — usually quality, or an underpaid linguist working faster than careful translation allows.
  • No clear answer about who actually does the work. Some vendors quietly subcontract to lower-cost providers without disclosing it, which makes quality inconsistent from project to project even when the invoice looks the same.
  • Reluctance to share a sample translation or a reference. A vendor genuinely confident in their quality will want to show it off, not deflect the request.
  • No mention of translation memory or terminology management at all. This usually signals a vendor still operating file-by-file rather than building any real system around your account over time.
  • Vague answers about data handling. If they can’t explain clearly where your files go and who touches them, don’t send anything sensitive until they can answer specifically.

No vendor scores perfectly on all ten points, and that’s fine — the goal of choosing a localization vendor isn’t finding a perfect score, it’s finding an honest one. A vendor that answers these questions directly, even when the honest answer is imperfect, is a better long-term bet than one that talks around every question smoothly without ever quite answering it.

Want a second opinion on a vendor you’re evaluating?

We’re happy to walk through this checklist with you against any proposal you’ve received — no obligation.

Get a Second Opinion

Related

Blogs

Team collaborating on accessible multilingual content with UI overlay icons
Translationary's approach: building accessibility and localization as one
Accessibility
Compliance
Localization
Most teams treat accessibility and localization as two separate projects, run by two different teams, on two different timelines. One group makes sure the product works with a screen reader. Another group makes sure it reads correctly in Spanish, German, and Japanese. They rarely talk to each other — and that's exactly backwards, because accessible localization isn't two problems solved twice. It's one problem, solved once, if you plan for it that way. Why These Are Actually the Same Problem Both accessibility and localization ask the same underlying question: can everyone actually use this, regardless of how they access it? A screen reader user and a non-English-speaking user hit strikingly similar walls when a product lacks flexibility. The same root cause usually explains both: the interface bakes content in directly, instead of pulling it from a structured, adaptable source. Picture a support page with a well-written FAQ. The English version has clean heading structure, proper alt text on screenshots, and good color contrast — it passes an accessibility audit easily. Then the team translates the page into Japanese, and nobody re-checks it. The accessibility work already happened once, so nobody thinks it needs to happen again. But the heading structure…
September 8, 2026
Team reviewing software localization checklist on a laptop
Getting software localization-ready starts long before the first translation request.
Localization
Your app looks perfect in English. Then it ships in German and every button overflows its container. It ships in Arabic and the layout doesn't just need new text — it needs to run in the opposite direction entirely. It ships in Japanese and half your date fields are formatted wrong. This software localization checklist exists because breakages like these are common, and mostly preventable, once you know where to look before translation starts. None of this happens because the translation was bad. It happens because software localization is a design problem first and a translation problem second. Most teams only discover that order after launch, when fixing it costs far more than planning for it would have. Why Software Localization Breaks More Often Than You'd Think Translating a website or a marketing document is largely a content problem: swap the words, keep the meaning, adjust the tone. Software is different. The words live inside a system with fixed constraints — button widths, character limits, hardcoded formatting, layout direction — and teams usually built every one of those constraints around English by default. German and Finnish words run 20–35% longer than their English equivalents on average. A "Save" button that…
September 4, 2026
Professional transcribing audio content on a laptop
Transcription is the first step in any multilingual audio or video project.
Transcription & Buyer Education
A global training team once recorded twelve product demo videos in English, sent the raw files straight to a translation vendor, and got a quote back that tacked on three unplanned days — for transcription nobody had budgeted, because nobody realized it was a separate step at all. The Step Everyone Forgets to Budget For It's an easy mistake to make, because the missing step is invisible until it isn't. A recording feels finished the moment it's recorded. But translators work from text, not audio — so somewhere between "we have the video" and "we have the translated version," someone has to turn spoken words into a clean written transcript. If all you have is a recording, someone turns it into words first — either you, unexpectedly, or your vendor, at an unplanned cost. Transcription vs. Captioning vs. ASR: Three Things That Get Confused Transcription, captioning, and automatic speech recognition often get lumped together. They're related, but they solve different problems. The American Translators Association treats a clean source transcript as the starting point for any downstream language work — and the distinctions below explain why: 1 Transcription converts speech to text in the same language. It's the raw material…
September 1, 2026