Business supplies and services: Inventory software for localisation providers
Inventory software for localisation providers that manages terminology files, translation memories and language assets per client, so every language team works with the current version and outdated terms stay out.
Where stock drifts for localisation providers.
A localisation provider's stock is not a warehouse but a collection of language assets: translation memories per client and language, glossaries, style guides, do not translate lists and screenshots of earlier versions. Those assets are scattered across the translation environment, shared folders and email attachments. A translator works from last year's glossary while the client has renamed a product. A style guide exists in two versions and nobody knows which applies. A translation memory still holds translations rejected in the previous release. Without an overview of what exists, which version applies and who owns it, old choices leak back into new work.
Inventory software for localisation providers
Example- 1
Inventory assets per client
DoneFor each client and language you record which assets exist: translation memory, glossary, style guide, do not translate list and reference screens.
- 2
Link assets to a release
In progressAt the start of a release, the applicable assets are linked to the string package.
- 3
Write changes back
NextAfter the release, decisions from review and the portal are written back: new terms into the glossary, improved translations into the translation memory.
From receipt to use.
Inventory assets per client
For each client and language you record which assets exist: translation memory, glossary, style guide, do not translate list and reference screens. Each asset shows its version, the date of its last change and its owner. Duplicate or outdated versions are flagged.
Link assets to a release
At the start of a release, the applicable assets are linked to the string package. Translators and reviewers see which glossary and style guide version applies to this release. If a newer version exists than the one linked, the project manager sees it before work begins.
Write changes back
After the release, decisions from review and the portal are written back: new terms into the glossary, improved translations into the translation memory. Rejected translations are flagged so they do not reappear as suggestions. Each change gets a date and a reference to the release it came from.
Alongside your purchasing and suppliers.
Localisation providers typically keep translation memories and terminology in their translation environment, and style guides and reference material in shared folders. The overview does not replace that storage but tracks which version sits where and which applies. The client owns the style guide and decisions on product names; ownership of translation memory and terminology is something to agree per client, because they sometimes have to be handed over when a relationship ends.
One memory per client or per product
A single translation memory per client keeps everything together and yields more matches. For clients with several products using different terminology, it produces wrong suggestions. A memory per product is cleaner but takes more management. The choice depends on how different the products and their audiences are.
Strict or advisory terminology
A strict glossary enforced by the translation environment prevents deviations but can force a term that does not fit a particular sentence. Advisory terminology leaves room but invites inconsistency. Many agencies make product names and core terms strict and the rest advisory, reviewing after each release whether that line still holds.
Clean up old translations or keep them
A translation memory that grows for years holds translations that no longer fit current style or terminology. Cleaning up takes time but stops old choices returning. Keeping them flagged as outdated is a middle path: the translation stays findable for reference but is no longer offered as a suggestion.
Which stock we record.
At the start there is an overview of assets per client and language with version and owner; the applicable assets are attached to a release and decisions are written back after the release. Together we replay an ordinary release for a regular client, and a situation where the client renames a product that appears in every language. Marking rejected translations and a handover overview for when a collaboration ends can be switched on later.
View pricingSupport and updatesGood to know.
Explore pricing and optionsHow do translators know which glossary applies?
The applicable version is linked to the release's string package, which translators see in their task. If a newer version exists that has not been approved, the linked version continues to apply until the project manager releases the new one.
What do we do when a client renames a product?
The new name is added to the glossary with the date it takes effect, and the old name is marked as replaced. The overview shows which translation memories still contain the old name, so you can decide whether existing translations need updating.
Who owns the translation memory if a client leaves?
That depends on your arrangements with that client, ideally agreed in advance. The overview shows per client which assets exist, so a handover is complete if one has been agreed. The system does not determine ownership; it only makes it visible.
Can we see which assets have not been updated in a while?
Yes. Each asset shows the date of its last change and the release in which it happened. A style guide or glossary untouched for a long time while releases continued is a reason to check with the client whether it is still current.
What often connects to this.
- Digital job cards for localisation providersDigital job cards for localisation providers: a string package with version reference that records translation, review and screen testing per language, so every delivery traces back to a release.
- Website for localisation providersA website for localisation providers that explains how software, apps and help content are translated and tested per release, so a product team knows what to supply and when.
- Enquiry form for localisation providersAn enquiry form for localisation providers that gathers source strings, screen context and release details, so the language team knows where every string appears before translation starts.
Know what is really there.
Start with a short intake. Then we schedule a call to show the software with your services, team and way of working.
WhatsAppinfo@vorlyo.com Inventory software for localisation providers: terminology files, translation memories and language assets per client managed with owner and version.
- Inventory assets per client
- Link assets to a release
- Write changes back