A clear path from here.
Practical guides to connecting your platforms, preparing regional prices, and reviewing every change.
Getting started
Create an account in the RevenueStack app, choose your workspace, and connect a supported platform. Import a subscription before creating a pricing plan. Begin with a preview so you can inspect the workflow without changing live prices.
Connecting platforms
Choose Apple App Store Connect, Google Play Console, Paddle, or Stripe in the app. Follow its credential and permission prompts. Use only the required access, and never paste platform secrets into a support message or AI conversation. Available operations depend on the platform connection.
Importing subscriptions
Import the available product catalog and price records from your connected platform. Check the subscription, billing period, currency, and source platform before calculating recommendations. If data looks stale, refresh the import before preparing changes.
Automatic pricing
Set a base price and billing period. Automatic Pricing applies editable purchasing-power groups: Core 100%, Strong 80%, Growth 50%, and Access 30%. Review group membership and the resulting complete price schedule. Platform rules may require a nearby valid price point.
Custom pricing groups
Use custom groups when your strategy needs specific countries or multipliers. Override individual markets, exclude protected territories, and recalculate affected subscriptions. Advanced configuration is optional; automatic pricing is a suitable starting point for most teams.
Pricing matrix
Compare current and proposed prices by territory and platform. Read the currency with every amount and inspect each validation state. A matching number in different currencies does not mean equivalent value.
Dry-run preview
Run a preview before deployment. Review current, target, and platform-valid proposed prices, percentage differences, warnings, and unchanged markets. Resolve maximum-change warnings and confirm exclusions before progressing. A dry run does not change live prices.
Deployments
Confirm the subscription, territories, and platform before approving a deployment. Consider a pilot market first. Human confirmations and approval settings protect sensitive changes. Stripe uses base-price and replacement-price workflows; platform capabilities differ.
Audit history
Use history to inspect the platform, subscription, territory, previous and new prices, initiating actor, status, timestamp, and API response. Plan reversals against the platform’s current rules; an audit record does not guarantee an automatic rollback.
AI agents and MCP
Connect an MCP-compatible client using the endpoint and permissioned key supplied by your workspace. An agent can list platforms, inspect prices, compare configurations, run audits, prepare previews, validate changes, and review pending confirmations. Exact connection details and tool schemas are provided in the authenticated app. Sensitive deployments remain protected by your approval settings.
API-key security
Use the smallest necessary key scope. Store keys in your client’s secure credential configuration, never in public repositories. Revoke exposed keys promptly and replace them in authorized clients. Platform credentials and service-role keys must not be used as MCP workspace keys.
Troubleshooting
If import or validation fails, check connection permissions, subscription configuration, supported currency and price points, and the latest platform response. Refresh stale data and rerun the preview. Do not retry a deployment blindly when its outcome is uncertain; inspect history first. Contact the team if the issue persists.