Missing Attributes standard_product_id



mine is a special case: as a manufacturer I requested the exemption of the EAN code to load products, which Amazon accepted me.
Now I am trying to upload products to the inventory via the SP-API, but the system replies with this message because it wants a mandatory EAN code. How can this be solved? Thanks

  1. How long has it been since granted? It can take 24-48 hrs sometimes for the back end to register things.

  2. Are you entering the exact brand as granted?


1 yes, more than 48 hours have passed

2 yes



What’s the code you submitted and the exact response? I haven’t made the switch yet to the SP-API but maybe I or someone else can spot something.


[MessageID] => 1
[ResultCode] => Error
[ResultMessageCode] => 8560
[ResultDescription] => SKU 1A017704, Missing Attributes standard_product_id. SKU 1A017704 doesn’t match any ASINs. Make sure that all standard product ids (such as UPC, ISBN, EAN, or JAN codes) are correct. To create a new ASIN, include the following attributes: standard_product_id. Feed ID: 0. For more troubleshooting help, see http://sellercentral.amazon.co.uk/gp/errorcode/200692370
[AdditionalInfo] => SimpleXMLElement Object
[SKU] => 1A017704


This is the response, but not the submission.

> <?xml version="1.0" encoding="utf-8"?>
> <AmazonEnvelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="amzn-envelope.xsd">
>   <Header>
>     <DocumentVersion>1.01</DocumentVersion>
>     <MerchantIdentifier>************</MerchantIdentifier>
>   </Header>
>   <MessageType>Product</MessageType>
>   <PurgeAndReplace>true</PurgeAndReplace>
>   <Message>
>     <MessageID>1</MessageID>
>     <OperationType>Update</OperationType>
>     <Product>
>       <SKU>1A017704</SKU>      
>       <DescriptionData>
>         <Brand>Piaggio</Brand>
>         <MSRP currency="EUR">379.00</MSRP>
>         <Manufacturer>Piaggio</Manufacturer>
>         <MfrPartNumber>1A017704</MfrPartNumber>
>         <ItemType>motor-starter</ItemType>
>         <CountryOfOrigin>IT</CountryOfOrigin>
>       </DescriptionData>
>       <ProductData>
>         <Motorcycles>
>           <ProductType>
>              <Accessories></Accessories>
>           </ProductType>
>         </Motorcycles>
>       </ProductData>
>     </Product>
>   </Message>
> </AmazonEnvelope>


Hoping someone will hop in to correct me.


Thanks for the reply,

but where is this “GtinExemptionReason” in the amazon documentation? I’ve searched but can’t find it


Product.xsd, which is the basis for forming the XML

ETA - I’m on vacation and don’t have the link handy to the XSD’. but you can find them through Seller Central Help (at least the old ones)


I think this it the product.xsd that Oneida was referring to. Also here is the link for all of the other XSD’s.




The (supposed - I say this because they are not the most recent and I don’t expect Amazon is going to fix that) current XSD’s are found here: https://sellercentral.amazon.com/help/hub/reference/1611?ie=UTF8

However, over a year ago I received an email from Amazon with this in it (I never got another email on this):

    As previously announced on May 11, 2021, Amazon is launching new Product Types across XSDs worldwide. The goal is to enable enhanced product search and a simplified product overview by surfacing key product information in a structured format at the top of product detail pages instead of unstructured bullet points. This will help customers to read through the top product specifications, evaluate key differences between products and make purchase decisions quicker.

    This first phase of 120 new Product Types are available as of July 14, 2021. You can download the list of affected Product Types (link removed but see ** Below) with the corresponding XSD categories in Microsoft Excel format (.xlsx).

    For each new Product Type, you can view the XSD by clicking the link in the Microsoft Excel list.

**If you want to PM me I’ll give you the excel doc that is downloaded with the links to many new XSD’s. I’m not sure I should post the link in the forums. I think it would be OK, but just in case.