/asc-revenuecat-catalog-sync

name: asc-revenuecat-catalog-sync
description: Reconcile App Store Connect subscriptions and in-app purchases with RevenueCat products, entitlements, offerings, and packages using asc and RevenueCat MCP. Use when setting up or syncing subscription catalogs across ASC and RevenueCat.

asc RevenueCat catalog sync

Use this skill to keep App Store Connect (ASC) and RevenueCat aligned, including creating missing ASC items and mapping them to RevenueCat resources.

When to use

• You want to bootstrap RevenueCat from an existing ASC catalog.
• You want to create missing ASC subscriptions/IAPs, then map them into RevenueCat.
• You need a drift audit before release.
• You want deterministic product mapping based on identifiers.

Preconditions

• `asc` authentication is configured (`asc auth login` or `ASC_*` env vars).
• RevenueCat MCP server is configured and authenticated.
• In Cursor and VS Code, OAuth auth is available for RevenueCat MCP. API key auth is also supported.
• You know:
• ASC app ID (`APP_ID`)
• RevenueCat `project_id`
• target RevenueCat app type (`app_store` or `mac_app_store`) and bundle ID for create flows
• Use a write-enabled RevenueCat API v2 key when applying changes.

Safety defaults

• Start in **audit mode** (read-only).
• Require explicit confirmation before writes.
• Never delete resources in this workflow.
• Continue on per-item failures and report all failures at the end.

Canonical identifiers

• Primary cross-system key: ASC `productId` == RevenueCat `store_identifier`.
• Keep `productId` stable once products are live.
• Do not use display names as unique identifiers.

Scope boundary

• RevenueCat MCP configures RevenueCat resources; it does not create App Store Connect products directly.
• Use `asc` commands to create missing ASC subscription groups, subscriptions, and IAPs before RevenueCat mapping.

Modes

1) Audit mode (default)

1. Read ASC source catalog. 2. Read RevenueCat target catalog. 3. Build a diff with actions:

• missing in ASC
• missing in RevenueCat
• mapping conflicts (identifier/type/app mismatch)

4. Present a plan and wait for confirmation.

2) Apply mode (explicit)

Execute approved actions in this order: 1. Ensure ASC groups/subscriptions/IAP exist. 2. Ensure RevenueCat app/products exist. 3. Ensure entitlements and product attachments. 4. Ensure offerings/packages and package attachments. 5. Verify and print a final reconciliation summary.

Step-by-step workflow

Step A - Read current ASC catalog

asc subscriptions groups list --app "APP_ID" --paginate --output json
asc iap list --app "APP_ID" --paginate --output json
# for each subscription group:
asc subscriptions list --group-id "GROUP_ID" --paginate --output json

Step B - Read current RevenueCat catalog (MCP)

Use these MCP tools (with `project_id` and pagination where applicable):

• `mcp_RC_get_project`
• `mcp_RC_list_apps`
• `mcp_RC_list_products`
• `mcp_RC_list_entitlements`
• `mcp_RC_list_offerings`
• `mcp_RC_list_packages`

Step C - Build mapping plan

Map ASC product types to RevenueCat product types:

• ASC subscription -> RevenueCat `subscription`
• ASC IAP `CONSUMABLE` -> RevenueCat `consumable`
• ASC IAP `NON_CONSUMABLE` -> RevenueCat `non_consumable`
• ASC IAP `NON_RENEWING_SUBSCRIPTION` -> RevenueCat `non_renewing_subscription`

Suggested entitlement policy:

• subscriptions: one entitlement per subscription group (or explicit map provided by user)
• non-consumable IAP: one entitlement per product
• consumable IAP: no entitlement by default unless user asks

Step D - Ensure missing ASC items (if requested)

Resolve every parent and version before writing. Match groups by exact reference name and products by `productId`; never treat a display name as identity. Reuse the canonical ID when the resource already exists, and run a create command only when the fully paginated read proves it is missing. A RevenueCat product mapping is not proof that the corresponding ASC subscription is review-ready.

# Resolve GROUP_ID by exact referenceName.
asc subscriptions groups list --app "APP_ID" --paginate --output json
# If and only if the fully paginated list has zero exact matches:
asc subscriptions groups create --app "APP_ID" --reference-name "Premium" --output json
# For one match, reuse its ID. For more than one, stop and require an explicit GROUP_ID.

# Resolve SUB_ID by exact productId within GROUP_ID. Run setup only for a missing
# parent or an explicitly approved reconciliation of that same product ID.
asc subscriptions list --group-id "GROUP_ID" --paginate --output json
# If and only if the fully paginated list has zero exact matches, run setup:
asc subscriptions setup \
  --app "APP_ID" \
  --group-id "GROUP_ID" \
  --reference-name "Monthly" \
  --product-id "com.example.premium.monthly" \
  --subscription-period ONE_MONTH \
  --review-screenshot "./review.png" \
  --price "3.99" \
  --price-territory "USA" \
  --territories "USA" \
  --no-verify \
  --output json
# For one match, reuse its ID. For more than one, stop and require an explicit SUB_ID.
# Re-run setup for an existing SUB_ID only for an explicitly approved reconciliation.

# Resolve the unique mutable group version for this review lifecycle.
asc subscriptions groups versions list --group-id "GROUP_ID" --state PREPARE_FOR_SUBMISSION --paginate --output json
# If and only if the list has zero matches:
asc subscriptions groups versions create --group-id "GROUP_ID" --output json
# For one match, reuse .data[0].id. For more than one, stop and require an explicit GROUP_VERSION_ID.

# Resolve the en-US localization on GROUP_VERSION_ID. Create it only when
# missing; update the resolved localization ID when its values differ.
asc subscriptions groups versions localizations list --version-id "GROUP_VERSION_ID" --paginate --output json
asc subscriptions groups versions localizations create --version-id "GROUP_VERSION_ID" --locale "en-US" --name