PhotopilotPhotopilot
All integrations
Supplier channel FTP, SFTP, ZIP and brand portals

Also automatically process individual supplier sources

Many suppliers are not neatly in a standard platform. Photopilot therefore also processes FTP, SFTP, ZIP files, email attachments, folder structures, and brand portals.

  • Filename templates per supplier
  • Folder and ZIP indexing
  • FTP/SFTP source monitoring
After the connection

What this integration makes possible next

The integration is the beginning. After that, Photopilot can automatically create and improve images, write product texts, check, and publish.

Daily Photopilot interface

See what arrives, matches, and needs attention

Supplier files remain visible by supplier. Reliable matches can continue automatically; conflicts and missing links remain visible to your team.

Supplier intake in Photopilot with linked files, conflicts, and exceptions
Supplier files in production

From supplier folder to linked products

For each supplier, you can see which files are reliably linked, which conflict, and which still need attention. Automatic approval is configured per brand or collection.

View supplier workflow
FTP, SFTP, ZIP and brand portals

What does this mean for your product team?

In practice, many brands deliver via folders, files, and portals. Photopilot reads filenames, item codes, and folder structures and reliably links the material to the correct items.

From source to publication

  1. Files are received via upload, folder, SFTP, ZIP, or portal download.
  2. Naming conventions and source rules are stored per supplier.
  3. Images are linked to article, color, variant, and image slot.
  4. Per brand or collection, decide if new deliveries flow automatically or require prior approval.

What your team does less manually

  • Filename templates per supplier
  • Folder and ZIP indexing
  • FTP/SFTP source monitoring
  • Version control per delivery
  • Match percentages and conflict status
Fits well with

When is this relevant?

  • Brands outside Fashion Cloud or Stockbase
  • Teams receiving many seasonal folders and ZIPs
  • Retailers wanting source management without extra manual work
Pre-arrangements

This keeps the connection manageable

  • We record per supplier how file names, folders, and article codes should be read.
  • Photopilot shows match percentage, conflicts, and remaining work per supplier.
  • This fits directly alongside Fashion Cloud, Stockbase, ACA, and webshop integrations.
Reliably linked

Let files flow without separate handoffs

Files from the studio, FTP, ZIP, or other sources remain linked to the right product. Photopilot processes them according to fixed rules and instantly shows what is ready for publication.

Your systems FTP, SFTP, ZIP and brand portals Shopware FTP / SFTP
PhotopilotFrom separate sources to ready for publication.
Smart retailers
The StoneBerden FashionRinsma ModepleinVan DijkJeroen BeekmanVan Tilburg Mode & Sport
300.000+ articles processed
9,5M+ supplier images linked
~3.200 photos automatically edited per day

One product status

Source system, studio, and e-commerce work from the same product status — without separate lists.

Fixed image and content rules

Cropping, sequence, product copy, and channel rules are applied automatically to each product.

Automatic publishing

Trusted brands or collections flow through automatically; exceptions remain visible to your team.

Consultation and demo

Trial route first, technology second

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

  • We map the trial route on your own sources and systems.
  • You immediately see where the collection can move faster, which risks remain and which agreements are needed.
  • Only then do we choose whether a demo, pilot, or technical intake makes sense.
01
Source

What is the source of truth?

Define which fields, images, barcodes, and sources are leading for item, color, and variant.

02
Rules

What can be automated?

Choose where Photopilot can link and crop images, create texts, or show an exception.

03
Destination

Where should it go?

Define what needs to go to the webshop, PIM, DAM, feed, FTP, or studio before anything is built.

In practice

Where this integration creates room for growth

An e-commerce manager is usually not asking for technology, but for control: which products are complete, which images are still missing, which studio or supplier images may go live, and what can be published without extra handover.

Discuss this integration
Practical question

FTP, SFTP, ZIP and brand portals in your product process

FTP, SFTP, ZIP and brand portals koppeling wordt pas waardevol wanneer artikeldata, beeldstatus en publicatie op dezelfde productkaart samenkomen.

For teams already familiar with the source system and mainly want to know how images and data are reliably published.

  • Filename templates per supplier
  • FTP/SFTP source monitoring
View AI model photos
Work for image teams

Make product photos sales-ready

FTP, SFTP, ZIP and brand portals product photo editing gaat voor beeldteams vooral om vaste afspraken voor uitsnede, marge, volgorde, bestandsnaam en controle.

Relevant when images from different sources still need the same crop, margin, order, and review.

  • Folder and ZIP indexing
  • Version control per delivery
View AI packshot editing

See together how Photopilot fits you

In a consultation, we identify the leading source, where collections are waiting, and how images, copy, and data can be published together sooner.

Book a consultation