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 item source, for PIM, custom shops, or suppliers.

  • Available after intake
Schedule a demo Try it yourself
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.

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 ClubGentiHarper & Yve
300.000+ articles processed
9,5M+ supplier images indexed
~3.200 photos automatically edited per day
FAQ

Frequently Asked Questions

Which feed formats does Photopilot read?

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

How often does Photopilot read our product feed?

Every two hours by default. A shorter schedule is possible.

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 unnecessary or unavailable, such as with custom shops, PIM 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.

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.