Seller Forums
user profile
Seller_8oxW2B1GQc66h

Community Manager escalation requested – Case 13165119802 – GS1 GTIN misuse unresolved after 5+ weeks

o,

I am requesting Community Manager assistance with Amazon Seller Support case 13165119802.

This case has been open since 11 August and concerns 15 Hayes Meadow GTINs issued under our GS1 UK Company Prefix 5065022564.

Amazon has already confirmed that:

Hayes Meadow is the verified brand owner;

Hayes Farm owns the relevant GS1 GTINs;

the affected EANs are linked to existing Amazon catalogue entries associated with an unrelated brand;

this is a GTIN matching conflict, not a rebrand request.

Amazon’s specialist team granted matching exemptions for the exact 15 SKU/GTIN combinations.

We were then instructed to use:

the exact approved SKUs;

the correct seller account / MCID;

the GTINs in 14-digit format.

We have now followed those instructions exactly.

The result is still:

19 total SKUs

4 ready to submit

15 action required

Amazon continues to force our GTINs back onto the unrelated existing ASINs.

Example:

SKU: SK16G

GTIN: 05065022564218

Amazon still links it to: B0GQ2QKZ1Z

Seller Central reports:

“Your bar code 05065022564218 is already linked to product B0GQ2QKZ1Z which seems different to the product you are trying to list.”

GS1 UK has also reviewed the issue and advised that it appears to be a GTIN misuse issue. They have issued us with a contingency allocation while allowing us to retain our original prefix and GTINs.

However, our original GTINs are already printed on our product packaging and remain the correct identifiers for these Hayes Meadow products.

We have now spent more than six weeks supplying every document requested and following every technical instruction provided by Seller Support, but the underlying catalogue conflict remains.

Could a Community Manager please review case 13165119802 and escalate it to the appropriate catalogue / GTIN technical team?

We need the original Hayes Meadow GTINs to validate correctly under our brand, not another workaround.

Thank you.

75 views
14 replies
Tags:Brand Registry, Brand Stores
10
Reply
user profile
Seller_8oxW2B1GQc66h

Community Manager escalation requested – Case 13165119802 – GS1 GTIN misuse unresolved after 5+ weeks

o,

I am requesting Community Manager assistance with Amazon Seller Support case 13165119802.

This case has been open since 11 August and concerns 15 Hayes Meadow GTINs issued under our GS1 UK Company Prefix 5065022564.

Amazon has already confirmed that:

Hayes Meadow is the verified brand owner;

Hayes Farm owns the relevant GS1 GTINs;

the affected EANs are linked to existing Amazon catalogue entries associated with an unrelated brand;

this is a GTIN matching conflict, not a rebrand request.

Amazon’s specialist team granted matching exemptions for the exact 15 SKU/GTIN combinations.

We were then instructed to use:

the exact approved SKUs;

the correct seller account / MCID;

the GTINs in 14-digit format.

We have now followed those instructions exactly.

The result is still:

19 total SKUs

4 ready to submit

15 action required

Amazon continues to force our GTINs back onto the unrelated existing ASINs.

Example:

SKU: SK16G

GTIN: 05065022564218

Amazon still links it to: B0GQ2QKZ1Z

Seller Central reports:

“Your bar code 05065022564218 is already linked to product B0GQ2QKZ1Z which seems different to the product you are trying to list.”

GS1 UK has also reviewed the issue and advised that it appears to be a GTIN misuse issue. They have issued us with a contingency allocation while allowing us to retain our original prefix and GTINs.

However, our original GTINs are already printed on our product packaging and remain the correct identifiers for these Hayes Meadow products.

We have now spent more than six weeks supplying every document requested and following every technical instruction provided by Seller Support, but the underlying catalogue conflict remains.

Could a Community Manager please review case 13165119802 and escalate it to the appropriate catalogue / GTIN technical team?

We need the original Hayes Meadow GTINs to validate correctly under our brand, not another workaround.

Thank you.

Tags:Brand Registry, Brand Stores
10
75 views
14 replies
Reply
14 replies
user profile
Seller_hOZNPw7G8FIjl

You needed to tag some moderators, otherwise they might not see this

@Billy_Amazon @Amyy_Amazon @Indy_Amazon @Roberto_Amazon @KJ_Amazon

10
user profile
Seller_8oxW2B1GQc66h

Forum follow-up for 25 September

@Indy_Amazon @Roberto_Amazon @Josh_Amazon @Glenn_Amazon

Could an Amazon Community Manager please acknowledge this escalation and take ownership of case 13165119802?

It is now 25 September. This case has been open since 11 August, and we are still unable to list 15 Hayes Meadow products using our own GS1 GTINs.

We have followed the specialist team's latest instructions, using the exact approved MCID, SKUs and 14-digit GTINs. All 15 products continue to fail validation.

Despite providing the requested evidence and reporting that the exemptions still do not work, we have received no substantive resolution.

Our original GTINs are already printed on our product packaging. GS1 UK has also reviewed the situation and issued a contingency allocation, but replacing the original numbers does not address the underlying Amazon catalogue problem.

