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.

Hi, i would like to understand the same. We’re working on an app that has exceeded the max number of the Non-Consumable SKUs (we noticed 40.000 SKU not 10.000). The problem now is that we need to remove old SKUs to free the space for the new ones and this process is really slow and it is impossible to work in this way, considering that we upload hundreds of SKUs each month. Our SKUs, like those of the OT should be, are non-consumable because are daily magazines, and we read from other user that moving this type of product from non-consumable to consumable causes an app rejection. @PBK Are you sure that just a note to the App Store Review Team on how we can “re-implement” the restorePurchase will be enough to use consumable products in this way? Can I ask if you already have/know something app that uses a logic like this in AppStore? Thanks.

Ok thanks a lot for the clarification about the review. For “daily magazines” i meant that a user can buy just one daily copy of the magazine and not a autorenewable subscription. We already have subscriptions but i’m just talking about non-consumable products. We sell a lot of daily in-app purchase but now we can’t handle anymore the process of deleting/loading a lot of new SKUs every time. I want to ensure that changing the non-consumable to consumable iaps, using the “tokens” logic you exaplained, will be approved by reviewers. I know that each reviewer could use different metrics to review the iap products, but for us now it’s difficult to apply this change if the new products will be rejected.