Labels FAQ
How-to guides: Change labels with Claude and Change labels from your own code or agent.
Why did my label apply to every marketplace?
On purpose. MixShift keeps an ASIN's label the same across the marketplaces of one seller account (for example US, Canada, Mexico and Brazil together), so a report grouped by a label never splits one ASIN into two groups. Changing a label for one marketplace only is not offered; asking for it is refused and nothing changes.
How do I include my other seller accounts?
By default a change reaches one seller account. To reach every account of the same type (every Seller account, or every Vendor account) in your MixShift database, say "across all our accounts" to Claude, or use scope all in the API.
An ASIN is sold under two of our seller accounts. Why did only one change?
An ASIN sold under two seller accounts has a label on each, and a change on one account does not reach the other unless you choose all accounts ("across all our accounts", or scope all). Check the preview's account list before you confirm: it names every account the change will reach.
I named a field. Why do MixShift reports still say Item Label 1?
Your own field name (for example "Collection") is used by Claude and the API. MixShift's report screens keep the standard name. The name is also kept per account, so to use it everywhere, name it on all accounts: "Name Item Label 1 Collection on all our accounts."
How long until I see the change in reports?
A few minutes after the change is applied. In the API a changed value reads pending until it has reached your reports, then synced.
Can I undo a change?
Yes. Every change can be undone: say "undo that last label change", or call undo in the API. Undo is a new preview that puts the earlier values back; commit it like any change. An item that was changed again since is left alone and reported.
Who on my team can change labels, and can I turn it off for someone?
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.
Some ASINs were skipped. Why?
MixShift only changes items it has already seen. An ASIN it has not pulled yet is left out and counted in the preview. Try again once it shows up in MixShift. Items that changed between the preview and your yes are also left alone and reported.
How many items can I change at once? How big can a file be?
Up to 1,000 ASINs or campaigns in one change. A spreadsheet can hold up to 1,000 rows (each ASIN once) and up to 10 different combinations of values; split a larger file into several. A larger import is planned.
Can we still edit labels in MixShift's own screens?
Yes. Those edits still work and are picked up within about 15 minutes. The one exception: if the same label was just changed from Claude or the API, that change wins until it has reached your reports.
Can I see who changed a label?
Yes. Every change records who made it. Ask Claude "show me the label changes from this week", or read the change history in the API.
Is label editing on for my account?
MixShift turns label changes on for each customer database. If a change answers that it is not turned on yet, ask MixShift to turn it on. Claude also needs MixShift plugin 0.8.22 or later: say "update the MixShift plugin".
Can I label campaigns too?
Yes. Campaigns carry Item Group, Brand, Item Label 1 and 2, Tag 1 to Tag 4, Manager and Objective. A campaign belongs to one account, so a campaign change reaches only that account.
Can an automation or our own code change labels?
Yes, over the REST API or the MCP tools, with a preview and a commit. A service credential is made on Machine credentials (an owner, admin or builder, for organizations with member sign-in) with the "Change labels" permission switched on, or, for an organization on one shared team login, at mcp.mixshift.io/admin with "Also grant Labels write access" ticked. Without that permission a credential is read-only for labels. Changes it makes are recorded under the credential's label. See Get access. A credential limited to named accounts cannot read labels at all.
Shifty is the MixShift docs assistant. Pick a question or open the chat for anything else.