Could a Community Manager please escalate this to the appropriate technical team and provide an update on who is handling the case and what happens next?

Thank you.

Graham Macklin

Hayes Meadow

00
user profile
Christine_Amazon

Hi @Seller_8oxW2B1GQc66h

At this time, the case is still being reviewed by the appropriate team. Since the investigation is ongoing, we’ll need to allow them to complete their review before any additional steps can be taken.

For now, please keep the case open and wait for their response.

Once the review is complete, if you still have questions or feel that something was not fully addressed, please feel free to return to the forums with the outcome, and we’ll be happy to take another look.

Christine 🍂☕

00
user profile
Seller_8oxW2B1GQc66h

Hi

@Christine_Amazon

Thank you again for confirming that case 13165119802 was being reviewed by the appropriate team.

We have kept the case open as requested, but we have now had no substantive update from Seller Support since 18 September, and today is 3 October.

The case itself has been open since 11 August.

The 15 affected Hayes Meadow GTINs still cannot be listed successfully, despite Amazon having:

- confirmed our ownership of the Hayes Meadow brand and relevant GS1 GTINs;

- granted matching exemptions;

- instructed us to use the exact approved MCID, SKUs and 14-digit GTINs; and

- acknowledged that the exemptions were still not functioning correctly.

We followed those instructions exactly and all 15 products continued to fail validation.

Could you please check with the reviewing team and let us know whether there has been any progress, who currently owns the technical review, and what the next step is?

We would be very grateful if you could continue monitoring this escalation until the technical issue is actually resolved.

Many thanks,

Graham Macklin

Hayes Meadow

00
user profile
Seller_8oxW2B1GQc66h

Hi @Christine_Amazon

I am following up again as unfortunately there has still been no substantive update or resolution.

Tomorrow marks 56 days since case 13165119802 was opened on 11 August, and Seller Support has provided no substantive update since 18 September.

You previously confirmed that the case was being reviewed by the appropriate team, but the 15 Hayes Meadow GTINs remain unusable and we have received no indication of what action is actually being taken.

@Indy_Amazon @Roberto_Amazon

Tomorrow marks 56 days since case 13165119802 was opened on 11 August

Could one of you please assist Christine in obtaining a concrete update from the technical team and confirm who currently owns this escalation?

We have supplied every document requested, followed the exact approved MCID/SKU/14-digit GTIN instructions, and demonstrated that all 15 exemptions still fail.

We need a technical resolution, not another request to wait indefinitely.

Many thanks,

Graham Macklin

Hayes Meadow

00
user profile
Abbie_Amazon

@Seller_8oxW2B1GQc66h, Thank you for your patience and persistence on this matter.

We can confirm your case 13165119802 is actively being worked on by the appropriate team. We are aware that the steps taken so far have not yet resolved the listing issue, and this is being addressed.

In the meantime, please continue to keep your case open and respond to any communications from the support team directly through Seller Central.

We appreciate your patience and are committed to getting this resolved for you.

-Abbie

00
user profile
Seller_8oxW2B1GQc66h

**Update – 29 October – Case 13165119802 still unresolved after 79 days**

Amazon has again confirmed that matching exemptions have been granted for our 15 Hayes Meadow GTIN/SKU combinations.

We retested the exact unchanged spreadsheet on 23 October using the exact approved SKUs and 14-digit GTINs.

@Indy_Amazon @Roberto_Amazon

The result remains:

**19 total SKUs

4 ready

15 action required**

Every affected GTIN is still being matched to the same unrelated catalogue ASIN.

This is no longer simply a support delay. It is now creating direct commercial loss.

The limited Hayes Meadow range we currently have live on Amazon is producing increasing daily orders. We have a much larger range ready to sell, but 15 genuine Hayes Meadow variants remain blocked by this unresolved catalogue issue.

Amazon has repeatedly told us that the exemptions are granted and the problem is fixed, but Amazon’s own validator repeatedly demonstrates that it is not.

Could a Community Manager please escalate case **13165119802** again and request a named technical owner / internal escalation reference from the catalogue or GTIN team?

After 79 days, we need a technical resolution and completion date rather than another request to wait for the specialist team.

Thank you.

Graham Macklin

Hayes Meadow

00
user profile
Seller_8oxW2B1GQc66h

Hi @Abbie_Amazon

Thank you for your earlier update.

I am following up because unfortunately the issue is still unresolved.

Since your message, Amazon has again confirmed that matching exemptions have been granted for the 15 affected Hayes Meadow GTIN/SKU combinations.

We then retested the exact unchanged spreadsheet on 23 October using the exact approved SKUs and 14-digit GTINs.

The result is still:

**19 total SKUs

4 ready to submit

15 action required**

All 15 affected GTINs are still being matched to the same unrelated Amazon catalogue ASINs.

At this stage, it is **not acceptable for us to keep being told that the exemptions have been granted or that the issue has been fixed when Amazon’s own validator repeatedly proves that it has not been fixed.**

This case has now been open since **11 August**.

We have supplied every document requested, followed every technical instruction, repeated the validation tests several times, and each time the same 15 errors remain.

