Connect JTL with armincx: AI Customer Service Directly on Your JTL Data

What Can the JTL armincx Integration Do?

The first question we hear in almost every conversation with JTL users: do you actually have a working JTL integration? Behind that question lies a legitimate concern. JTL is known for being difficult to integrate. The API has limitations, standard tools often only connect superficially, and most helpdesk systems ignore JTL entirely.

armincx has built its own dedicated JTL integration. Custom-developed, because standard interfaces simply do not work with JTL. The AI accesses your orders, customer data, tracking numbers and invoices in JTL in real time. And it executes real actions: cancellations, returns, address changes and invoice delivery directly in your JTL backend.

This fundamentally sets armincx apart from Zendesk, Freshdesk or Gorgias. Those tools show you a Shopify panel in the ticket at best. JTL data? Not available. Your team copies order numbers from JTL into the reply draft and jumps between three to five tabs.

When a customer writes asking where their shipment is, your team currently has to look it up manually in JTL. armincx eliminates this manual lookup entirely.

AI Actions Based on JTL Data

The armincx AI recognizes the intent of a customer inquiry and executes the matching action directly in JTL. Fully automated, without manual intervention:

• "Where is my order?" The AI pulls order status and tracking number directly from JTL. When the DHL tracking number sits in JTL (rather than Shopify), armincx accesses JTL. WISMO inquiries account for 30-50% of all tickets at most shops. Without automation, your team answers this question dozens of times a day, every time with the same manual process: open JTL, search order number, check status, copy tracking link, write reply
• Cancellation: The AI recognizes the cancellation request, checks in JTL whether the order can still be cancelled and executes the cancellation. Without AI: five manual steps, three minutes per ticket
• Return: armincx creates the return in JTL, generates a return label and sends it via email or WhatsApp to the customer
• Invoice: The AI retrieves the invoice document directly from JTL and sends it to the customer. Invoice requests feel like small things, but in aggregate they eat hours per week
• Address change: The shipping address is updated by the AI in JTL, provided the order has not yet been shipped
• Custom fields: The AI populates JTL fields based on information from the customer inquiry. Example: writing the return reason as a custom field in JTL
• Order intake (B2B): Dealers order via WhatsApp, including photos or voice messages. The AI recognizes the order and creates it in JTL

Each action is configurable. You decide what the AI handles independently and what goes to an agent for approval.

The B2B Wholesale Use Case

One of the strongest use cases for the JTL integration involves B2B wholesalers. Some wholesalers receive up to 100 orders per day via WhatsApp. Currently, an employee manually enters every single order into JTL. That is several working hours per day spent on data entry.

With armincx, the AI recognizes orders from WhatsApp messages and creates them automatically in JTL. This works with photos too: a dealer sends a picture of their order list via WhatsApp, the AI reads the line items and creates the order in JTL. A full employee hour saved per order batch.

This is not a theoretical use case. These are real scenarios from sales conversations with DACH wholesalers who solve this exact problem manually today.

Why JTL Integration Is So Rare

JTL has a limited API. Standard tools cannot simply dock in like they do with Shopify (one-click installation). That is why most helpdesk systems offer no JTL integration. Zendesk, Gorgias, Freshdesk, Intercom. None of these tools can directly access JTL data or execute actions in JTL.

The Chatarmin team custom-built the JTL integration because the DACH market cannot be served without JTL connectivity. 89% of JTL customers in our sales conversations also use Shopify. The typical DACH stack looks like this: Shopify or Shopware as the shop frontend, JTL as the ERP backend, DHL as the shipping provider. armincx connects all three systems and pulls data from the correct backend.

When the tracking number sits in JTL (because your shipping runs through JTL rather than the Shopify DHL app), armincx pulls tracking from JTL. When order data sits in Shopify, armincx accesses Shopify. The AI automatically decides which system has the most current data.

Who Benefits From the JTL Integration?

The armincx JTL integration targets DACH mid-market retailers with 200+ tickets per month and JTL as their ERP system. Three typical profiles:

• Shopify + JTL retailers: You use Shopify as your shop frontend and JTL as your ERP. Your team jumps between both systems. armincx unifies data from both in one inbox. The AI automatically knows where each piece of information lives
• B2B wholesalers with WhatsApp orders: Your dealers order via WhatsApp. Currently someone types every order into JTL manually. The AI takes this over completely
• Teams with DHL tracking in JTL: When your DHL tracking is stored in JTL (not Shopify), other tools ignore this information. armincx pulls tracking directly from JTL

