All integrations
Headless commerce · import Medusa
Enhance Medusa Commerce with Photopilot
Import products, variants, and images from Medusa.
- Available after intake
- Read only
Medusa
This is the route
- You create an API token in Medusa.
- Photopilot imports products, variants, metadata, and images.
- Images and copy are matched to the right product by SKU or handle.
- The output is sent to your publication layer via FTP, the Webshop Excel, or the API.
Medusa at a glance
- What is exchanged
- Photopilot uses the Medusa API to read products, variants with SKU, metadata, and images. Photopilot does not write to Medusa.
- How often
- Every two hours by default. Photopilot imports only the products updated in Medusa since the previous run.
- What you provide
- The URL of the Medusa API and an API token with read permissions for products.
- Good to know
- The integration has been tested against a real Medusa installation in our test lab.
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 Medusa?
Every two hours by default, each time with only the products updated in Medusa.
What does Photopilot need to connect Medusa?
The URL of the Medusa API and an API token with read permissions for products.
Where does Photopilot's output go?
Via FTP/SFTP, the Webshop Excel, or the API to your publication layer. Photopilot does not write back directly to Medusa.
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.