The delay is now causing direct commercial loss. Our currently limited Amazon range is generating increasing daily orders, while 15 genuine Hayes Meadow variants remain blocked from sale because this catalogue issue is still unresolved.

@Christine_Amazon

Could one of you please obtain a substantive technical update on case **13165119802**, including:

- who currently owns the technical resolution;

- what root cause has been identified;

- what corrective action is actually being taken;

- why Amazon has repeatedly confirmed the exemptions are granted when they are still not functioning; and

- when the issue is expected to be fully resolved.

We now need a technical resolution and a completion date, not another confirmation that the case is still being worked on.

Many thanks,

Graham Macklin

Hayes Meadow

00
user profile
Christine_Amazon

Hi @Seller_8oxW2B1GQc66h

I was checking that the team in charge has been actively responding to you.

Please follow up on the case ID 13165119802.

Christine🦃🍂☕️

00
user profile
Seller_FwNZ3OOTo1Rls

If GS1 has confirmed the contingency barcodes can be used for these products, I’d personally be tempted to use them to get the launch moving.

Once the listings are accepted, you could cover the original barcodes with replacement labels on your existing stock, then update the packaging artwork for future batches so you don’t have to keep relabelling.

I appreciate that doesn’t fix the original issue, but after this much delay, I’d be weighing the cost of relabelling against keeping the launch on hold.

Is the printed packaging the main reason you haven’t used the contingency barcodes, or is there another complication?

00
Follow this discussion to be notified of new activity
user profile
Seller_8oxW2B1GQc66h

Community Manager escalation requested – Case 13165119802 – GS1 GTIN misuse unresolved after 5+ weeks

o,

I am requesting Community Manager assistance with Amazon Seller Support case 13165119802.

This case has been open since 11 August and concerns 15 Hayes Meadow GTINs issued under our GS1 UK Company Prefix 5065022564.

Amazon has already confirmed that:

Hayes Meadow is the verified brand owner;

Hayes Farm owns the relevant GS1 GTINs;

the affected EANs are linked to existing Amazon catalogue entries associated with an unrelated brand;

this is a GTIN matching conflict, not a rebrand request.

Amazon’s specialist team granted matching exemptions for the exact 15 SKU/GTIN combinations.

We were then instructed to use:

the exact approved SKUs;

the correct seller account / MCID;

the GTINs in 14-digit format.

We have now followed those instructions exactly.

The result is still:

19 total SKUs

4 ready to submit

15 action required

Amazon continues to force our GTINs back onto the unrelated existing ASINs.

Example:

SKU: SK16G

GTIN: 05065022564218

Amazon still links it to: B0GQ2QKZ1Z

Seller Central reports:

“Your bar code 05065022564218 is already linked to product B0GQ2QKZ1Z which seems different to the product you are trying to list.”

GS1 UK has also reviewed the issue and advised that it appears to be a GTIN misuse issue. They have issued us with a contingency allocation while allowing us to retain our original prefix and GTINs.

However, our original GTINs are already printed on our product packaging and remain the correct identifiers for these Hayes Meadow products.

We have now spent more than six weeks supplying every document requested and following every technical instruction provided by Seller Support, but the underlying catalogue conflict remains.

Could a Community Manager please review case 13165119802 and escalate it to the appropriate catalogue / GTIN technical team?

We need the original Hayes Meadow GTINs to validate correctly under our brand, not another workaround.

Thank you.

75 views
14 replies
Tags:Brand Registry, Brand Stores
10
Reply
user profile
Seller_8oxW2B1GQc66h

Community Manager escalation requested – Case 13165119802 – GS1 GTIN misuse unresolved after 5+ weeks

o,

I am requesting Community Manager assistance with Amazon Seller Support case 13165119802.

This case has been open since 11 August and concerns 15 Hayes Meadow GTINs issued under our GS1 UK Company Prefix 5065022564.

Amazon has already confirmed that:

Hayes Meadow is the verified brand owner;

Hayes Farm owns the relevant GS1 GTINs;

the affected EANs are linked to existing Amazon catalogue entries associated with an unrelated brand;

this is a GTIN matching conflict, not a rebrand request.

Amazon’s specialist team granted matching exemptions for the exact 15 SKU/GTIN combinations.

We were then instructed to use:

the exact approved SKUs;

the correct seller account / MCID;

the GTINs in 14-digit format.

We have now followed those instructions exactly.

The result is still:

19 total SKUs

4 ready to submit

15 action required

Amazon continues to force our GTINs back onto the unrelated existing ASINs.

Example:

SKU: SK16G

GTIN: 05065022564218

Amazon still links it to: B0GQ2QKZ1Z

Seller Central reports:

“Your bar code 05065022564218 is already linked to product B0GQ2QKZ1Z which seems different to the product you are trying to list.”

GS1 UK has also reviewed the issue and advised that it appears to be a GTIN misuse issue. They have issued us with a contingency allocation while allowing us to retain our original prefix and GTINs.

However, our original GTINs are already printed on our product packaging and remain the correct identifiers for these Hayes Meadow products.

