asc-revenuecat-catalog-sync

To sync App Store Connect and RevenueCat catalogs, you can use a tool that automatically maps ASC subscriptions and IAPs to RevenueCat products, entitlements, offerings, and packages. It requires ASC CLI authentication and RevenueCat API write access.

Yes, you can audit App Store Connect and RevenueCat IAP mismatches using a read-only mode that generates a diff of missing or mismatched items without making changes. This allows you to review discrepancies safely before committing any updates.

The best way to align ASC in-app purchases with RevenueCat offerings is by using an automated apply mode that creates missing ASC groups and subscriptions, then directly maps them to the corresponding RevenueCat products, entitlements, offerings, and packages.

Yes, you need write-enabled RevenueCat MCP API keys and ASC CLI authentication to sync catalogs. Write access is required for the apply mode to successfully create missing items and map them between the two platforms.

No, syncing catalogs between ASC and RevenueCat does not automatically delete mismatched products. Safety defaults prevent automatic deletions, utilizing confirmation prompts and per-item failure reporting to ensure you maintain full control over your catalog data.

Yes, you can use catalog sync for both iOS and macOS app subscriptions. The synchronization applies to any apps where App Store Connect and RevenueCat need consistent product identifiers and entitlements across these Apple platforms.