Automate the import of your Products
Every time your catalog changes — new products, seasonal updates — someone has to update THRON. With the Product Import automation, that work disappears: THRON connects to your server, retrieves the updated file, and synchronizes the catalog recurrently and without manual intervention.
This guide walks you through the complete configuration of the flow, from server access to reading the results.
When to use this automation
| Scenario | Use Product Import if… |
|---|---|
| Initial Onboarding | You have an existing catalog on an external system and want to import it into THRON without copy-pasting |
| Periodic sync | Your ERP system updates product data regularly and you want to keep it aligned in THRON |
| Mass update | You have frequent variations on many products (availability, seasonal attributes) that you don't want to manage manually |
Before starting
Verify that you have these elements ready:
- Families and attributes configured in THRON — the automation populates existing attributes, it does not create them.
- FTP/SFTP/FTPS server access — host, port, username, password and source folder path.
- Mapping file — a CSV or XLSX that maps your file's columns to THRON product attributes.
- Permissions in THRON — you must be able to create and edit products.
Haven't configured Families and attributes yet? Start from Configure Product Families and Variations.
Configure the flow in 5 steps
Step 1 — Create the automation
- Go to Platform Settings → Flows & Automations → Automations.
- Click on New and select Product Import.
- Assign a clear and recognizable Name (e.g.,
Product Import – ERP Season SS26).
Step 2 — Connect the source server
Enter the connection parameters to the server from which THRON will read the files:
| Parameter | Description |
|---|---|
| Connection type |
FTP, FTPS or SFTP
|
| Host | Server address (e.g., ftp.company.com) |
| Port |
21 for FTP · 22 for SFTP · 990 for FTPS |
| Username / Password | Server access credentials |
| Read path | Remote folder path (e.g., /export/products/) |
Don't know which protocol to use? Choose SFTP (port 22): it is the safest and most supported by modern servers.
Step 3 — Upload the mapping file
The mapping file tells THRON how to read your file: which column corresponds to which product attribute.
File structure (CSV or XLSX, two columns):
| Source column | THRON attribute |
|---|---|
product_code |
sku |
product_name |
product_name |
price |
price |
| (your column) | (the THRON attribute code) |
How to upload it:
- Click on Upload mapping file and select your file.
- The system recognizes the columns automatically and shows a mapping summary.
- Check each mapping and correct any unmapped columns.
- For localized attributes, add the Locale (e.g.,
en-001). - Click Save mapping.
Warning: All files that the job will process must always have the same column structure. If the structure changes, update the mapping file first.
Step 4 — Set the error folder and scheduling
Error folder: select a dedicated folder in THRON. Every time a product is not imported correctly, the system drops an Excel file here with the details of the errors per row and attribute.
Scheduling — choose the frequency that best suits your flow:
| Frequency | Suitable for… |
|---|---|
| Every hour | Catalog with high change rate |
| Every 6 hours | Frequent updates during the workday |
| Every 12 hours | Morning/evening sync |
| Every day at 01:00 | Nightly update — the most common choice |
| Every day at 02:00 | Nightly alternative if you have other active jobs at 01:00 |
Step 5 — Monitor the results
Go to the Executions tab of the automation. For each execution you will find:
- Date and time of start and completion
-
Status:
SuccessorError - Downloadable report with the list of imported products and the error details per attribute and column
Recommended Configuration
If this is the first time configuring this automation, start here. You can always change the configuration later.
| Parameter | Recommended value | Why |
|---|---|---|
| Connection type | SFTP (port 22) | Secure, widely supported protocol |
| Scheduling | Every day at 01:00 | Runs at night, without impact on performance |
| Mapping file | Map only mandatory attributes | Validate the end-to-end flow, then add optional fields |
| Error folder | Dedicated folder, monitored by the team | Isolates errors and simplifies troubleshooting |
What happens at each execution
The automation performs these steps in sequence, completely automatically:
- Connection to the server with configured credentials
- Reading the CSV/XLSX file from the read path
- Automatic conversion of the file into the format compatible with the import job
- Application of the mapping columns → attributes
- Start of the import job in the THRON Products section
- Writing results: if successful, the file is moved to the "completed content" folder; in case of errors, a detailed Excel file is generated and placed in the error folder
Error Management
| Error | Probable cause | How to solve it |
|---|---|---|
| Connection error | Incorrect credentials, server unreachable or wrong port | Check host, port and credentials in the configuration |
| Invalid file | Missing columns, unsupported format or corrupted file | Check that the file is CSV or XLSX and respects the expected structure |
| Mapping error | Non-existent attribute or value not compatible with the field type | Update the mapping file and check values in the source file |
| Import error | Data not compliant with the structure of configured attributes | Open the execution report and read the details per row |
| Execution not completed | System error | Contact support@thron.com attaching the execution log |