{"section":"known-issues","requestedLocale":"en","requestedSlug":"fixed-prices-import-may-incorrectly-report-success-when-sku-column-is-formatted-as-a-number","locale":"en","slug":"fixed-prices-import-may-incorrectly-report-success-when-sku-column-is-formatted-as-a-number","path":"docs/en/known-issues/Pricing & Promotions/fixed-prices-import-may-incorrectly-report-success-when-sku-column-is-formatted-as-a-number.md","branch":"main","content":"## Summary\n\nWhen importing Fixed Prices using a spreadsheet where the **SKU column is formatted as a number**, the import may behave unexpectedly.\nTwo behaviors have been identified:\n\n- The SKU may be incorrectly saved with a decimal suffix, such as `77,0`, instead of the expected SKU value.\n- If there is also a validation error in the spreadsheet, the validation may fail silently for the affected item. The import report can incorrectly return an **\"OK\" status**, even though the fixed price was not actually saved.\n\nThis can cause confusion because the merchant receives a successful import report while the corresponding fixed price is not updated in the Admin.\n\n## Simulation\n\n1. Prepare a Fixed Prices import spreadsheet.\n2. Format the **SKU column as a number** instead of text/string.\n3. Include a valid fixed price to be imported.\n4. Import the spreadsheet through the Fixed Prices import flow.\n5. Check the import result and the corresponding fixed price in the Admin.\n\nIn scenarios where the SKU is interpreted as a numeric value, it may be saved with a decimal suffix.\nThe issue can become more severe when the spreadsheet also contains an input validation error. In this case, the affected item may fail validation without the error being properly reflected in the import result, while the report still shows **\"OK\"**.\n\n##\n\n## Workaround\n\nBefore importing the spreadsheet, make sure that the **SKU column is formatted as text/string**, rather than as a number.\nAfter the import, merchants should also validate the updated fixed prices in the Admin instead of relying exclusively on the import report.\nThis workaround helps avoid the scenario identified in the investigation while the underlying validation behavior is being addressed"}