
# Change labels with Claude

You can change the labels on your items and campaigns by telling Claude what you want, in the MixShift plugin (Cowork or Claude Code) or from a Claude or ChatGPT connector. Claude shows you a preview first and applies the change only after you say yes. If you would rather call it from your own code, see [Change labels from your own code or agent](/knowledge-base/labels/how-to/change-labels-from-your-own-code-or-agent).

## Before you start

Label changes need MixShift plugin 0.8.22 or later. Say "update the MixShift plugin" and Claude walks you through it.

MixShift turns label changes on for each customer database. If Claude says label changes are not turned on yet, ask MixShift to turn them on.

## How every change works

1. You say what you want. Claude shows a preview: how many items, which accounts, a sample of before and after, and any warnings. A preview changes nothing.
2. You say yes to that exact preview, and Claude applies it. If an item was changed by someone else in between, it is left alone and reported, and the rest apply.
3. Every change records who made it and can be undone.

A preview expires after 24 hours, and you can have at most 25 open previews at a time.

## Name a field once

You can give a field your own name, such as "Collection" for Item Label 1 (up to 80 characters). Claude uses your name from then on. MixShift's report screens keep the standard name, Item Label 1.

A name is kept per account, so to use it everywhere say:

"Name Item Label 1 Collection on all our accounts."

## Set a value on a list of ASINs

"Set Collection to Spring 2027 for B0EXAMPLE01, B0EXAMPLE02 and B0EXAMPLE03."

One change can hold up to 1,000 ASINs. By default the change reaches every marketplace of that seller account (see "Which accounts a change reaches" below).

## Set a value by filter

"Set Tag 1 to Review on every item in Item Group Outdoor."

Claude finds the matching items when it builds the preview and freezes that list, so what you approve is what is applied. This works for campaigns too ("every campaign whose Manager is Pat").

## Rename a value everywhere

"Rename the Item Group Outdoor to Outdoor and Camping."

Every item whose Item Group is "Outdoor" becomes "Outdoor and Camping".

## Clear a value

"Clear Tag 2 on B0EXAMPLE01 and B0EXAMPLE02."

Clearing is its own action: a label is never cleared unless you say "clear".

## Import a batch from a spreadsheet

For a long list, give Claude a CSV file. The first column is `asin` (or `campaign_id` for campaigns) and the other columns are field keys, one row per item:

```
asin,label_1,tag_1
B0EXAMPLE01,Spring 2027,Review
B0EXAMPLE02,Spring 2027,
B0EXAMPLE03,Summer 2027,<clear>
```

- An empty cell leaves that field alone.
- `<clear>` removes the label.
- If your header says "Collection" instead of `label_1`, Claude can rename the column for you.

One file can hold up to 1,000 rows (each ASIN once) and up to 10 different combinations of values. Each combination becomes one change, and Claude previews them all together. Split a larger file into several; a larger import is planned.

## Field keys

| Name | Key | Items | Campaigns |
|---|---|---|---|
| Item Group | `item_group` | yes | yes |
| Item Nickname | `nickname` | yes | no |
| Brand | `brand` | yes | yes |
| Parent ASIN | `parent_asin` | yes | no |
| Item Label 1, Item Label 2 | `label_1`, `label_2` | yes | yes |
| Tag 1 to Tag 4 | `tag_1` to `tag_4` | yes | yes |
| Manager | `manager` | no | yes |
| Objective | `objective` | no | yes |

## Which accounts a change reaches

- **Items, by default:** every marketplace of that seller account (for example US, Canada, Mexico and Brazil together). MixShift keeps an ASIN's label the same across the marketplaces of one seller account so a report grouped by a label never splits an ASIN. Changing a label for one marketplace only is not offered.
- **Other seller accounts:** add "across all our accounts" to include every account of the same type (every Seller account, or every Vendor account) in your MixShift database. For example: "Set Collection to Spring 2027 for B0EXAMPLE01 across all our accounts."
- **Campaigns:** a campaign belongs to one account, so a campaign change reaches only that account.
- **An ASIN sold under two of your seller accounts** has a label on each. A change on one account does not reach the other unless you choose all accounts. The preview names every account it reaches, so check that list before you say yes.

## Rules for values

Values are trimmed, cannot be blank or contain control characters, and cannot be longer than the field holds; the preview names the problem. A value that differs only in capitals from one already in use gets a warning, so you do not end up with "spring 2027" next to "Spring 2027".

Only items and campaigns MixShift has already seen can be changed. An ASIN MixShift has not pulled yet is left out and counted in the preview. Try again once it shows up in MixShift.

## Check the result

"Show me what Collection is set to for B0EXAMPLE01."

"Which values of Collection are in use, and how many items have each?"

The new value reaches your MixShift reports within a few minutes.

## Undo

"Undo that last label change."

Claude previews putting the earlier values back. Say yes to apply it. An item that was changed again since is left alone and reported.

## See recent changes

"Show me the label changes from this week."

Claude lists recent changes and who made them. Edits made directly in MixShift's own screens still work and are picked up within about 15 minutes (a label changed from Claude moments earlier keeps Claude's value until it has reached your reports).

## Who can do this

Anyone who signs in to MixShift can, through the plugin or an AI connector, except people with the Viewer role (or the older Member role) in your organization. On a shared team login with no individual sign-ins, everyone on it can. An organization admin can also turn label changes off for one person at [mcp.mixshift.io/admin](https://mcp.mixshift.io/admin).