Undo: what it restores, and what it doesn't
Undoing a change takes a store's design, settings, and technical setup back to an earlier version, but never its orders, products, or media.
How every change is checked before it goes live gives the big picture of going back to an earlier version: it is handled as just another change going live, not as a fragile reversal. This page answers the next question: exactly what comes back, and what doesn't.
What comes back, and what doesn't
| Restored exactly | Restored as far as possible | Never touched |
|---|---|---|
| The software versions your store runs | Technical setup that Reqursor Platform manages for you | Orders, customers, and other business data |
| Settings and on/off switches for features | Links to stored passwords and keys (if the password or key was changed since then, it may need to be changed again) | Uploaded media and images |
| Design basics: colors, fonts, and the rest | Outside services Reqursor doesn't directly manage, like your domain name (DNS) settings | |
| Page layouts | ||
| How much computing power the store can use | ||
| The settings that keep each store separate |
The one sentence to remember
Undoing a change restores your store's design, settings, and technical setup. It never touches your orders, products, customer data, or uploaded images.
Why some things are restored only "as far as possible"
An undo can't always reverse everything cleanly. Say a newer version changed how the store's data is organized behind the scenes (a change to the database structure, for instance). Going back to the old version of the store's application alone could leave it out of step with data that has moved forward since. Reqursor Platform spots this kind of situation. It either warns you or stops the undo completely, rather than quietly finishing only part of it.
Why some things are never touched at all
Business data (orders, customers, products, uploaded media) was never part of a store's saved setup to begin with (see Core concepts). An undo only reverts what is in that saved setup. It was never going to affect what your customers have done on the store since.
Why this matters for your agency
- You can undo with confidence. A bad design or settings change can be reversed without any risk to sales made in the meantime.
- The scope is predictable and easy to explain to a client. "Your design and settings go back; your orders and data don't move" is a simple, accurate sentence.
- You're told, not surprised, when something can't fully reverse. An undo that can't finish cleanly says so up front.
Where to go next
How an undo gets triggered
The ways an undo like this actually starts: suggested by the AI, requested by your agency, or run across all your stores.
How 'go back to yesterday' finds the right version
How a plain-language request turns into one exact version before you confirm anything.
Why you can't undo just part of a change
Why an undo always goes back to a whole version, and what to do if you only need part of one back.