Hello,
You have me slightly confused so perhaps I should request clarity:

I believe that each product should have its own ID value. If this value requires more than a single field - such as a product code and type then this should give you its primary key sufficient to meet the requirements of your design.

This would require the implementation of a "Candidate Key value" within the table.

The Distribution Centre entity will have a relationship with the store and will have a relationship with the product BUT the MAJOR relationship will be with the store.

My advice now would be to start working from the two types of product and to build a way to seperate them within the system through treating them as a specialisation of a product (a product can be a fresh product or a non fresh product. Two tables) OR using a candidate key value (such as fresh/Nonfresh) as a field within a table to identify the difference between them.

If any of this post has further confused you then my apologies. What you must not do is look at a product and use its price as a description of what it is, especially as this is the only part of the product that will change.

Kind regards

Steve