NEW Let your AI agent preview price changes MCP
RevenueStack.
Sign inStart free
← All documentation

Dry runs and approvals

A dry run verifies the intended rows without writing to a provider. Deployment requires a fresh, matching preview and an authenticated human decision.

  1. Run the analysis

    Open Preview & Dry-Run, select the application and subscription, then choose Re-run Analysis.

  2. Review every row

    Check current, target, final, difference, provider identifiers, warnings, excluded markets, and unchanged rows.

  3. Resolve blockers

    Refresh stale data, correct invalid rows, remove unintended protections, or reduce territories when a plan limit applies.

  4. Acknowledge the confirmation

    An OWNER or ADMIN confirms the exact signed rows in the deployment modal.

  5. Follow progress

    The deployment view reports totals, the current step, and per-row success or failure.

Approval model

Live

Web deployments can be approved by an OWNER or ADMIN. MCP WRITE tools only stage a confirmation; an OWNER or ADMIN must approve it in RevenueStack. There is no multi-approver or maker/checker rule.