In app purchase for a large amount of items

Question

Created May ’19

Replies 2

Boosts 0

Views 1.7k

Participants 3

My app lets photographers upload their work and offer it for sale. There are hundreds of images uploaded daily. I've created a single Consumable in-app purchase products with a set price and all photos can be purchased using this single IAP product (all images are offered for the same price). We store the purchase information on our database so the buyer can later download it (on the iOS app, android and web).

However - the review team rejected the in-app-purchase product, saying it has to be a Non-Consumable product. My problem is that is we set the product to non-consumable, if a user buys photo A, they'll be able to get every photo for free because Apple will think they already own the product. Making a separate non-consumable product for each photo is not feasible because there are tens of thousands of photos and hundreds of new ones uploaded daily.

Any ideas? I've been trying to resolve this issue with the review team for 3 weeks now with no luck...

Boost

Answer 1

MMarras OP

Apr ’20

I'm pretty curious to understand the same for Non-Consumable products. We're working on an app that has exceeded the limits of SKUs (40.000), all of those are Non-Consumable (they are daily magazines). Now, everytime we want to add new SKUs, we have to delete a lot of old SKUs to free the space.

Big problem is that the process to insert and delete is really slow (up to 2 minutes to create just a new one!), we're using a script that uses Fastlane to upload/delete the in-app purchases to AppStore Connect, beacuse it is impossible through the AppStore Connect console or with the iTMSTransporter.

Have you maybe found a solution on this? We were thinking the same, so by creating just one SKU for differente products, but as you said i imagine that will be rejected.

0

Answer 2

PBK OP

Apr ’20

The solution is to create the consumable IAP 'credit' and to exchange a certain number of credits for each 'product'. Because of App REviews valid concern that the purchase should be 'non-consumable' you also need to create a record of the exchange of credits for a 'product' so the user can restore their 'product' purchases. And then include a note for App Review explaining what you did - how you are actually selling the product as a non-consumable but using a consumable 'credit' system to effect the purchase - and how you have implemented a restore function.

The user's iCloud key-value file is an easy way tpo implement the 'restore' function.

0