MMh... It depends what you are trying to do really. If you want to treat this as the same product but just track it as SCD2 then you need to find out how you can figure out that you're dealing with the same product. You need some sort of business rule to help you with that. For instance, is it the product name, or perhaps another candidate key (e.g., UPC, etc.)? This will allow you to reconcile these differences in your ETL and handle these cases any way you want.
If you track an aggregate fact with those you'll also need to reconcile across products though. For instance, add up the sales of your "old product" with the "new" one.
Anyway it's feasible, you just need to derive a rule and then do the work. If you use the SCD SSIS component I don't know how it works, but from a T-SQL or a Script task perspective, it's not complicated. You just need to have a rule you can rely on to do this.