JTL
Items 1 - 17 of 17
“Price on request” is right — except for the handful of articles that really should be free: samples, add-ons, service items. Customers simply put those in the cart from now on, while the rest of the range stays on application.
Not every article in your range is one you ship yourself. For the ones that sit with a partner, the product page sends the customer straight there — and at the end of the month you can see which of them anyone actually clicked. No IP addresses, no cookie of its own.
If you sell age-restricted goods you have to ask before the visitor sees the range — and JTL-Shop brings nothing for it. This check sits in front of the shop, looks like your shop, and can be limited to the categories that actually need it.
In image search the file name counts, and your product shots are called IMG_0042.jpg. Wawi holds exactly one name; for every further image there is no field. Here each one gets its own — and the next sync no longer wipes it.
Between “I need that again” and a placed order there are normally five clicks. With a link from your newsletter, a QR code on the shelf or a support mail, the article is already in the cart by the time the customer arrives.
“Where is my file?” — everyone selling digital goods gets that mail, and it comes from customers who have not even ordered yet. The downloads tab now says for itself that the file appears in the customer account after the purchase. One question less, every day.
Not because the store is bad — it just sits where you keep clicking when you move quickly through the backend. Afterwards the entry is gone or sits where you want it, and nothing in your shop's files has changed.
The backup app for JTL databases enables simple and automated backup of your data. Schedule backups at hourly intervals or at fixed times on different days and save them on two different drives.
Anyone selling software knows what follows every order: generate a key, write the mail, hope nothing was missed. With your own LicenseManager app behind it, the shop does that the moment the order arrives - your customer has their licence before they think to ask.
A shop that should not be found yet: staging, a maintenance window, the weeks before go-live. One switch closes both doors - meta tag and robots.txt - and opens them again the moment you are ready.
Your best salespeople are not on the payroll: they are customers who pass the word on. To make that more than a thank-you, every partner gets a code, every new customer a discount — and you get a statement at the end of the month that you did not have to assemble yourself.
Three plugins, one goal: getting your JTL-Shop found in Google and by AI assistants. Structured data for rich results, SEO image names for image search and Web MCP so ChatGPT and co. read your catalogue correctly.
Spam in contact and registration forms costs you a few minutes of clearing up every day. This check runs on your own server: bots do not get through, customers barely notice it, and your visitors' data goes to nobody else.
Analytics in a shop rarely fails on the tool, it fails on consent: codes pasted into the template run without agreement — and are gone after the next template update. Here Matomo, GA4 and the Tag Manager register properly with the consent manager and only load afterwards.
Anyone seeing your shop for the first time has no idea whether anybody buys there — and that is what costs you the first order. A small notice shows what was ordered recently. From real orders, not from a list you had to invent.
Google, and by now ChatGPT too, only read a shop as well as it is marked up. Without markup, price, availability and reviews stay invisible to both. Afterwards your range is machine-readable — without you having to touch the template.
Your shop becomes usable by AI assistants: they search the catalogue, read product data, fill the cart and show a signed-in customer their own orders. Nothing is ordered or paid for — checkout stays with the human.
Items 1 - 17 of 17