How to Change Amazon Listing Barcodes from Non-GS1 to GS1 (and Merge Listings with a New UPC)

Amazon has started taking action against product listings that use unauthorized or non-GS1 barcodes. A GS1 barcode is a globally unique, brand-traceable identifier issued by GS1, the global standards organization that issues and manages product barcodes (UPCs and EANs) worldwide. 

If you bought your barcodes from a third-party reseller instead of directly from GS1, your listing is now at risk, because Amazon cross-verifies every barcode against the official GS1 database and has stepped up enforcement against non-GS1 codes through 2025 and 2026.

This makes a GS1 barcode effectively non-negotiable for most sellers. To stay safe, you need to change your Amazon listing barcodes from a non-GS1 barcode to a GS1 barcode, then merge the Amazon listings so your reviews, rank, and sales history move to the compliant version. 

This guide walks you through every step to change your UPC to GS1 on Amazon and protect your listings from suppression or removal.

What Amazon’s GS1 Barcode Policy Requires

Amazon’s barcode rule is straightforward: the UPC or EAN on your listing must be issued by GS1 and registered to your brand. Amazon checks each code against the GS1 database, and when a barcode is not registered under your company prefix, it can be flagged as invalid and the listing can face search suppression or removal. Enforcement against non-GS1 and reseller barcodes has become noticeably stricter through 2025 and 2026.

There is one important exception. Amazon still offers a GTIN (Product ID) exemption that lets approved sellers list without a GS1 UPC, typically for brand owners whose products have no barcode yet, handmade or generic goods, parts and accessories that carry no manufacturer code, and self-made bundles. 

Amazon retired the standalone exemption application page in 2024, so the exemption is now requested during listing creation. The exemption does not apply once a product already uses GS1 barcodes, so for most established listings the right move is to change the non-GS1 UPC to a GS1 UPC using the process below.

How to Change Your Amazon Listing Barcode from Non-GS1 to GS1: 8-Step Process

Changing an existing barcode to a GS1 barcode is an 8-step process. 

You cannot simply overwrite the UPC on a live listing, so the approach is to create a new GS1-verified listing and then merge it with the original to keep your performance history. Here is the full process in detail.

Step 1: Download Your Inventory Report

Before making any updates, you need a clear picture of the barcodes on your current listings, so start by downloading your full inventory report from Seller Central.

Log in to Amazon Seller Central and find the Reports tab, just above the Payments tab. 

Select Inventory Reports, then choose Category Listings Report. 

Click Request Report, wait a few minutes while it generates, and download the file in .CSV format.

This report contains critical columns such as ASIN, SKU, Product ID (UPC), and Brand Name, which lets you identify which listings use non-GS1 barcodes. Save the file as your master tracking document and label it something like “GS1 Transition Tracker [Month-Year].” 

You will refer back to it throughout the migration, as it becomes your blueprint for barcode validation, mapping, and merge tracking. With every ASIN and UPC centralized, you reduce errors and speed up validation across large or multi-market catalogs.

Step 2: Verify Whether Your Barcodes Are GS1-Compliant

Now confirm which barcodes are legitimate and registered to your brand in the GS1 database. On GS1.org, use the Verified by GS1 / Check Company Prefix lookup tool and enter a UPC or company prefix from your report. 

The tool displays the registered company name tied to that code. If your brand name appears, that product already has a valid GS1 barcode. If nothing appears, or a different company shows, you need a GS1 barcode for that product.

Return to your spreadsheet and add a column titled “GS1 Verified / Non-GS1.”

Highlight the non-GS1 entries so you can see exactly which listings need a GS1 barcode. This distinction matters later, because Amazon may request your GS1 prefix certificate to validate ownership when you open a support case.

Step 3: Purchase Official GS1 Barcodes

Once you know which products need a GS1 barcode, obtain authentic codes directly from GS1, the only source Amazon recognizes. 

Visit your regional GS1 website (such as GS1 US or GS1 UK) and select the plan that fits your catalog. Small sellers can buy single GS1 UPCs, while established brands usually license a Company Prefix for multiple barcodes. Complete registration with a business name that exactly matches your Amazon Brand Registry details.

