Why variant families matter
Amazon parent-child relationships, variation themes and child SKUs must be checked before JTL import. Incorrect mappings can disrupt offers during the first synchronization.
Parent-child variations
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 usWhat we prepare
Parent and child records, variation values and import-ready structures based on the data actually available in the seller files.
Practical guidance for Amazon product migration
Example: a T-shirt in sizes and colors
One Amazon parent listing may group a T-shirt available in three sizes and two colors. Its six purchasable child SKUs need clear parent references and variation values. A simple offer export may not preserve the complete family structure.
Fields that need checking
Parent SKU, child SKU, relationship type, variation theme, and values such as size or color should be consistent. Missing parent references and inconsistent labels require review before import.
Before the first Amazon synchronization
Import the prepared data using JTL-Ameise, then verify SKU assignments, variation combinations, images, and existing Amazon offers in JTL-Wawi. WDEPOS does not write directly to the JTL database.
When a preflight check helps
Complex variation families with usable descriptions, brands, manufacturer details, and image references are promising candidates. If most content is missing, a simpler standard import may be more suitable.
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.