> For the complete documentation index, see [llms.txt](https://help.smartrr.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartrr.com/docs/support/bulk-updates.md).

# Bulk Updates

Smartrr allows customers to do 2 bulk updates at the moment: Next order date changes and price updates.

**Bulk Updates** lets you make changes to many subscriptions at once, instead of editing them one by one. This is the place to go whenever you need to update subscription data across your customer base — whether that's shifting order dates or syncing subscription prices with your latest Shopify pricing.

Currently, Bulk Updates supports two workflows:

* [**How to Bulk Update the Next Order Date for Subscriptions**](/docs/support/bulk-updates/how-to-bulk-update-the-next-order-date-for-subscriptions.md) — upload a CSV to change the next order date for multiple subscriptions at once.
* **How to Manage Subscription Price Updates** — review and apply Shopify product price changes across your existing (grandfathered) subscriptions, with optional customer email notifications.

***

*Related articles:*

* [*How to Bulk Update the Next Order Date for Subscriptions*](/docs/support/bulk-updates/how-to-bulk-update-the-next-order-date-for-subscriptions.md)
* [*How to Manage Subscription Price Updates*](/docs/support/bulk-updates/how-to-manage-subscription-price-updates.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.smartrr.com/docs/support/bulk-updates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.