After purchase, GS1 issues a Company Prefix Certificate that officially links your UPCs to your business. Save it as a PDF, because Amazon often requires it when you merge Amazon listings. Each unique variant (color, size, or pack count) must receive its own GS1 UPC. Reusing one GS1 barcode across products violates GS1 standards and triggers errors in Amazon’s system.

To stay organized, build a mapping spreadsheet:

This file keeps you accurate when you create new listings and request a merge later.

Step 4: Create a New Listing Using the GS1 Barcode

Amazon does not let you overwrite an existing UPC in the Manage Inventory interface, so you will create a new GS1-verified listing through a controlled flat-file process and merge it with the original afterward.

Open and filter your Category Listings Report: Open the report in Excel, click the Filter icon on the header row, and filter the SKU column for the one product you are correcting. Hide or delete the other rows so only that single SKU remains.

Edit the listing fields for GS1 compliance: In that row, change the SKU to a brand-new identifier (for example, from ABC-123 to XYZ-789), enter your new 12-digit GS1 UPC under Product ID, and set Product ID Type to “UPC.” 

Confirm that all core data (title, bullets, description, brand, dimensions, and images) matches the existing listing exactly, since this new listing must mirror the original before it becomes your primary ASIN. This is a good moment to confirm your listing content is fully optimized. 

Save the edited report as a fresh CSV, which you will upload to create the new ASIN.

Step 5: Upload the Edited File to Create the New Listing

Now upload the corrected file so Amazon can generate the new product tied to your GS1 barcode. 

In Seller Central, hover over Catalog and select Add Products via Upload. 

Under Upload Your Inventory File, choose the option to list a product using a file, then upload the edited CSV you saved with only one SKU. 

Double-check that the file name and data match your GS1 listing, then click Upload.

Amazon begins processing the file and creates a new product detail page using your GS1 UPC. Monitor progress under Monitor Upload Status, then open the Processing Report to view results.

Troubleshooting upload errors, If errors appear, read each message in the Processing Report:

• “Invalid value for BulletPoint1” means a bullet field is blank.
  
• “UPC code is not in proper format” means your GS1 UPC is missing digits or contains spaces.

Fix the flagged fields in Excel, re-save, and upload again until the file processes with no errors. Once approved, your new ASIN appears in Manage Inventory, fully verified against the GS1 database. 

At this point your catalog contains two versions of the product: the original ASIN with the non-GS1 UPC, and the new GS1 ASIN, compliant but without reviews yet. 

The next step is to merge the Amazon listings so performance data carries over.

Step 6: Request the Catalog Team to Merge the Listings

With the same product live under two different UPCs, you now merge the Amazon listings so reviews, rankings, and sales history consolidate under the GS1-compliant ASIN.

Open Seller Support, navigate to Catalog, and select Merge Listings. 

Provide both ASINs, clearly labeled:

• Old ASIN: non-GS1 barcode
• New ASIN: GS1-compliant barcode

Attach evidence, including product images showing identical packaging and both barcodes, your GS1 certificate or company-prefix invoice, and any Brand Registry or purchase proof confirming ownership. 

Keep your request concise and professional, for example: “Please merge the GS1-compliant ASIN with the existing ASIN to retain reviews, rank, and sales history. Both listings represent the same product, now updated with a verified GS1 UPC.”

Regular support agents cannot always perform merges that involve barcodes, so politely request escalation to the Catalog Team. 

Note that both listings are identical except for the product ID and that you are updating per Amazon’s GS1 barcode policy. Follow up every 24 to 48 hours until you reach catalog escalation. 

Bear in mind that Amazon does not guarantee a review or history transfer, but once a genuine duplicate merge is approved, your old listing’s ranking signals, reviews, and metrics should move to the GS1 listing.

Step 7: Confirm the Merged Listing Shows Both UPCs

After Amazon confirms the merge, verify everything linked correctly. Merges can take several hours to reflect, so wait before checking, and then:

