Quick search:eBay DataTransfer JTL-Worker PayPal

JTL-Links

Thank you for using the English version of the JTL-Guide!
We are currently still building up the English documentation; not all sections have been translated yet. Please note that there may still be German screenshots or links to German pages even on pages that have already been translated. This guide mostly addresses English speaking users in Germany.

Note: On 1 September 2024, JTL introduced new editions that bundle most of the previous individual services into different packages. In order for you to continue working as smoothly as possible, existing customers were automatically switched to the package configuration that best matched their existing contract. The individual packages differ in terms of limitations and/or range of functions. Therefore, some of the features described in the JTL-Guide may not be available to you as part of your booked JTL edition. You can change your package configuration in your JTL customer account. Find out more about the new editions and packages here. Check our FAQ for frequently asked questions about the product editions.

Contents

Your task/initial situation
Structure of the CSV file
Doing an import

Importing deliveries via data exchange

Your task/initial situation

You have exported data about inbound deliveries from a third-party system and would now like to import it into the JTL-Fulfilment Network so that you can then transfer it to your fulfilment service provider.

Structure of the CSV file

Data that you export from third-party systems must be in CSV format. The CSV file can contain the following columns:

Columns für inbounds

Name in FFN

Description

Mandatory field

warehouse_id

Identification number of the warehouse of your fulfilment service provider. Your service provider will give you this ID. You can also find the warehouse ID from which the sales order is to be sent in the table https://fulfillment.jtl-software.com/merchant/warehouses

Yes

merchant_inbound_number

An inbound ID that can be freely assigned as necessary. For each inbound in your system, there is a unique number. If coming from external systems, this might for example be a stock transfer number.

Yes

item_quantity

The quantity of the respective items in the inbound.

Yes

item_merchant_sku

Merchant SKU of the item (For correct allocation, the SKU must exist in the JTL-Fulfillment Network. For this, the items must have been created beforehand in JTL-FFN.)

item_jfsku

The JFSKU is an SKU that is automatically generated by JTL-FFN for each item of a merchant that is sent to the network. After creating the items in the JTL-Fulfillment Network, you will find this number in the item overview and detailed view. The JFSKU can be used as a unique identifier and as an alternative to the normal SKU, but is not mandatory.

item_supplier_sku

SKU of the item at the supplier end

item_supplier_product_name

SKU of the item at the supplier

item_note

Comment on the item, e.g. “This item contains hazardous substances.”

note

Comment about inbound

purchase_order_number

Sales order ID

external_inbound_number

External sales order ID

status

Status with which the sales order is to be imported into the JTL-Fulfillment Network. You can assign a fixed default value to the status in the import template.

attribute_type

Type of the attribute. This is already defined as the default value in the inbound template. Possible types are “String”, “Date”, “Decimal”, “Boolean” and “Integer”. A value is not required in this column. Use the attributes to pass extended information.

attribute_key

Name of the attribute

attribute_value

Value of the attribute

Doing an import

Create an export of your inbound data in CSV format.
Create an import template for the CSV import based on the table shown above. Please read Creating import templates in the portal to learn how to create an import template for inbound data. Above all, make sure that all mandatory fields are linked to a column in your CSV file or have a default value.
In the FFN Portal (Go to JTL-Fulfillment Network), go to Data exchange > Import.
Click on the Direct import button. The dialogue Direct import opens.

Direct import into the JTL-Fulfillment Network Portal

Under Import template, select the template you created for this inbound import.
Under Select import file, click Browse and select your CSV file.
Select Start import. The import is now carried out. You will then find your inbounds here: My operations > Inbounds.

Name	Duration	Purpose
_ga	2 years	Used to differentiate between users.
_gid	24 hours	Used to differentiate between users.
_gat	1 minute	Used to throttle the request rate. When Google Analytics is provided via the Google Tag Manager, this cookie is named _dc_gtm_.
AMP_TOKEN	30 seconds up to 1 year	Contains a token that can be used to retrieve a client ID from the AMP client ID service. Other possible values indicate an opt-out, an inflight request, or an error while retrieving a client ID from the AMP client ID service.
_gac_	90 days	Contains campaign-related information for the user. If you have linked your Google Analytics and Google Ads accounts, this cookie will be read by the conversion tags of the Google Ads website, unless you choose not to.

Name	Duration	Purpose
_pk_id	12 months	Used to store details about the user, e.g. the unique visitor ID
_pk_ref	6 months	Used to store the attribution information. The referrer that was originally used to access the website
_pk_ses	Until end of session	Short-lived cookies that cache data for the visit
_pk_testcookie	Until end of session	Is created to check if the browser supports the visitor's cookie
_privacy	Unlimited	Saves the desired privacy settings