ComparisonEarly access
Reqursor Platform or updating stores by hand
The short answer
Updating by hand means making each change in one store at a time. In Reqursor Platform every change passes three separate checks, shows a preview you confirm and can be undone in one click.
At a glance
| What to compare | By hand | Reqursor Platform |
|---|---|---|
| How a change starts | A person edits one store | You describe it in plain words |
| Where a change is made | In the store's own admin or on its server | In Reqursor Platform, then live after you confirm a preview |
| Stores per change | One store at a time | One store per change; updating all stores at once is still being built out |
| Edits made in a store's own admin | Made directly in that store | Designed to show in your dashboard as an unexpected change |
What updating by hand means
By hand means a developer opens a store's own admin, or its server, makes the change there and then repeats it in the next store.
Your team can still do this with Reqursor Platform. A store's own admin stays open to them, and Reqursor Platform is designed to spot the change and show it in your dashboard.
How a change works in Reqursor Platform
You describe the change in plain words and the AI drafts it. Each change passes three separate checks before it touches a store, and anything that fails is stopped with a clear report. The change goes live only after you review a preview and confirm.
The same request always gives the same result, because the part that changes your stores has no AI in it. Afterward the store is compared with the setup you approved, to confirm the two match.
When a change is made outside Reqursor
Reqursor Platform keeps one approved setup per store. A change made by hand is designed to show up in your dashboard as an unexpected change, and you decide what happens next: put the saved setup back, or update it to match.
Updating many stores
Updating all your stores at once is being built out progressively, so it is not something to rely on today.
The design is to group stores by tag, share a base setup through templates with changes per store, and send a change across many stores in stages, with a pause if something goes wrong.
Going back
Every version of a store's setup is kept, so any change can be undone in one click. Orders and customers stay untouched.
Good fit
- Agencies where each update is repeated in every store.
- Teams that want every change previewed and kept on the record.
- Agencies that want edits made outside the process to show up instead of going unnoticed.
Not the right fit
- You need one change pushed to every store at once today. Updating all your stores at once is still being built out.
- You make occasional edits in a store's admin and do not want them tracked. Reqursor Platform is designed to list each one as an unexpected change for you to review.
- Your clients' stores run on a store platform other than the one supported today, or you cannot start with a pilot.
- Running stores around the clock is still in progress in early access.
Frequently asked questions
Updating by hand means a person makes the change in the store's own admin or on its server, then repeats it in the next store. In Reqursor Platform you describe the change in plain words and the AI drafts it. It passes three separate checks and goes live only after you confirm a preview.
Yes. Changes made outside Reqursor are designed to be spotted and shown in your dashboard, where you choose to put the saved setup back or update it to match. We recommend making changes through Reqursor Platform, where every change is checked before it goes live.
Updating all your stores at once is still being built out, so it is not something to rely on today. The design sends a change across many stores in stages, with a pause if something goes wrong. For each store, every change still passes three separate checks and shows a preview.
Yes. Every confirmed change stays in the store's history, credited to whoever or whatever proposed it, so you can review it later, for example for a client. A change made by hand outside Reqursor is reported as an unexpected change instead.
Related pages
Compare it on your own stores
Early access starts with a pilot, so you see the results on your own stores before you choose a plan.