Translation Vendor Management: How Manufacturers Keep Several Suppliers, Subsidiaries and Markets Consistent
Translation vendor management works when the company, not its suppliers, owns the assets: one translation memory, one approved glossary, common quality criteria and one request route that every vendor and subsidiary uses. Suppliers can then be added, compared or replaced without losing consistency or paying twice. DEMA Solutions helps manufacturers set up exactly this, and keeps those assets under the client’s control.
Is this your situation: several vendors, and nobody owns the assets?
This guide is written for the people who inherit a translation landscape rather than design one: procurement managers asked to explain a line of spend nobody can break down, operations and quality directors who want fewer suppliers and less liability risk in safety content, localization and technical documentation managers who receive the same manual back from three countries with three different names for the same component. Many of them work at manufacturers of machinery, HVAC, lifting, packaging or automation equipment with subsidiaries across Europe, or at the Italian arm of an international group whose parent expects group-consistent terminology.
Their questions are practical: what is this many translation vendors really costing us, should we consolidate, who should own the glossary, and how do we move work to a new supplier without breaking a product launch?
What translation vendor management actually covers
In many companies, “managing translation vendors” means sending files out and paying invoices. Real translation vendor management covers which suppliers you use and for what, which linguistic assets they must use, how requests reach them, how output is checked and compared, and what happens to your assets when a relationship ends. It matters because the problems of a multi-vendor setup rarely sit inside one supplier. They sit in the gaps between suppliers: terminology nobody coordinates, memories nobody shares and coordination work that lands on your own teams.
Why manufacturers end up with several translation vendors
Few companies decide to work with five translation suppliers. It happens gradually, and each step makes sense when it is taken.
Subsidiaries are often the first source: the German sales company works with a local supplier it trusts, the French one with another, the Spanish distributor reviews everything in house. Acquisitions are the second. An acquired company arrives with its own documentation, its own suppliers and its own memories and glossaries, often stored with those suppliers rather than with the company, and overnight the group has two names for the same part. Decentralised buying is the third, as documentation, marketing, legal and training each find a supplier for their content and pay from their own budget. New markets add to it, because a new language goes to whoever can start next week, and stays there.
The result is a translation landscape nobody planned and nobody fully sees. It is what happens when translation is bought as a series of separate purchases rather than managed as a shared process.
The real cost of several unmanaged translation vendors
The cost of a fragmented supplier base is rarely visible on a single invoice. It builds up in places that are easy to overlook.
Fragmented memories mean paying twice. Every supplier builds its own translation memory from the jobs it handles. When content translated by one vendor goes to another, the second has no access to the first one’s memory, so sentences you have already paid for are translated, reviewed and paid for again. In technical documentation, where new manuals reuse large parts of older ones, this is often the largest hidden cost. What really drives the price of a manual is explained in our guide to what makes technical manual translation expensive.
Inconsistent terminology reaches the user. The same component gets one name in the German operating manual, another in the French spare parts catalogue and a third on the HMI. A technician who reads “pressure relief valve” in the manual and sees a different term on the screen hesitates, and in safety warnings that hesitation is a liability. One shared, approved glossary fixes this, which is why keeping terminology consistent across suppliers is the first thing to centralise.
Review is duplicated. Subsidiaries re-check translations they did not commission, and engineers spend hours correcting terms another supplier chose differently. Those corrections reach one vendor’s memory but not the others’, so the same problem is fixed again next year.
There is no leverage. Volume spread across five suppliers gives you a weak position with each, and the memory leverage that should reduce the cost of every update is split five ways.
Coordination falls on your teams. Someone in each office chases quotes, deadlines, missing files and corrections, usually by email. That time never appears in the translation budget, but it is real.
Spend is invisible. Translation costs are booked across subsidiaries and cost centres, sometimes inside marketing or engineering projects, so nobody can say what the group spends in total or how much was duplicated.
Changing supplier means starting over. If your memories and glossaries sit with your vendors, moving work elsewhere means losing years of approved translations, or negotiating to get them back. That is why owning your translation memory matters more than which supplier happens to hold it today.
When working with several suppliers makes sense
Managing multiple translation vendors is not a problem in itself. There are good reasons to keep more than one: a specialist for patents or legal content, a supplier with rare language pairs, local partners for marketing copy that needs a strong national voice, or a second supplier to avoid depending entirely on one. Large programmes sometimes need more capacity than one supplier can guarantee at peak times, for example ahead of a product launch or a regulatory deadline. Marketing teams weighing plugins, bilingual colleagues and professional providers for their own site will find the trade-offs set out in our guide to website translation options and cost.
What makes a multi-vendor setup work is not the number of suppliers but the rules they share. Several vendors working from the same memory and glossary, through the same request route and against the same quality criteria, can be more resilient than one. Several vendors each working from their own assets will drift apart, however good each of them is.
Consolidate, share assets or appoint a lead partner
There are three realistic models, and the right one depends on your size, your structure and how much your subsidiaries need to keep their own relationships.
Keep several vendors, share the assets. Each supplier keeps its markets or content types, but all of them work from one translation memory and one glossary that you own. Local relationships stay intact, duplicate work and terminology drift disappear. This model asks the most from you, because someone has to own the assets and make sure every supplier uses the current version.
Consolidate to fewer vendors. One or two suppliers cover most languages and content types. Coordination becomes simpler, volumes give you a stronger position, and memory leverage is concentrated where it can work. Translation vendor consolidation is safe only if the assets remain yours and you keep the practical ability to change supplier later.
Appoint a lead partner. One partner manages the programme, the assets and the request route, and works alongside specialist suppliers where needed. Your teams deal with one contact, while you keep ownership of everything that has been built. For groups with many subsidiaries, this is often the model that removes the most internal coordination.
All three depend on the same condition: the translation memory, the glossary and the style guides belong to you, not to whoever translated the content.
The governance rules every multi-vendor setup needs
Whichever model you choose, four rules carry most of the weight.
- One terminology owner. A named person or small group, usually in technical documentation or product management, approves terms and decides on local variants.
- Shared assets the client owns. One translation memory and one glossary, held in portable formats such as TMX and TBX, used by every supplier on every job.
- Common quality criteria. The same definition of an error, the same revision requirement and the same way of handling complaints, whoever translates.
- One request process. Every subsidiary and department sends requests the same way, so nothing bypasses the shared assets.
The terminology owner is the rule companies most often skip, and the one that matters most. Without it, every supplier makes its own choices and every subsidiary reviewer overrides them differently. With it, a disputed term is decided once, recorded in the glossary and sent to every supplier, and local variants become recorded exceptions rather than accidents.
Style guides belong in the same set of assets. A translation style guide records how warnings are phrased, how units and numbers are written and how formal the text should be, so voice and conventions do not depend on which supplier received the job. Common quality criteria then make it possible to compare suppliers fairly. If one vendor revises every translation with a second linguist and another does not, their prices are not comparable, and the questions worth asking about this are covered in our guide to checking a supplier’s quality before you hire them.
The request process is where governance becomes real. When requests travel by email to whichever supplier the requester knows, the shared assets are bypassed the first time someone is in a hurry. A single route, whether a portal, a central project manager or both, makes the shared assets the default rather than the exception, and lets you stop managing translation by email and spreadsheets.
Consolidating translation memories and glossaries
Merging linguistic assets is usually the first concrete step, and it is more than copying files into one folder.
Start by recovering what exists. Ask every current supplier for the translation memories and glossaries built on your content, in standard formats, and agree in writing that they are yours. If ownership was never discussed in the contract, this is the moment to settle it, ideally before you announce any change of supplier. Include the acquired company’s assets and anything held by subsidiaries or distributors.
Then align terminology before you merge memories. Compare the glossaries side by side, decide which term becomes the standard for each concept, and record the rejected alternatives so they can be found and corrected. Doing this first means the merged memory can be cleaned against an approved glossary rather than against whichever supplier’s choice happens to dominate.
Merging the memories themselves means removing duplicates, resolving segments where the same source sentence has several different translations, marking outdated terminology and keeping track of where each entry came from. Some segments will need a decision from the terminology owner. Where approved translations exist only as finished documents, with no memory behind them, source and target files can be aligned to recover them, which is the job of translation memory alignment. A merged memory full of conflicting translations is worse than two separate ones, because it spreads inconsistency into every future job.
Evaluating suppliers on the same basis
Price per word says little on its own. One supplier may quote a lower rate but ignore your memory, skip revision or require hours of internal correction. A fair comparison needs the same assets and the same criteria for every vendor.
The useful measures are how much of each job comes from your memory, how closely output follows your glossary, who revises the translation and how complaints are handled, turnaround from request to a usable document (including layout in the original format), and how much internal effort each supplier requires from your teams. That last measure is the one most often forgotten and the one operations directors care about most. A supplier that delivers on time but needs two rounds of corrections from your engineers is more expensive than its invoice suggests.
Once every vendor works from your assets, these comparisons become fair, and decisions about consolidation become business decisions rather than leaps of faith. If you are adding a supplier or replacing one, our ten questions for choosing a technical translation company are a good start.
Moving work between vendors without disruption
Fear of disruption keeps many companies with suppliers they are unhappy with, but most of that risk can be managed. Do not move everything at once. Choose a pilot, ideally a real project with a clear scope, a few languages and content that reuses earlier translations, so the memory transfer is tested in practice. Brief the new supplier with the merged memory, the approved glossary, the style guide and examples of documents your subsidiaries consider correct. Ask the subsidiary reviewers who will judge the result to agree in advance on what counts as an error, so feedback is about quality and not about preference. Each stage of that move, including how to check the exported memory before the pilot, is covered in our article on changing translation supplier.
Keep the outgoing supplier on open projects until they are delivered, and make sure their final memory updates come back to you. Avoid switching during a regulatory deadline. With the Machinery Regulation (EU) 2023/1230 applying from 20 January 2027, many manufacturers are revising instructions and declarations, and the translation requirements of the Machinery Regulation are better handled by a stable process than by a supplier change in mid-project. Formats matter too: if your manuals are in InDesign, FrameMaker or XML, test that the new supplier hands files back clean in the same format before you move the large volumes.
Measuring spend and leverage
You cannot manage what you cannot see. The first step is a simple inventory of translation spend across every subsidiary, department and cost centre for the last year or two: who bought what, from whom, in which languages and for which product lines. It is often the first time anyone has seen the total.
The second step is leverage reporting. For every job, ask your suppliers to show how many words were new, how many were fuzzy matches and how many came fully from the memory, and how each category was priced. Over time, that tells you how much of your content is genuinely new and how much reuse you are actually getting. As an illustration only: if a manual update of 20,000 words contains 12,000 words that already exist in your memory, a supplier using the full memory translates and charges for far less new content than a supplier who never received it. The difference is your duplicated spend.
Tracking spend by supplier, reuse, glossary compliance, turnaround and correction rounds every quarter is enough to show whether consolidation is working, and lets procurement negotiate on what really drives cost rather than on rate alone.
A step-by-step plan for translation vendor management
Step 1: map the landscape. List every supplier, what they translate, for whom, in which languages and at what cost. Include subsidiaries, distributors and departments that buy translation independently.
Step 2: recover and secure the assets. Collect memories and glossaries from every supplier in standard formats and confirm in writing that they belong to you. Add ownership and export clauses to every future contract.
Step 3: appoint the terminology owner. Give one person or small group the authority to approve terms, and agree how subsidiaries can propose changes.
Step 4: align terminology and merge the memories. Build one approved glossary first, then merge and clean the memories against it, resolving conflicts rather than keeping all versions.
Step 5: set common quality criteria and one request route. Define revision requirements, error categories and complaint handling, and route every request through the same channel.
Step 6: choose the vendor model. Decide whether to share assets across current suppliers, consolidate, or appoint a lead partner, based on what the first five steps revealed.
Step 7: move work in phases. Pilot, review, then transfer larger volumes, keeping open projects with their current supplier until they close.
Step 8: measure and review. Report spend, leverage and quality every quarter, and revisit the vendor model once a year or after any acquisition.
What to ask a supplier who will work in a multi-vendor setup
A supplier joining or leading a multi-vendor programme should be comfortable working from assets it did not build and handing back assets it did. Ask whether it will use your memory and glossary on every job and return the updates to you in portable formats. Ask how it revises translations and whether reused text is checked again in safety or regulatory content. Ask how it reports leverage, and whether its prices reflect reuse rather than a flat rate. Ask whether it can deliver in your original formats, including layout, so your teams do not fix files after delivery. And ask how it handles terminology disagreements with your subsidiaries: the right answer involves your terminology owner, not the translator’s preference.
How DEMA Solutions works with multi-vendor organisations
Groups with several brands, departments and subsidiaries often reach us with assets scattered across suppliers, so our first principle is the one this guide argues for: the language assets belong to you. We build your translation memories and glossaries and deliver them in TMX and TBX whenever you ask, which keeps every supplier, including us, replaceable. Requests from internal teams arrive through one route, and memories can be split by brand or content type where different voices must stay apart.
Each translation follows our ISO 17100 certified process, audited every year, with a second qualified linguist revising the text, and in sensitive projects translations taken from the memory are checked again; our quality page sets out the full process. Manuals, catalogues and leaflets come back from our in-house DTP team in their original formats, and our teams in Italy, Serbia and Spain work on one shared set of assets. Leverage reporting is open, so you can compare what each project reused.
An international fashion retail group turned this into a long-term programme, with style guides and translation memories per brand, stable linguist pools and central coordination, so several departments now share one language partner without losing their brand voice. Our multi-brand case study describes how it was set up.
Where TUBE fits
In a multi-vendor setup, the risk is that each supplier keeps its own version of your language. TUBE turns that around: your glossary and translation memory guide machine translation in an AI-managed process, and every approved translation lands in a memory you own and can hand to any supplier. Leverage reports show what share of each job came from reuse, which gives procurement the figure that multi-vendor organisations usually cannot produce.
Frequently asked questions
It is the way a company selects, coordinates and measures its translation suppliers: who translates what, with which translation memory and glossary, through which request route, against which quality criteria, and what happens to the assets when a supplier changes.
Not necessarily. Several vendors can work well if they share one translation memory and one glossary that you own and follow the same quality criteria. Consolidation helps when coordination costs are high, volumes are spread too thin to give you any leverage, or terminology keeps drifting despite shared assets.
Your company, not a supplier. In practice, one named terminology owner, usually in technical documentation or product management, approves terms and local variants, and every supplier receives the same approved version.
Make sure every vendor works from the same translation memory, owned by you and available in a standard format such as TMX, and ask for leverage reports that show how much of each job came from the memory and how it was priced.
They should be recovered from the acquired company's suppliers in standard formats, its terminology aligned with yours, and the memories merged and cleaned, so both companies' approved translations are reused from then on.
Give them the same assets and measure the same things: reuse from your memory, glossary compliance, revision process, turnaround to a usable document and the internal effort they require, not only price per word.
Secure your memories and glossaries first, run a pilot on a real but contained project, let open projects finish with the current supplier, and avoid switching in the middle of a regulatory deadline or product launch.
Bring your vendors under one set of assets
If your subsidiaries or departments work with different translation suppliers and nobody has the full picture, start with the assets and the spend. Tell us how your translation is organised today and we will show you what to centralise first and how to move without disrupting your projects.
How can we help?
Tell us what you need and we’ll get back to you with the solutions.