This guide explains how to create and manage an import job using an FTP client connection in DJUST back office.

✅ Prerequisites

Before configuring a job, make sure you have:

• An active FTP connection. See How to configure an FTP client .
• A file path on the FTP server where import files are stored.
• (Optional) An outbound directory where processed files can be moved after import.

💡

Folder Path Name

The path must include the full directory and filename.

Example: folder/sub-folder/import-products.csv

⚠️

FTP Users Rights

Ensure the FTP user has sufficient read/write access rights to the target folders.

⚙️ FTP Import Job Configuration

Creation

To configure an import job from the DJUST back office:

Step 1 – Access the Data Hub

1. Go to the Data Hub section.
2. Click + Create a new job.
3. Select Import.

Step 2 – Job configuration

Fill in the left side of the form:

• Job name (must be unique)
• Objects: choose the object you want to import (e.g., Products, Offers, Orders).
• Client type: select your type of client connection (SFTP in this case)
• Client: select your FTP client connection
• Bulk import toggle (enable if importing multiple files)- If enabled, define:
  • Inbound directory (folder containing incoming CSVs)
  • Outbound directory (folder where processed files will be moved)
• If not using bulk, define a file path (including file name)
• CSV delimiter (required): select the delimiter used in your CSV file (, or ;). This field has no default value — you must explicitly choose the correct delimiter before saving the job. If the selected delimiter does not match the actual file format, the import may succeed without any data being integrated.
• Scheduler: choose frequency (:warning: displayed time is in UTC)

Multi-store selector (multi-store tenants only)

For tenants with multiple stores and compatible job types (isMultiStore = true), a multi-store selector is available in the job configuration form. It allows you to define the target stores to which imported entities will be automatically assigned.

• The selector appears only for multi-store compatible job types on multi-store tenants.
• The field is optional: if no store is selected, the store must be defined in the import file (default behavior).
• If stores are configured on the job and in the import file, the job configuration takes precedence.
• A "Select all / Deselect all" button is available for convenience.

⚠️

The NAVIGATION_CATEGORY job type retains its existing behavior with a single-store + store view selector.

Fill in the right side of the form:

• Map your CSV columns to DJUST field names.

For more details on how to configure mappings for each data entity, refer to this page: Data Hub Mapping Overview.

Step 3 – Save

• Click Create to finalize the job creation

💡

Bulk Import Mode

Bulk import mode processes multiple files in a folder automatically.

• Files are retrieved from the inbound directory
• Each file is imported one by one
• Once processed, files are moved to the outbound directory

Manage and Update

Once your job is created, you can manage it from the Data Hub interface:

• Go to the Data Hub > Import section.
• Find the job in the list.
• Click the ⚙️ icon.

Update

• Change any configuration: client, file path, delimiter, scheduler, mapping
• Click Save to apply changes

Activate, Disable or Delete a FTP Import Job

• Click More actions
• Choose:
  • Activate: to enable the job
  • Disable: to pause the job without deleting
  • Delete: to permanently remove the job (⚠️ irreversible)

📌

Best Practices

✔️ Use clear and unique job names

✔️ Always validate your CSV file format and delimiter

✔️ Test jobs in a test environment before live deployment