Contract templates setup

Go to Commercial → Templates to review existing documents or create a new one.

Create a new template, give it a name, choose the type, and pick one of the two primary modes:

- HTML for flexible, signer-aware contracts built in Resvo. - PDF for exact uploaded legal forms with positioned fields.

Existing Markdown and plain-text templates remain available as legacy formats, but new authoring now centers on HTML and PDF.

Add your standard terms and insert variables from the editor panel instead of typing raw placeholders manually.

For HTML templates: - Edit the source in the HTML editor, use the starter snippets for common blocks, and keep Browser Preview visible while you work. - Use scalar variables like {{booking.code}} or {{customer.name}}. - Use core legal and tax values like {{customer.tax_id}}, {{customer.tax_legal_name}}, {{company.tax_id}}, {{organization.legal_name}}, {{organization.tax_id}}, {{organization.tax_person_type}}, {{organization.tax_country_code}}, {{organization.tax_legal_structure}}, and {{organization.logo_url}} when the agreement needs RFC, billing, or business-profile branding details. - Use repeat sections like {{#pricing.line_items}} ... {{/pricing.line_items}} when you need one row per pricing item. - Use repeat sections like {{#booking.additional_drivers}}- {{name}} | {{license_number}} | {{date_of_birth}}{{/booking.additional_drivers}} when your contract needs every attached driver. - Use lightweight branching like {{#if booking.has_company}} ... {{/if}} and {{#unless booking.is_company_rental}} ... {{/unless}} for renter-type clauses. - Insert inline signer fields such as a required customer name field and a required customer signature field directly from the toolbar. - Required signer fields stay visible in preview diagnostics until the signer provides them, and the captured signature image is rendered directly in the final HTML and generated PDF. - Use Generated PDF as the export fidelity check, because it now renders the resolved HTML through the PDF pipeline instead of a text fallback.

For PDF templates: - Bind only scalar variables to mapped fields. - Use summary-style scalar fields like {{booking.additional_driver_names}} or {{booking.additional_driver_summary}} instead of repeat sections. - Use manual fields for values staff or the signer must complete later.

Legacy Markdown and plain-text templates can still be edited, and you can convert them to HTML when you are ready.

Review the preview to make sure the contract reads the way you expect before saving or sending.

Save your changes, review any unsupported-token warnings, then set the template as active or default if you want it used automatically.