We have now spent more than six weeks supplying every document requested and following every technical instruction provided by Seller Support, but the underlying catalogue conflict remains.

Could a Community Manager please review case 13165119802 and escalate it to the appropriate catalogue / GTIN technical team?

We need the original Hayes Meadow GTINs to validate correctly under our brand, not another workaround.

Thank you.

Tags:Brand Registry, Brand Stores
10
75 views
14 replies
Reply
user profile

Community Manager escalation requested – Case 13165119802 – GS1 GTIN misuse unresolved after 5+ weeks

by Seller_8oxW2B1GQc66h

o,

I am requesting Community Manager assistance with Amazon Seller Support case 13165119802.

This case has been open since 11 August and concerns 15 Hayes Meadow GTINs issued under our GS1 UK Company Prefix 5065022564.

Amazon has already confirmed that:

Hayes Meadow is the verified brand owner;

Hayes Farm owns the relevant GS1 GTINs;

the affected EANs are linked to existing Amazon catalogue entries associated with an unrelated brand;

this is a GTIN matching conflict, not a rebrand request.

Amazon’s specialist team granted matching exemptions for the exact 15 SKU/GTIN combinations.

We were then instructed to use:

the exact approved SKUs;

the correct seller account / MCID;

the GTINs in 14-digit format.

We have now followed those instructions exactly.

The result is still:

19 total SKUs

4 ready to submit

15 action required

Amazon continues to force our GTINs back onto the unrelated existing ASINs.

Example:

SKU: SK16G

GTIN: 05065022564218

Amazon still links it to: B0GQ2QKZ1Z

Seller Central reports:

“Your bar code 05065022564218 is already linked to product B0GQ2QKZ1Z which seems different to the product you are trying to list.”

GS1 UK has also reviewed the issue and advised that it appears to be a GTIN misuse issue. They have issued us with a contingency allocation while allowing us to retain our original prefix and GTINs.

However, our original GTINs are already printed on our product packaging and remain the correct identifiers for these Hayes Meadow products.

We have now spent more than six weeks supplying every document requested and following every technical instruction provided by Seller Support, but the underlying catalogue conflict remains.

Could a Community Manager please review case 13165119802 and escalate it to the appropriate catalogue / GTIN technical team?

We need the original Hayes Meadow GTINs to validate correctly under our brand, not another workaround.

Thank you.

Tags:Brand Registry, Brand Stores
10
75 views
14 replies
Reply
14 replies
14 replies
Quick filters
Sort by
user profile
Seller_hOZNPw7G8FIjl

You needed to tag some moderators, otherwise they might not see this

@Billy_Amazon @Amyy_Amazon @Indy_Amazon @Roberto_Amazon @KJ_Amazon

10
user profile
Seller_8oxW2B1GQc66h

Forum follow-up for 25 September

@Indy_Amazon @Roberto_Amazon @Josh_Amazon @Glenn_Amazon

Could an Amazon Community Manager please acknowledge this escalation and take ownership of case 13165119802?

It is now 25 September. This case has been open since 11 August, and we are still unable to list 15 Hayes Meadow products using our own GS1 GTINs.

We have followed the specialist team's latest instructions, using the exact approved MCID, SKUs and 14-digit GTINs. All 15 products continue to fail validation.

Despite providing the requested evidence and reporting that the exemptions still do not work, we have received no substantive resolution.

Our original GTINs are already printed on our product packaging. GS1 UK has also reviewed the situation and issued a contingency allocation, but replacing the original numbers does not address the underlying Amazon catalogue problem.

Could a Community Manager please escalate this to the appropriate technical team and provide an update on who is handling the case and what happens next?

Thank you.

Graham Macklin

Hayes Meadow

00
user profile
Christine_Amazon

Hi @Seller_8oxW2B1GQc66h

At this time, the case is still being reviewed by the appropriate team. Since the investigation is ongoing, we’ll need to allow them to complete their review before any additional steps can be taken.

For now, please keep the case open and wait for their response.

Once the review is complete, if you still have questions or feel that something was not fully addressed, please feel free to return to the forums with the outcome, and we’ll be happy to take another look.

Christine 🍂☕

00
user profile
Seller_8oxW2B1GQc66h

Hi

@Christine_Amazon

Thank you again for confirming that case 13165119802 was being reviewed by the appropriate team.

We have kept the case open as requested, but we have now had no substantive update from Seller Support since 18 September, and today is 3 October.

The case itself has been open since 11 August.

The 15 affected Hayes Meadow GTINs still cannot be listed successfully, despite Amazon having:

- confirmed our ownership of the Hayes Meadow brand and relevant GS1 GTINs;

- granted matching exemptions;

- instructed us to use the exact approved MCID, SKUs and 14-digit GTINs; and

- acknowledged that the exemptions were still not functioning correctly.

We followed those instructions exactly and all 15 products continued to fail validation.

Could you please check with the reviewing team and let us know whether there has been any progress, who currently owns the technical review, and what the next step is?

We would be very grateful if you could continue monitoring this escalation until the technical issue is actually resolved.

Many thanks,

