Kinds of template
System template. A template supplied by Qlero for a known provider layout, available on all plans. Its structure is read-only, but after adding it to your Library you can save custom mappings for your record company. Custom template. A template your record company owns and can edit in full. Creating and editing custom templates is available on Pro and Enterprise plans. Library. The system and custom templates you keep for regular use. Adding a system template doesn’t create a copy; it keeps the shared template and stores your custom mappings alongside it. Duplicate. An independent custom copy of an existing template. Later changes to the copy don’t touch the original. Start with a system template when one matches your provider. Use custom mappings for vocabulary differences, and create a custom template only when the file structure or processing rules differ.Fields
Template Name Required The name shown in the Library and the template selector. Template Provider. The optional group the template sits under in the Library, such as FUGA. A provider organises templates; the Source and Store on each sales row are separate settings. See Template Providers, Sources and Stores. Example sales file. The CSV or Excel file used to build and preview the template. It doesn’t import sales. Qlero accepts.csv, .xlsx, and .xls files up to 20 MB.
Sheet number. For an Excel workbook, the sheet Qlero reads. CSV files stay on sheet 1.
Header row number. The row holding the source column names. Set it to 0 when the file has no header row; Qlero then identifies columns by position and header-row matching isn’t available.
Data row number. The first row Qlero treats as sales data.
Column mapping. Connects a source column to a Qlero sales field, such as Gross to Gross amount. One source column can feed more than one field.
Date format. How Qlero reads a mapped Sale date or Transaction date, such as yyyy-MM-dd for 2026-08-01.
Default value. A fixed value used only when the field is otherwise empty. Use it when every row shares a value the file omits, such as one source or currency; map the column when the value changes between rows.
Transformation. Builds or changes a field from a source column, a cell, another processed field, or a fixed value, with conditions that control when it runs. Use one when a mapping and a default aren’t enough.
Line skip rule. A rule under Transformations that excludes rows whose conditions match, such as a totals row. All requires every condition, Any at least one.
Custom mapping. Translates an incoming value into one of your configured territories, format types, stores, sources, sale types, or currencies, such as US to United States. Qlero uses a matching custom mapping first, then a case-insensitive match on the configured name or code. A custom mapping overrides a system mapping for the same value.
Criteria matching. When Qlero suggests the template for a new file. Match by Header Row compares the header row and Match by File Name compares the file name with the text you enter. With both on, the file must satisfy both; with neither, the template is never suggested automatically.
Preview. How the current settings read the example file, with a counter of required fields that have a mapping, default, or transformation. Refresh it after changing a setting.
Required sales fields
Every processed sales row needs these 11 values, each from a column mapping, a default value, or a transformation. For the two dates, the import card’s Sale Date and Transaction Date fields can supply a fallback instead.
A template can be saved before all 11 are configured. A row still missing one after processing stays invalid until you fix it.
Repertoire identifiers. Map ISRC for tracks, or Barcode or Catalog number for releases. Each row needs at least one identifier that matches repertoire in Qlero. Track title, Track artist, Release title, and Release artist only preserve descriptions from the file.
If a report has no barcode, see Matching releases without a UPC for catalogue numbers, aliases and files that only identify tracks.
Price fields. Price category classifies the sale for terms that use one. Unit price, Retail price, and PPD keep the provider’s pricing values; map only the ones your terms use.
Using PPD in a custom template is available on Pro and Enterprise plans.