PhotopilotPhotopilot
Suppliers & sources New

Get supplier images faster to the correct item

Connect Fashion Cloud, Stockbase, brand portals, FTP, ZIP files, or email attachments per supplier. Photopilot shows the percentage of images truly linked to articles per source.

Not every supplier delivers neatly. Some brands are in Fashion Cloud or Stockbase, others send a portal link, ZIP file, or messy folder structure. Photopilot first searches by article number, EAN, and file name. Only doubtful cases reach your team.

Sources

Every channel, one workflow

FTP, SFTP, brand portal, folder structure, ZIP archive, or email attachment: Photopilot indexes the source and monitors it. Per supplier, you can connect multiple channels simultaneously, each with its own rules.

FTP / SFTP
Brand portal
ZIP file
Dropbox / Google Drive
Email attachment
Folder structure
Supplier portalPhotopilot supplier portal with folders, files and match percentages

Hard codes first

Supplier item number, EAN, item number, and public ID are matched without AI when reliably present.

Structure from folder and name

In portals and folders, file names, folder segments, brand, season, and color are read as if a merchandiser is organizing the delivery.

Percentage per supplier

In the app you see, per supplier, how many files are truly linked to an article variant, not just to a model.

Manual as the last step

Only files without candidate, conflict, or too low certainty remain for human review.

Name template {brand}/{season}/{group}/{vendor_item_no}_{slot}.{ext} Supplier's filename Nike/S2025/Boxers/P6-BX-06_1.jpg
  • Brand
  • Season
  • Article group
  • Supplier item
Name templates

Supplier names translated to your structure

Each supplier uses its own naming conventions. With a naming template per source, Photopilot extracts brand, season, article group, and article number from the path, even when the structure differs per supplier.

Matching engine

Matching rules before manual work, percentages before assumptions

Photopilot first uses reliable codes and fixed matching rules. Then, deviant structures and descriptive filenames are read as candidates. What remains is not hidden: you see the percentage linked, not linked, and conflict per supplier.

  1. 01

    Read name structure

    Filename and path are read according to a naming template per supplier. This way, brand, season, article group, and article number become recognizable without manual research.

  2. 02

    Translate segments

    Segments like 'Nike', 'S2025' or 'Boxers' are translated to your internal structure: brand, season and article group. In case of doubt, confirm the proposed mapping once.

  3. 03

    Fast item matching

    Then Photopilot searches at item level: first exactly by supplier item number, EAN, or public ID, then via normalized variants. This keeps large file sets quick to process.

  4. 04

    Matching with differing names

    When filenames mainly contain article name and color, Photopilot compares that name with article name and ACA color. Clear matches are linked; doubts return as suggestions.

  5. 05

    Manual linking only for remaining exceptions

    Only when no candidate, a conflict or low certainty remains does a file go to manual linking. This keeps manual work visible, measurable and limited.

What else is included

Version control, audit logs, segment mappings, and automatic approval for suppliers who regularly provide new material.

Segment mappings

Set up once, use for years

Photopilot suggests the first mapping: 'S2025' is recognized as season SS25 and collection Summer 2025. After verification, Photopilot remembers this automatically, also for future deliveries from that supplier.

Version control

New delivery does not overwrite anything unintentionally

A second delivery from the same supplier becomes a new version. Live photos remain live until someone explicitly approves the new material.

Audit log

Who, when, which articles are affected

Each upload batch gets a log: source, timestamp, user, matched articles, and unmatched files. In case of doubt, this can be easily traced back later.

Multiple sources

One supplier, multiple channels

A brand can use FTP, a brand portal, and a ZIP file simultaneously. Photopilot treats them as different sources under the same supplier, with separate rules per source.

Automatic approval

Approved immediately with high certainty

If a match exceeds your certainty requirement, the photo goes directly through the workflow. Doubtful cases remain available for human review.

Uniform workflow

Supplier images follow the same standard

Once the material is linked, it goes through the same crop templates, editing, approval flow, and publication as your other product images.

Which supplier is still blocking your publishing?

Provide us with a brand portal, ZIP file, or sample folder. In the workflow scan, we show what percentage connects directly, where naming rules help, and how much manual control remains.

Book a consultation