Troubleshooting & Reference · Article 7.16
"The email or PDF arrived in the wrong language"
Locale is pinned to the proposal at send time. If you change the proposal language after sending, already-sent emails stay in the original language. New emails (resends, follow-ups) use the new language.
Language is a per-proposal property, set when you start the proposal wizard and inherited by every email and PDF for that proposal. Changing it later is a manual operation — for already-issued legal documents, it's intentionally sticky.
Step by step
Open the proposal
detail page.
Edit the language
(Actions →
Change language, available for proposals not yet at terminal status).Regenerate any documents
affected (Documents dropdown → Regenerate).
Resend the relevant email
(Actions → Resend).
Why this works this way
Supported locales: en, de, nl, fr, pl, es. Fallback is en if the proposal somehow has an unsupported locale (rare; validation usually prevents this).
The client's country code drives the default — a German client gets a German proposal by default, a French client gets French. You can override per-proposal in the wizard. The chosen locale flows into:
- Email subject and body (template name pattern: {task_name}_{locale}.html).
- PDF template (Jinja files per locale).
- Currency formatting (€1,234.56 in EN; 1.234,56 € in DE).
- Date format (2026-05-03 in international; 03/05/2026 in some locales).
Troubleshooting
Keep reading
Working with Clients
Multi-language proposals: matching the client's language
Each proposal is rendered in exactly one language — pick the one your client prefers and Clozo translates everything legally significant: emails, PDF section headers, VAT disclaimers, payment terms.
Refunds & Notifications
Every email Clozo sends, in one table
Clozo dispatches 13 distinct transactional emails across the proposal and amendment lifecycle. This page lists each one, who triggers it, who receives it, and what's attached.