{"section":"known-issues","requestedLocale":"en","requestedSlug":"vtexstructureddata-settings-page-shows-gtin-value-ean-as-default-but-the-app-uses-the-sku-id-until-the-setting-is-saved","locale":"en","slug":"vtexstructureddata-settings-page-shows-gtin-value-ean-as-default-but-the-app-uses-the-sku-id-until-the-setting-is-saved","path":"docs/en/known-issues/Store Framework/vtexstructureddata-settings-page-shows-gtin-value-ean-as-default-but-the-app-uses-the-sku-id-until-the-setting-is-saved.md","branch":"main","content":"## Summary\n\nThe settings page of `vtex.structured-data` shows **EAN** as the default selected GTIN Value. However, if no one has saved the app settings, the app falls back to a different default (`itemId`, i.e. the VTEX SKU ID). The default in `manifest.json` (`\"ean\"`) and the default in the code (`DEFAULT_GTIN_VALUE = 'itemId'`) are not the same.\n\nAs a result, stores that never saved the setting send the SKU ID in the JSON-LD `gtin` field, padded with leading zeros (e.g., SKU ID 512839 becomes `00512839`), and the `sku` field shows the same value. The EAN registered in the catalog is not used.\n\n## Simulation\n\n1. Use an account where `vtex.structured-data` is installed and the app settings were never saved.\n2. In the Admin, open the app settings (`/admin/apps/vtex.structured-data@<version>/setup`). The GTIN Value shows **EAN** as selected.\n3. Without saving, open a PDP of a product that has an EAN registered in the catalog.\n4. Inspect the `application/ld+json` script.\n5. Result: `gtin` and `sku` (in `Product` and `Offer`) show the SKU ID padded with zeros, not the EAN.\n\n## Workaround\n\n1. Make sure the app is installed in the account (`vtex install vtex.structured-data`). If it is only a dependency, the settings can’t be changed.\n2. In the Admin, open the app settings, select **EAN** as the GTIN Value and click **Save**.\n\n\nAfter saving, `gtin` shows the EAN. If the product has no valid EAN, `gtin` is left empty and `sku` shows the SKU ID."}