title: Using generic in-app purchase items for a dynamic range of digital products
body: <p>Have any of you implemented something similar to the below scenario? </p>
  
  <p>Consider an app which provides audiobooks:  </p>
  
  <ul>
  <li>The books are maintained dynamically from a web based UI by the authors.</li>
  <li>The books become available for users of the iOS app, as in-app purchase items.</li>
  </ul>
  
  <p>By default Apple guidelines suggests using non-consumable IAP, and adding continuously as many IAP items as many books we have. But this is not proper for us, as the authors won’t have access to iTunesConnect, so it cannot be dynamic, “self-serving”.  </p>
  
  <p>Therefore we are planning to create a set of generic "consumable" IAP items like “Book worth $0.99”, “Book worth $1.99”, and so on. Then in the app we’ll show the corresponding IAP item for the books as specified by the authors, when they added it to our system.</p>
  
  <p>Of course we store the purchased items on the server side, so the user will always have access to the purchased items -- even if they access it later from another device.</p>
  
  <p>Will Apple approve this implementation?<br>
  Does it fit with their IAP policy?  </p>
  
  <p>I’ve found some similar quite old topics in the forum but the answers were confusing. 
  Have you implemented something similar and get approval from Apple?</p>