Graham Macklin

Hayes Meadow

00
user profile
Seller_8oxW2B1GQc66h

Hi @Christine_Amazon

I am following up again as unfortunately there has still been no substantive update or resolution.

Tomorrow marks 56 days since case 13165119802 was opened on 11 August, and Seller Support has provided no substantive update since 18 September.

You previously confirmed that the case was being reviewed by the appropriate team, but the 15 Hayes Meadow GTINs remain unusable and we have received no indication of what action is actually being taken.

@Indy_Amazon @Roberto_Amazon

Tomorrow marks 56 days since case 13165119802 was opened on 11 August

Could one of you please assist Christine in obtaining a concrete update from the technical team and confirm who currently owns this escalation?

We have supplied every document requested, followed the exact approved MCID/SKU/14-digit GTIN instructions, and demonstrated that all 15 exemptions still fail.

We need a technical resolution, not another request to wait indefinitely.

Many thanks,

Graham Macklin

Hayes Meadow

00
user profile
Abbie_Amazon

@Seller_8oxW2B1GQc66h, Thank you for your patience and persistence on this matter.

We can confirm your case 13165119802 is actively being worked on by the appropriate team. We are aware that the steps taken so far have not yet resolved the listing issue, and this is being addressed.

In the meantime, please continue to keep your case open and respond to any communications from the support team directly through Seller Central.

We appreciate your patience and are committed to getting this resolved for you.

-Abbie

00
user profile
Seller_8oxW2B1GQc66h

**Update – 29 October – Case 13165119802 still unresolved after 79 days**

Amazon has again confirmed that matching exemptions have been granted for our 15 Hayes Meadow GTIN/SKU combinations.

We retested the exact unchanged spreadsheet on 23 October using the exact approved SKUs and 14-digit GTINs.

@Indy_Amazon @Roberto_Amazon

The result remains:

**19 total SKUs

4 ready

15 action required**

Every affected GTIN is still being matched to the same unrelated catalogue ASIN.

This is no longer simply a support delay. It is now creating direct commercial loss.

The limited Hayes Meadow range we currently have live on Amazon is producing increasing daily orders. We have a much larger range ready to sell, but 15 genuine Hayes Meadow variants remain blocked by this unresolved catalogue issue.

Amazon has repeatedly told us that the exemptions are granted and the problem is fixed, but Amazon’s own validator repeatedly demonstrates that it is not.

Could a Community Manager please escalate case **13165119802** again and request a named technical owner / internal escalation reference from the catalogue or GTIN team?

After 79 days, we need a technical resolution and completion date rather than another request to wait for the specialist team.

Thank you.

Graham Macklin

Hayes Meadow

00
user profile
Seller_8oxW2B1GQc66h

Hi @Abbie_Amazon

Thank you for your earlier update.

I am following up because unfortunately the issue is still unresolved.

Since your message, Amazon has again confirmed that matching exemptions have been granted for the 15 affected Hayes Meadow GTIN/SKU combinations.

We then retested the exact unchanged spreadsheet on 23 October using the exact approved SKUs and 14-digit GTINs.

The result is still:

**19 total SKUs

4 ready to submit

15 action required**

All 15 affected GTINs are still being matched to the same unrelated Amazon catalogue ASINs.

At this stage, it is **not acceptable for us to keep being told that the exemptions have been granted or that the issue has been fixed when Amazon’s own validator repeatedly proves that it has not been fixed.**

This case has now been open since **11 August**.

We have supplied every document requested, followed every technical instruction, repeated the validation tests several times, and each time the same 15 errors remain.

The delay is now causing direct commercial loss. Our currently limited Amazon range is generating increasing daily orders, while 15 genuine Hayes Meadow variants remain blocked from sale because this catalogue issue is still unresolved.

@Christine_Amazon

Could one of you please obtain a substantive technical update on case **13165119802**, including:

- who currently owns the technical resolution;

- what root cause has been identified;

- what corrective action is actually being taken;

- why Amazon has repeatedly confirmed the exemptions are granted when they are still not functioning; and

- when the issue is expected to be fully resolved.

We now need a technical resolution and a completion date, not another confirmation that the case is still being worked on.

Many thanks,

Graham Macklin

Hayes Meadow

00
user profile
Christine_Amazon

Hi @Seller_8oxW2B1GQc66h

I was checking that the team in charge has been actively responding to you.

Please follow up on the case ID 13165119802.

Christine🦃🍂☕️

00
user profile
Seller_FwNZ3OOTo1Rls

If GS1 has confirmed the contingency barcodes can be used for these products, I’d personally be tempted to use them to get the launch moving.

Once the listings are accepted, you could cover the original barcodes with replacement labels on your existing stock, then update the packaging artwork for future batches so you don’t have to keep relabelling.

I appreciate that doesn’t fix the original issue, but after this much delay, I’d be weighing the cost of relabelling against keeping the launch on hold.

Is the printed packaging the main reason you haven’t used the contingency barcodes, or is there another complication?

00
Follow this discussion to be notified of new activity
user profile
Seller_hOZNPw7G8FIjl