• Go to Manage Inventory and search for both ASINs. The old one should redirect to the new GS1 listing.
  
• In the Product ID column, confirm both barcodes are associated: your original non-GS1 UPC for backward reference, and your new GS1-verified UPC as the compliant identifier.
  
• Open the product detail page and confirm that reviews, ratings, and sales history are intact, images and descriptions match the original, and pricing, inventory, and ad connections are unchanged.

If you do not see both UPCs, or reviews are missing, reopen the same case ID with Seller Support, explain that the merge did not retain both identifiers, and request re-evaluation. Attach before-and-after screenshots for faster resolution. 

This dual-record setup keeps your catalog compliant and preserves sales continuity.

Step 8: Run a Final Compliance Check

Once the merge is confirmed, run a final compliance check:

• Verify the GS1 UPC appears as the primary Product ID in Seller Central.
  
• Confirm your product still ranks for major search terms and remains fully indexed.
  
• Run a barcode lookup on GS1.org to confirm the product is registered under your company prefix.
  
• If you use FBA, make sure your inbound labels display the GS1 barcode that matches this listing.

Only once all data aligns should you delete the old SKU to prevent confusion or stranded stock, which is part of keeping your Amazon inventory management clean. Your product is now GS1-compliant, fully merged, and protected from suppression during Amazon’s ongoing barcode verification.

Alternate Methods if Amazon Blocks a Direct Change

Sometimes Amazon’s system blocks a merge or a UPC update, usually on older ASINs, brand-registered listings, or stricter categories such as Health, Beauty, or Grocery. When that happens, use one of these fallback routes to stay compliant while protecting your rank and reviews. 

Complex merges and product-ID corrections are also the kind of work Amazon catalog services handle day to day.

Option 1: Request a Manual UPC Update from the Catalog Team

If the self-service merge fails or is denied, open a manual case with Amazon’s Catalog Team. This works well when both listings clearly represent the same product but Amazon’s automated system blocks the merge due to conflicting identifiers.

In Seller Central, open Help, select Get Help and Resources, then My issue is not listed. Explain that you are updating the product’s identifier to a GS1-verified barcode, and attach your GS1 certificate showing the company prefix and packaging images showing both the old and new barcodes. 

A short message helps: “This product is owned by our brand and is now updated with a GS1-verified UPC as per Amazon’s current catalog policy. Please manually update the Product ID to reflect the GS1 code.”

The Catalog Team can override system restrictions and replace the old UPC with your GS1 barcode while keeping your existing ASIN intact. This typically takes 3 to 5 business days, depending on case volume.

Option 2: Contact Brand Registry Support

If your brand is enrolled in Amazon Brand Registry, you have a faster escalation path. The Brand Support Team can intervene in catalog updates that normal Seller Support cannot resolve, including product-ID mismatches and GS1 enforcement errors.

Log in to Brand Registry, click Support, and select Contact Brand Support. In the left panel, choose Report Technical Error, then provide the affected ASINs and the old and new UPCs with a message such as: “We are the registered brand owner and have updated this listing with a valid GS1 barcode as required by Amazon’s GS1 policy. Please assist in correcting the product ID and merging both listings.” 

Choose your contact method, then upload your GS1 ownership certificate, because Brand Support has direct catalog access, it often processes the update within 24 to 48 hours.

Pro tip: Always open these cases from the Brand Registry portal, not Seller Central. The system tags your request as a brand-authorized edit, which improves approval odds and response times.

Option 3: Delete and Recreate the Listing Under the GS1 UPC

If nothing above works, or the listing keeps getting rejected for barcode conflicts, the last resort is to delete the old listing and relist under your GS1 barcode. It is more drastic, but it guarantees a clean tie to your brand’s GS1 record.

To do it safely: delete the old SKU from inventory but do not delete the ASIN, which preserves catalog data. Wait 24 to 48 hours for Amazon to clear cached data and release the old UPC. Recreate the listing using your new GS1 UPC, keeping all content identical (title, bullets, images, and brand). Once the new ASIN is live, open a merge request with Seller Support to combine it with the old ASIN and transfer reviews. 

