Create a catalogue-number convention for your label

Choose a simple convention

A fictional label might use BOLT-001 for a product and BOLT-002 for the next. Define the prefix, sequence, formats and approval owner. Do not insert a real private project code into public materials without checking whether it is intended to be public.

Map identifiers by level

Record the internal catalogue number beside the product and its UPC where assigned. Link the product’s track rows to their ISRCs. IFPI distinguishes recording identity from product identifiers. One internal label number should not be copied into an ISRC field merely because it looks unique.

Manage revisions deliberately

Define how alternate products and editions are represented without changing the underlying recording identity by assumption. Keep a dated register and avoid reusing a retired number for an unrelated product. Record corrections rather than silently overwriting earlier assignments.

Use the reference in operations

Include the internal number in appropriate work briefs and private reports while supplying the actual identifier required by a destination. Check the mapping before import or reconciliation. This guide assigns no live codes, changes no store metadata and does not certify a universal industry numbering format.

Sources and review

Reviewed 4 November 2026. Platform requirements and plan terms can change. Examples are planning aids, not a promise of account access, release acceptance or earnings.

• IFPI identifier distinctions
• DistroBolt product versus recording codes

Continue your release planning

• Audit a label catalogue before moving distributors
• Prepare artist royalty reports from a label ledger
• Keep label, artist and payout identities separate

Ask the DistroBolt team about your release. Send a concise question and release reference; never send account passwords or verification codes.