If all this info is in the same table it's a lot more easier to create the query...
So i need to come up with a solution that do all this, without making my query's extremely complicated and more or less flexible to increase or decrease the number of departments/states that the product can pass/have in the future.
Don't get me wrong, but isn't that a contradiction all by itself?
I guees I have to disagree that a concept of "all in one table" by purposely violating the basic normalization rules will help you in the long run.
I strongly recommend to normalize your tables. The sooner the better. Normalization is the key for flexibility, I'd say.