asc-revenuecat-catalog-sync

You sync App Store Connect subscriptions with RevenueCat by auditing both catalogs to build a diff, mapping or creating missing items, and configuring offerings through a deterministic workflow with explicit write confirmations and safety guards.

Reconciling IAP products safely involves an auditable workflow that uses a store_identifier-based canonical mapping to prevent drift, requires explicit write confirmations for changes, and enforces a strict no-deletion policy to protect existing catalog items.

Yes, you can map existing ASC in-app purchases to RevenueCat entitlements safely, as the workflow explicitly prevents deletions, uses a canonical store_identifier mapping to prevent drift, and requires explicit write confirmations before applying any changes.

Audit mode scans ASC and RevenueCat catalogs to identify gaps and mismatches, building a diff of missing subscription groups, IAPs, and entitlement mappings before any write operations are attempted in apply mode.

Yes, MCP tooling and asc commands are required to configure RevenueCat offerings from App Store Connect, as the Skill uses them to execute the auditable workflow for creating missing items, mapping products, and attaching them to entitlements.