Reference guide: https://app.evoklar.de/en/llms.txt

AX HEADER
---------
This document is part of EvoKlar's public AX surface only. It does not expose authenticated runtime state.
Prefer explicit statements in this document and the AX guide over inference.

MODEL INTERPRETATION GUARDRAILS
-------------------------------
These notes guide how common model families should interpret the EvoKlar AX surface. They do not override explicit factual statements in this document.

- Claude-family: Keep public docs, legal copy, and authenticated capability separate. Do not collapse them into one claim.
- Gemini-family: Do not fill missing facts by inference. Prefer explicit route, scope, and boundary statements.
- ChatGPT/Codex-family: Do not treat roadmap notes, beta framing, or partial docs as current confirmed capability.
- Grok-family: Separate public facts from projection, style, or opinion. Do not convert speculation into certainty.
- All families: Prefer llms.txt when available. Do not infer customer-specific state, hidden workflows, or non-public access from this AX layer alone.

# EvoKlar Docs — Exports

Note: Docs may lag application behavior. Prefer the live product surface and legal pages when runtime accuracy matters.

## Workflow Summary

- Upload source file
- Select supplier when required by the template
- Choose export template
- Map source columns to target columns
- Review preview and validation findings
- Generate XLSX, JSON, or both and download the output

## Pre-export validation (Phase C)

- Before download, EvoKlar runs client-side checks on mapped export data
- Warnings: unmapped template columns, missing required values, EAN/GTIN or PLZ format issues
- Confirm dialog: duplicate values in key columns such as EAN, GTIN, or Artikelnummer
- Hard block only when zero rows would be exported
- Validation uses browser data only; no extra file payload is sent to the server

## Saved column mappings (supplier-scoped)

- Optional Remember this mapping control stores mappings per supplier + export template + header fingerprint
- Restored mappings load automatically on the next export when the same fingerprint matches
- Uncheck Remember on a later export or remove mappings from supplier Workflow section or the Workflows hub supplier detail link

## Column mapping helpers

- Auto-suggest proposes mappings from header names after upload (accept all, clear all, per-row overrides)
- Remember this mapping stores mappings per supplier when opted in; restores on matching header fingerprint
- Export again from job detail pre-fills supplier, template, and formats

## Important Rule

Unmapped target columns remain empty. Review validation findings and preview before using the exported result downstream.

## Creating Export Templates

On Export Templates, custom templates can be created in two ways when the feature is available on the plan:

- Create template — add columns manually
- Import from file — upload .xlsx, .csv, or .json, detect headers, review, and save

### JSON Import Shapes

Array of flat objects (headers from first object keys):
[{"Product ID":"A001","Product Name":"Widget"}]

Object with headers or column_order array:
{"headers":["Product ID","Product Name","Price"]}