Variants URLs/@id in structured data — question triggered by Shopping/Merchant

Hi Nicolas,

I’m reaching out with an SEO-oriented question about variants and URLs, triggered by what I’m seeing in Google Shopping / Merchant listings.

I have a main product page with variants (numbers 0–9). In the structured data, each variant Offer currently points to a URL built like:
index.php?option=com_hikashop&ctrl=product&task=show&cid=...&name=...&Itemid=...

In Shopping/Merchant listings, I sometimes see Google treating variants as distinct “items”, and it made me wonder whether my current variant URLs/identifiers in the structured data are ideal, or whether I should provide more stable unique identifiers for each variant.

ChatGPT suggested generating a stable, unique identifier/URL per variant in the structured data (for example a distinct @id and/or a distinct url per variant/offer) so Google can better understand each item/variant in the ProductGroup/hasVariant context.

Before attempting anything, I want to confirm the safest approach from both a HikaShop and SEO perspective:

Is it technically possible/recommended in HikaShop to output a distinct @id and/or distinct URL per variant inside the JSON-LD, without turning variants into separate product pages?

Could outputting unique URLs/identifiers per variant create SEO risks such as:

multiple URLs being discovered/indexed for essentially the same product (cannibalization)

conflicts with canonical tags (main product canonical vs variant URLs)

the need for 301 redirects if Google starts indexing variant URLs

issues caused by Itemid/menu routing generating different URL paths for the same content

If the recommended approach is to avoid unique variant URLs, what’s the best practice in HikaShop for variant structured data (ProductGroup + hasVariant) so Google understands the variants while keeping a single canonical product URL?

If it helps, I can paste the current JSON-LD excerpt (ProductGroup + hasVariant array) and my canonical setup.

Thanks a lot,
José Ángel