Brand and localize your calculator

Organization branding controls the business identity shown to customers. Estimator text, language and currency belong to the definition and its published revision. Treat these as related settings with different lifecycles.

Start with the business identity #

Open Branding as an owner or admin. Set the displayed business name, logo, contact details and website. Use details customers can recognize and contact; a calculator with unexplained branding is difficult to trust.

Choose a primary color, secondary color, background, available font, button style and radius. Review the live preview, then check the actual public calculator. A preview cannot replace testing long labels, validation messages or the mobile result.

Branding changes are organization configuration. They do not require changing the mathematical rules of every estimator. Historical PDF prices remain retained, while regenerated PDFs use current business branding and contact information.

Upload supported assets #

Logos and favicons accept PNG, JPEG or WebP up to 2 MB and 20 million pixels. The server decodes and normalizes them to generated WebP assets, removes metadata and limits dimensions. SVG, animation and customer document uploads are unsupported.

Brand assets are publicly readable. Do not upload private customer material as a logo. Local deployments persist them in the configured asset volume; S3 deployments serve them through the application from the selected bucket.

If an asset works before a restart but disappears afterward, investigate persistence before changing the UI. See storage and SMTP and troubleshooting.

Choose locale and timezone #

Organization settings support English and Portuguese (Brazil). The organization locale guides new estimator creation and administration copy. A published estimator retains the language in its revision; switching an organization does not rewrite live definitions.

Timezone expresses business context. A weekend price rule still reads a YYYY-MM-DD date answer as a calendar date. It does not infer a customer's timezone or convert a moving date using the server clock.

Translate meaningful text #

The bundled templates contain Brazilian Portuguese translations for names, descriptions, steps, fields, choices, rules and result copy. Custom content needs equivalent translations if you want a complete bilingual experience.

Translation metadata uses stable identifiers, for example:

{
  "pt-BR": {
    "name": "Estimativa de mudança",
    "step:route": "Sua mudança",
    "field:distance": "Distância (milhas)",
    "rule:distance": "Distância percorrida"
  }
}

This is a translations fragment for the Moving definition. Keep its referenced IDs unchanged. Translation affects presentation, not the unit: translating “miles” does not convert the quantity into kilometers.

If you want kilometers, rename the label, revise the rates and explain the unit. Publish and test that estimator as a deliberate pricing change.

Set currency without implying conversion #

The default organization currency applies to new estimators. Existing estimates are not converted. The estimator declares its currency and minor-unit exponent, and its monetary values must match that exponent.

BRL and USD both use two minor units, but swapping their codes does not apply an exchange rate. Review every rate, minimum, maximum and formula constant when creating a calculator in a different currency.

Test readability and the whole flow #

Check the calculator at a narrow mobile width, with keyboard focus visible, and with both successful and invalid answers. Test a long Portuguese label, a multiline description, the price explanation and contact consent.

Use distinguishable button and text colors. Do not use color alone to communicate a required field or an error. Keep the most important instructions close to the relevant control.

For a custom domain, finish DNS and proxy verification. Domain branding does not move administration or API credentials off the installation's canonical origin.