Catalog import

Import your catalog into Telden

Use the import workflow to turn a spreadsheet into structured SKU records. A clean file, careful column mapping, and a short review pass prevent most import issues.

Import does not approve compliance data

The import workflow creates and updates product records from your file. It does not decide whether a product is compliant. Review required fields, supplier evidence, and warnings before publishing or exporting records.

Use a supported file type

Telden supports CSV, TSV, XLSX, and ODS catalog files. Use one row per product and keep header names stable, such as SKU, product name, category, brand, manufacturer, importer, supplier, GTIN, and description. Remove totals, merged cells, hidden notes, and extra title rows before upload.

For the first import, test 10 to 50 products. After the mapping looks right, upload the full catalog with the same headers.

Map columns to product fields

After upload, Telden detects headers and suggests mappings. Check every required field before continuing: SKU or product code, product name, category, and the supplier or economic operator details you already have. Leave unrelated columns unmapped instead of forcing them into a field that almost matches.

If a supplier column contains several values in one cell, split it in your spreadsheet first. Clean source columns are easier to review later.

Choose encoding and delimiter settings

CSV and TSV files may use different encodings and separators. If accents, umlauts, currency symbols, or quotes look wrong in the preview, switch encoding or delimiter before importing. Semicolon-delimited CSVs are common in European spreadsheet exports.

A correct preview matters more than the file extension. Do not continue while product names or supplier addresses show broken characters.

Fix common import errors

Most import errors come from duplicate SKUs, empty required cells, invalid GTIN values, inconsistent column counts, unsupported formulas, or rows that mix products and notes. Fix the source file, upload it again, and confirm that the preview row count matches your expectation.

When Telden flags unmapped columns, decide whether they are useful compliance data before ignoring them. Some fields may belong in supplier evidence rather than the product catalog.

Review the records after import

When the import completes, open Products to spot-check new SKUs and open Review to work through missing fields or conflicts. Then upload supplier evidence so Telden can extract provenance-backed facts for each product.

Do not export immediately after a large import. First verify a sample of products, attach evidence, and resolve blockers in the review queue.