Official import tool
Import is performed through JTL-Ameise without direct database writes. Import formats and field mappings must be supported by the installed JTL-Wawi version; universal version compatibility is not guaranteed.
Amazon product data ready for JTL-Wawi — without weeks of manual work
WDEPOS reconstructs your existing Amazon product structures and prepares descriptions, images, parent-child variations, attributes and product features for import via JTL-Ameise.
Check an Amazon file for freeContact usOften ready for import the same day
Your prepared Amazon product data is typically ready for import via JTL-Ameise within one week, often even on the same day.
Actual processing time depends on the volume, completeness and quality of the source data. This refers to delivery of the prepared import files, not a completed import into JTL-Wawi.
Check an Amazon file for freeStructured category import and review with JTL-Ameise
WDEPOS prepares a practical JTL-Wawi category tree based on Amazon categories. Products are intended to be imported as inactive first, allowing descriptions, images, variations, attributes and categories to be reviewed before activation.
Typical import duration: 5–10 hours
The actual JTL-Ameise import typically takes about 5 to 10 hours. The number of product images is a major factor; item volume, system performance and configuration also matter.
New and existing JTL-Wawi systems
A new, empty JTL-Wawi is ideal, but additional imports into an existing system are also possible. The resulting category tree can be adjusted later in JTL-Wawi.
Review before activation
Products are imported as inactive when correctly configured and verified. Newly imported records may be corrected or removed after checking dependencies. This is a controlled, lower-risk process—not risk-free. Back up data and review existing product and marketplace links first.
Check all product mappings and synchronization settings before the first Amazon sync.
Everything your product catalog needs
Complete product data
SKUs, titles, descriptions, brands, manufacturers and product categories.
Images and local folders
Structured image assignment and a local product archive.
Parent-child variations
Reconstruct existing variant families and validate their relationships.
Attributes and features
Extract existing Amazon attributes and map suitable data to JTL attributes and product features.
Less manual work
Manually entering product data in JTL can take weeks and cause significant costs, depending on catalog size.
JTL-Ameise import
Prepare import files without directly accessing the JTL-Wawi database.
The quality of the results depends on the available Amazon source data. The first JTL–Amazon synchronization must be checked carefully.
How WDEPOS works
1. Request your Amazon data
Obtain Category Listings Reports (reverse feeds) through Seller Central or Amazon support, where available.
2. Analyze the files
We check product completeness, images, variants, attributes and features.
3. Prepare the JTL import
We structure the existing data for import through JTL-Ameise.
4. Validate before syncing
Review data and parent-child relationships before the first Amazon synchronization.
Local product management
Build a reusable local structure for products, images and variations. Generating new Amazon flat files from locally maintained data is planned, not yet available.
From Amazon to multichannel commerce
JTL-Wawi can serve as the hub for other marketplaces and your own JTL-Shop. Availability and costs depend on the respective integrations. WDEPOS prepares the initial product data; it does not connect marketplaces itself.