MAGPLAN: Multilingual B2B software and web structure
For MAGPLAN, multilingual content was organised as a system: product interface elements, categories and web content were maintained within one consistent structure.
Starting point
MAGPLAN is B2B software for maintenance and information processes. International use requires more than marketing pages: fields, categories, operating logic and recurring product updates have to remain aligned across languages.
The structure behind the project
Content was separated by function: product-interface elements, categories and web communication. This made it possible to maintain changes systematically across multiple language versions.
Implementation
- Separation of UI/data fields, categories and web communication
- Terminology consistency across recurring updates
- Maintenance of multiple language packages within the same product logic
- Revision of existing language versions rather than simple one-time creation
Outcome
The work created a reusable workflow across product and website. Project records document work in eight language versions; structured product and web-content packages are documented for Polish and French.
What the case shows for international B2B software
Consistency is central to software credibility and usability. Product interface, terminology, website and updates need to reflect the same market and product logic. At that point internationalisation becomes an operating system rather than a collection of isolated files.
Why software localisation is different from translating a website
In B2B software, the same concept appears in several places: fields, categories, interface elements, documentation and web communication. If these layers are handled independently, different terms can quickly emerge for the same function. That creates inconsistency for users and makes every later update more difficult for the company.
Separating content by function therefore created a working logic rather than additional bureaucracy. Software fields could be handled differently from longer web copy while remaining connected through shared terminology. This made it easier to see whether a change affected only the interface or also needed to be reflected in categories or website content.
Why ongoing updates matter more than the first translation
Software changes continuously. New functions, revised categories and updated copy create recurring localisation tasks. Without a shared structure, every update increases the risk that language versions drift apart.
The reusable workflow was therefore a central part of the project. Existing language packages could be revised and extended without restarting from zero each time. For international products, this maintainability is essential: multilingual content has to work in day-to-day operations.
What other B2B software companies can take from this case
Companies should define early which terms are binding across the product and where contextual variants are acceptable. A central terminology base helps product, marketing and support describe the same functions consistently.
A clear source for changes is equally important. If teams know which source text is current and which language versions are affected, releases can be coordinated more reliably. Internationalisation then becomes part of the product process rather than a downstream translation task.
Specific contribution to the project
The project work connected software fields, categories and website copy in a shared multilingual structure. The documented contribution consists of consistent terminology, structured language packages and recurring updates for the product and website.
Company
Maintenance and information management software.
Structuring an international B2B project?
Share the target market, offer and commercial question. We identify where market, buyer, content and visibility work should start.