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
Webshop · import Lightspeed eCom

Prepare Lightspeed eCom product content outside the shop

Import products from Lightspeed eCom by item code, SKU, and EAN.

  • Import via 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
Lightspeed eCom

This is the route

  1. You create an API key in Lightspeed eCom.
  2. Photopilot imports the products from your store.
  3. Items are matched by item code, SKU, or EAN.
  4. We deliver approved images and copy via FTP, the Webshop Excel, or the API so you can import them into Lightspeed.
Explanation

How Photopilot works with Lightspeed eCom

For many fashion stores, Lightspeed eCom is where the physical store and webshop come together. Photopilot reads products with their item code, SKU, and EAN from the Lightspeed API and takes over the work around images and text. The result is ready as an import file and image folder, exactly the way your Lightspeed store needs to receive it.

Which Lightspeed data Photopilot uses

Photopilot reads the products from your store, including title, brand, item code, SKU, and EAN. Custom fields and existing images are included too, so you can see which items are already complete. The data is read in the store's default language and through the cluster your Lightspeed account runs on. This means Photopilot works with the same items you see in your POS and online store.

Item code and EAN as a bridge to suppliers

Fashion suppliers usually provide images and product information by EAN or by their own item number. Photopilot compares that data with the item code, SKU, and EAN from Lightspeed and links everything to the correct product. This brings a collection from dozens of brands together in one place. If the match is not clear, Photopilot adds the item to a list for a quick review.

Create images and text in Photopilot

Supplier photos and your own shots are cut out, straightened, and cropped to your fixed format. For items without a good image, Photopilot creates packshots, ghost mannequin images, or AI model photos, while Iris keeps the store's visual language consistent as AI creative director. Product descriptions, titles, and SEO texts are written per item, using materials and care symbols recognized from the label. The team approves everything in one overview before anything is exported.

Back to Lightspeed eCom

Approved images are placed per item code, in the agreed order, in an FTP or SFTP folder, and copy is in the Webshop Excel or can be retrieved via the API. The Excel uses columns that match the Lightspeed eCom product import, so title, description, and SEO fields are correct in one step. The first image is the main image, and the following images fill the gallery. You decide when the import runs.

Multiple languages and brands in one store

Lightspeed eCom stores often run in multiple languages, such as Dutch and English or German. Photopilot reads the default language and writes product texts and SEO texts in every language you offer, ready to import per language. The brand structure is preserved as well: you can set fixed image rules and text guidelines per brand. This helps a multibrand store still feel like one cohesive whole.

How to get started

Create an API key and API secret in Lightspeed eCom and specify which cluster the store runs on and which language is the default. Photopilot then reads products changed in Lightspeed every two hours by default. The team sees daily which items are still missing images or text, and recurring edits run on autopilot. The first results are usually ready within a few days, without an IT project.

Lightspeed eCom at a glance

What is exchanged
Photopilot uses the Lightspeed eCom API to read products with their item code, SKU, and EAN, in the default language you choose. Photopilot does not write to Lightspeed.
How often
Every two hours by default. Photopilot imports only the products changed in Lightspeed since the previous run.
What you provide
An API key and API secret from Lightspeed eCom, plus your store’s cluster (for example, eu1) and the default language.
Good to know
The integration is built on the official Lightspeed eCom API. We test it together on your store before it runs on the fixed schedule.

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

How do I connect Lightspeed eCom to Photopilot?

In the Lightspeed eCom back office, go to the API settings and create a key and secret with read access to products. Share them with the store cluster, for example eu1, and the default language. Photopilot immediately checks whether the products are coming in.

Can Photopilot automatically edit product photos for Lightspeed eCom?

Yes. Supplier images and your own photos are cut out, cropped, and resized to your format. The approved set is ready by item code for import into Lightspeed.

Does Photopilot work with variants in Lightspeed eCom?

Yes. Photopilot matches by item code, SKU, and EAN, and organizes images by color. In the export, photos are grouped by color, so you can attach them to the correct variants in Lightspeed.

Does Photopilot write text in multiple languages for Lightspeed?

Yes. Product descriptions, titles, and SEO texts can be created in any language your store uses. They are included by language in the export, so you can import them into Lightspeed eCom per language.

Do I need to install an app in Lightspeed eCom to use Photopilot?

No. Photopilot only uses an API key for reading. Writing back is done through the product import already available in Lightspeed eCom.

How much do AI model photos cost for Lightspeed stores?

AI photos cost €0.05 to €0.21 per photo at queue pricing and are often ready within an hour. If you want extra-sharp details in fabric and print, choose Precision+. Your own AI model with a fixed face costs €1.37.

Can I approve images before they appear in Lightspeed?

Yes. Nothing goes live automatically: everything is reviewed in Photopilot first. Only approved images and copy are included in the export set for Lightspeed eCom.

What does Photopilot do if a brand in Lightspeed does not provide product photos?

The item appears in the missing images overview. With a quick photo of your own, Photopilot turns it into a cut-out packshot or an AI model photo in the same style as the rest of the store.

Does Photopilot work alongside the Lightspeed POS for the physical store?

Yes. Photopilot reads from Lightspeed eCom and leaves the POS alone. If the store and webshop use the same EANs, the image and copy are automatically linked to the same item that is also available in the store.

How often does Photopilot read our Lightspeed store?

Every two hours by default, each time with only the products changed in Lightspeed.

What does Photopilot need to connect Lightspeed eCom?

An API key and API secret, your store’s cluster, and the default language.

Restore Photopilot images and texts in Lightspeed?

No, the integration imports. Approved images and texts are sent via FTP/SFTP, the Webshop Excel, or the API to your shop.

When does the Lightspeed integration go live?

Only once language, product fields, article codes, EANs, and the publishing route have been verified against the actual shop.

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.