bugs on variant id

services/productService.go

@@ -17,6 +17,7 @@ type ProductService interface {
 	GetCatalougeProducts(tenantID, locationID, subcategoryID, pageno, pagesize int, keyword string) ([]models.Products, error)
 	GetProductStocks(tenantID, locationID string) ([]models.Productstocks, error)
 	UpdateProductStatus(productIDs []int, status string) error
+	UpdateProductVariant(productid, variantid int) error
 	CreateProductStock(stocks []models.Productstock) error
 	CreateProduct(product models.Products) error
 	UpdateProduct(product models.Products) error
@@ -132,6 +133,16 @@ func (s *productService) CreateProductStock(stocks []models.Productstock) error
 	return nil
 }
 
+// UpdateProductVariant groups an existing product, or ungroups it with 0.
+//
+// The ordering screen reads products.variants to decide whether a product is
+// one choice or several, and nothing could write that column after creation —
+// so a catalogue import, which is how products actually arrive, produced
+// permanently ungrouped products.
+func (s *productService) UpdateProductVariant(productid, variantid int) error {
+	return s.repo.UpdateProductVariant(productid, variantid)
+}
+
 func (s *productService) UpdateProductStatus(productIDs []int, status string) error {
 	return s.repo.UpdateProductStatus(productIDs, status)
 }