Skip to Content
Build with FinquLiquid ThemesCustomer CommunicationsPrintsOverview

Print Themes Overview

Finqu print themes provide a structured way to customize printable documents such as invoices and packing lists. Use the directory layout and Liquid templates to create branded, localized documents for order-related workflows.

Directory Structure

Print themes are organized into specific folders, each serving a distinct purpose:

  • assets/: Custom stylesheets (.scss.liquid or .css.liquid) for your prints. Styles are compiled and injected into templates.
  • config/: Contains settings_data.json for theme configuration and future graphical editing support.
  • layout/: Layout files (e.g., theme.liquid) define the overall structure of your prints.
  • locales/: Translation files for supporting multiple languages.
  • snippets/: Reusable components to simplify template maintenance.
  • templates/: The actual print templates, each corresponding to a specific print type or event.

This structure keeps your print theme organized and maintainable.

Templates are the core of your print theme. Each template defines the content and structure for a specific type of print document (such as invoices or return forms). Templates are organized by context (e.g., orders), which determines the available variables and special features.

A template file typically includes:

  1. HTML: The main print content, written in HTML and Liquid for dynamic data. The HTML is automatically converted to PDF when printed or downloaded.
  2. Plaintext: (Optional) A simple text version for maximum compatibility.
  3. Schema: Defines the document title and other metadata, supporting variables and localization.

Templates can use global variables (like order, customer, or channel) and special variables for dynamic content. Unlike emails, print templates do not support special tags. All changes can be previewed in the Finqu admin using the built-in preview functionality.

Example Print Templates

The following print templates are available in the templates/orders/ folder:

  • credit_note.liquid
  • invoice.liquid
  • packing_list.liquid
  • receipt.liquid
  • return_form.liquid

Best Practices

  • Keep styles simple and printer-friendly.
  • Always provide a plaintext version for accessibility if possible.
  • Use snippets for reusable components.
  • Localize templates and schema fields for multilingual support.
  • Maintain a consistent naming convention and structure for easier management.
  • Use the admin preview to test changes before publishing.