This multi-system reality is exactly what armincx solves. Your team no longer needs to search across three systems simultaneously.

Scale Without Hiring

Your JTL-based shop is growing but you do not want to proportionally expand the support team. With armincx you decouple growth from headcount.

The AI answers 70-95% of repetitive inquiries automatically. Instead of spending all day on WISMO questions and invoice requests, your team has capacity for complex complaints and cases that require real product expertise.

During seasonal peaks (Q4 brings 2-3x the normal ticket volume for many shops), the AI absorbs the extra load. You do not need to train temporary staff who leave after the peak. And you do not need to close support on Friday afternoon because nobody is left. The AI responds on Sunday evenings too, when customers shop from the couch.

5 to 15x cheaper than a manually handled ticket. That is the benchmark from over 450 e-commerce brands working with Chatarmin.

What Does the JTL Integration Cost?

armincx works on a flat-rate model. You pay no per-agent seat costs and no per-ticket costs. For JTL shops with growing volume this means: your costs stay predictable even when ticket volume triples in Q4.

Meta costs for WhatsApp messages are 11 cents per marketing message in Germany and around 5 cents in Austria and Switzerland (as of 2026). Service messages within the 24-hour window are free. WhatsApp generates 2 to 3x higher revenue per recipient than email. After deducting the Meta fee, you retain 139% higher net margin than via email.

armincx software pricing is not publicly communicated. In a demo we calculate your individual business case together based on ticket volume, number of channels and desired automation level.

Why armincx Over Zendesk or Gorgias?

The short answer: Zendesk and Gorgias have no JTL integration. Full stop.

The longer answer: Zendesk shows you Shopify data in a side panel at best. JTL data must be looked up manually. The Zendesk AI generates text suggestions but does not execute actions in JTL. Large Zendesk installations cost an additional EUR 20,000-40,000 in setup through implementation partners like Leafworks.

Gorgias charges per ticket and also has no JTL connectivity. Your team copies order numbers from JTL into Gorgias macros and jumps between tabs.

armincx was built for the DACH e-commerce market. The JTL integration was not an afterthought but a deliberate decision, because the German mid-market cannot be served without JTL connectivity. The AI executes actions directly in JTL, without tab switching, without copy-paste.

What Happens When the AI Cannot Answer?

The AI automatically recognizes when it cannot confidently answer an inquiry and escalates to a human agent. It delivers a prepared draft and all collected customer data. The agent only needs to review and send.

For incomplete inquiries (e.g. missing order number, no photos for a complaint), the AI first asks for the missing information before escalating. This saves your team the back-and-forth.

You configure the escalation rules yourself. Refunds under EUR 50 are handled by the AI independently. Above EUR 50 it creates a draft for approval. Complaints on high-value products go directly to a senior agent.

Onboarding and Setup

Onboarding for the JTL integration runs in four steps:

1. Set up JTL API access and establish the armincx connection. The Chatarmin team knows the JTL API quirks and handles the technical setup
2. Connect channels: Set up email forwarding, activate WhatsApp Business API, connect social media channels
3. Build knowledge base: Your existing macros, FAQ texts and product information are imported as a foundation for the AI. The Chatarmin team structures your knowledge so the AI can use it optimally
4. Configure AI workflows: Together with the Chatarmin team you define which actions the AI executes independently and which escalate to agents. WISMO, cancellation, returns and invoices are available as templates

The entire onboarding is guided personally by the Chatarmin team, in German. No external implementation partner. First automated responses go live within days.

If you have a multi-system setup (Shopify + JTL + DHL), the Chatarmin solution engineering team coordinates the integration of all systems. For JTL customers this is the norm, because JTL almost always runs alongside a shop system.

GDPR and Data Privacy

armincx hosts all data on servers in Germany. The AI processes customer data exclusively on EU infrastructure. A data processing agreement (DPA) is standard. The WhatsApp Business API runs GDPR-compliant via the official Meta Cloud API.

The AI accesses JTL data within the scope of customer service interactions. Data is not used for training purposes. Data separation between armincx and your JTL system is technically guaranteed.