Amazon GDSN Vendor Guide - 1WorldSync

Amazon GDSN Vendor Guide

January 11, 2021

1

2 GDSN Overview

3 Amazon supports the use of GDSN for enhancing the quality of your existing Amazon catalog 4 on a specific set of attributes detailed later in this guide.

5 GDSN is also a helpful way to provide your packaging hierarchies for the upcoming Supplier 6 Pack Hierarchy (SPH) program. As part of SPH, you will need to provide package hierarchy 7 details for your products, as well as unique identifiers and dimension/weight information for 8 each package level. The unique identifiers, also known as Merchant SKUs (MSKU), could either 9 leverage the Global Trade Identification Number (GTIN) as per GS1 guidelines or be your 10 internal model/part number, as long as you can guarantee their uniqueness across package 11 levels.

12 To provide this information, you will have the flexibility to use automated feeds (i.e., Global 13 Data Synchronization Network (GDSN)) or Vendor Central. These catalog changes will be 14 critical in establishing a common language between Amazon and you, as we will start using 15 these identifiers and package hierarchy information in creating and communicating our 16 Purchase Orders (PO). We will expect you to use the same identifiers in your PO Confirmation, 17 Advance Shipment Notice (ASN) and Invoice documents in return.

18 To ingest the new attributes under SPH, Amazon will support the Global Data Synchronization 19 Network (GDSN), through the data synchronization process under GS1 Global Standards 20 authority.

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

24

1. GDSN Implementation guide

25

2. Amazon GDSN attributes guide

26

3. How do I know my item was successfully synchronized?

27

4. Amazon GDSN FAQs

28

29 1. GDSN IMPLEMENTATION GUIDE

30 1.1 Amazon's data synchronization information

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

32 1.2 Steps to begin syncing your data with Amazon

33 1.2.1 Check data availability

34

a. If not already a member, join the GDSN data pool of your choice.

35

b. Have your accurate item data loaded into your home data pool and insure it is ready for

36

publication.

37

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

38

step.

39

Please review the Amazon Attribute Guide and ensure you're meeting the

40

attribute requirements.

Page 2

41

c. If you believe that you are already publishing data to Amazon via GDSN, please ensure

42

that you are publishing your complete catalog along with all relevant hierarchies. If you

43

would like to get in touch about your existing subscription, please refer to Section 1.2.3:

44

"How to Report a Problem" to contact the Catalog Feeds Management team within

45

Amazon.

46

47 1.2.2 (CRITICAL) Connect to Amazon GDSN through your Vendor Central account 48 NOTE: This is a critical step! Forgetting to connect to Amazon GDSN through Vendor Central 49 will result in Amazon not receiving your GDSN data.

50 Step 1: Login into Vendor Central and select `Manage Catalog feeds' under `Items'.

51 52 53

Page 3

54 Step 2: Select `GDSN Subscription' as shown below.

55 56 57 Step 3: Enter your Global Location Number (GLN) in highlighted box and click validate GLN

58

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

61 Our recommendation is to choose the vendor code:

62

1) Choose the vendor code(s) against which you submit content using Vendor Central

63

2) On the right side of the screen, you will see the business groups corresponding to

64

vendor codes as additional information.

65

3) You can choose as many vendor codes as possible. This means your GDSN submission

66

will be applied to all the selected vendor codes.

67

4) GLN and vendor codes are not one on one mapping, but many to many mapping. You

68

can map many vendor codes to a GLN. If you have multiple GLNs, you can link multiple

69

GLNs to a single vendor code as well.

70

a. Note: If you are attempting to connect multiple GLNs to a vendor code (or

71

multiple GLNs to multiple vendor codes), Amazon support will need to do this

72

for you. Please see section 1.2.3 in this guide on how to reach out to Amazon

73

support with this information. Provide all vendor codes and GLNs that you are

74

trying to connect.

Page 4

75 76 77 Step 5: Post successful mapping of GLN to vendor codes, you can choose `View GDSN 78 Subscription' to see the mapped vendors as needed.

79 80

Page 5

 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download