cancel
Showing results for 
Search instead for 
Did you mean: 
CommunityJedi22
Community Manager
Community Manager

Please click below to access the Amazon Vendor Guidelines for the US and CA.  The Vendor Guides provide you with details on how to get started and successfully synchronize your content with Amazon.  

GDSN Overview

Global Data Synchronization Network (GDSN) contains important product data supporting supply chain attributes (package hierarchy, weights/dimensions, quantity-based attributes), and customer-facing attributes (nutritional value, allergen information, etc.), all stored in an authoritative data source that you upload, maintain, and share with trading partners.

Amazon is making it a top priority to improve our usage of industry-standard data, particularly from the use of GDSN with GS1 standards. Our immediate focus involves integrating the GDSN data more effectively in our catalog, using it in our fulfillment operations to improve receive accuracy, and setting up guardrails to prevent overrides of your existing catalog. We’ve successfully tested all three components with a small group of Vendors, and we’re interested in scaling GDSN usage across all relevant Vendors.

The initial use of the data will be to improve receiver accuracy to reduce Vendor shortages. This use case will focus on a small subset of key package hierarchy attributes (Global Trade Item Number, dimensions/weights, package level, etc.) to aid in fulfillment operations. Once that use case is successfully proven, we will expand the initiative by using GDSN data to reduce procurement errors, as well as streamline catalog updates and new item setup. Amazon currently has 85 GDSN attributes mapped to Amazon attributes, which cover various categories to support the above use cases.

To synchronize your product information with Amazon through GDSN, please follow the simple steps outlined in the Implementation Guide. Please review the attributes guide and FAQs for further information.

  1. GDSN Implementation Guide
  2. Amazon GDSN FAQs

 

  1. GDSN IMPLEMENTATION GUIDE

1.1 Amazon’s data synchronization information

Amazon’s Global Location Number (GLN) - Publish To Production: 0848719000016 (for US)

1.2 Steps to begin syncing your data with Amazon

1.2.1 Check data availability

  1. If not already a member, join the GDSN data pool of your choice.
  2. Have your accurate item data loaded into your home data pool and ensure it is ready for publication.

- Contact your data pool for any education you might require to complete this step.

- Please review the Amazon Attribute Guide and ensure you’re meeting the

    attribute requirements.

  1. If you believe that you are already publishing data to Amazon via GDSN, please ensure that you are publishing your complete catalog along with all relevant hierarchies. If you would like to get in touch about your existing subscription, please refer to Section 1.2.3: “How to Report a Problem” to contact the Catalog Feeds Management team within Amazon.

 

1.2.2 (CRITICAL) Connect to Amazon GDSN through your Vendor Central account

NOTE: This is a critical step! Forgetting to connect to Amazon GDSN through Vendor Central will result in Amazon not receiving your GDSN data.

 Step 1: Log in to Vendor Central and select ‘Manage Catalog feeds’ under ‘Items’.

 
CommunityJedi22_1-1754483445700.png

Step 2: Select ‘GDSN Subscription’ as shown below.

CommunityJedi22_2-1754483489427.png

Step 3: Enter your Global Location Number (GLN) in the highlighted box and click Validate GLN

CommunityJedi22_3-1754483530687.png

Step 4: Post successful validation of GLN, you can choose appropriate vendor code(s) against which your GDSN product content will be submitted (see the following screenshot).

Our recommendation is to choose the vendor code:

  1. Choose the vendor code(s) against which you submit content using Vendor Central
  2. On the right side of the screen, you will see the business groups corresponding to vendor codes as additional information.
  3. You can choose as many vendor codes as possible. This means your GDSN submission will be applied to all the selected vendor codes.
  4. GLN and vendor codes are not on one mapping, but a many-to-many mapping. You can map many vendor codes to a GLN. If you have multiple GLNs, you can link multiple GLNs to a single vendor code as well.
  5. Note: If you are attempting to connect multiple GLNs to a vendor code (or multiple GLNs to multiple vendor codes), Amazon support will need to do this for you. Please see section 1.2.3 in this guide on how to reach out to Amazon support with this information. Provide all vendor codes and GLNs that you are trying to connect.

 

CommunityJedi22_4-1754483594902.png

 

1.2.3 How do I report a problem?

Step 1: Log in to Vendor Central and go to the Manage Catalog Feeds tab under Items.

CommunityJedi22_5-1754483649378.png

Step 2: Choose the link “Support” at the center top shown in screen below

CommunityJedi22_6-1754483692676.png

Step 3: Choose the link “Contact Us” at the center bottom shown in screen below

CommunityJedi22_7-1754483717561.png

Step 4: Choose Issue “Manage My Catalog” and then “Catalog Feeds Management”.

CommunityJedi22_8-1754483739169.png

Step 5: Choose “Send Email”, describe your problem, and submit.

CommunityJedi22_9-1754483763403.png

1.2.4 Publish your content to Amazon via your home data pool

  1. If not already a member, join the GDSN data pool of your choice.
  2. Have your accurate item data loaded into your home data pool and ensure it is ready for publication. Contact your data pool for any education you might require to complete this step.
  3. Publish your catalog to Amazon’s GLN: 0848719000016

 1.2.5 Target Attribute List in 2025

CommunityJedi22_10-1754483808044.png
 
AMAZON GDSN FAQS
  1. Why is Amazon inviting suppliers/vendors to publish their product content via GDSN?

