# Keep the catalogue clean

<Lead>
  Bulk fixes across dozens of releases, in one sentence. You describe the
  change, the assistant shows you exactly what it will do, you say go, and you
  check the result in Labelcamp.
</Lead>

<Callout type="info">
  Not every scenario is available to every account: it depends on your profile
  in Labelcamp. Ask the assistant "What can I do with Labelcamp?" to see what
  yours allows.
</Callout>

## Clean up a messy import in one sentence

A DDEX transfer filed 40 albums under Pop, on the wrong price code. One
request covers the whole batch:

<Conversation>
<You>

The Blue Harbor import filed everything under Pop. Remap these 40 albums to
Jazz / Contemporary Jazz, and move them to price code B2, tracks included.

</You>
<Assistant>

Here is the plan for **40 albums, 486 tracks**:

- Genre: Pop → **Jazz / Contemporary Jazz** on the 40 default offers
- Price: **B2** on the albums, track price code **T1** on the tracks
- Left alone: 3 tracks carry their own genre on purpose, _Night Train_,
  _Blue in Green (Live)_ and _Solar_

Nothing is changed yet. Shall I apply it?

</Assistant>
</Conversation>

Or ask it another way:

- "Change the subgenre to Deep House on these 15 EPs"
- "Put label Y's albums released before 2020 on price code B2"
- "Which price codes and subgenres can I use?"

## Open a new territory for a whole label

<Conversation>
<You>

We're selling in the UK now: add the territory to label Y's rights.

</You>
<Assistant>

Label Y has **214 products**. The UK will be added to their rights; the other
territories stay as they are. Confirm?

</Assistant>
</Conversation>

Or ask it another way:

- "Remove Japan from this album's rights"
- "Add Switzerland and Liechtenstein to the whole contract X catalogue"
- "Where can this single be sold today?"

## Move a catalogue to the right contract

An ingestion landed on the wrong contract? Re-attach it without losing the
history.

<Conversation>
<You>

Attach label Y and its products to contract X from today.

</You>
<Assistant>

**Label Y and 214 products** will be attached to contract X from 2026-09-23.
The previous attachment is kept as history; rights, offers and deliveries are
not touched. Confirm?

</Assistant>
</Conversation>

Or ask it another way:

- "Move these 8 products to contract Z, without their label"
- "Attach label Y to contract X from January 1st, but keep its catalogue where it is"
- "Attach these music videos to contract X"

## Find and fix ISRC conflicts

An ISRC locks six fields across every release of a recording: performer,
featuring, remixer, title, ISWC and parental advisory. When they drift apart,
Labelcamp flags the conflict and blocks validation until it's resolved.

<Conversation>
<You>

Which ISRCs on Northern Lights Records conflict between their references?

</You>
<Assistant>

**4 ISRCs** conflict, on 11 releases. The main one:

- **FRXXX2600123**, _Halcyon_: the featuring artist is missing on the
  compilation _Winter Sessions_ and on the single edit.

Want me to align them on the album version?

</Assistant>
</Conversation>

Or ask it another way:

- "Are there ISRC conflicts on this album?"
- "Align the title of FRXXX2600123 on the single version everywhere"
- "Check contract X for ISRC conflicts"

## Also in one sentence

> Tag all of this artist's Christmas releases with "holiday"

> Deactivate radio on this catalogue, streaming only from now on

> Set the YouTube policy to monetize on this batch

> Import these Spotify and Apple artist IDs

> Archive these 12 products

> Export our full tracklisting as a CSV

## Good to know

- **There is no undo yet.** Try two or three releases, check them in
  Labelcamp, then scale up.
- **Archiving is not a takedown.** It ends the distribution of a product; the
  takedown itself is a delivery made in Labelcamp.
- **Artist IDs** are only added: an ID that differs from the one stored is
  reported, never overwritten.
- **Exports** run in the background; the download link arrives by email.
