Headless commerce · import Medusa

Enhance Medusa Commerce with Photopilot

Import products, variants, and images from Medusa.

Import via Medusa API + export
Export via FTP, Excel, or API

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

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.

See what comes in and matches Conflicts remain visible to your team.

Explanation

How Photopilot works with Medusa

With Medusa, a team builds its own commerce stack, and product content should not depend on releases. Photopilot reads products, variants, metadata, and images from Medusa, handles the image and text work, and delivers the results so your own module or import can process them. This lets the content team keep working at a steady pace, separate from sprint planning.

What Photopilot retrieves from Medusa

Photopilot uses the Admin API to read products with title, handle, status, metadata, thumbnail, and images. For each variant, SKU, title, inventory, and custom metadata are included. If you prefer to use the Store API, you can also connect with a publishable API key. Each run only requests products that have been updated since the previous run.

Match by SKU, handle, and EAN

Photopilot matches images to Medusa products using SKU, handle, and an EAN from the variant or product metadata. If the metadata contains your own product number, we use that as the main key. Supplier images that come in by EAN or item number can then find their own way to the right product. Variants with the same color share one image set.

Images and text in Photopilot

Supplier images and packshots are corrected in Photopilot: cut out, cropped, and placed on the background your storefront uses. Where a model photo is missing, Photopilot creates AI model photos or a ghost mannequin, and with Iris as AI creative director, campaign images are created in your brand style. Materials and care symbols are recognized and used in product texts and SEO texts. The content team reviews and approves every product.

Back in Medusa through your own module

Approved images and copy are retrieved by a subscriber, scheduled job, or custom module via the Photopilot API, or they are ready on FTP/SFTP and in the Webshop Excel. The image order is fixed per product, including which image becomes the thumbnail, and each image has alt text. Copy and SEO fields are included per product and language. Because the delivery format does not change, the processing only needs to be built once.

Content independent of development releases

In many Medusa projects, product content sits in the same backlog as features, so a new collection has to wait for a release. With Photopilot, that work moves to the content team: new products appear in the worklist automatically, and the overview of missing images shows where action is needed. With autopilot, fixed steps such as creating cut-outs and cropping run without manual work. Reports show how complete the catalog is.

Quick setup, no IT project

You give us the Medusa backend URL and an API token with read access to products, or a publishable API key for the Store API. Together, we define which metadata keys contain EAN, color, and material, and how your module retrieves the output. The first run uses your own products right away. After that, Photopilot reads updates every two hours by default.

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

FAQ

Frequently Asked Questions

How do I connect Medusa to Photopilot?

Share the URL of your Medusa backend and an API token with read access to products. Photopilot then reads products, variants, metadata, and images through the Admin API.

Can Photopilot also read through the Store API of Medusa?

Yes, with a publishable API key, Photopilot reads the products via the Store API. This is useful if you do not want to issue an Admin token.

How do product images from Photopilot get into Medusa?

Your own module, subscriber, or scheduled job retrieves approved images through the Photopilot API or from FTP/SFTP. The order and thumbnail are defined per product, so processing is straightforward.

Which fields does Photopilot use to match Medusa products?

By SKU, handle, and an EAN from the variant or product metadata. Your own product number in metadata can be used as the primary key.

Does Photopilot work with color and size variants in Medusa?

Yes. Photopilot reads all variants with SKU and inventory, and groups images by color so sizes in the same color share one image set.

Do I need to install a Medusa plugin for Photopilot?

Not for importing; an API token is enough. To write the data back, your own module processes Photopilot’s standard delivery.

Can I approve images and texts before they go into Medusa?

Yes. Everything is reviewed in Photopilot first, and only approved content is included in the delivery. For each product, you can see what is new or changed.

What if a Medusa product has no supplier photo?

It is then listed in the missing images overview. From a simple product photo, Photopilot creates a packshot, ghost mannequin, or AI model photos, which you review first.

How much do AI model photos cost for a Medusa online store?

AI photos cost €0.05 to €0.21 per photo at queue pricing and are often ready within an hour. Your own AI model with a fixed face costs €1.37.

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.

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.