View all features
View all suite

Growing & production

Trade, export & supply

Retail & e-commerce

Beyond horticulture

View all industries
Library Contact sales
EN IT
library · field guide

Bolt-on translation always breaks.

Plants cross borders long before the software does. A grower in one country sells to a garden centre in another, ships against paperwork in a third language, and hires staff who each read best in their own. A system that treats language as an afterthought cracks at exactly these seams, and the cracks are always most visible to your customers.

the premise

Language is structure, not decoration.

Where a plant came from, what its label must say, how a validation error reads to the person fixing it — every one of these is language, and every one has to be right in the reader's tongue. That is a decision about architecture, made on day one.

the retrofit trap

Why translation added late never quite fits.

Most business software is born speaking one language. The screens, the buttons, the error messages, the report headings — all written directly into the code in whatever tongue the first developers used. It works, it ships, and for a while nobody notices the assumption baked into every line: that there is only ever one language, and it is this one.

Then the business crosses a border, and the retrofit begins. A translation layer is bolted on top. It catches the obvious things, the menu and the big headings, and misses a hundred small ones: the validation message that still scolds in English, the date that reads in the wrong order, the status pill hard-coded years ago, the email that goes out half-translated. Each gap is small; together they read as unprofessional. Worse, every new feature reopens the wound, because the original habit of writing it in one language and translating it later never actually went away.

The alternative is a system where no text is ever written assuming a single language: every label, message and word the user sees is a translatable value from the first day, and adding a language means supplying words rather than re-plumbing the software.

Every layer the user meets.

all the way down

Every layer the user meets.

A system built multilingual from the ground up reaches every layer the user actually meets: menus, field labels, validation messages, system text, alerts and confirmations. That is the small print of everyday use, and it is where bolt-on translations usually fail first.

That completeness is the whole difference. A retrofit translates the parts someone remembered; a system built multilingual translates the parts nobody thinks about until a user hits them. The measure of good localisation is the error message you see on a bad day, and whether it speaks your language too.

One nursery, one language — every language ready.

shown in your language

One nursery, one language — every language ready.

Most businesses work in a single language, so a well-built system simply shows that one. The configured workspace is set to how your team actually works, and the interface, labels and messages all appear in it, with no half-and-half screens and no toggling for staff who only ever need the one.

But ready and shown are different things. Because every language lives in the system already, switching or adding one is a configuration choice. A business that grows across a border, or hires a team that reads best in another tongue, finds the words already there, waiting to be turned on.

help, everywhere

Even the help speaks every language at once.

Good contextual help holds all supported languages together, even though a deployment usually shows just one.

In a well-designed system, screens and sections offer short contextual help — a plain explanation of what a field or area is for, right where you are working. The best of them serve that help from a separate service and pull it in on demand. The reason is practical: help is improved far more often than the software itself, and shouldn't require redeploying the whole app each time.

The multilingual point is quieter but telling. A good help library holds every supported language at once, even though a deployment typically shows only one. When guidance is written, it is written for everyone, so the day a team switches language, the explanations switch with it, already complete.

Where a bolt-on comes apart.

the seams that show

Where a bolt-on comes apart.

Retrofitted translation fails in predictable places, and they are exactly the places a serious buyer looks. A label printed for a customer in the wrong language. An invoice heading that never got localised. A status that reads in English on an otherwise Italian screen. A validation error that stops someone mid-task in a language they don't read.

None of these is catastrophic on its own, and that is the trap. They accumulate into a quiet impression of a system that wasn't really made for you, run by a company that treats your language as someone else's problem. It doesn't cost you a crash. It costs you credibility, one untranslated word at a time.

Horticulture was always multilingual.

trade has no border

Horticulture was always multilingual.

The nursery trade has crossed borders for as long as it has existed: Dutch stock in Italian garden centres, Italian growers supplying across the continent, plant passports and phytosanitary paperwork moving between authorities that each work in their own language. In this industry, language is the everyday reality of selling a living thing to someone in another country.

Software that serves this trade has to start from that reality rather than discover it late. When many languages are present from day one, a business can follow its plants across a border without waiting for its system to catch up.

atlas core

How Atlas Core handles multilingual horticulture

Atlas Core applies the principles above to the cross-border reality of the nursery trade:

  • Built multilingual from the ground up across English, Italian, Romanian and Spanish — every language present in the system now, so adding or switching one is a configuration choice rather than a migration project.
  • Localisation reaches every layer a grower meets — menus, field labels, validation messages, system text, alerts, confirmations and printed output like plant labels and invoice headings.
  • A single working language is shown per deployment, with no half-translated screens, while every other supported language stays ready to turn on.
  • Contextual help is served from a separate companion service that holds all supported languages at once, so guidance switches language with the interface and improves without redeploying the app.
  • It fits everyday cross-border trade: stock, plant passports and phytosanitary paperwork moving between countries that each work in their own language.

Read further

In praise of boring technology Tech brief · 2026

In praise of boring technology

The software that runs your nursery will still be running it in ten years - exactly the wrong place to chase the newest tool. What 'boring' technology buys: fewer moving parts, fewer 3am surprises, and excitement kept for the plants.

6 min read · Jul 2026 Read →

See a system that speaks your language, all the way down.

Run your nursery in the language your team and your customers actually use — interface, validation, system text and contextual help, all localised from the ground up. Talk to us about what that looks like for your business.

Talk to us