LVNDRInstall
Install LVNDR from the Shopify App Store. Shopify asks you to approve the app's access.
The app reads and writes products, collections, pages, blogs, menus, themes, inventory and sales channels. It never requests orders or customers.
| Access | Used for |
|---|---|
| Products | Products, variants, options, media, metafields and the undo of each |
| Online store pages | Pages, blogs and blog posts |
| Publications | Which sales channels a product or collection is published to |
| Navigation | Menus |
| Themes | Reading theme settings files, and editing product media alt text |
| Inventory and locations | Available quantity per location on tracked variants |
The first snapshot
The first snapshot starts on its own when the app is installed. It reads every tracked record once and stores it as version 1.
While it runs, the change log shows a card: “Taking the first snapshot”, with how many records are saved so far. It updates on its own. On a large catalogue it can take several minutes, and it runs in passes that carry on where the last one stopped.
When it is done, a “First steps” card shows for a week, and the “What LVNDR watches” panel on the right shows counts: products, collections, pages, blogs, blog posts, menus, themes and metafield definitions.
Until a record has a snapshot, its first change has no “before” state. The log marks such a change “First time seen; no before state”.
If the snapshot stops with an error, a red banner shows it: “The first snapshot did not finish”. “Try again” carries on; records already saved are kept. Later, Settings > Data > “Re-read every record” reads everything again and logs anything that differs.
What the change log shows
The home page is the change log: the 50 most recent changes, newest first. Each row has four columns.
| Column | Content |
|---|---|
| When | How long ago. Click it to open the change. |
| Resource | The record's title and its type (product, collection, page and so on). Click the title for the record's history. |
| What changed | Created, Edited or Deleted, with a one-line summary of the fields. |
| Who | An actor badge with a short note on how LVNDR knows. See Reading the change log. |
Above the list, filters narrow it by type, action, actor, text and date. The page header has two actions.
- Mark restore point: records the current moment so everything after it can be rolled back. Use it before an import or a bulk edit.
- Refresh: checks Shopify's admin event log for who did what right now. The scheduler does this every minute anyway.
The side panels show what LVNDR watches, your alert threshold (change it in Settings), recent restore points, agent runs, and who made changes in the last 30 days.
How quickly changes appear
| Change | Appears |
|---|---|
| Product, page, blog or post edit | Within seconds, from a Shopify event delivery |
| Who made it (when Shopify records it) | Within a minute, from the admin event poll |
| Collection rules, sources or SEO; menus; themes; metafield definitions | Within 10 minutes, from a periodic re-read |
| Media alt text | Daily, from the full sweep |
See Coverage for the full list and the reasons.
Where things are
The app's navigation has five entries.
| Entry | Content |
|---|---|
| Change log | The home page described above |
| Agent runs | Work announced by AI agents and scripts, each with its changes and an undo of the whole run. See Running agents safely. |
| Restore points | Every restore point, where it came from, and the rollback preview for each |
| Stores | Links to other stores whose change logs you can read from here, the codes that let another store read this one, and whether that store may run restore proofs here |
| Settings | Agents & API (keys and OAuth connections), plan and usage, alerts (email, threshold, test email), the alert webhook, which apps count as agents, the restore proof store, backups, summaries when they are on, data (export, re-read every record, delete all history), the audit log |
Backups and agent access
Settings > Backups downloads a ZIP of the latest snapshot of every tracked record, or uploads one daily or weekly to your own S3-compatible bucket. See Backups and exports.
The REST API, the MCP server and the CLI are included on every plan. New keys can read and undo; rolling back and exporting are switched on per key.
If AI agents or scripts change your store, read Running agents safely next.