Why you can't undo just part of a change
An undo always goes back to a whole saved version, not just one piece of it, and the new-change alternative when you only need part of an earlier version back.
An undo always goes back to one complete version of a store's setup, never just a piece of it. Today, Reqursor Platform doesn't support undoing only the design while keeping current settings, or only the settings while keeping the current design.
Why not
At any saved point, a store's setup is one complete unit that can't be split up (see Core concepts). Picking pieces from two different versions would mean inventing a version that never actually existed: one nobody ever previewed or confirmed as a whole. That would quietly weaken the promise that every saved version is something a real confirmation step approved.
What to do instead: a new change, not an undo
If you only need part of an earlier version back, the answer isn't a partial undo. It's a new, ordinary change that happens to borrow from an earlier version:
Describe what you want
Say what you'd like to keep from now and what you'd like to bring back from before. For example: "keep the current homepage copy, but bring back the old color scheme."
The AI drafts a new version of your setup
It combines both into one consistent, valid version.
You review and confirm
The same preview-and-confirm step as any other change.
It goes live as a new version
Not a return to an old one: a new entry in the store's history that happens to include some parts from an earlier point.
Still fully recorded
Because it's an ordinary confirmed change, it's recorded and can be reviewed exactly like anything else. It just isn't labeled an "undo."
Why this matters for your agency
- No unreviewed mix ever reaches your store. Every version that goes live was previewed and confirmed as a whole, never put together afterward from two different ones.
- You're not limited to all-or-nothing. You just ask for a partial change the same way you'd ask for any other change, in plain language.
- The history stays honest. A new change that borrows from the past is recorded as what it is, not disguised as an undo to a version that never actually existed.
Where to go next
Undo: what it restores, and what it doesn't
What a full undo actually covers.
How the AI writes your store's setup safely
The same draft, check, confirm and record steps this new change goes through.
How 'go back to yesterday' finds the right version
How a full undo finds the version to go back to, for comparison.