This takes patience, but it aligns the product fully with Amazon’s GS1 barcode requirements, free of legacy data errors.

Documentation and Troubleshooting for GS1 Compliance

Keep complete documentation for audits and support cases:

• GS1 ownership certificate (PDF).
• Purchase invoices from GS1.
• Mapping spreadsheet (old versus new UPCs).
• Amazon case IDs and response threads.

If a merge request fails, reopen the same case ID rather than starting a new one, attach side-by-side screenshots comparing both ASINs, re-include your GS1 certificate and product images, and request escalation to the Catalog Escalations Team. 

Organized records noticeably reduce resolution time.

5 Common Mistakes to Avoid

1. Using resold or unauthorized barcodes: Amazon cross-verifies every UPC against the GS1 database, and any barcode not registered under your brand prefix is flagged as invalid, risking suppression or deactivation. Buy only from GS1.

2. Editing UPCs directly in existing listings: Amazon locks product identifiers to protect data integrity, so overwriting a UPC with the Edit function is rejected. Always create a new GS1 listing and request a catalog merge.

3. Deleting both listings before the merge: If both ASINs are removed before the merge is approved, you lose all reviews, rank, and sales history permanently. Only delete the non-GS1 listing after the merge is confirmed.

4. Assigning one GS1 barcode to multiple SKUs: Each variation (color, size, or bundle) must have its own unique GS1 UPC. Reusing one barcode confuses Amazon’s catalog mapping and can cause errors, removals, or brand mismatches.

5. Failing to keep records for future audits: Store your GS1 certificates, invoices, and mapping sheets securely. During compliance audits, Amazon may request proof of barcode authenticity, and having it on hand prevents listing disruptions.

Final Thoughts

Amazon’s GS1 enforcement is a permanent shift toward verified catalog authenticity. Moving early protects you from suppressed ASINs, keeps your rankings stable, and future-proofs your listings against counterfeit risks. 

Beyond compliance, GS1 barcodes signal professionalism and brand credibility, keeping your listings active and your catalog aligned with Amazon’s direction. If you get stuck at any stage, AMZDUDES, a full-service Amazon agency, can handle the transition for you and keep your listings live and compliant through our Amazon account management services.

Book Your Free Consultation Today

Frequently Asked Questions (FAQs)

Do I need a GS1 barcode to sell on Amazon? 
In most cases, yes. Amazon requires product barcodes (UPCs or EANs) to be issued by GS1 and registered to your brand, and it cross-checks them against the GS1 database. The main exception is Amazon’s GTIN (Product ID) exemption, available to some brand owners and to handmade, generic, parts, or self-made bundle products with no manufacturer barcode. The exemption does not apply once a product already uses GS1 barcodes.

Does Amazon require GS1 barcodes? 
Yes, with limited exceptions. Amazon cross-checks every UPC against the official GS1 database to confirm authenticity and prevent counterfeit listings. Products granted a GTIN exemption are the main exception.

How do I change a UPC on an Amazon listing? 
You cannot overwrite a UPC on a live listing. To change the UPC on an Amazon listing, create a new listing with your GS1 UPC through a flat-file upload, then open a case with Seller Support to merge it with the original ASIN so your reviews and rank carry over.

How do I merge Amazon listings with different UPCs? 
Open Seller Support, go to Catalog, and select Merge Listings. Provide both ASINs (the old non-GS1 and the new GS1 version), attach proof that they are the same product plus your GS1 certificate, and request escalation to the Catalog Team if a standard agent cannot complete the merge.

How do I add a UPC to an Amazon listing? 
Use a flat-file upload in Seller Central. Enter your new GS1 UPC in the Product ID field, set the Product ID Type to “UPC,” and upload the file through Add Products via Upload.

What happens if I use non-GS1 barcodes? 
Amazon may suppress or remove your listings when your UPCs do not match the GS1 database. Always use barcodes licensed directly from GS1.