PhotopilotPhotopilot
Content enrichment for your online store Available after intake

Content enrichment for commercetools: attributes and copy for each locale.

In commercetools, Photopilot fills the description, metaTitle, and metaDescription as LocalizedString, and sets target group, color, material, and Web only in the attributes of your product types.

Photopilot connects commercetools during intake; we’ll agree on fields and permissions together.

How it appears in commercetools Via the commercetools API, using your product types.
Photopilotcommercetools
Product text description LocalizedString, by locale
SEO title and meta description metaTitle · metaDescription LocalizedString
Target audience target group attribute (lenum) on the product type
Color color attribute (lenum) usable as a facet
Material material attribute (ltext)
Web only web-only attribute (boolean)
Language each project locale
From source to online store

Every source in, one complete product page in commercetools.

Photopilot enriches the data from your ERP, feeds, and suppliers, and puts it in the fields that commercetools 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 commercetools Target group, color, attributes, copy and SEO
What Photopilot fills

Attributes and copy for commercetools.

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 by locale
  • metaTitle and metaDescription
  • Target audience and color as enum attributes
  • Material as an attribute
  • Web only label
  • Translations in the same run
  • Enrich older items with pricing agreed in advance
Typically commercetools

Where things often go wrong in commercetools.

  1. Attributes with the wrong constraint

    Target group and material are the same for all variants; with SameForAll, they are stored once per product. Photopilot fills them in at the level required by your product type.

  2. Enum values that do not exist

    A lenum attribute only accepts the keys it knows. Photopilot fills target group and color with your own keys.

  3. Locales that remain empty

    A LocalizedString with only Dutch leaves other shops empty. Photopilot fills every locale in the project.

Connect

How we connect commercetools.

  1. 1

    Create an API client in commercetools

    You create an API client in the Merchant Center with permissions for products and product types, and share the client ID and secret.

  2. 2

    Map fields and picklists

    We define which fields in commercetools 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 commercetools

Which fields does Photopilot populate in commercetools?

The description, metaTitle, and metaDescription for each locale, plus target audience, color, material, and Web only as attributes on your product types.

Do the attributes work as facets in our storefront?

Yes. You can use enum attributes for target audience and color as facets in Product Search.

Can Photopilot use our existing product types?

Yes. Photopilot fills the attributes that your product types already have, using your own keys.

Does this work for multiple stores and locales?

Yes. Text and SEO are added per locale for every store in the project.

What if our ERP specifies a different target audience than Photopilot?

For each attribute, you choose which source takes priority: the source system or Photopilot. If Photopilot differs, you see a warning on the item.

Is custom work needed in commercetools?

No. Photopilot uses the standard API and your existing product types.

What does content enrichment for commercetools 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.