SFTP ZIP Supplier channel FTP, SFTP, ZIP, and portals

Also automatically process individual supplier sources

Approved images with your folders and filenames on FTP or SFTP, and supplier files imported centrally.

Export via FTP or SFTP

Schedule a demo Try it yourself

GDPR-compliant, data in the EU
SLA and a dedicated contact
Connects to Shopware, Shopify, and your ERP
13 retailers and brands in production

FTP, SFTP, ZIP, and portals

This is the route

You provide the FTP or SFTP server and the target folder.
Filenames and folders follow a fixed template for each organization.
An approved image is usually on the server within a few minutes.
Suppliers provide images by upload; Photopilot recognizes the item from the filename.

See what comes in and matches Conflicts remain visible to your team.

Explanation

How Photopilot works with FTP, SFTP, ZIP, and portals

Many online stores, ERPs, and POS systems simply read their product images from a folder on a server. Photopilot writes approved images to that exact folder via FTP or SFTP, using your own file names. In the other direction, supplier images from uploads, ZIP files, and portals are collected centrally and automatically matched to the right item.

Supplier files in one central place

Suppliers provide images through an upload, a ZIP file, or their own portal. Photopilot extracts ZIP files automatically, and with a portal connection, Photopilot logs in to a supplier portal and downloads new images. Photopilot reads filenames, folder structures, and item codes to identify the item and color. We define that naming rule once per supplier, and it is reused for every new delivery.

Recognize by item number, EAN, and color code

A filename such as artikelnummer_kleurcode_2.jpg or one folder per EAN is enough to link an image to the right item. Photopilot compares this with the items from your ERP, POS system, or web store. For each supplier, you see the match rate, conflicts, and remaining work. Uncertain matches go into a review list instead of ending up on the wrong product.

From raw file to shop-ready image

Incoming content is rarely ready to use: backgrounds, crops, and formats all vary. Photopilot standardizes everything based on your shop rules, turns mannequin photos into a ghost mannequin, and fills in missing positions with packshots, AI model photos, or campaign images. Labels and laundry symbols in the photos are recognized for material information and product text. For each brand or collection, you choose automatic processing or prior approval.

File names and folders based on your template

Photopilot writes approved images to your FTP or SFTP server, in the folders and with the file names your webshop or POS system expects, for example with item number, color, and sequence number. This means the file name also determines the image order. A second server can receive the images per product group, and Azure Blob can run at the same time. An image is usually on the server within a few minutes of approval.

Kept up to date, even when images are replaced

Photopilot tracks every file it writes. If your team replaces or deletes an image, the old file on the server is cleaned up too, so outdated photos do not linger. If an upload fails, Photopilot automatically tries again. Supplier uploads are processed every half hour by default, and the missing images overview shows which items are still waiting.

What you need to get started

For export, we need the host, username, password, and target folder for your FTP or SFTP server, plus the file naming rule your webshop uses. For suppliers, we agree per supplier what their files are called and where they come from. This can be set up in a few days and does not require an IT project: the server your webshop already uses is enough.

FTP, SFTP, ZIP, and portals at a glance

What is exchanged: Photopilot writes approved images to your FTP or SFTP server, using folders and filenames based on your own template. A second server can receive the images for each product group, and Azure can run at the same time. Suppliers provide images by upload, and Photopilot automatically extracts ZIP exports such as ACA exports.
How often: Usually within a few minutes after approval. If an upload fails, Photopilot automatically retries it. Supplier uploads are processed every half hour by default.
What you provide: Host, username, password, and target folder for your FTP or SFTP server, plus the filename rule your online store expects.
Good to know: Five customers export via FTP or SFTP this way. Every file written is tracked, so a replaced or deleted image is also cleaned up on the server.

Then in Photopilot

Reliably linked

Let files flow without separate handoffs

300.000+ articles processed

9,5M+ supplier images indexed

~3.200 photos automatically edited per day

FAQ

Frequently Asked Questions

Can Photopilot automatically upload product photos to my FTP server?

Yes. After approval, Photopilot writes the image to your server via FTP or SFTP, usually within a few minutes. Folders and filenames follow the template your webshop expects.

Does the Photopilot export also work with SFTP instead of FTP?

Yes, both FTP and SFTP are supported. You enter the host, username, password, and target folder, and choose the protocol your server uses.

Can I define the file names for the FTP export myself?

Yes. You define one template with, for example, item number, color code, and sequence number, and optionally a folder structure. Photopilot uses that template for every image, so your webshop can recognize the images immediately and place them in the right order.

Can Photopilot process ZIP files from suppliers?

Yes. Photopilot extracts ZIP files automatically, reads the file names and folders, and links each image to the right item by item number, EAN, or color code. Anything that cannot be matched is shown as remaining work.

Can Photopilot retrieve images from a supplier portal?

Yes, with a portal connection, Photopilot logs in to the supplier's portal and downloads new images. They then go through the same matching and processing as other supplier images.

Is a replaced photo also removed from the FTP server?

Yes. Photopilot keeps track of which file it wrote, so a replaced or deleted image is also cleaned up on the server. This prevents old photos from staying in your webshop.

Can Photopilot export to two FTP servers at the same time?

Yes. A second server can receive the images for each product group, for example for a second store label. Azure Blob can also run at the same time.

What happens if an FTP upload from Photopilot fails?

Photopilot then tries again automatically. If it keeps failing, for example because a password has changed, you will see it in the reporting so it does not go unnoticed.

Do I have to set up naming conventions again for each delivery?

No. The naming rule is set once per supplier and then reused for every new delivery. If a supplier changes its naming convention, you only need to adjust that rule.

How quickly does an approved image appear on our FTP server?

Usually within a few minutes after approval. If an upload fails, Photopilot automatically retries it.

What does Photopilot need for export via FTP or SFTP?

Host, username, password, and target folder, plus the filename rule your online store expects.

What happens with conflicts or unclear files?

Photopilot shows match percentage, conflicts, and remaining work per supplier. Per brand or collection you choose automatic flow-through or prior approval.

Knowledge base

Read also

How to start

First the trial route, then the technique

The integration is the starting point. After that, Photopilot keeps linking, editing, writing, checking, and publishing together.