PhotopilotPhotopilot
All integrations
Feed source CSV, JSON, and XML feeds

Connect product feeds: complete product data for your webshop

Any product feed as the source, enriched with target audience, color, attributes, copy, and SEO for the online store.

  • Integration via CSV, JSON, or XML
CSV, JSON, and XML feeds

This is the route

  1. You give Photopilot access to the feed.
  2. Photopilot matches every item and variant by EAN and item number.
  3. Target audience, color, attributes, copy, and SEO are completed and approved.
  4. The enriched attributes are in the feed, and everything is in the online store.
Explanation

How Photopilot works with product feeds

Not every system has a standard integration, but almost every system can create a CSV, JSON, or XML feed. Photopilot reads that feed as an item source, whether it comes from an ERP, a custom shop, or a seasonal file from a supplier. Columns are mapped once, and then it runs automatically.

What Photopilot retrieves from a feed

Photopilot reads item numbers, SKUs, EANs, colors, and sizes from the feed, along with anything else it contains: description, brand, category, image links, material fields, and care symbols. We use the column names exactly as your export writes them, even if they differ from the standard. With field mapping, each row becomes a variant, and rows are grouped into styles and color items. This gives a feed the same product structure as a webshop or ERP integration.

Match by SKU, EAN, and color code

Because the feed provides item numbers and EANs, Photopilot can automatically attach supplier images from Fashion Cloud, Stockbase, FTP folders, and portals to the correct rules. The color code determines which variants share one image set. Image links in the feed are retrieved and checked, so existing photos do not need to be submitted again. Duplicate or conflicting rules are included in the report instead of being silently overwritten.

What happens to the items

Every item from the feed goes through the same processing as items from a direct integration. Supplier images and packshots get your shop’s background and crop, garments on a mannequin become ghost mannequin images, and where images are missing, Photopilot creates AI model photos or campaign images. Materials and care symbols from the feed or from the label are recognized and used in product descriptions and SEO text. Your team approves where that has been agreed.

Publish to any destination

A feed is only the source; you choose separately where images and copy go. Photopilot publishes directly to a connected webshop, writes files via FTP or SFTP using your file names, puts them in Azure Blob, or delivers them through the Webshop Excel or the API. Image order and alt text are included. That way, a custom webshop or ERP can pick up the images in the way it already expects.

Monitoring and daily overview

By default, Photopilot reads the feed every two hours; a shorter schedule is possible. A feed that returns nothing, or where no fields can be mapped, is treated as an error rather than an empty catalog, so items never disappear silently. New rows automatically appear in the missing images and texts overview. With autopilot, they go straight into processing without anyone having to upload a file.

From sample file to running integration

You provide a feed URL, optionally behind basic authentication, and a sample file. With a test import, we can immediately see which fields match well, which are missing, and which are duplicated. We then lock in the field mapping and run the feed on a schedule. This is often up and running within a day, without your developers needing to build anything if the export already exists.

CSV, JSON, and XML feeds at a glance

What is exchanged
Photopilot uses every column from your CSV, JSON, or XML feed: model, color, size, EAN, composition, and anything else your ERP provides, and adds target audience, color family, and material as new columns, plus the Web only label. Product copy, SEO, and translations go directly to the online store.
How often
Every two hours by default. A shorter schedule is possible.
What you provide
A feed URL, optionally behind basic authentication, and a sample file so we can map the fields.
Good to know
A feed that returns nothing, or where no fields can be matched, is treated as an error rather than an empty catalog. This prevents products from disappearing silently.

Then in Photopilot

Reliably linked

Let source data flow through to sales-ready product pages

The StoneBerden FashionRinsma ModepleinVan DijkJeroen BeekmanVan Tilburg Mode & SportDuifhuizenSkiHutBouchier Sport2000Van Dal MannenmodeCalico ClubGentiluomoHarper & YveGenti
300.000+ articles processed
9,5M+ supplier images indexed
~3.200 photos automatically edited per day
FAQ

Frequently Asked Questions

Can Photopilot use a CSV product feed as a source?

Yes. Photopilot reads CSV, JSON, and XML files with items, variants, EANs, image links, and materials. Column names do not need to be changed; we map them once to item, color, size, and EAN.

How do I connect an XML product feed to Photopilot?

You enter the URL of the XML feed, with a username and password if needed, and send a sample file. With a test import, we map the elements to the correct fields, and after that Photopilot reads the feed automatically on schedule.

Does a product feed in Photopilot work with colors and sizes?

Yes. Each row in the feed becomes a variant, and Photopilot groups them into models and color items. Images belong to the color, so all sizes in the same color automatically get the same photos.

Can I use the product feed from my PIM for Photopilot?

Yes, a CSV, JSON, or XML export is a great source. Photopilot uses the existing structure and column names, so your system remains the source of truth for item data while Photopilot handles images and text. You can read more about whether you still need a PIM alongside your ERP in our knowledge base.

Does Photopilot retrieve images from the links in my product feed?

Yes. Image links in the feed are fetched and assigned to the correct item. They can then be cropped, placed on the right background, or supplemented with other images.

How often does Photopilot read our product feed?

Every two hours by default, and more often if needed. Changes in the feed, such as new items or updated EANs, then appear in Photopilot automatically.

What happens if my product feed is empty or broken?

Photopilot treats that as an error, not as an empty catalog. So no items disappear, and the reporting shows what is wrong so it can be fixed quickly.

Can Photopilot use materials and care symbols from a product feed?

Yes. Material fields and care symbols from the feed are standardized to one fixed list and used in product text and material fields. If they are missing, Photopilot can recognize them in photos of the label.

Is a product feed suitable for a custom webshop?

Yes, that is exactly where it works. The feed provides the items, Photopilot adds target audience, color, material, copy, and SEO, and everything goes straight into the online store. This means no separate integration has to be built.

Can Photopilot return an enriched feed?

Yes. Target group, color family, material, Web only, and the copy for each language are added as columns in the enriched feed and go straight to the online store.

Does Photopilot write back to the feed?

Yes. The enriched attributes are written back to the feed, and approved copy, SEO, and attributes go straight to the online store.

Which feed formats does Photopilot read?

CSV, JSON, and XML, with items, variants, EANs, media, and materials.

What does Photopilot need to connect a feed?

A feed URL, optionally with basic authentication, and a sample file for mapping the fields.

When is a feed the right choice?

When a standard integration is not needed or not available, such as for custom-built stores, ERP exports, or seasonal supplier files.

Knowledge base

Read also

Flip the switch

Ready to flip the switch?

Enter your web shop and flip the switch. You'll see how much of your range we get online automatically, with a price estimate and a plan.

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.

  1. What is the source of truth?

    Which fields, images, and barcodes define the item.

  2. What can be automated?

    Link, crop, and text, or show an exception first.

  3. Where should it go?

    Webshop, FTP, Azure, or API, before anything is built.