{"section":"known-issues","requestedLocale":"en","requestedSlug":"intelligent-search-returns-products-generated-by-sku-split-with-incorrect-availability","locale":"en","slug":"intelligent-search-returns-products-generated-by-sku-split-with-incorrect-availability","path":"docs/en/known-issues/Intelligent Search/intelligent-search-returns-products-generated-by-sku-split-with-incorrect-availability.md","branch":"main","content":"## Summary\n\nWhen an SKU specification is configured as a split attribute, Intelligent Search generates a derived product for each \"splitted SKU\". However, the availability data indexed for these derived products is not scoped to the individual split SKU, but instead it's flattened from the original product's stock balance, which aggregates the availability of all SKUs sharing that stock balance.\n\nAs a result, a split-generated product whose SKU is actually unavailable (zero stock confirmed at checkout) can still be returned by the main search query with availableQuantity: 0, instead of being correctly treated as unavailable/hidden, because the indexed availability doesn't reflect that specific SKU's real stock.\n\nThis issue is exclusive to scenarios where regionalization is enabled, since the affected availability field only comes into play when stock is being evaluated per seller/region rather than through a single, store-wide availability value.\n\n## Simulation\n\n- Configure an SKU specification as a split attribute for a product with multiple SKUs sharing the same stock balance in a store with regionalization enabled.\n- Ensure at least one SKU in that stock balance has available stock and another has zero (confirmed unavailable at checkout).\n- Index the catalog with Intelligent Search enabled.\n- Search for the product without applying the split attribute as a filter.\n- The split-generated product corresponding to the unavailable SKU is still returned, with `availableQuantity: 0`, instead of being excluded.\n\n## Workaround\n\nN/A"}