You needed to tag some moderators, otherwise they might not see this

@Billy_Amazon @Amyy_Amazon @Indy_Amazon @Roberto_Amazon @KJ_Amazon

10
user profile
Seller_hOZNPw7G8FIjl

You needed to tag some moderators, otherwise they might not see this

@Billy_Amazon @Amyy_Amazon @Indy_Amazon @Roberto_Amazon @KJ_Amazon

10
Reply
user profile
Seller_8oxW2B1GQc66h

Forum follow-up for 25 September

@Indy_Amazon @Roberto_Amazon @Josh_Amazon @Glenn_Amazon

Could an Amazon Community Manager please acknowledge this escalation and take ownership of case 13165119802?

It is now 25 September. This case has been open since 11 August, and we are still unable to list 15 Hayes Meadow products using our own GS1 GTINs.

We have followed the specialist team's latest instructions, using the exact approved MCID, SKUs and 14-digit GTINs. All 15 products continue to fail validation.

Despite providing the requested evidence and reporting that the exemptions still do not work, we have received no substantive resolution.

Our original GTINs are already printed on our product packaging. GS1 UK has also reviewed the situation and issued a contingency allocation, but replacing the original numbers does not address the underlying Amazon catalogue problem.

Could a Community Manager please escalate this to the appropriate technical team and provide an update on who is handling the case and what happens next?

Thank you.

Graham Macklin

Hayes Meadow

00
user profile
Seller_8oxW2B1GQc66h

Forum follow-up for 25 September

@Indy_Amazon @Roberto_Amazon @Josh_Amazon @Glenn_Amazon

Could an Amazon Community Manager please acknowledge this escalation and take ownership of case 13165119802?

It is now 25 September. This case has been open since 11 August, and we are still unable to list 15 Hayes Meadow products using our own GS1 GTINs.

We have followed the specialist team's latest instructions, using the exact approved MCID, SKUs and 14-digit GTINs. All 15 products continue to fail validation.

Despite providing the requested evidence and reporting that the exemptions still do not work, we have received no substantive resolution.

Our original GTINs are already printed on our product packaging. GS1 UK has also reviewed the situation and issued a contingency allocation, but replacing the original numbers does not address the underlying Amazon catalogue problem.

Could a Community Manager please escalate this to the appropriate technical team and provide an update on who is handling the case and what happens next?

Thank you.

Graham Macklin

Hayes Meadow

00
Reply
user profile
Christine_Amazon

Hi @Seller_8oxW2B1GQc66h

At this time, the case is still being reviewed by the appropriate team. Since the investigation is ongoing, we’ll need to allow them to complete their review before any additional steps can be taken.

For now, please keep the case open and wait for their response.

Once the review is complete, if you still have questions or feel that something was not fully addressed, please feel free to return to the forums with the outcome, and we’ll be happy to take another look.

Christine 🍂☕

00
user profile
Christine_Amazon

Hi @Seller_8oxW2B1GQc66h

At this time, the case is still being reviewed by the appropriate team. Since the investigation is ongoing, we’ll need to allow them to complete their review before any additional steps can be taken.

For now, please keep the case open and wait for their response.

Once the review is complete, if you still have questions or feel that something was not fully addressed, please feel free to return to the forums with the outcome, and we’ll be happy to take another look.

Christine 🍂☕

00
Reply
user profile
Seller_8oxW2B1GQc66h

Hi

@Christine_Amazon

Thank you again for confirming that case 13165119802 was being reviewed by the appropriate team.

We have kept the case open as requested, but we have now had no substantive update from Seller Support since 18 September, and today is 3 October.

The case itself has been open since 11 August.

The 15 affected Hayes Meadow GTINs still cannot be listed successfully, despite Amazon having:

- confirmed our ownership of the Hayes Meadow brand and relevant GS1 GTINs;

- granted matching exemptions;

- instructed us to use the exact approved MCID, SKUs and 14-digit GTINs; and

- acknowledged that the exemptions were still not functioning correctly.

We followed those instructions exactly and all 15 products continued to fail validation.

Could you please check with the reviewing team and let us know whether there has been any progress, who currently owns the technical review, and what the next step is?

We would be very grateful if you could continue monitoring this escalation until the technical issue is actually resolved.

Many thanks,

Graham Macklin

Hayes Meadow

00
user profile
Seller_8oxW2B1GQc66h

Hi

@Christine_Amazon

Thank you again for confirming that case 13165119802 was being reviewed by the appropriate team.

We have kept the case open as requested, but we have now had no substantive update from Seller Support since 18 September, and today is 3 October.

The case itself has been open since 11 August.

The 15 affected Hayes Meadow GTINs still cannot be listed successfully, despite Amazon having:

- confirmed our ownership of the Hayes Meadow brand and relevant GS1 GTINs;

- granted matching exemptions;

- instructed us to use the exact approved MCID, SKUs and 14-digit GTINs; and

- acknowledged that the exemptions were still not functioning correctly.

We followed those instructions exactly and all 15 products continued to fail validation.

Could you please check with the reviewing team and let us know whether there has been any progress, who currently owns the technical review, and what the next step is?

