Guide
Subscription Bundles
Fixed recurring subscription bundles are implemented for checkout, upgrades, downgrades, proration, scheduled changes, entitlements, customer library cards, and lifecycle recovery.
SoundSync
Current support table
This table is the canonical public status for fixed developer-created subscription bundles.
| Capability | Status | Evidence or boundary |
|---|---|---|
| Offer creation | Implemented | POST /api/developer/subscription-bundles creates fixed recurring bundles from subscription-enabled products |
| Eligible products | Implemented | Products must be subscription-enabled; one-time products are rejected for fixed recurring bundles |
| Shared interval enforcement | Implemented | Each fixed bundle has one monthly or yearly billing interval |
| Checkout | Implemented | POST /api/subscriptions/bundles/checkout creates provider-backed checkout for the bundle |
| Proration | Implemented | change-preview and change-confirm support immediate upgrade proration and scheduled downgrades |
| Entitlements | Implemented | Bundle entitlement source and per-product subscription rows keep library and plugin access active |
| Already subscribed handling | Implemented | Duplicate active bundle checkout is rejected with a change recommendation |
| Dynamic build-your-own checkout | Not public | Build-your-own subscription checkout remains separate from fixed subscription bundles |
Current boundary
Mixed monthly/yearly products inside one bundle and dynamic build-your-own subscription checkout remain out of public scope. Use fixed bundle versions for public checkout and plan-change flows.