An assistant connected to your store can change your storefront design: sections, layout, colors, fonts and text, on any of your pages. It works on the same saved design the builder edits, so a change made this way shows on your live store right away. To edit inside the builder instead, see Using the builder and Building with the AI assistant.
The three levels of access
- Read storefront design: the assistant can look at your pages and tell you what is on them. It changes nothing.
- Edit storefront design: the assistant can save changes to your live storefront.
- Add custom code: needed on top of the other two before an assistant may touch custom JavaScript, custom CSS or a custom code section. Only the store owner can grant this, and it is never offered as part of a normal connection.
The safe order to work in
- Let it read the page first. Pages differ, so a change written without reading is guesswork.
- Ask for a preview. With read access the assistant can run the whole change through Storeep's checks and show you the result without saving anything.
- Then allow the edit and let it save the same change for real.
Reading and previewing need only Read storefront design, so you can hold back the edit permission until you have seen what the assistant plans to do.
Storefront changes cannot be undone
Storeep keeps no history for changes made this way, and the builder's undo button does not reach them. Once saved, a change is live, and the only way back is to put the old values in again. Before you approve an edit, ask the assistant to note the current values so it can restore them if you do not like the result.
What is refused even with edit access
- Custom code. Any change that would alter custom JavaScript, custom CSS or a custom code section is refused unless the owner granted Add custom code. That code also runs on your checkout, where customers type their details, which is why it is kept apart.
- A checkout with no way to reach the buyer. A change that would leave the checkout asking for neither email nor phone is refused, because orders would arrive with no way to contact the customer.
- Changes that change nothing. A change that would not actually alter anything is refused rather than reported as done, so an assistant cannot claim an edit it did not make.
Markets and pages
Twelve pages can be edited: home, product, landing, collection, collections, cart, checkout, thank you, search, policy, contact and the 404 page. See Which pages you can edit.
- Every market has its own full copy of the design settings and of every page. Colors changed for one market do not reach another, so a two-market store needs two sets of changes.
- Markets drift apart. One market's home page may have a section another does not, so the assistant has to read each market's page before changing it.
- Shared sections still need care. The header, footer and announcement bar sit on each page separately, so changing them everywhere means touching each page.
Rules and corner cases
- Split large redesigns. A very large change sent in one go can fail, sometimes with a message about signing in again. That is the size of the change, not your connection. Smaller batches fix it, reconnecting does not.
- A wrong target is refused, not applied elsewhere. Changes name the section they target, so pointing at the wrong place comes back as a refusal and changes nothing.
- Ask for a second confirmation on a live store. The Ask me again before every change option, ticked when you connect the app, is the safest way to let an assistant near your published pages.
- Every change is logged. See Recent activity in MCP connections.