title: Django ORM and dependencies
body: <p>I am currently brainstorming about building an existing PHP CodeIgniter project in Django.
  I spit through the documentation a bit already and done some online tutorials to test how it works and am really charmed by it.</p>
  
  <p>The theoretical design issue I'm currently facing is that in what I have in mind; <strong><em>Apps</em></strong> will be dependent on each other, yet the Django documentation itself states that it <strong><em>Apps</em></strong> should be <em>pluggable</em>.</p>
  
  <p>The thing is that I have a <strong><em>Products</em></strong> App with different sub-properties like colors, groups, models (foreign key relationships). Now I started thinking on how to use my <strong><em>Invoices</em></strong> App, but I instantly notice that the <strong><em>Invoices</em></strong> App will need products from the <strong><em>Products</em></strong> App.</p>
  
  <p>I wonder how other people do this in their Django projects? Would I need to rethink the way I design my whole application (Products, Invoices, Orders, Deliveries, Email, etc.) and how they are linked individually?</p>
  
  <p>Would I tell Django that my <strong><em>Invoices</em></strong> App <em>needs</em> my <strong><em>Products</em></strong> App to be initialized , or do I totally remodel the situation having something like an <strong><em>ERP</em></strong> App that house all those parts as their own <em>Models</em>?</p>
  
  <hr />
  
  <p>In the end I want to have my front-office to also be converted to Django (Webshop) and access my back-office (ERP) products. I also wonder how I would incorporate that then.</p>