- Industry
- Procure AI
- Department
- Content
- Team
- Content Production
- Kind
- Assistant
- Approver
- Localization Lead
- Code
- CON-06
It localises supplier onboarding guides, requisitioner instructions, RFx templates and marketing content into the languages of client and supplier regions, using the glossary and translation memory and adapting tax, e-invoicing and legal notices per country. It returns each locale's version with the passages a native reviewer must check and opens one review job per locale.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the translation management system: the translation memory matches, procurement glossary and do-not-translate list for the source content and locales named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Localization Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the translation management system: it creates one review job per locale with the localised draft for a native reviewer. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The localization kit: per-locale style guides, the procurement term glossary and do-not-translate list, each country's e-invoicing, VAT/GST and supplier-registration requirements, and regional legal and disclosure text.
Reads from
the translation management system: the translation memory matches, procurement glossary and do-not-translate list for the source content and locales named.
Acts in
the translation management system: it creates one review job per locale with the localised draft for a native reviewer.
Hands back
A list with one entry per target locale, each with locale, title, body, tm_leverage_percent, glossary_terms_used (a count), country_rule_changes (a list of tax and e-invoicing steps adapted) and review_points (a list of passages a native reviewer must check).
Asks a person when
A target locale is not in es-MX, pt-BR, de-DE, fr-FR, en-GB, the content is a contract clause or compliance statement, or a country's tax or e-invoicing rule is missing from the kit.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Locales it may produce | es-MX, pt-BR, de-DE, fr-FR, en-GB | Comma-separated. Any other locale needs the approver. |
| Reuse translation memory at or above (%) | 85 | Translation memory matches at or above this are reused; the rest is translated fresh and marked. |
| Adapt tax and e-invoicing steps per country | On | When on, supplier guides carry the target country's tax ID, VAT/GST and e-invoicing steps instead of the source country's. |
| Most length growth for UI strings (%) | 30 | Platform UI strings may run at most this much longer than the source. |
| Legal and contract text needs a native reviewer | On | When on, contract clauses, terms of supply and compliance statements always go to a native reviewer. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Localise only into es-MX, pt-BR, de-DE, fr-FR, en-GB; any other locale needs the Localization Lead.
- Reuse translation memory matches at or above 85 percent; translate the rest fresh and mark it for review.
- Use the glossary term for every procurement term (purchase order, goods receipt, three-way match) and leave do-not-translate terms, field names and system labels as they are.
- When on is true, replace tax ID, VAT/GST and e-invoicing steps with the target country's rules from the kit and list each change; never guess a country's rule the kit does not hold.
- Keep platform UI strings within 30 percent of the source length.
- When on is true, every contract clause, terms-of-supply and compliance passage is a review point for a native reviewer.
- Localise dates, number formats and currency formats; never convert a price or threshold between currencies.
See the Localization Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.