In 2025, Amazon is interested in leveraging GDSN primarily to improve receive accuracy and remove the need to manually maintain the GTIN GoldList. In 2026+, Amazon will explore using GDSN to reduce procurement defects and improve catalog enrichment. To remove manual touchpoints and obtain the full benefit of automated feeds, we encourage you to publish your complete catalog to Amazon.

 

  1. What information is Amazon taking through GDSN?

Currently, Amazon is focusing on supply chain/fulfillment attributes, including GTIN, package hierarchy, quantity-based attributes, weights & dimensions, package level, etc. However, in 2026, Amazon will also have the capability of ingesting regulatory and consumer-facing attributes via GDSN, with a plan to ingest more attributes by the end of 2026.

 

  1. Will my POs or detail pages get impacted by publishing GDSN data?

No - the GDSN data is ingested in the backend Amazon catalog, where guardrails are in place to prevent immediate catalog enrichment. This means your POs and detail pages will be business as usual, and the data will solely be used during Receive alongside the GTIN GoldList.

 

  1. Should suppliers share all GTINs in an underlying product hierarchy for SPH through GDSN?

Vendors should share all GTINs from the same underlying item package hierarchy (e.g. pallet, master pack, inner pack, each).

 

  1. Have other vendors adopted GDSN at Amazon, and what results have they seen?

In 2025, multiple large and small vendors have already published their full Amazon catalog via GDSN. This has driven meaningful improvements to Amazon’s ability to efficiently and accurately receive shipments, particularly when compared to existing GTIN GoldList data.

 

  1. Is the GDSN initiative still in the evaluation/testing phase?

Today, Amazon is live with multiple large vendors synchronizing their product content via GDSN and is ready to receive product content and updates from all Consumables Retail vendors who subscribe to the GDSN integration. That being said, 2025 is focused primarily on fulfillment attributes and improving receive accuracy.

 

  1. How does this affect the current New Item Setup process performed via Vendor Central?

In 2026, we plan on building solutions to integrate GDSN into the New Item Setup process, but for 2025, the process will be the same by listing products via Vendor Central (through NIS template or VSSC template). If the product has not yet been created as an ASIN in Amazon’s systems, Amazon will still accept the GDSN contribution for the product. Then, when you complete New Item Setup through Vendor Central, Amazon will use the GDSN data and combine it for the newly created ASIN.

  1. Do data poolers have access to Vendor Central?

No.

 

  1. Does Amazon process the submissions made through Vendor Central NIS Excel templates and GDSN differently?

No. The product data submitted through Vendor Central spreadsheets and the GDSN will be processed in the same way by Amazon. The last set of values for integrated attributes, regardless of the source i.e., Vendor Central or GDSN, will be the values used by Amazon.

 

  1. When will Amazon be taking all attributes required for item maintenance?

Due to the data quality and Amazon prioritization decisions, we will not take all attributes. We are prioritizing Regulatory, Supply Chain, and other attributes.

 

  1. How often is Vendor Central syncing with GDSN?

Data synchronization occurs continuously whenever there is a Publish and Subscription match (Pub-Sub match) between 2 GLNs. If Amazon is subscribed to a data provider GLN that publishes updated data on GDSN, then the data gets pushed to the Amazon Catalog as well.

 

  1. Our products are already on Amazon.com. What do we have to do next?

Your next step is to syndicate product content for the items currently sold on Amazon.com via the GDSN.

 Publish your GDSN product content for the items currently sold on Amazon.com to the Amazon GLN 0848719000016, through your data pooler.

 Connect to Amazon GDSN via Vendor Central (follow steps from Part 1.2.2)

 

  1. Do we have to provide data for items we manufacture but are only sold on Amazon by 3P sellers?

We recommend providing information for all of your items you sell on Amazon.

 

  1. Can suppliers opt out of this initiative?

You can opt out of this initiative by stopping publishing to the Amazon recipient GLN or contacting your GDSN data pool provider.

 

  1. Do suppliers still need to manage the GTIN gold list (aka GTIN library) after moving to GDSN?

For 2025, the GTIN GoldList will continue to be used as a backup data source for Receive as GDSN coverage increases. However, the north star vision is to deprecate the GTIN GoldList in 2026. There are already multiple large vendors who have transitioned to maintain GDSN data versus GoldList.

  1. Will GDSN help me merchandize eaches and cases of the same product?  

GDSN data on its own will not enable merchandizing two levels of a package hierarchy. However, the PH data from GDSN will be a key input to the new systems being launched by our Amazon Fulfillment Technologies team at the end of 2025, which will enable this capability. 

You can also download this guide below and access the Amazon GDSN Vendor Guide - CA

Please ask any questions in the comments below.

Comments
ppatel1009
New Contributor

What is Amazon asking suppliers to publish by GDSN versus vendor central?

Val_P
Community Support

Hello, @ppatel1009, thank you for reaching out to our customer community. Welcome.

On pages 9 and 10 of the attached file you can check the 58 attributes which Amazon can receive through GDSN. Amazon offers you the flexibility to use automated feeds (i.e., Global Data Synchronization Network (GDSN)) or Vendor Central for enhancing the quality of your Amazon catalog and for the Supplier Pack Hierarchy (SPH) program. 

Hope this helps. Please let us know if there is anything else we may assist with and we would be happy to. Thanks!

Version history
Revision #:
2 of 2
Last update:
‎08-06-2025 08:43 AM
Updated by:
 
Contributors