Properly handle import when a Product Model has the same code of a different Product in Akeneo

[mmenozzi]

Currently if on Akeneo there's a Product Model whose code is the same of a different Product which is not a variant of the Product Model itself, the importer puts everything inside the same Product on Sylius.

For example if on Akeneo you have:

• Product Model A
• Product A.1 (variant of A)
• Product A.2 (variant of A)
• Product A

On Sylius you'll have:

• Product A
• Product Variant A (variant of A)
• Product Variant A.1 (variant of A)
• Product Variant A.2 (variant of A)

Instead, expected result on Sylius should be:

• Product A
• Product Variant A.1 (variant of A)
• Product Variant A.2 (variant of A)
• Product ?
• Product Variant A (variant of ?)

The issue here is that Akeneo have Product Models only for configurable products but Sylius always have Product (which is the Product Model on Akeneo) and Product Variant (which is Product on Akeneo). When the product importer imports a simple Product from Akeneo it creates a the Product and Product Variant on Sylius with the same code. So there would be a code collision between Product on Sylius if on Akeneo a Product Model has the same code of a different Product.

How should we handle this?