We would be very grateful if you could continue monitoring this escalation until the technical issue is actually resolved.

Many thanks,

Graham Macklin

Hayes Meadow

00
Reply
user profile
Seller_8oxW2B1GQc66h

Hi @Christine_Amazon

I am following up again as unfortunately there has still been no substantive update or resolution.

Tomorrow marks 56 days since case 13165119802 was opened on 11 August, and Seller Support has provided no substantive update since 18 September.

You previously confirmed that the case was being reviewed by the appropriate team, but the 15 Hayes Meadow GTINs remain unusable and we have received no indication of what action is actually being taken.

@Indy_Amazon @Roberto_Amazon

Tomorrow marks 56 days since case 13165119802 was opened on 11 August

Could one of you please assist Christine in obtaining a concrete update from the technical team and confirm who currently owns this escalation?

We have supplied every document requested, followed the exact approved MCID/SKU/14-digit GTIN instructions, and demonstrated that all 15 exemptions still fail.

We need a technical resolution, not another request to wait indefinitely.

Many thanks,

Graham Macklin

Hayes Meadow

00
user profile
Seller_8oxW2B1GQc66h

Hi @Christine_Amazon

I am following up again as unfortunately there has still been no substantive update or resolution.

Tomorrow marks 56 days since case 13165119802 was opened on 11 August, and Seller Support has provided no substantive update since 18 September.

You previously confirmed that the case was being reviewed by the appropriate team, but the 15 Hayes Meadow GTINs remain unusable and we have received no indication of what action is actually being taken.

@Indy_Amazon @Roberto_Amazon

Tomorrow marks 56 days since case 13165119802 was opened on 11 August

Could one of you please assist Christine in obtaining a concrete update from the technical team and confirm who currently owns this escalation?

We have supplied every document requested, followed the exact approved MCID/SKU/14-digit GTIN instructions, and demonstrated that all 15 exemptions still fail.

We need a technical resolution, not another request to wait indefinitely.

Many thanks,

Graham Macklin

Hayes Meadow

00
Reply
user profile
Abbie_Amazon

@Seller_8oxW2B1GQc66h, Thank you for your patience and persistence on this matter.

We can confirm your case 13165119802 is actively being worked on by the appropriate team. We are aware that the steps taken so far have not yet resolved the listing issue, and this is being addressed.

In the meantime, please continue to keep your case open and respond to any communications from the support team directly through Seller Central.

We appreciate your patience and are committed to getting this resolved for you.

-Abbie

00
user profile
Abbie_Amazon

@Seller_8oxW2B1GQc66h, Thank you for your patience and persistence on this matter.

We can confirm your case 13165119802 is actively being worked on by the appropriate team. We are aware that the steps taken so far have not yet resolved the listing issue, and this is being addressed.

In the meantime, please continue to keep your case open and respond to any communications from the support team directly through Seller Central.

We appreciate your patience and are committed to getting this resolved for you.

-Abbie

00
Reply
user profile
Seller_8oxW2B1GQc66h

**Update – 29 October – Case 13165119802 still unresolved after 79 days**

Amazon has again confirmed that matching exemptions have been granted for our 15 Hayes Meadow GTIN/SKU combinations.

We retested the exact unchanged spreadsheet on 23 October using the exact approved SKUs and 14-digit GTINs.

@Indy_Amazon @Roberto_Amazon

The result remains:

**19 total SKUs

4 ready

15 action required**

Every affected GTIN is still being matched to the same unrelated catalogue ASIN.

This is no longer simply a support delay. It is now creating direct commercial loss.

The limited Hayes Meadow range we currently have live on Amazon is producing increasing daily orders. We have a much larger range ready to sell, but 15 genuine Hayes Meadow variants remain blocked by this unresolved catalogue issue.

Amazon has repeatedly told us that the exemptions are granted and the problem is fixed, but Amazon’s own validator repeatedly demonstrates that it is not.

Could a Community Manager please escalate case **13165119802** again and request a named technical owner / internal escalation reference from the catalogue or GTIN team?

After 79 days, we need a technical resolution and completion date rather than another request to wait for the specialist team.

Thank you.

Graham Macklin

Hayes Meadow

00
user profile
Seller_8oxW2B1GQc66h

**Update – 29 October – Case 13165119802 still unresolved after 79 days**

Amazon has again confirmed that matching exemptions have been granted for our 15 Hayes Meadow GTIN/SKU combinations.

We retested the exact unchanged spreadsheet on 23 October using the exact approved SKUs and 14-digit GTINs.

@Indy_Amazon @Roberto_Amazon

The result remains:

**19 total SKUs

4 ready

15 action required**

Every affected GTIN is still being matched to the same unrelated catalogue ASIN.

This is no longer simply a support delay. It is now creating direct commercial loss.

The limited Hayes Meadow range we currently have live on Amazon is producing increasing daily orders. We have a much larger range ready to sell, but 15 genuine Hayes Meadow variants remain blocked by this unresolved catalogue issue.

