PhotopilotPhotopilot
Content enrichment for your online store

Enrich Magento product data: texts and attributes per store view.

Your ERP fills the catalog; Photopilot completes it. In Magento and Adobe Commerce, Photopilot fills the description, SEO fields, target audience, color, material, and Web only for each store view, while the ERP fields remain untouched.

How it appears in Adobe Commerce / Magento Directly through the REST API, per store view.
PhotopilotAdobe Commerce / Magento
Product text description · short_description
SEO title and meta description meta_title · meta_description plus meta_keyword
Target audience photopilot_doelgroep or your own attribute, after the mapping has been confirmed
Color photopilot_kleur select attribute, also as a filter
Web only photopilot_web_only your own select attribute
Material and care custom_attributes label becomes an existing option ID
Alt text label in the media gallery
Language store view (store code) without store views: scope all
From source to online store

Every source in, one complete product page in Adobe Commerce / Magento.

Photopilot enriches the data from your ERP, feeds, and suppliers, and puts it in the fields that Adobe Commerce / Magento uses.

  1. Source ERP or product feed ACA · Business Central · SRS · LS Central · Excel
  2. Photopilot Complete, decide, write
    1. 1 Your own data What your ERP, feed, or team already knows comes first.
    2. 2 Rules Codes, sizes, and paths that already provide a clear answer.
    3. 3 Photo Color measured from the packshot, never from a model photo.
    4. 4 AI One short AI question, only where something is still unresolved.
  3. Destination Adobe Commerce / Magento Target group, color, attributes, copy and SEO
What Photopilot fills

Attributes and copy for Adobe Commerce / Magento.

Every attribute comes from a closed picklist with fixed codes, never from free text. Anything you have already filled in takes priority.

  • You choose who wins for each feature: the source or Photopilot
  • If Photopilot differs from the source, you’ll see a warning
  • Enrich older items with pricing agreed in advance
  • Description and short description
  • Meta title, meta description, and meta keywords
  • Target audience as a select attribute and filter
  • Color family as a select attribute and filter
  • Material and care in your attributes
  • Web only label as a custom attribute
  • Copy per language, per store view
  • Enrich older items with pricing agreed in advance
Typically Adobe Commerce / Magento

Where things often go wrong in Adobe Commerce / Magento.

  1. Store-view scope that overrides values

    Writing through the general REST route silently overwrites the values of the first store view. Photopilot always writes to an explicit store code, or to the all scope if no store views have been configured.

  2. Select attributes with separate option IDs

    A picklist in Magento expects an option ID, not text. Photopilot maps each value to the correct option so the filters in layered navigation are accurate.

  3. Copy on a simple product that no one sees

    For configurable products, the copy the customer reads is on the visible product. Photopilot writes exactly there, never on a simple product that is not visible on its own.

  4. ERP attributes and the url_key

    In many stores, color, season, supplier and collection come from the ERP. Photopilot leaves those protected attributes and the url_key unchanged so no links break.

Connect

How we connect Adobe Commerce / Magento.

  1. 1

    Create integration in Magento

    Under System, Integrations, create an integration with product permissions and share the four OAuth keys. You do not need to install a module.

  2. 2

    Map fields and picklists

    We define which fields in Adobe Commerce / Magento are leading, which ones Photopilot fills, and which values belong to your option lists.

  3. 3

    Trial run on your items

    Photopilot enriches a selection of real items. You can review the changes field by field before anything goes live.

  4. 4

    Enable by attribute and by field

    After that, it runs automatically for every new item. We always enable publishing to the live shop together.

FAQ

Frequently asked questions about content enrichment in Adobe Commerce / Magento

Which fields does Photopilot fill in Magento?

Description, short description, meta title, meta description and meta keywords, plus target group, color and Web only as select attributes, material and care in your attributes, and alt text for the photos.

How does Photopilot handle store views and scope?

Each language is linked to a store code, and Photopilot writes the text to that store view. If no store views are set up, Photopilot writes to the all scope.

Can target group become a filter in layered navigation?

Yes. Photopilot creates the attributes photopilot_doelgroep and photopilot_kleur as select attributes, including their options, and adds them to your attribute sets. For each attribute, you choose whether to show it on the product page or also use it as a filter.

We already have a target audience attribute. Can Photopilot fill it?

Yes. You choose the existing attribute. Photopilot suggests which option belongs to which target audience and fills it after you confirm.

Will Photopilot overwrite values from our ERP?

No. Photopilot leaves protected ERP attributes unchanged, and if the ERP system writes a value back, Photopilot respects it. A field is never cleared.

Does this work with both Adobe Commerce and Magento Open Source?

Yes. Photopilot uses the standard REST API that both use, so no server module is needed.

What does content enrichment for Adobe Commerce / Magento cost?

Product copy, SEO and translations in a single run start at €0.01 per product. For enriching older items, you see the price in advance, and attributes are billed at cost.