The Recurring Import tool keeps Acenda in sync with a file on an external server, on a schedule you control. It's commonly used to pull catalog, inventory, or pricing updates from a PIM, ERP, or warehouse system without anyone re-uploading a file by hand.
Before you start: You'll need the SFTP connection details for the server where the file lives: your own, your PIM or ERP's, or a 3PL's. Acenda connects out to that server; it doesn't host an SFTP server for this feature. It also helps to know which Acenda field each column in your file should map to.
What data can I update with Recurring Imports?
Each Recurring Import keeps one of these models up to date:
Catalog: product titles, descriptions, attributes, and images.
Inventory Detail: stock levels by warehouse. See How to Bulk Update Inventory Using the Import Tool.
Channel Item Mapping: item-to-channel mappings.
SKU Presentation: channel SKU aliases.
Promotion: see How to Set Up Price Promotions.
Custom Pricing: see How to Update Pricing – Step-by-Step for Manual and Bulk Uploads.
Tracking: shipment tracking numbers.
How do I set up a new Recurring Import?
In the sidebar, under DATA TRANSFERS, click Imports.
Click Recurring Imports in the top right. A panel opens listing any recurring imports you've already set up.
Click New.
Under Import Settings, choose the Import Type (one of the models above), the Format (CSV or XLSX), and an Import Name your team will recognize. You can't change the format after saving, so delete and recreate the import if you need to switch later.
Under Connection & Schedule, enter the SFTP server details: Host (for example
sftp.example.com), Port (default 22), Username (YOUR_SFTP_USERNAME), and Password (YOUR_SFTP_PASSWORD). Then fill in Glob, the path and file name pattern Acenda should look for, for example/outbound/products/*.csv.Set the schedule: click a preset (Every 15 Minutes up through Every Year), or type a custom five-part cron expression (minute, hour, day, month, weekday). crontab.guru can help you build one. Schedules run on Acenda's server clock (UTC), not your local time zone.
Click Save to move on to field mapping.
How do I map my data fields?
After the connection settings are saved, click Validate Headers/Connection. Acenda connects to your SFTP server, confirms a file matching your Glob pattern is there, and reads its column headers. You can't add or edit mappings until this check succeeds.
Once it passes, add your mappings in one of two ways:
Add Headers (N): bulk-adds every column from your file that isn't mapped yet.
Add Rule: adds a single mapping by hand, for a Static String or Logic / Rule value, or to map a column with different settings.
For each row, pick a Mapping Type, fill in the source, and choose the Target Acenda Attribute. If the attribute doesn't exist yet, click the + button next to it to create a custom field without leaving the page. For more on how columns and mapping work, see Using the Import Feature: How to Import Product Data into Acenda.
What are the different mapping types?
Type | What it does | Example |
File Header | Maps a column from your file directly to an Acenda field. | Map brand_column to fields.brand |
Static String | Applies one fixed value to every row. | Set the value to Acme |
Logic / Rule | Runs a small template to transform the source value. |
|
Note: Logic / Rule mappings use Go template syntax, not Twig. If a source column name has a dot in it, like variant.name, replace the dot with an underscore: {{ .variant_name }}. An AI assistant can help you draft a template if you describe what you want it to do.
Tip: Recurring Imports always run like the Overwrite option in a manual import: matching records are updated, new ones are created, and existing values are kept for any column you don't map. For a Catalog import, a blank value mapped to a custom field clears that field (a blank value mapped to a standard field is left alone). Leave a column unmapped if you want its current value left untouched.
Finishing setup
Click Save. Your import now runs automatically at its next scheduled time. If the file at your Glob path is identical to the one from the last successful run, Acenda skips that run instead of re-importing an unchanged file.
Editing or deleting a Recurring Import
Open Recurring Imports from the Imports page and click the pencil icon next to an entry to edit its settings, connection, schedule, or field mapping.
There's no pause switch today. To stop a recurring import, open it and click Delete; you can set it up again later.
Where do I see run history and errors?
There's no separate history view for recurring imports. Each run creates a normal import record, so it appears in the DATA TRANSFERS > Imports list alongside manual uploads, with the same file details, status, and View Errors link. The list doesn't label which recurring import created a row, so match it by file name and run time.
No one is notified automatically when a run fails. If a feed looks stale, check the Imports list for a failed or missing run.
Troubleshooting & FAQ
Validate Headers/Connection fails: double-check Host, Port, Username, and Password, and confirm a file matching your Glob pattern exists on the server right now. Upload one and try again.
I can't edit field mappings: mapping stays locked until a Validate Headers/Connection check succeeds.
My import ran but nothing changed: first check whether the file is identical to the last successful run's file, since unchanged files are skipped. If it's different, check that the identifying column (like SKU) and each Target Acenda Attribute are mapped correctly.
My import ran at an unexpected time: schedules use Acenda's server clock (UTC), so convert from your local time when you set the cron expression. If runs still land at the wrong hour, contact Acenda Support.
Recurring Imports vs. Scheduled Exports: Recurring Imports bring a file in. DATA TRANSFERS > Scheduled Exports sends export data out to your SFTP server on a schedule (reports can't be scheduled this way). See Using the Export Feature: How to Export Data from Acenda.
Related articles
Still stuck? Contact Acenda Support and tell us the Import Name and any error you see in the Imports list.