Rollback and stale protection

Overview

Rollback helps you return variant pricing toward values captured before a SalePilot execution, using snapshots and current data from Shopify. It is a safety tool — not a substitute for backups, manual review, or compliance with your own pricing policies.

What rollback does

When you roll back, SalePilot attempts to restore prices (including compare-at where applicable) from saved snapshot information tied to your task, subject to Shopify API behavior and stale protection rules.

Rollback does not guarantee restoration of every field in every edge case; concurrent edits, manual admin changes, or third-party apps may affect outcomes.

How SalePilot uses snapshots

Before or during execution, SalePilot records snapshot data sufficient to know prior variant prices for rollback workflows. The accuracy of rollback depends on what was captured at the time and what Shopify returns when rollback runs.

If snapshot data is incomplete or a variant changed structure (for example, options merged or split), rollback may not map cleanly to every row.

When rollback is available

Rollback is available when your task history and configuration support it — for example, after a successful execution where snapshots exist and the task has not been invalidated by unrelated destructive changes.

Scheduled rollback (when offered) runs according to your scheduling settings and the same snapshot and stale rules as manual rollback.

Stale protection explained

Stale protection means SalePilot may skip rolling back a variant if the current Shopify price no longer matches what we expect from the post-execution state. That usually indicates the merchant or another process changed the price after SalePilot’s run.

In those cases, blindly restoring an old snapshot could overwrite legitimate newer prices. Skipping is a safeguard — not an error in SalePilot’s logic.

Why a row may be skipped

Common reasons include:

• The variant was edited in Shopify Admin or another app after execution.
• Inventory or catalog structure changed in a way that breaks the expected mapping.
• Permissions or API limits prevented reading or writing the variant at rollback time.
• Stale protection detected a mismatch between snapshot expectations and live data.

Manual rollback

You can initiate rollback from the task workflow when the product supports it. Review the preview or summary of affected variants before confirming, and inspect skipped rows in the results if any appear.

Scheduled rollback

For scheduled sales, you may configure SalePilot to restore prices after the sale ends. Timing follows your schedule and background processing; see the scheduling guide for status labels and timing expectations.

What to do if rollback needs review

Export or screenshot affected SKUs, compare current Shopify prices to your campaign records, and adjust manually where rollback skipped rows or partial updates occurred.

Email info@esafqa.com with your store domain, task ID, and screenshots if you believe a skip was incorrect — we will help interpret logs where possible.

Best practices

• Preview carefully before any execution; rollback is a remedy, not a replacement for review.
• Avoid overlapping bulk tools on the same variants during sale windows.
• Keep a separate record of critical price lists if your business requires auditability.
• After rollback, spot-check high-value SKUs in Shopify Admin.