hi,
if you design an entity relationship model (ERM) there are only entities and relationships. There aren't any "tables" there. Once you might map your ERM into relational model, which consists of tables (relations) only.
Your shown relationship ' (ONE) Warehouse-> could have many -> orders' expresses the trivial fact that a warehouse has many orders. It is already clear that those orders belong to a sole warehouse because your given task is headlined by "Design a ERM datamodel for a warehouse". Thus, we should omit the entity warehouse.
Your warehouse datamodel may have these entities: products, customers, orders, orderlines, suppliers, stock (to record products on stock)
where the following relationships can be found:
customers ------ one-to-many ----<- orders
orders ----- one-to-many -----<- orderlines
products ----- one-to-many ----<- orderlines
products ->---- many-to-many ----<- suppliers
products ----- one-to-many ----<- Stock
If you are to design the relationship between suppliers and products more detailed in an analogous way to customers/orders, you have to adopt similar entities such us purchase and purchase_orderline.
You also may have a look at
http://www.databaseanswers.org/data_models/index.htm.
brs, cliff