Amazon has repeatedly told us that the exemptions are granted and the problem is fixed, but Amazon’s own validator repeatedly demonstrates that it is not.

Could a Community Manager please escalate case **13165119802** again and request a named technical owner / internal escalation reference from the catalogue or GTIN team?

After 79 days, we need a technical resolution and completion date rather than another request to wait for the specialist team.

Thank you.

Graham Macklin

Hayes Meadow

00
Reply
user profile
Seller_8oxW2B1GQc66h

Hi @Abbie_Amazon

Thank you for your earlier update.

I am following up because unfortunately the issue is still unresolved.

Since your message, Amazon has again confirmed that matching exemptions have been granted for the 15 affected Hayes Meadow GTIN/SKU combinations.

We then retested the exact unchanged spreadsheet on 23 October using the exact approved SKUs and 14-digit GTINs.

The result is still:

**19 total SKUs

4 ready to submit

15 action required**

All 15 affected GTINs are still being matched to the same unrelated Amazon catalogue ASINs.

At this stage, it is **not acceptable for us to keep being told that the exemptions have been granted or that the issue has been fixed when Amazon’s own validator repeatedly proves that it has not been fixed.**

This case has now been open since **11 August**.

We have supplied every document requested, followed every technical instruction, repeated the validation tests several times, and each time the same 15 errors remain.

The delay is now causing direct commercial loss. Our currently limited Amazon range is generating increasing daily orders, while 15 genuine Hayes Meadow variants remain blocked from sale because this catalogue issue is still unresolved.

@Christine_Amazon

Could one of you please obtain a substantive technical update on case **13165119802**, including:

- who currently owns the technical resolution;

- what root cause has been identified;

- what corrective action is actually being taken;

- why Amazon has repeatedly confirmed the exemptions are granted when they are still not functioning; and

- when the issue is expected to be fully resolved.

We now need a technical resolution and a completion date, not another confirmation that the case is still being worked on.

Many thanks,

Graham Macklin

Hayes Meadow

00
user profile
Seller_8oxW2B1GQc66h

Hi @Abbie_Amazon

Thank you for your earlier update.

I am following up because unfortunately the issue is still unresolved.

Since your message, Amazon has again confirmed that matching exemptions have been granted for the 15 affected Hayes Meadow GTIN/SKU combinations.

We then retested the exact unchanged spreadsheet on 23 October using the exact approved SKUs and 14-digit GTINs.

The result is still:

**19 total SKUs

4 ready to submit

15 action required**

All 15 affected GTINs are still being matched to the same unrelated Amazon catalogue ASINs.

At this stage, it is **not acceptable for us to keep being told that the exemptions have been granted or that the issue has been fixed when Amazon’s own validator repeatedly proves that it has not been fixed.**

This case has now been open since **11 August**.

We have supplied every document requested, followed every technical instruction, repeated the validation tests several times, and each time the same 15 errors remain.

The delay is now causing direct commercial loss. Our currently limited Amazon range is generating increasing daily orders, while 15 genuine Hayes Meadow variants remain blocked from sale because this catalogue issue is still unresolved.

@Christine_Amazon

Could one of you please obtain a substantive technical update on case **13165119802**, including:

- who currently owns the technical resolution;

- what root cause has been identified;

- what corrective action is actually being taken;

- why Amazon has repeatedly confirmed the exemptions are granted when they are still not functioning; and

- when the issue is expected to be fully resolved.

We now need a technical resolution and a completion date, not another confirmation that the case is still being worked on.

Many thanks,

Graham Macklin

Hayes Meadow

00
Reply
user profile
Christine_Amazon

Hi @Seller_8oxW2B1GQc66h

I was checking that the team in charge has been actively responding to you.

Please follow up on the case ID 13165119802.

Christine🦃🍂☕️

00
user profile
Christine_Amazon

Hi @Seller_8oxW2B1GQc66h

I was checking that the team in charge has been actively responding to you.

Please follow up on the case ID 13165119802.

Christine🦃🍂☕️

00
Reply
user profile
Seller_FwNZ3OOTo1Rls

If GS1 has confirmed the contingency barcodes can be used for these products, I’d personally be tempted to use them to get the launch moving.

Once the listings are accepted, you could cover the original barcodes with replacement labels on your existing stock, then update the packaging artwork for future batches so you don’t have to keep relabelling.

I appreciate that doesn’t fix the original issue, but after this much delay, I’d be weighing the cost of relabelling against keeping the launch on hold.

Is the printed packaging the main reason you haven’t used the contingency barcodes, or is there another complication?

00
user profile
Seller_FwNZ3OOTo1Rls

If GS1 has confirmed the contingency barcodes can be used for these products, I’d personally be tempted to use them to get the launch moving.

Once the listings are accepted, you could cover the original barcodes with replacement labels on your existing stock, then update the packaging artwork for future batches so you don’t have to keep relabelling.

I appreciate that doesn’t fix the original issue, but after this much delay, I’d be weighing the cost of relabelling against keeping the launch on hold.

Is the printed packaging the main reason you haven’t used the contingency barcodes, or is there another complication?

00
Reply
Follow this discussion to be notified of new activity