How to Control File Names for FTP/SFTP Exports in Shopware 6

The following article explains how to use custom names for export files in Shopware 6 when transferring data via FTP/SFTP. We not only explain the functionality behind the new feature of the Improved, Import, Export & Mass Actions app but also describe practical use cases and the benefits Custom FTP/SFTP Export File Name introduces.

The Story Behind File Names for FTP/SFTP Export in Shopware 6

Automating data exports in Shopware 6 presents a challenge: the default platform restricts you to manual file downloads. It does not natively support automated exports to remote servers via FTP or SFTP.

The Improved Import, Export & Mass Actions app bridges this gap, enabling you to send product feeds, stock levels, and other data directly to external servers.

However, connectivity is only half the battle. External systems — like ERPs, BI tools, or supplier portals — often require strict file naming conventions. If your automation sends stock_2025-10-12_1400.csv when the receiving system expects stock.csv, the integration fails.

The Custom FTP/SFTP Export File Name feature gives you full control over how your files are labeled and stored on remote servers. This guide explains how to use this feature to choose between maintaining a historical archive or a single, always-up-to-date file.

Static vs. Dynamic Filenames: Which Strategy Fits Your Workflow?

The Custom FTP/SFTP Export File Name feature controls how the app writes files to your FTP or SFTP server. Depending on your integration needs, you can choose between two distinct naming strategies:

How Custom Naming Automation Works

Option A: Dynamic Naming (History Mode)

If you leave the “Custom File Name” field empty, the app uses a dynamic naming logic.

• Logic: The system generates a unique name for every single export run, typically appending the date and time to the filename.
• Storage Impact: No files are ever deleted. If you run the export daily for a year, you will have 365 distinct files on your FTP server.
• Use Case: Perfect for “paper trails.” If you need to prove what your stock level was exactly three weeks ago, you can simply locate and download that specific date’s file.

Option B: Static Naming (Overwrite Mode)

If you enter a specific name in the field, the app switches to “Overwrite” mode.

• Logic: The app uses exactly the name you provide. It does not append dates or times.
• Storage Impact: Every time the export runs, the system looks for the file with that name on the remote server and overwrites it with the new data.
• Use Case: Essential for rigid integrations. If your ERP script is programmed to fetch products_latest.xml every night at 3 AM, this mode ensures that products_latest.xml always contains the freshest data, without your IT team needing to write complex scripts to find the “newest” file in a folder of thousands.

Step-by-Step: Configuring Custom File Names for FTP

Setting this up takes seconds but saves hours of maintenance.

1. Open the Improved Import, Export & Mass Actions app.
2. Navigate to your Export Job.
3. Go to Export Destination → FTP/SFTP Settings.
4. Locate the File Name field.

Configuration Rules

• To Enable Overwriting: Enter the full name including the extension.
  • Correct: daily_stock.csv, orders.json, feed.xml
  • Incorrect: daily_stock (Missing the extension may cause the file to be unreadable by receiving systems).
• To Enable History: Simply delete the text and leave the field empty. The system will revert to auto-generating unique timestamped names immediately.

Why You Need Static Filenames for Integrations

Why should you switch from the default timestamped format to a custom static name?

• Seamless Integration: External tools (like accounting software or supplier portals) no longer need “wildcard” logic to guess the filename. They just read the same file path every time.
• Server Hygiene: Prevents your FTP server from filling up with thousands of obsolete files that waste storage space and clutter your directories.
• Reduced Maintenance: Eliminates the need for manual “clean-up” scripts or cron jobs that delete old files from the server.

Conclusion: Automating Your Data Pipeline

The ability to export to FTP/SFTP is a game-changer for Shopware merchants, but the ability to control how those files are delivered is what makes true automation possible.

By utilizing the Custom Export File Name feature, you transform your export jobs from simple data dumps into reliable, predictable data pipelines. Whether you need a historical archive for auditing or a single, self-updating file for your ERP, the Improved Import, Export & Mass Actions app gives you the flexibility to adapt to any requirement.

Stop managing files manually. Start automating your workflow today.

Get the Improved Import, Export & Mass Actions App

FAQ: Common Questions About FTP Export Naming