Skip to main content

Import templates

Overview​

An import template defines the structure of the XLSX file you'll fill in: which product and variant fields to include, which variant axes your catalog has, which custom properties, and how many image columns. Once designed, you download a .xlsx already built with the headers, the dropdown menus, and the per-column comments — ready to fill in and upload. Ideal for standardizing recurring loads with the same format.

Unlike the previous approach (upload a CSV and map columns), today you design the schema and Aurora generates the file from it.

How to Access​

  • Navigate to Sales Catalog > Settings > Import templates (/sales/settings).
  • Required role: Administrator.

Interface Overview​

The Import templates screen shows the list of templates with their name, their structure (axes, properties, images), the update date, and actions. From there you can:

  • New template — opens the editor.
  • Download XLSX — generates the file from the template.
  • Set as default — the template that's preselected when importing.
  • Delete — deactivates the template (previous imports that used it keep working).

The template editor​

The editor ("Compose the template schema: choose the fields, define the variant axes, and preview the resulting XLSX file") is organized into sections:

  • Basic data — Name and description (what you use it for, what it prioritizes).
  • Product fields — Mark the fields that will appear as a column. Name, SKU, Price, and Currency are always included.
  • Variants — Enable "This catalog has products with variants" and define the axes (Color, Size…). Each axis is a column; maximum 4. A ProductHandle column is included to group the variants of the same product.
  • Variant fields — Fields specific to each variant.
  • Custom properties — If your catalog has custom properties, choose them to include them as columns.
  • Images — How many image URL columns per variant. Each column expects a public URL (http/https).
  • Sample rows and Preview — Show you the columns in order, just as they'll come out in the XLSX.

When done, Save and download XLSX saves the template and downloads the file ready to fill in.

Features & Actions​

Create a template​

What it does: Defines a new column schema you can reuse.

Steps:

  1. In Import templates, click New template.
  2. Enter Name and, optionally, Description.
  3. In Product fields, mark the columns you want (remember: Name, SKU, Price, and Currency are always included).
  4. If your catalog has variants, enable them and define the axes (up to 4).
  5. Add custom properties and image columns if you need them.
  6. Review the preview and click Save and download XLSX.

Important notes: The template saves the schema, not data. The labels and categories that appear in the file are created automatically when you confirm the import.

Edit a template​

What it does: Changes the name, the description, or the schema.

Steps:

  1. From the list, open the template.
  2. Adjust the fields, axes, properties, or images.
  3. Save (and download the updated XLSX if the structure changed).

Set the default​

What it does: Defines which template is preselected when importing.

Steps:

  1. In the list, use Set as default on the desired template.
  2. That template will appear already marked in step 1 of the import.

Delete a template​

What it does: Deactivates the template.

Steps:

  1. From the list, click Delete and confirm.

Important notes: Deleting a template doesn't affect the imports that already ran with it; it just stops being available for new loads.

Use a template in an import​

What it does: Download the XLSX and upload it filled in.

Steps:

  1. From Products, click New import and choose the Template card.
  2. Select the template, download the XLSX, fill it in, and upload it.
  3. Aurora validates the file and takes you to the staging editor.

Best practices​

One template per structure, not per file​

If you handle catalogs with different structures (one simple, another with variants and properties), create one template per structure. If everything comes in the same format, a single one is enough.

Name your templates well​

"Full catalog Q1 2026" is better than "Template 1". Your team in six months will thank you.

Combine with Draft products​

By default, imported products land in Draft status. This way you can import with confidence: if the file has rows with undetected errors, the products aren't exposed to the AI agent until your team reviews and activates them.

FAQ​

Q: Do templates support custom properties? A: Yes. Any custom property defined in your catalog can be included as a column from the Custom properties section of the editor.

Q: Do templates include image URLs? A: Yes. In the Images section you define how many image URL columns per variant. Each column expects a public URL.

Q: Can I import without designing a template? A: You need at least the default template (it works for most catalogs). Manual column mapping appears as Coming soon.

Q: I changed my catalog's structure. What do I do? A: Edit the template, download the XLSX again, and use it for your next load.