title: Database Design for Order management for multiple sources
body: <p>I would like to know what's the best method for building an order management database where there are multiple shops, each with their own list of products and prices.</p>
  
  <p>My Current Design</p>
  
  <pre><code>Product
  ------
  name
  image
  price_per_item
  
  
  Shop
  ------
  name
  product_list - Manytomany field 
  
  
  Order
  ------
  order_id    primary key
  shop 
  
  
  Order Content
  ------
  order_id    foreign key to Order
  product
  quantity
  </code></pre>
  
  <p>The problem I foresee with this is that each shop may have the same item but may sell that item at a different <code>price_per_item</code>.</p>
  
  <p>How exactly do I build a db where Shops can manage to have different price per items and yet have multiple items to sell?</p>