Skip to content

Exports

Last updated: June 24, 2026

In the export workflow, you map source data into your export template structure and download the output file.

What you need before starting

  • An Excel or CSV source file.
  • At least one active export template.
  • Optional: active suppliers (depending on template requirements).

Export workflow step by step

  1. Upload your file and confirm detected columns.
  2. Select a supplier (or use default supplier behavior).
  3. Select an export template.
  4. Map columns, review validation findings, and check the preview.
  5. Choose export format (XLSX and/or JSON).
  6. Generate the export and download the file.

Supplier rule in exports

A supplier is only mandatory if your export template contains a supplier column. In that case, a valid active supplier must be available (selected or default).

Creating export templates

On Export Templates, you can create custom templates when this feature is available on your plan. There are two paths:

  • Create template — add and edit columns manually.
  • Import from file — upload a reference file, detect columns automatically, review, and save.

JSON structure for file import

Import from file supports .xlsx, .csv, and .json reference files. For JSON, two valid shapes are supported:

  1. Array of flat objects — column names are taken from the keys of the first object:
    [
  { "Product ID": "A001", "Product Name": "Widget", "Price": "12.99" },
  { "Product ID": "A002", "Product Name": "Gadget", "Price": "8.50" }
]
  2. Object with a headers or column_order array:
    {
  "headers": ["Product ID", "Product Name", "Price"]
}

    Alternatively, you can use column_order:

    {
  "column_order": ["Product ID", "Product Name", "Price"]
}

After import

Detected columns are loaded into the editor. Review names, keys, data types, and order before saving the template.

Pre-export validation

Before the final export, EvoKlar checks mapped data directly in your browser. Validation is warn-first by default — you stay in control unless no rows would be exported at all.

  • Unmapped template columns (warning)
  • Missing values in required columns (warning)
  • Duplicate values in key columns such as EAN, GTIN, or Artikelnummer (confirm before export)
  • Invalid EAN/GTIN or German PLZ format where applicable (warning)
  • Zero rows to export (blocked)

Validation privacy

Validation uses the file already loaded in the browser. No additional file content is sent to the server.

Use column mapping correctly

  • Your export template defines target columns and their order.
  • Map source columns to target columns as needed.
  • Unmapped target columns remain empty in the export.
  • Review preview data before final export.

Auto-suggest

After upload, EvoKlar suggests mappings from column names. Accept all, clear all, or adjust individual rows.

Remember mapping

Use Remember this mapping for [supplier] to save mappings for repeat exports (concrete supplier only). See the Workflows guide for details.

Export again

From export job detail, Export again starts with the same settings; a new source file is required.

Practical default

For recurring exports, keep templates stable and use consistent source column names whenever possible.

Format and download

  • You can generate XLSX, JSON, or both formats in one run.
  • Files are downloaded directly in the browser.

After export

The export run is saved as a job so you can trace history and metadata.

Output responsibility

You are always responsible for reviewing and verifying output results. DO NOT use processed or exported files in production workflows until you have fully verified that everything is correct.
Agent view