# GS1 UPC Certificate

**URL:** <https://sellersasksellers.com/t/gs1-upc-certificate/4539>\
**Category:** Listings and Variations\
**Tags:** gtin, code8572\
**Created:** [August 10, 2024, 3:12am UTC](https://sellersasksellers.com/t/gs1-upc-certificate/4539 "2024-08-10T03:12:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![VTR](https://sellersasksellers.com/user_avatar/sellersasksellers.com/vtr/32/14279_2.png) [@VTR](https://sellersasksellers.com/u/VTR)\
**Post date:** [August 10, 2024, 3:12am UTC](https://sellersasksellers.com/t/gs1-upc-certificate/4539/1 "2024-08-10T03:12:50Z")

</div>

So I have limited experience with GS1 but last time I checked the UPC prefix number of digits determined the numbers covered right? We have a prefix of 81001234 meaning 81001234000-81001234999 and the corresponding check digit are registered to us correct??  
Amazon SS is saying only one UPC is listed because they see the GLN# on the certificate. Has anyone dealt with this level of stupid before, or am I the one who needs to stop feeling intellectually superior?

We are dealing with an 8572 code on our file upload.

 ![8572](https://sellersasksellers.com/uploads/default/original/2X/7/73950dfb466b32f02fe13c46254b524493da25c9.jpeg)

---

<div class="post-metadata">

**Author:** ![Lost\_My\_Marbles](https://sellersasksellers.com/user_avatar/sellersasksellers.com/lost_my_marbles/32/2919_2.png) [@Lost\_My\_Marbles](https://sellersasksellers.com/u/Lost_My_Marbles)\
**Post date:** [August 10, 2024, 3:21am UTC](https://sellersasksellers.com/t/gs1-upc-certificate/4539/2 "2024-08-10T03:21:50Z")

</div>

> [@VTR](#):
>
> So I have limited experience with GS1 but last time I checked the UPC prefix number of digits determined the numbers covered right?

Yes

> [@VTR](#):
>
> We have a prefix of 81001234 meaning 81001234000-81001234999 and the corresponding check digit are registered to us correct??

Yes … if you paid for that many

> [@VTR](#):
>
> Amazon SS is saying only one UPC is listed because they see the GLN# on the certificate.

That employee (rep) doesn’t know how to read the certificate for what it means (stands for).

> [@VTR](#):
>
> Has anyone dealt with this level of stupid before, or am I the one who needs to stop feeling intellectually superior?

Yes … but not over the GS1 certificate … but instead over brand name hijacking …

Definitely would ask to be escalated to a superior.

---

<div class="post-metadata">

**Author:** ![Chimanimani](https://sellersasksellers.com/user_avatar/sellersasksellers.com/chimanimani/32/1899_2.png) [@Chimanimani](https://sellersasksellers.com/u/Chimanimani)\
**Post date:** [August 10, 2024, 6:06am UTC](https://sellersasksellers.com/t/gs1-upc-certificate/4539/3 "2024-08-10T06:06:47Z")

</div>

I just checked my certificate

GS1 Company Prefix is 7 digits  
UPC Company Prefix is 6 digits

I own all 10,000

I see yours is 8 digits, but you are claiming 1,000

So yes, I would agree with you. (that is how it is read)

Since I am grandfathered in (my original issue date is 08/08/1990)  
GS1 gives me limited access in their website.

But I was under the assumption that those that “rent” get full access, in that you can enter data specific for a product on the website.

I do not know, maybe since you own only a partial of the full prefix, this is the issue.

---

<div class="post-metadata">

**Author:** ![Chimanimani](https://sellersasksellers.com/user_avatar/sellersasksellers.com/chimanimani/32/1899_2.png) [@Chimanimani](https://sellersasksellers.com/u/Chimanimani)\
**Post date:** [August 10, 2024, 6:24am UTC](https://sellersasksellers.com/t/gs1-upc-certificate/4539/4 "2024-08-10T06:24:07Z")

</div>

Is it possible that you have already used the UPC that is giving you the 8572 error.

As well, someone could have used your UPC code without your knowledge, thus when you enter it conflicts and gives an error.

maybe the check digit is wrong?

I made an excel sheet that can calc the check digit for any number of UPCs needed, if you need

---

<div class="post-metadata">

**Author:** ![VTR](https://sellersasksellers.com/user_avatar/sellersasksellers.com/vtr/32/14279_2.png) [@VTR](https://sellersasksellers.com/u/VTR)\
**Post date:** [August 10, 2024, 4:20pm UTC](https://sellersasksellers.com/t/gs1-upc-certificate/4539/5 "2024-08-10T16:20:48Z")

</div>

> [@Chimanimani](#):
>
> Is it possible that you have already used the UPC that is giving you the 8572 error.

Nope, freshly cut off the UPC stack this week.

---

<div class="post-metadata">

**Author:** ![VitRhea](https://sellersasksellers.com/letter_avatar_proxy/v4/letter/v/d07c76/32.png) [@VitRhea](https://sellersasksellers.com/u/VitRhea)\
**Post date:** [August 12, 2024, 1:22pm UTC](https://sellersasksellers.com/t/gs1-upc-certificate/4539/6 "2024-08-12T13:22:14Z")

</div>

> [@Chimanimani](#):
>
> I made an excel sheet that can calc the check digit for any number of UPCs needed, if you need

[GS1 has one as well](https://www.gs1.org/services/check-digit-calculator)
