PhotopilotPhotopilot
Log in
Schedule a demo
Try it yourself
EN
NL Nederlands EN English DE Deutsch FR Français ES Español IT Italiano PT Português PL Polski SV Svenska DA Dansk
All integrations
Feed source CSV, JSON, and XML feeds

Product feeds as a reliable source for Photopilot

A CSV, JSON, or XML feed as the product source, from an ERP, a custom webshop, or suppliers.

  • Import via CSV, JSON, or XML
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
CSV, JSON, and XML feeds

This is the route

  1. You provide a feed URL, optionally with a password.
  2. Photopilot imports the feed and maps columns to item, color, size, and EAN.
  3. Rows are grouped into models, color articles, and variants.
  4. Images and text are added to those items.
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 imports a CSV, JSON, or XML feed with items, variants, EANs, media, and material. Field mapping turns each row into a variant, and rows are grouped into models and color items. We use the column names exactly as your export writes them.
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 & SportDuifhuizenSkiHutVan 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, especially there. If there is no standard connector, the feed provides the items and images and text are sent back via FTP or SFTP, Azure Blob, the Webshop Excel, or the API. That way, no separate integration has to be built.

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.

What happens when fields are missing or deviate?

Deviations show up in reporting instead of failing silently. A trial import quickly shows which fields are missing, duplicated, or matching well.

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.

Schedule a demo Try it yourself

  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.