The short answer: UPC is a common name for the product code identifying an entire single, EP or album. An individual recording within the release has a different identifier: its ISRC. When you deliver music through creator, the product code is created automatically.
Why a music release needs a product code
A UPC, or Universal Product Code, is required for a release, whether it is a one-track single or a twenty-track album. Major platforms such as Spotify, Apple Music and Russia’s Yandex Music need it to accept the release. This is an infrastructure requirement: the code lets a platform group the tracks into a single product.
The good news is that you do not need to obtain it yourself. Your distributor assigns it automatically. Here is how the code works in practice.
When you upload through a distributor, a UPC is assigned automatically. You do not need to register it separately with GS1.
Scenario 1: a release without a UPC
In practice, this rarely happens because distributors generate the code during upload. If you tried to bypass that step, the platform would reject the delivery: it could not create an album or single page in its system.
Scenario 2: reissuing the same album under a new title
A new release title means a new UPC, even if the track list stays the same. The old code remains linked to the previous edition. Individual tracks can retain their ISRCs because they are the same recordings, while the release as a product receives a new identifier.
Scenario 3: a deluxe edition with bonus tracks
The same principle applies. A deluxe album with additional tracks is a different product, so it receives its own UPC, separate from the original edition. The original release and its code remain in the catalog unchanged.
Scenario 4: using one UPC for two different releases
This is where manual intervention can cause problems. Platforms can interpret reusing a UPC as spam or data substitution and block both deliveries. Each distinct single, EP or album needs its own unique code.
How a UPC differs from an ISRC
The codes are easy to confuse, but the distinction is straightforward:
- ISRC identifies one sound recording. A ten-song album has ten different ISRCs.
- UPC identifies the whole release as a product. That same ten-track album has one UPC.
An ISRC answers, “Which recording is this?” A UPC answers, “Which album or single is this, and what does it contain?”
A ten-track album has ten separate ISRCs, one for each recording, and a single UPC for the complete release.
How you get a code at no extra charge
You can register independently through the GS1 organization in your territory. The rights holder obtains a prefix and manages its own range of codes. Fees and rules vary by country and change over time, so check the local GS1 organization’s official website. This usually makes more sense for a label with an ongoing catalog than for one single.
If you release one or two projects per quarter, independent registration may be an unnecessary expense. When delivering through creator, the distribution partner can assign a code if the release does not already have one. The code appears during release processing; timing and availability depend on the partner and platform requirements.
Scenario 5: a release by several artists
A featured collaboration, split album or joint project still receives one UPC for the entire product, regardless of how many artists appear in the metadata. Artist attribution and royalty splits are handled through release details and agreements rather than the code itself. Unlike reusing one code for different releases, this is one product with several rights holders.
What listeners see
Listeners generally do not see the UPC or ISRC directly on a track page. They are identifiers used by platforms and distributors for catalog management. Listeners see the result: an album with the right tracks in the right order, separate from the artist’s other releases and editions. Duplicate albums or mixed-up editions in a platform catalog often point to UPC problems in the original delivery.