StoreKit Win-Back Offers in 2026: Still Underused, Still Converting
Apple's win-back offers let you target lapsed subscribers with a discounted comeback price — two years after launch, adoption is still low. iOS 26's redesigned subscription UI makes now the right moment to enable them before fall.
Apple shipped win-back offers as part of StoreKit 2 at WWDC 2024, giving developers a first-party way to automatically surface a discounted comeback price to lapsed subscribers — on the App Store product page and inside the Manage Subscriptions sheet — with no push notification, no third-party SDK, and no marketing spend required. Two years on, adoption remains surprisingly low. Reports from subscription-app practitioners suggest the majority of eligible apps have never configured one. With iOS 26 now in beta and its redesigned subscription management UI giving win-back offers more visual prominence, the window between now and fall launch is the right time to fill that gap.
What Win-Back Offers Actually Are
Apple's subscription offer stack has four distinct mechanisms, and it's easy to conflate them:
| Offer type | Target audience | How it's served |
|---|---|---|
| Introductory offer | First-time subscribers | App Store product page & in-app, automatic |
| Promotional offer | Current or past subscribers | In-app only, developer-triggered |
| Win-back offer | Lapsed subscribers | App Store & Manage Subscriptions sheet, automatic |
| Offer code | Anyone with the code | Manual distribution (email, social, QR) |
The critical distinction: win-back offers are targeted and served automatically by Apple based on its own lapse signals — you configure the discount in App Store Connect (price, duration, billing periods), and the App Store handles delivery. You can also surface win-back offers manually inside your app using Product.SubscriptionOffer.OfferType.winBack in StoreKit 2, but the automatic App Store placement is the compounding value most teams leave unconfigured.
What Changes in iOS 26
A More Prominent Subscription Sheet
iOS 26 redesigns the Manage Subscriptions sheet as part of the broader Liquid Glass UI overhaul. Early beta builds show the win-back offer occupying a more prominent card position when a lapsed user navigates to re-subscribe. It's too early in the beta cycle to have conversion data, but the structural change means your localized offer title and promotional description — the copy you write in App Store Connect — will carry more visual weight than before. Worth testing now in your TestFlight build to confirm the copy renders cleanly at all Dynamic Type sizes and in your primary locales before you're in the fall submission crunch.
WB Offer Reporting in App Store Connect
App Store Connect's Subscription Report now includes a distinct Offer Type = WB row, letting you measure win-back conversion separately from promotional and introductory offers without building a custom filter. If you pull subscription reports programmatically via the App Store Connect API, audit your parser: apps that enumerate offer types as a fixed list will silently drop WB rows until updated. For ASC API reporting patterns more broadly, the rate limits and reporting guide on the AppsOps blog covers the subscription reports endpoint in detail.
Why Adoption Stays Low
Win-back offers require no extra infrastructure and no recurring cost. The reasons most apps have not enabled them are structural, not technical:
- Discovery gap: The configuration screen lives under App Store Connect → Subscriptions → [Group] → Win-Back Offers, a panel that looks like an advanced tab and gets skipped during initial setup.
- Cannibalization concern: Teams worry the discounted price will apply to subscribers who would have returned at full price anyway. In practice, if a user allowed their subscription to lapse, they have already declined to renew. A win-back offer at 40–50% of list price recovers revenue that otherwise stays at zero.
- Localization friction: Win-back offers require a localized promotional description for every storefront. For apps covering 39 localizations, that is a real one-time lift — see the AppsOps localization cost guide for a realistic effort estimate. The compounding effect over multiple renewal cycles makes it worthwhile.
Five-Step Implementation Checklist
- Open App Store Connect → Subscriptions → [Your Group] → Win-Back Offers and create the offer (recommended starting point: 50% off for one to three billing periods).
- Verify your StoreKit 2 integration handles
Product.SubscriptionOffer.OfferType.winBackif you want in-app surfacing in addition to the automatic App Store placement. - Write localized offer titles for your top markets — specific copy ("Welcome back — 3 months at 50% off") converts measurably better than generic ("Special Offer").
- For markets where you use PPP-adjusted pricing, consider anchoring the win-back price to the local PPP tier rather than a flat global discount. Re-subscription barriers are highest in price-sensitive markets, and many churned users left over affordability, not product quality. The PPP churn data reported here supports this pattern.
- Update your ASC API subscription report parser to handle the "WB" offer type so you can track recovery rates from day one.
With the iOS 26 beta refining fast and the fall submission window roughly ten weeks out, any win-back offer you configure today will accumulate real subscriber data before your next major update — which is exactly the retention baseline worth having going into Q4.
Sources and further reading
- Apple Developer — StoreKit documentation
- Apple — In-App Purchase and subscriptions overview
- RevenueCat Blog — subscription analytics and offer strategy
- Apple Developer News and Updates
Share this