Skip to content
Illustration: Product catalog with separate export folders

Interfaces & Data Exports in JTL-Shop 5

Interfaces

JTL-Shop 5 enables structured data exchange with marketplaces, price comparison engines, and external services via flexible interfaces and export formats. Management is handled directly via the shop backend in combination with the central ERP system JTL-Wawi.

Key takeawayCentralised Data Distribution to External Channels

Using integrated export formats, the internal task scheduler, and connected plugins, JTL-Shop 5 automatically supplies price comparison engines, platforms, and feed recipients with consistent product data.

Interface Architecture and System Integration in JTL-Shop 5

JTL-Shop 5 acts primarily as the frontend within the e-commerce setup, supplied with inventory, item, and order data via standard JTL-Wawi synchronisation. This close coupling ensures that stock levels, prices, and product master data remain synchronised across all channels.

Depending on the installed shop version and configured plugins, various interface technologies are available for third-party systems. Alongside the progressively expanded REST API, the integrated export engine forms the backbone for connecting external marketing and sales channels.

Supplementary interfaces to payment providers, shipping carriers, and niche marketplaces are obtained via the JTL Extension Store. This enables modular functional expansion without altering the core architecture of the online shop.

Export Formats and Automated Generation via Task Scheduler

To reliably supply price comparison engines and partner networks with product data, JTL-Shop 5 features a powerful export engine. Formats for common price search engines are pre-configured as templates in the system and can be adapted to project-specific requirements as needed.

The generation of extensive export files is managed via the integrated task scheduler (cron job system). Administrators can define execution intervals so that feeds are re-generated without manual intervention, for instance overnight or during low-traffic periods.

This automated generation ensures that price comparison services consistently receive up-to-date pricing and availability data, minimising the risk of outdated information and wasted ad clicks.

Schematic illustration

Workflow of Export and Interface Generation in JTL-Shop 5

From master data synchronisation to deployment for external portals

JTL-Shopexport formats
  • Data Synchronisation with JTL-Wawi

    Products, stock levels, and prices are transferred from JTL-Wawi to the shop database.

  • Configuration of the Export Format

    Field mappings, attribute filters, header rows, and data rows are defined in the backend.

  • Control via Task Scheduler

    An execution interval is configured to schedule the export as a cron job.

  • File Generation on the Server

    JTL-Shop 5 generates the CSV or XML file within the web server's file system.

  • Retrieval by Third-Party Systems

    Price comparison engines or external platforms fetch the generated file via a static URL.

Product Data Export to Google Merchant Center and Marketplaces

Specialised plugins and export templates are available for marketing channels such as Google Shopping (historically known as Google Base). These make it possible to export mandatory attributes—such as GTIN, brand, condition, and Google product categories—as well as optional functional attributes from shop products into a structured XML file.

The system also provides interface formats for online platforms and sales portals such as Yatego. In addition to standard items, these account for variation combinations (child items) and real-time stock levels to prevent discrepancies between the shop and external channels.

These feeds are likewise linked to the task scheduler to guarantee daily updates. Depending on the plugin version, advanced attribute mappings are configured directly via the backend dialogue.

Price Comparison Services and shopinfo.xml via ELMAR Formats

Historically established industry standards, such as the ELMAR format (Elektronischer Markt) and shopinfo.xml, remain supported by JTL-Shop 5. These formats historically served numerous price comparison engines and directories as a unified basis for ingesting product data.

Portals such as Idealo, Billiger.de, Schottenland, and specialist niche directories leverage this structured data provision. The shop generates corresponding metadata and product listings in the required format to secure optimal visibility across aggregators.

While modern price comparison platforms increasingly demand proprietary CSV or API structures, the ELMAR-compatible format still provides broad coverage for traditional portals and web directories.

Automated RSS Feeds for Special Offers and Content

Alongside sales-oriented marketplace exports, JTL-Shop 5 features built-in functionality for generating RSS feeds. These feeds are updated automatically by the system and aggregate various content areas.

Feeds can output new product arrivals, blog posts, news announcements, and recent customer reviews. External feed readers, newsletter tools, or third-party applications can subscribe to these data streams directly.

As a result, the RSS feed functions as a lightweight push interface to keep existing customers and content aggregators up to date on shop news without complex integration logic.

Terms explained

JTL Task Scheduler
An internal shop system for the scheduled background execution of maintenance and export tasks via cron jobs.
shopinfo.xml / ELMAR
A legacy XML standard format for price comparison portals and directories to retrieve shop and product metadata.
Google Merchant Center Feed
A structured data feed (commonly XML or TSV) that delivers product information in compliance with Google specifications for shopping ads.
JTL-Wawi Synchronisation
The interface between JTL-Wawi and JTL-Shop for synchronising master data, orders, and stock levels.

Good to know: requirements & limits

  • Large product catalogues with tens of thousands of items require balanced server resources (memory limit, script execution time) for export routines.
  • Certain marketplace and portal plugins require separate licences via the JTL Extension Store, as well as regular compatibility checks during shop updates.
  • Interface formats such as 'Google Base' or 'ELMAR' are partly based on legacy standards; target platforms may require alternative or modernised specifications.
  • The feature set of the JTL-Shop 5 REST API is version-dependent and undergoing continuous development.

Contact

Let’s discuss your project.

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