{"section":"known-issues","requestedLocale":"en","requestedSlug":"ean-field-as-string-being-ignored-when-approved-on-received-skus","locale":"en","slug":"ean-field-as-string-being-ignored-when-approved-on-received-skus","path":"docs/en/known-issues/Marketplace/ean-field-as-string-being-ignored-when-approved-on-received-skus.md","branch":"main","content":"## Summary\n\n\nThe seller sends the sku with all fields declared on this article (https://developers.vtex.com/docs/api-reference/marketplace-apis-suggestions#put-/suggestions/-sellerId-/-sellerSkuId-) for the marketplace to approve on the Received Skus module.\n\nThe ean field is declared as string type on the above article. However, despite appearing on the Received Skus UI, is being ignored by the matcher backend system and also by the catalog module, meaning the sku is being created with this field empty.\n\n\n##\n\n## Simulation\n\n\n1. Send a sku to the marketplace with the ean field set as string: `\"ean\": \"123456\"`\n2. Approve the sku as a new product on the marketplace's Received Skus module;\n3. Check that on the catalog this field is set as empty.\n\n##\n\n## Workaround\n\n\n**Before this issue is fixed and the system is working according to our docs**, the format that is currently working is sending the ean field as an array:\n`\"ean\": [\"123456\"]`\n\nAnother way is to set this field manually on the catalog side once the sku is approved."}