All integrations
Headless commerce · import commercetools
commercetools as a headless product source for Photopilot
Import products, variants, and attributes from a commercetools project.
- Available after intake
- Read only
commercetools
This is the route
- You create an API client in commercetools.
- Photopilot imports products with SKU, key, and attributes.
- Images and text are added to the right products and variants.
- The output is sent to your PIM or publication layer via FTP, the Webshop Excel, or the API.
commercetools at a glance
- What is exchanged
- Photopilot reads the products from your commercetools project, including their variants, SKU, key, and attributes. Photopilot does not write to commercetools.
- How often
- Every two hours by default. Photopilot fetches only the products changed in the project since the previous run.
- What you provide
- The project key and an API client with a client ID, secret, and read access to products.
- Good to know
- The integration is built on the official commercetools API. We test it together on your project first.
Then in Photopilot
Reliably linked
Let source data flow through to sales-ready product pages
300.000+ articles processed
9,5M+ supplier images indexed
~3.200 photos automatically edited per day
Frequently Asked Questions
How often does Photopilot read from commercetools?
Every two hours by default, with only the products changed in the project.
What does Photopilot need to connect commercetools?
The project key and an API client with a client ID, secret, and read access to products.
Where does Photopilot's output go?
Via FTP/SFTP, the Webshop Excel, or the API to your PIM, DAM, or publication layer. Photopilot does not write back directly to commercetools.
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.
What is the source of truth?
Which fields, images, and barcodes define the item.
What can be automated?
Link, crop, and text, or show an exception first.
Where should it go?
Webshop, FTP, Azure, or API, before anything is built.









