Skip to main content
Documents settings page

Settings > Documents

This view can look different dependent on your user role.
See Visibility & Permissions for details.

​
Primary Purpose

Create document templates that TWICE renders for your records and customers.
Build templates for an order (such as an invoice or receipt), a listing, a stock item, a customer, or a collection.
Author the template as HTML, then preview it rendered with sample data before publishing.
Each document template can have per-language content. Select a language in the template editor to write a translated version of the body.When rendering a document, the system resolves content in this order:
  1. Per-language override — the translated body for the requested language, if one exists.
  2. Template content — the body saved on the template itself (your source language version).
  3. Code default — for system templates (order confirmation, receipt), the built-in default in the requested language.
Custom document templates have no code default — if no per-language override exists, the source-language content is used.
Mark one template per type as the default, choose which entity types can use it, and keep it draft or active.
Document numbering is applied automatically when a document is issued — it isn’t configured here.

Emails

Email templates with the same per-language support and language routing

Multi-Language Content

How translations work across your catalog, locations, and templates

​
Visibility and Permissions

Access to this view is controlled by your .