Skip to content
Illustration: Data tiles streaming between two servers with product photos

Data management with JTL-Ameise

Dynamic Import/Export

With JTL-Ameise, you can transfer data in bulk and maintain existing records in JTL-Wawi. Imports and exports use CSV files. Templates make recurring tasks easier; bulk changes require careful preparation and an up-to-date backup.

Key takeawayWorking with large amounts of data takes preparation

With JTL-Ameise, you can exchange data through CSV files and update existing data in JTL-Wawi in bulk. Reliable mappings, an up-to-date backup and a small test run help you identify import errors early.

What JTL-Ameise does

With JTL-Ameise, you can transfer and edit large datasets in bulk rather than handling each record individually. This can reduce manual work. How much time you save depends in part on the quality and structure of your source data. This import and export tool for JTL-Wawi uses CSV files to exchange data. Typical data types include product data, product images and prices.

Importing brings information from a file into your inventory management system. Exporting makes data from JTL-Wawi available for further processing or sharing. CSV stores tables as text: each row contains a record, and the columns contain the individual details. Image files are not embedded; instead, CSV files can contain image references. Before planning your workflow, check which data types and fields JTL-Ameise supports in the version you use.

Templates for recurring imports and exports

Templates let you reuse prepared mappings for recurring tasks. This is particularly helpful when your files always follow the same structure. JTL-Ameise uses templates: during a CSV import, the mapping determines which file column corresponds to which data field. For example, a product name must not accidentally end up in the price field. The template provides a reusable starting point based on the columns and contents of the file used to create it.

Agree on a consistent file structure for recurring imports and exports, and keep a clear record of any changes. Descriptive column headings make mapping easier; all required fields must be completed for the relevant import. Before reusing a template, check whether any columns have been added, removed or given a different meaning—a template does not replace this check. For exports, the required information and the recipient's processing needs determine the file structure.

  • Templates map CSV columns to the corresponding data fields
  • Maintain a defined file structure and document changes
  • Check columns and complete required fields before each reuse

Bulk changes to existing data

With JTL-Ameise, you can update existing data in bulk. These bulk changes do not create new records; they make targeted changes to existing data. Decide in advance which records and fields you want to edit. Also identify what should remain unchanged: include that data in the scope of the changes only if there is a specific reason to do so. This keeps the planned changes clear, even when working with large files.

Bulk changes help you maintain your product range and the underlying data for different sales channels, such as online shops and marketplaces. However, they do not automatically mean that data is transferred directly to every connected sales channel. For updates, each file row must map unambiguously to the intended existing record. Before importing, check that the identifiers used are complete and unique, and confirm how empty fields are handled when updating existing information.

Schematic illustration

An Ameise import in five steps

The workflow combines technical preparation with a limited test run and a subsequent check of the results.

step_01Back up your data

Back up your current data and confirm how to restore it if needed.

step_02Prepare the file

Check the CSV structure, character set, delimiter, required fields and the content you want to import.

step_03Template and mapping

Use a template that matches the file and map each column to the intended data field.

step_04Test import

Start by importing a few selected records as a test before processing the full dataset.

step_05Check the results

Compare the updated records with the intended results and investigate any discrepancies.

Taking over supplier and manufacturer data

Data from suppliers and manufacturers can make recurring data maintenance easier and faster, provided the supplied files have a reliable structure. Prepare the data for JTL-Wawi and process it using suitable import templates. Agree with the data provider on which information is included, what it means and how to interpret different terms or spellings. This helps you avoid treating information with different business meanings as equivalent.

The character set and delimiter determine how external CSV files are read: the character set affects how umlauts and special characters are displayed, while the delimiter marks the boundary between columns. Commas and semicolons are common delimiters. Decimal and date formats must also be unambiguous. Text fields that contain delimiters or line breaks must be properly enclosed or escaped. Correct the file before importing if the columns are visibly misaligned or characters are displayed incorrectly.

Prior knowledge, backups and test runs

An up-to-date backup and a sound understanding of the task are essential preparations whenever you use JTL-Ameise. Back up your data before each use, especially before changing existing data. Incorrect use can cause serious data errors. Before importing, you therefore need to understand the affected data and assess the consequences of your planned changes. Preparation also includes knowing how to restore your backup. Having a backup file alone is not enough if you do not know how to restore it when something goes wrong.

A test import with a few selected records helps you assess the results before processing a larger dataset. This limited trial run is a practical precaution, not a dedicated product feature assumed here. Afterwards, check the affected records in JTL-Wawi and compare them with the intended results. Only proceed with the larger dataset once you have verified the results. WAWIHEROES shows you what Ameise can do and discusses the knowledge and preparation required for your specific use case.

  • Back up data before each use and know how to restore it
  • Assess affected data and the impact of planned changes before importing
  • Run a test import with a few records and check the results

Terms explained

CSV
CSV is a text-based file format that represents tabular data using rows and delimited fields.
Column mapping
Column mapping determines which data field receives the contents of a particular file column.
Required field
A required field contains information that must be provided for the relevant import.
Character set
The character set determines how text characters are stored and interpreted when a file is read.
Delimiter
A delimiter marks the boundary between two fields in a CSV file.

Good to know: requirements & limits

  • The available import and export options and data fields must be compatible with the JTL-Wawi version in use.
  • A template remains usable only if the file structure and the meaning of its contents still match.
  • Updates to existing data require an unambiguous mapping to the intended records.
  • A successful test with a few records does not rule out errors elsewhere in the file.
  • Incorrect use can cause serious data errors, so prior knowledge and an up-to-date backup are essential.

Contact

Let’s discuss your project.

Free initial consultation on JTL-Wawi, JTL-Shop, JTL-WMS and hosting.