Six ways your store's setup gets written
Building a new store, moving one over, changing a live one, fixing a problem, editing by hand, and using a template are six ways a store's setup gets written, and all are treated the same once you confirm.
How the AI writes your store's setup safely covers the single path every store setup goes through: draft, check, confirm, record. But "the AI drafted it" can mean several different things depending on what's happening. Reqursor recognizes six categories, and every one of them ends at the same place: a confirmed store definition (the official written description of a store) that Reqursor treats exactly the same way.
The six categories
| Category | What triggers it | Who reviews it |
|---|---|---|
| AI generation | You describe a brand-new store from scratch. | You, in the preview-and-confirm step. |
| AI migration | You bring an existing store onto Reqursor. | You, before anything is brought over. |
| AI customization | You ask for a change to a live store: a new page, a different color scheme, a promotion. | You, in the preview-and-confirm step. |
| AI remediation | The AI works out what caused an unexpected change or a failure and proposes a fix based on the evidence. | You, in the preview-and-confirm step. |
| Human-direct edit | Someone edits the setup's underlying files directly, bypassing the AI. | Whoever made the edit, reviewed the same way any direct edit to the record is. |
| Template resolution | A store template and the changes you chose on top of it are combined into one complete setup. | No new review: you already approved the template and the changes that produced it. |
A closer look at each:
AI generation
The AI builds a complete store setup from a one-line brief. See How AI store generation works.
AI migration
The AI analyzes an existing store and drafts a matching setup for you to review before anything is brought over. Full end-to-end migration is rolling out progressively: see what's live in What is Reqursor?.
AI customization
The same conversational approach, applied to a store that's already live: "make the brand warmer," add a wholesale page, run a seasonal promotion.
AI remediation
Human-confirmed by design
Reqursor does not automatically fix problems on its own. When it detects an unexpected change (a change nobody asked for) or a failure, it works out the cause and proposes a fix for you to approve: the same preview-and-confirm step as any other change. See How Reqursor fixes unexpected changes with AI for the full path from detection to a confirmed fix.
Human-direct edit
Occasionally, someone with direct access to a store's setup files edits them without going through the AI at all. This is the rare exception, not the common path; most agencies never need it.
Template resolution
When a store is built or updated from a template, Reqursor combines the template's standard settings with the changes you chose into one complete setup automatically. That's a mechanical merge of choices you've already made, not a new judgment call, so it doesn't need a fresh approval.
Why the category doesn't matter afterward
All six categories produce the same kind of result: a set of fields that follows the store definition, confirmed and put on the record. Once that's done, Reqursor can't tell, and doesn't need to know, which category produced it. See How the AI writes your store's setup safely. Every change behaves predictably, leaves a record you can look back on, and can be undone in one click, back to the last version that worked. That applies equally to all six.
Where to go next
How the AI writes your store's setup safely
How a plain-language request becomes a checked, confirmed, on-the-record store setup, and why the result is no different from one a person wrote by hand.
How a change is planned, made and checked
A closer look at the three steps every change goes through: what each one guarantees, and why every change is safe to repeat.