> ## 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.
# RollbackPro Restore Center, Single, Bulk, and Point-in-Time Rollback
> The RollbackPro Restore Center workflow. Filter by text, date, and entity type. View tracked versions side by side in Summary or JSON. Restore one item, bulk restore many, or roll back the entire entity type to a specific point in time.
Restore Center is where rollback actually happens. From a single screen you can search for any record, filter by date or entity type, view the full version history, compare any two versions side by side, and restore one record, many records, or an entire entity type back to a specific moment in time.
## Section title and navigation
The header shows the section name with a brief overview, plus the standard four-tab navigation across the top (Dashboard, Restore Center, Change Logs, Settings).
## Filters section
Three filter controls work together to narrow the grid down to the records you actually need.
### Text search
Type a keyword (e.g. a product name like "infinity") and click the search icon or press Enter.
> The search runs across **all fields** of the entity, not just Name and SKU. So a search for "blue" will match products whose description contains "blue" as well as those whose name contains it.
### Date picker
Pick a preset range or specify exact dates:
* All Time.
* 12 months.
* 30 days.
* 7 days.
* Today.
For a custom range, use **Select Dates**, pick start and end, click **Apply**, then **Submit** to apply the filter.
### Backup Entity (Content Type) filter
Filter by content type to view tracked versions for a specific entity:
Only one content type can be selected at a time. After selecting, click **Apply**.
## Snapshot of change history
The grid columns adapt to the selected entity type. For Products, the columns are:
| Column | What it shows |
| ------------------ | ---------------------------------------------------------- |
| **ID** | BigCommerce Product ID |
| **Name** | Product name |
| **SKU** | Product SKU |
| **Price** | Price at the time of this version |
| **Date Modified** | When the product was modified for this version |
| **Date Created** | When the first tracking record was created |
| **Version** | Version number; each version represents a backup or update |
| **Preview button** | Opens the side-by-side version comparison |
For other entities the columns adjust accordingly (Categories show parent and tree IDs, Customers show email and group, etc.).
## Side-by-side version comparison
Click **Preview** on a row to compare the current version with the selected version. The default view is **Summary**:
Switch to **Source code** for a JSON-format comparison:
The version dropdown lets you scroll through every tracked version. Pick the version you want to compare against, review the differences, and click **Restore to this version** if the older version is what you want.
> The Summary tab always shows the **complete dataset**. Difference highlighting (showing only what changed) is available only in the Source Code view.
## 1. Single-item rollback
The most common workflow:
1. Filter the grid to find the record (text search, date, or entity type filter).
2. Click **Preview** on the row.
3. Pick the version from the dropdown to compare against.
4. Review the side-by-side diff in Summary or Source Code.
5. Click **Restore to this version**.
The single record is restored. If the record exists, it is updated to match the stored version. If the record was deleted, it is recreated (BigCommerce assigns a new ID for deleted-then-restored records, see the FAQs).
## 2. Bulk rollback
Bulk Rollback restores **multiple entities** in one orchestrated operation. Use it when an editor changed many records at once and you need to revert a defined set, but not the whole entity type.
### How bulk rollback works
1. **Select items**, tick the rows you want to restore in the Restore Center grid.
2. **Initiate the rollback**, click the bulk rollback action.
3. **Parallel processing**, the system processes the selected items in parallel batches with built-in BigCommerce API rate limiting (default sub-batches of 5 with 3-second delays between every 10 records).
4. **Track progress**, monitor in real time via the status indicator.
5. **Review results**, including any errors.
### Key capabilities
* **Real-time progress tracking**, see how many items have been processed, succeeded, or failed.
* **Automatic retry**, transient API errors trigger automatic retry. If individual items still fail, you can manually retry only the failed records without re-processing the ones that succeeded.
* **Cancellation**, cancel a running bulk rollback at any time. Items already processed retain their restored state.
* **Error reporting**, view detailed error info for failures, escalate to support with one click.
## 3. Point-in-time rollback
Point-in-time Rollback restores an **entire entity type** to its state at a specific date and time. Use it when a bulk operation (CSV import, mass update, configuration change) has affected many records and you need to revert all of them to a known good state.
### How point-in-time rollback works
1. **Select the entity type**, e.g. Products, Categories, Customers.
2. **Select the target date and time**, the moment you want to restore to.
3. **Automatic discovery**, RollbackPro finds every record of that entity type modified at or before the target date.
4. **Orchestrated restore**, all discovered records restore in parallel batches with the same rate limiting, retry, and error handling as bulk rollback.
5. **Track and review**, real-time progress and per-record results.
### When to use point-in-time rollback
* After a bad CSV import that overwrote prices or descriptions across hundreds of products.
* After an accidental bulk edit that affected the wrong set of records.
* After a configuration change that cascaded across multiple categories or channels.
* For disaster recovery when many entities went wrong simultaneously and you need fast reversal.
Point-in-time rollback uses the same progress tracking, retry, cancellation, and error reporting capabilities as bulk rollback.
## How items are matched on rollback
Each item is matched by its **original ID**:
| Entity | Matched by |
| ----------------- | ---------------------------- |
| Products | Original Product ID |
| Categories | Original Category ID |
| Brands | Original Brand ID |
| Customers | Original Customer ID |
| Coupons | Original Coupon ID |
| Promotions | Original Promotion ID |
| Channels | Original Channel ID |
| Pages | Original Page ID |
| Blog Posts | Original Blog Post ID |
| Email Templates | Template Type ID |
| 301 Redirects | Original Redirect ID |
| Gift Certificates | Original Gift Certificate ID |
This ensures precise rollback. Even if you renamed a product or changed a page URL, the correct record is updated based on its unique ID.
### What happens during rollback
* **If the item exists**, it is updated to match the stored version.
* **If the item was deleted**, it is recreated with the stored data. BigCommerce may assign a new ID for the recreated record because BigCommerce IDs are incrementally generated.
## Help button
A **Help** button in the corner opens the corresponding help article in the knowledge base.
## Cross-links
* [Understanding the dashboard](/vortex-apps/rollback-pro/understanding-the-dashboard), where to spot which entity needs attention.
* [Change logs](/vortex-apps/rollback-pro/change-logs), audit of completed rollback operations.
* [Settings](/vortex-apps/rollback-pro/settings), per-entity backup configuration.
* [What we backup](/vortex-apps/rollback-pro/what-we-backup), the field reference of restorable data.
* [FAQs and known issues](/vortex-apps/rollback-pro/faqs-and-known-issues), known constraints (deleted brand IDs, multi-shipment orders, image gaps).
## FAQs
**Q. Why does a deleted-then-restored Product get a new ID?**
BigCommerce generates Product IDs incrementally and does not allow reuse. RollbackPro recreates the product with all its fields preserved, but the ID changes. SKU is the canonical reference and is preserved.
**Q. Why can I not restore Orders?**
Orders in BigCommerce cannot be deleted, and restoring them could trigger customer notification emails. RollbackPro stores order versions for viewing and comparison only, not restoration.
**Q. Can I cancel a running point-in-time rollback?**
Yes. Both bulk and point-in-time rollbacks support cancellation. Items already processed retain their restored state. Items not yet processed are skipped.
**Q. The point-in-time rollback discovered fewer records than I expected.**
Most likely cause: the backup index has gaps because real-time backup was disabled or paused for that entity during the period. Check Settings to confirm.
**Q. Some items failed during a bulk rollback. What do I do?**
Click the failed items to see the error detail. Use **Retry failed items** to re-process only the failed records (successful ones are not re-processed). For persistent failures, use the support escalation path on the Change Log entry.
**Q. Can I restore data to a different store?**
No. RollbackPro restores within the same BigCommerce store where it is installed. Cross-store recovery via [StagingPro](/vortex-apps/staging-pro) staging environments is on the roadmap.
**Q. Can I restore product images?**
The image metadata (URL, alt text) is restored. The image files themselves load from BigCommerce CDN at restore time. WebDAV-only or Image Manager images are not in the backup due to BigCommerce API limitations and are not restored.