How can I bulk edit product configurations?

When you have a large number of configurations and you want to do edits to multiple configurations at a time, it can be time-consuming opening them up and doing the edits manually

The admin app UI does not support bulk editing of product options, mainly because there are a large amount of different settings for every type of product option and preview layer.

Our MCP connector allows you to bulk edit product options via JSON-based tools. The steps below explain how this can be done.

MCP bulk editing

The bulk editing is only available when you connect to our app via ChatGPT or Claude to the MCP Live Product Options server. Our AI assistant in the app currently does not support bulk editing.

When you are connected, tell your AI agent what you want to do. Here is a prompt template to replace images in bulk (make sure to replace the placeholders before sending it):

Bulk-replace images in my LPO options configs without an editor session, using the stored-config get/update tools (not the live-UI draft tools).

Task: in config(s) <names or "all matching <search>">, set the image URL of layer(s) <layer names> to <local file path>. Layers can sit in the main preview or in additional views, so search both.

Steps:
  1. List configs, read each stored config, and locate the target layers. Show me a table (config, view, layer, old URL) and wait for my OK before writing anything.
  2. If the new image is a local file, upload the asset first to get a URL. Upload once and reuse the URL.
  3. Backup first: ask me which strategy I want before the first write. The options are (a) a disabled duplicate of each config, or (b) a local JSON dump of each stored config to ./backups/<uuid>-<version>.json. I prefer (b) for bulk runs.
  4. Update each config to make the changes. If there are lots of configs to change, ask me to verify after the first patch, after my confirmation apply to thre rest.
  5. Report per config: changed, errors, warnings.

Limitations

When you update data inside a configuration, related fields like area coordinates are not updated automatically
It's the responsibility of the user to first create a backup before bulk editing. This can be done by the agent before applying the changes. (If something goes wrong, it can be restored.)