Changelog

What’s new

Dates are build dates. Versions before the App Store listing are numbered 0.x.

1.0 · 2026-10-19

Listed on the Shopify App Store.
Changes: a field pill and a percent chip on every row, All / Not restored / Restored, a bottom bar that jumps to Batches, Issues and the restore log, and Refresh — it reads the store again right away.
Restore where you stand: one preview box next to the row, the alert, the batch or the snapshot; the products of a small scope are read live before the preview, so an edit whose webhook has not landed yet is still seen.
Free: every variant remembered (the 2,000 cap is gone) and one restore a day, one product each; every preview and picker is open on Free, only the write of more than one product asks for Pro.
Issues: a tick per row and one action for the ticked rows; Home shows the newest restores with their status.
A burst of edits is told by its quiet, not by the clock: the chat message comes once the import has stopped.
Channels: a switch per channel — off keeps its settings and its place on the plan, receives nothing.

First build on the njX watch core: a snapshot of every variant, a log of every price, compare-at and status change from product webhooks and a nightly re-read, five catalogue rules with alerts to Telegram, Slack, Discord and e-mail.
Restore in three steps: what (a product; on Pro a collection, a vendor or tag search, a time window), back to when (before the last change, yesterday, a named snapshot, an exact moment), a preview of every value now → will be, and a button that names the number of values it writes. Every value is read again right before it is written; a value that moved since the preview is skipped and listed. Every restore has an Undo and reports to your channels.
Alerts with a Restore button for the three rules a restore fixes; the daily digest ends with “Restore yesterday’s changes” on paid plans.
Business: named snapshots and timers — back to “Before BFCM” at 00:00, by itself; timers pause without Business and resume when it is back.
Tested on a 2,000-product store replayed through the real pipeline: 500 edits, a restore to a moment in the middle, the store back exactly to that state; skipped moves and throttled writes handled.