{"section":"known-issues","requestedLocale":"en","requestedSlug":"api-allows-registering-many-eans-to-the-same-sku","locale":"en","slug":"api-allows-registering-many-eans-to-the-same-sku","path":"docs/en/known-issues/Catalog/api-allows-registering-many-eans-to-the-same-sku.md","branch":"main","content":"## Summary\n\nIt is possible to register many EANs to the same SKU via the API  (method InsertSkuEanAsync on Splunk) and via another still not identified method.\nWhen we have multiple EANs for the same SKU, we get the last inserted value on the file export, and on the interface we see the EAN value that comes last on the alphabetical order of all registered values.\n\n## Simulation\n\n- create an SKU and register an EAN = 3 .\n- with the GET `https://.vtexcommercestable.com.br/api/catalog/pvt/stockkeepingunit//ean` API, check that this EAN value (3) is the only entry.\n- insert a new EAN = 2 to this SKU via the POST`https://catalog.vtexcommercestable.com.br/api/catalog/pvt/stockkeepingunit//ean/?an= `\n- with the GET `https://.vtexcommercestable.com.br/api/catalog/pvt/stockkeepingunit//ean` API, check that now EAN is an array with two values, on alphabetical order \\{2, 3\\}\n- go to the catalog interface and see that the EAN shown for this SKU is 3 (last one on the array)\n- export the SKU info and see that the EAN shown is 2 (last one registered)\n- if you now set a new EAN via the catalog interface, let's say \"1\", it will exclude the last EAN of the array, and include this new value. So the GET API would return \\{1, 2\\} for our example. With 2 being shown on the interface and 1 being shown on the exported files.\n\n## Workaround\n\nGet a list of problematic SKU ID and their correct EAN, clean all EANs from these SKUs with `DELETE ``https://catalog.vtexcommercestable.com.br/api/catalog/pvt/stockkeepingunit//ean?an=`` ` and then insert the correct EANs to these SKUs via the `POST ``https://catalog.vtexcommercestable.com.br/api/catalog/pvt/stockkeepingunit//ean/?an=`` ` API."}