Skip to main content
This page consolidates the V1 Change Logs and Restore Centre articles into one place. The Change Logs tab is the audit trail of restores and settings changes; the Restore Centre is where you search, compare versions, and run a restore. Most rollback work happens in the Restore Centre, with Change Logs as the verification step afterwards.

​
Change logs \

The Change Logs page displays the logs of data restores and changes to settings. Use it as the audit trail when you need to explain a change to an auditor, a colleague, or yourself a week later. Change logs page

​
What is captured

Each row in the Change Logs grid includes:
  • Date and time of the change.
  • User who triggered the change.
  • Entity type affected.
  • Entity ID that was changed.
  • Action (Restore, Settings change).
  • Status (Success, Failure).
  • Details / error message for failed actions.

​
When to use Change Logs

  • After a rollback, to confirm it succeeded.
  • When investigating a regression to see if a recent restore caused it.
  • Compliance and audit reporting.
  • Triage of failed restores; the error message in the Details column tells you why a restore failed (missing dependency, validation error, rate limiting, permission issue).

​
Investigating restore failures

If a restore failed, open the Change Logs entry and read the error. Common causes:
  • Missing dependencies. Related data (for example, products for a manual collection) does not exist.
  • Shopify API errors. Validation errors or rate limiting.
  • Permission issues. Insufficient access for the operation.
If the issue is unclear, contact helpdesk@vortexiq.ai with the Change Logs entry ID, the Restore ID, and the source store URL.

​
Help button

Clicking the Help button opens the Help page in the knowledge base.

​
Restore Centre \

The Restore Centre lets you search for specific data from your store or channels, view various versions of that data, and restore it to a chosen version. The restore functionality is essential for businesses needing to recover from issues such as data corruption, erroneous updates, or accidental deletions.

​
Content type filter

Select the entity type you want to browse. Available types include:
  • Catalogue: Products, Collections.
  • Customer: Customers, Orders, Discount Codes, Discount Automatic.
  • Content: Blogs, Pages, Files.
  • Settings: Themes, Gift Cards, Navigation Menus, URL Redirects.
  • Commerce and Markets: Markets, Delivery Profiles, Locations, Price Lists, Catalogs.
  • Metafield and Metaobject: Metafield Definitions, Metaobject Definitions, Metaobjects.

​
Restore button

Clicking the Restore button on a specific version displays the comparison view between the current version and the selected version. Click “Restore to this version” and confirm in the popup. The platform updates the record (or recreates it if deleted) to match the selected version.

​
Products

The Restore Centre lists every backed-up product. Click into one to see its version history. Products listed in Restore Centre Version differences of a product: Product version comparison Clicking “Restore to this version” displays a popup window asking for confirmation. After confirming, the product data is restored to the selected version. Restore confirmation popup What gets restored for Products:
  • Title, description, handle, product type, vendor, status, tags, template.
  • SEO title and description.
  • All variants with SKU, price, compare-at price, barcode, weight, inventory.
  • Product options and modifiers.
  • Images and media.
  • Metafields.
  • Inventory quantities per location (matched by location name).
  • Sales channel publishing assignments.

​
Collections

The Restore Centre lists every backed-up collection. Collections listed in Restore Centre Version differences of a collection: Collection version comparison Clicking “Restore to this version” displays a confirmation popup. After confirming, the collection data is restored. Collection restore confirmation For manual collections, product associations are removed and re-added from the backup. For smart collections, rules and conditions are restored; product membership is automatically determined by Shopify based on the restored rules.

​
Themes

Theme restore creates a new theme from the backed-up ZIP file with the name suffix _restored_{timestamp}. The restored theme is unpublished by default; review it before publishing. All theme files including templates, sections, snippets, layouts, CSS / JS assets, and settings are included. Menu restore returns the complete nested structure including all items, links, and parent-child hierarchy. If the menu was deleted, a new menu is created with the same handle and item structure.

​
Delivery profiles (shipping)

Delivery profile restore is a two-phase operation. Current zones, rates, and associations are removed first, then backup data is applied. Includes shipping zones, rate definitions with conditions, location groups, and product associations.

​
Markets

Market restore returns the name, handle, and active / inactive status. For deleted markets, regions are created from the backup’s country codes.

​
Discounts

Discount restore determines the type (code-based or automatic) from backup data and applies the appropriate update or create operation. Title, dates, usage limits, and combination rules are restored.

​
Other entity types

All other supported entity types (Customers, Pages, Blogs, Files, Gift Cards, URL Redirects, Locations, Price Lists, Catalogs, Metafield Definitions, Metaobject Definitions, Metaobjects) follow the same restore pattern:
  1. View available versions in the grid.
  2. Click Restore to compare current vs selected version.
  3. Review in Summary or Source Code view.
  4. Click “Restore to this version” and confirm.

​
Side-by-side comparison

The comparison view has two tabs:
  • Summary. Always displays the complete dataset for both versions in a readable format. Difference highlighting is not supported here; use Source Code for that.
  • Source Code. Raw JSON data for exact difference comparison. The recommended view for confirming “exactly what changed”.

​
Help button

Clicking the Help button opens the corresponding Help page in the knowledge base. The standard rollback flow looks like this:
  1. Customer service ticket arrives: “this product is wrong / missing / broken”.
  2. Open the Dashboard and click View on the relevant entity.
  3. The Restore Centre opens filtered to that entity. Search by ID or title.
  4. Click the version dropdown to see the version history.
  5. Click Restore on the version you suspect is the last good state.
  6. Compare in Source Code view to confirm the regression.
  7. Confirm the restore.
  8. Open Change Logs to verify the restore succeeded.
  9. Reply to the customer service ticket with the resolution.
The whole flow takes a few minutes for a single product or customer record.

​
FAQ

​
Why does the version dropdown not show a “deleted” version for some entities?

For non-webhook entities (Discounts, Blogs, Pages, Files, Themes, Gift Cards, Navigation Menus, URL Redirects, Markets, Delivery Profiles, Locations, Price Lists, Catalogs, Metafield Definitions, Metaobject Definitions, Metaobjects), webhook events are not available, so the deleted version cannot be indicated in the version dropdown list.

​
Why does the Summary view not highlight differences?

Difference comparison is not supported in the Summary view; it always displays the complete dataset. Use the Source Code view to see exact differences as a JSON diff.

​
What if my rollback fails?

Open Change Logs, find the failed entry, and read the error message. Common causes include missing dependencies, validation errors, and rate limiting. See the troubleshooting section above.

​
Can I restore to a version older than the most recent backup?

Yes. The version dropdown shows every captured version. Older versions remain restorable as long as the version is still in the version log.