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

# Vortex Backup, getting started with rollback

> The four-step rollback walkthrough for Vortex Backup, from connecting your Shopify store to identifying the item, initiating the rollback, and verifying the result. Includes common scenarios and what gets restored.

This guide walks through the rollback process step by step. By the end you will have rolled back one item to a previous stored version, verified the result, and understand what gets restored versus what does not.

## Before you begin

### Preparation checklist

* Identify the item to roll back. Know the specific product, customer, or other entity you want to restore.
* Have the item ID ready. You need the document ID to perform the rollback.
* Verify the stored version exists. Ensure the item has a stored version available.

## Step 1. Connect your store

Provide your store credentials to connect to the rollback platform. You will need:

* Your Shopify store URL (for example, `mystore.myshopify.com`).
* Access credentials for the Vortex Backup app.

Your data is secure. The platform uses encrypted connections.

If Vortex Backup has been installed and the initial backup has run, your store is already connected. See [Setup and onboarding](/vortex-apps/vortex-backup/setup-and-onboarding) if not.

## Step 2. Identify the item to roll back

Rollback works on individual items. You specify two parameters:

| Parameter   | Description                                                     |
| ----------- | --------------------------------------------------------------- |
| Index Name  | The entity type (for example, products, customers, collections) |
| Document ID | The unique Shopify ID of the specific item to restore           |

### Finding the item ID

Each entity in your store has a unique Shopify ID. This ID is used to precisely identify which item to roll back. You can find IDs in:

* The Shopify Admin URL when viewing an item.
* The Vortex Backup Restore Centre item grid.
* An export from the Shopify GraphQL API.

## Step 3. Initiate the rollback

Once you have identified the item:

1. Select the index (entity type).
2. Enter the document ID.
3. Submit the rollback request.

The platform will:

* Retrieve the stored version of that item.
* Update (or recreate) the item in your store to match the stored version.

You can also initiate rollback directly from the [Restore Centre](/vortex-apps/vortex-backup/change-logs-and-restore#restore-centre) by clicking the Restore button on the version you want; this is the recommended path because you get a side-by-side comparison before confirming.

## Step 4. Verify the rollback

After rollback completes:

1. Check the item in your store. Verify the data is restored correctly in Shopify Admin.
2. Review related data. If you rolled back a product, check its variants and images. If you rolled back a collection, check its product associations.
3. Test functionality. Ensure the item works as expected (a product appears on its PDP, a discount code applies at checkout, a navigation menu links to the right page).

## What gets restored

When you roll back an item, all fields for that item are restored. The exact field list depends on the entity type.

| Entity type            | What is restored                                                                               |
| ---------------------- | ---------------------------------------------------------------------------------------------- |
| Products               | Title, description, variants, images, pricing, inventory, metafields, sales channel publishing |
| Customers              | Name, email, addresses, tags, marketing consent, tax exemptions                                |
| Collections            | Title, handle, products (manual) or rules (smart)                                              |
| Pages                  | Title, content, handle, publish status                                                         |
| Discount Nodes         | Discount type, value, rules, applies-to configuration                                          |
| Navigation Menus       | Menu items, links, nested structure                                                            |
| Markets                | Market configuration, regions, currencies                                                      |
| URL Redirects          | Source path, target path                                                                       |
| Delivery Profiles      | Shipping zones, rates, product assignments                                                     |
| Locations              | Location name, address, fulfilment settings                                                    |
| Price Lists            | Prices, price adjustments, currency settings                                                   |
| Catalogs               | Catalog configuration and associations                                                         |
| Metafield Definitions  | Definition name, namespace, type, validations                                                  |
| Metaobject Definitions | Definition schema, field definitions                                                           |
| Metaobjects            | Metaobject field values and associations                                                       |

The full per-field reference is in [Settings and fields](/vortex-apps/vortex-backup/settings-and-fields#field-reference).

## Rolling back multiple items

If you need to restore multiple items:

1. Perform a rollback for each item individually.
2. Start with items that have dependencies (for example, products before collections that reference them).
3. Verify each rollback before proceeding to the next.

For large multi-item restore scenarios (for example, "we ran a botched bulk product update on 200 SKUs"), the recommended pattern is to restore one item to confirm the workflow, then script the remainder via the Vortex IQ API; contact the [Helpdesk](https://helpdesk.vortexiq.ai/portal/en/home) for the API token.

## Common scenarios

| Scenario                        | What to roll back                                                      |
| ------------------------------- | ---------------------------------------------------------------------- |
| Accidentally edited one product | Roll back that specific product ID                                     |
| Wrong price on a product        | Roll back that product to restore correct pricing                      |
| Customer data corrupted         | Roll back that specific customer ID                                    |
| Collection lost its products    | Roll back that collection ID                                           |
| Navigation menu broken          | Roll back that menu ID                                                 |
| URL redirect broken             | Roll back that URL redirect ID                                         |
| Shipping profile misconfigured  | Roll back the delivery profile ID                                      |
| Theme regression                | Restore the theme; a new theme is created so the live one is untouched |

## FAQ

### What if the item was deleted from my store?

If the item exists in the backup, it is recreated in the store with the stored data. New Shopify IDs are generated for recreated items, but Vortex Backup tracks the original ID so future rollbacks of the recreated item work correctly.

### Will rollback affect orders?

No. Order data is read-only at rollback time. Order history, financial records, and fulfilment data are never modified by Vortex Backup.

### Can I undo a rollback?

There is no automatic undo-rollback feature. However, the previous version of the item is still in the version history; select that version and roll back again to reverse.

### How fresh are the backups?

For Products, Collections, Customers, and Orders, backups are real-time (captured as Shopify fires the webhook). For all other entities, backups are as fresh as the last manual backup, which is why the [Settings page](/vortex-apps/vortex-backup/settings-and-fields) recommends running a manual backup before and after any major change to those entities.

## Related pages

* [Setup and onboarding](/vortex-apps/vortex-backup/setup-and-onboarding), install and the post-install walkthrough
* [What we backup and rollback](/vortex-apps/vortex-backup/what-we-backup-and-rollback), per-entity backup and rollback support
* [Change logs and restore](/vortex-apps/vortex-backup/change-logs-and-restore), the Change Logs audit and Restore Centre comparison
* [Understanding the dashboard](/vortex-apps/vortex-backup/understanding-the-dashboard), the dashboard layout
* [Settings and fields](/vortex-apps/vortex-backup/settings-and-fields), real-time vs manual settings plus the field reference
* [Shopify connector](/integrations/connector-catalogue), the underlying connector
