> ## Documentation Index
> Fetch the complete documentation index at: https://docs.appreval.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Tools: exporting data and bulk operations

> Export subscriptions, orders and price changes to CSV, and apply variant, price or status changes to many subscriptions at once.

The **Tools** section has two independent blocks: data export and bulk operations.

***

## Exporting data (CSV)

Generates a file that downloads in your browser. You choose what to export and with which filters:

| Data set          | What it contains                                 |
| ----------------- | ------------------------------------------------ |
| **Subscriptions** | Your subscriber base with their terms and status |
| **Orders**        | The orders generated by subscriptions            |
| **Price changes** | The history of amount modifications              |

Available filters:

* **Status**: all, active, paused, cancelled or pending
* **Products**: narrow to one or several products with the selector
* **Dates**: a **From / To** range, optional

Then you click **Generate and download CSV**.

<Tip>
  This is the route for cross-referencing data with your CRM, building your own reports or reviewing a cohort. Reval has no built-in cohort or LTV reports, so the CSV is what lets you calculate them externally.
</Tip>

***

## Bulk operations

Actions that affect several subscribers at once. **Each one shows you how many subscriptions it reaches and asks for confirmation before running.** Price and status changes take effect from the next cycle in Mercado Pago — they never alter a charge that already happened.

### Bulk variant change (swap)

The main operation. Replaces one variant with another across every subscription that uses it.

It's useful, for example, when you discontinue a format and want to migrate every subscriber to the replacement without asking them to do anything.

<Steps>
  <Step title="Choose the scope">
    Active and paused subscriptions, active only, or paused only.
  </Step>

  <Step title="Choose the variant to replace" />

  <Step title="Choose the destination variant" />

  <Step title="Review the scope and confirm">
    Before running you'll see how many subscriptions it reaches.
  </Step>
</Steps>

Details that matter:

* In subscriptions with several products, **only that line is changed**, the rest stays as it was
* It only reaches destination variants that have an **active plan on the same frequency**. Those that don't qualify are skipped and recorded as skipped
* The price is **recalculated according to the plan** of the new variant
* It takes effect from the next cycle

### Resyncing prices

Reapplies the plan's price to subscribers whose amount became out of date — typically after changing a plan's price or the list price of a product on percentage-based plans.

It's **retryable**: it skips subscriptions that are already up to date, so running it again is safe and only touches what's left.

<Note>
  **Paused subscriptions.** Mercado Pago doesn't accept modifying a paused mandate, so on those the change —price or variant— is stored in Reval and pushed to MP **on resume**. The end result is the same, but until the customer resumes, the amount in Mercado Pago is still the old one. You don't need to do anything: the sync is automatic.

  If you ran bulk operations before August 2026, in the history you'll see paused ones counted as "with error". That was a limitation since fixed — those subscriptions weren't left broken.
</Note>

### Bulk pause and resume

Pause a whole segment for a temporary closure, and resume it afterwards.

<Warning>
  Resuming restarts the charge cycle **from the resume date**, not from where it had left off. A two-week bulk pause shifts everyone's charge date by two weeks. That's a characteristic of Mercado Pago mandates, not of the bulk action.
</Warning>

***

## History and traceability

Every operation run is recorded with its date, the total reached and the breakdown between successful, skipped and errored.

From the history you can **download the CSV for that specific operation**, with per-subscription detail: what changed, from which variant to which, from which amount to which, and the reason in the skipped or failed cases. The record stores the email and the values as they were at the time, so the detail stays accurate even if the subscription changes later.

***

## What isn't there

| Doesn't exist                                       | Alternative                                                    |
| --------------------------------------------------- | -------------------------------------------------------------- |
| Condition builder (by product, amount, with AND/OR) | The export filters, and the per-status scope on each operation |
| Bulk cancellation                                   | You cancel one by one from the detail                          |
| Applying a coupon or discount code in bulk          | Price resync, or changing the plan's price                     |
| Scheduling an operation for later                   | They run immediately                                           |