Jtl

FAQ

Solutions to common questions and issues when using Clerk with JTL

Running into issues with your JTL integration? This FAQ covers the most common problems and their solutions, from sync errors to missing products.

Common sync errors #

When importing data with the JTL plugin, your webshop’s generated feed is responsible for sending product, category, and sales data to Clerk.

However, in some cases, the feed’s configuration might stop the Importer from getting access, causing an error in Data Sync.

Below is a list of the most common errors and how to fix them.

This error happens if your server blocks the importer from accessing it.

In most cases, you simply need to whitelist the importer’s IP address to give it access.

The latest IP address can be found here.

Also check your public key, private key, and import URL are correct for the store you are operating within my.clerk.io.

What if I have already whitelisted but the same error still occurs?

There are a few instances when you have whitelisted the importer’s IP address, and the error still persists.

In these cases, we recommend you look into these parts:

The authentication part of the body may be removed from the request from the shop’s server.
Rate limit for the server in regards to Cloudflare.

This error happens if your webshop’s generated feed is no longer available.

This is solved by generating another feed URL.

Copy and paste the URL and insert it in your data sync settings in the store in your my.clerk.io account.

This usually happens when all products are not included in the generated feed.

Sometimes it is due to the host and capacity of the webshop hitting a maximum threshold for memory when a data feed is generated.

You will most likely get an error like this:

Fatal Error: Allowed memory size of X bytes exhausted (tried to allocate X bytes) in /FeedGenerator.php on line XXX.

The simple way to solve this would be to increase the memory cap for the host of the webshop.

This error occurs when the customer group within a feed no longer exists in the shop.

To fix the error, you can go through the following options:

First, uninstall the plugin. Note that the plugin’s own files should not be removed.
Reinstall the plugin.
Set up the plugin again and create the necessary feeds.
Enter the data in Clerk.

Only proceed if you have expertise in database modifications!

Here, you adjust the values directly in the database.
The ID in the database should be set to the value mentioned in the error message.