Build your store with PapelAI: an AI store builder that keeps you in control

Most store builders make you choose. Drag-and-drop editors are quick but stop at the edges of the template. Code gives full control but turns every headline change into a small project. AI site generators produce a first draft in seconds, then leave you to work out what they changed. An AI store builder is only useful if it gives you the speed without taking the decisions away from you.

This guide shows how to build an online store with the rebuilt PapelShip store builder and PapelAI: choosing a theme, editing on the live page, asking the AI Copilot for changes you approve, dropping into code or an MCP-connected agent when you need to, and publishing with version history behind you.

What should an AI store builder actually do?

AI is good at the slow, repetitive parts of building a store: drafting section copy, rewriting a product description in a different tone, turning a pile of support answers into a FAQ, or explaining where a setting lives. It is bad at facts it was never told, such as your refund terms, your delivery times or exactly what a license includes. A useful AI store builder plays to the first set of strengths and protects you from the second.

• –It works on your real store, not on a separate generated site you have to copy from.
• –It shows a change before it lands. You review an AI edit the way you would review a colleague's work.
• –It is reversible. Every change, whether a person or the AI made it, can be rolled back.
• –It doesn't lock you in. When a design needs something the editor or the AI can't express, you can open the code.

The PapelShip store builder was rebuilt from the ground up in Changelog 7.5 around exactly this split: a visual editor on the live page, PapelAI for describing changes, a code editor for full control and MCP for working from your own tools. The rest of this guide takes them in the order most sellers use them.

Start from a theme that fits what you sell

A theme is more than a colour scheme. It decides how the catalogue is filtered, what a product page shows before someone buys and how checkout opens. Picking the right one removes most of the structural work, which leaves the editor and the AI to handle wording and style, the parts that actually make a store yours.

Every theme comes with the same essentials: the visual editor, a cart drawer with discount codes and a single-page checkout, a customer portal, verified reviews, several languages and currencies, and separate designs for phone, tablet and desktop. You can preview each one on the themes page before you commit.

How visual editing on the live page works

The rebuilt editor works on the page your customers will see, not on a form that describes it. That sounds like a small difference until you try it: you stop translating between a settings panel and the result.

• –Click to select. Click any section, text, card or button on your store to select it.
• –Double-click to edit text in place. Headlines, descriptions and button labels change where they sit.
• –Use the layers panel for anything nested. Every section is listed together with the elements inside it: headings, texts, buttons and cards. It is the quickest way to reach an element tucked behind another.
• –Change content one item at a time. Stat cards, pricing plans, FAQ questions, reviews, badges, features, comparison rows and videos can each be added, duplicated, reordered, hidden or removed.
• –Style any block. Typography, colours, spacing, corner radius and visibility can be set per block, with separate visibility for mobile and desktop.

Guarda il video

Two details matter more than they look. First, every image and video in the builder is picked from your store's Files library, with folders, search and uploads, so a product shot lives in one place instead of being uploaded five times. Second, stat cards, available in Cards, Minimal and Bar styles for light and dark themes, take sold, rating, review and product counts from your real store data. You can't type a flattering number into them, which is exactly why visitors can trust them.

How to edit your store with the PapelAI Copilot

The AI Copilot lives inside your store and dashboard, and you can use it in two ways. Ask it questions, such as where a setting is or how to set up a feature you haven't used. Or describe a change in a sentence and let it make the edit. When it makes a change, it proposes it and waits: nothing is applied until you approve it.

Copilot requests are powered by monthly AI credits, so spend them on the work that is slow by hand: rewriting several product descriptions in one consistent voice, restructuring a long landing page into clearer sections, turning support answers into FAQ entries, or getting step-by-step guidance on a part of the dashboard you rarely visit.

The quality of an AI edit depends mostly on the instruction. Four habits make the difference between an edit you approve straight away and one you redo:

1. 01

   Name the target

   Say which page and section you mean: "the FAQ on the home page", not "the questions". The more precise the target, the smaller and safer the edit.

2. 02

   Give it the facts

   Supply prices, delivery times, platforms and what the product includes. The AI should phrase your facts, not invent its own.

3. 03

   Set the limits

   State the length, the tone and what must not change, for example "keep the product names and prices exactly as they are".

4. 04

   Review like an editor

   Read the proposed change as a customer would. Approve it, ask for a revision or reject it, and never approve a claim you can't stand behind.

Guarda il video

When to use the code editor or connect an agent through MCP

Most stores never need code. But some changes go beyond any visual editor: a custom section layout, an exact match with an existing brand system, an unusual interaction. For those, the store builder gives you two more ways in, and it helps to see all four together.

The code editor

You can open any section's Liquid and CSS when you want full control. Liquid is a widely used template language: HTML with placeholders and simple logic for things like product names, prices and loops over a collection, so it is approachable for anyone who has written a web page. If you plan to work mostly in code, the Obsidian theme is written in Liquid throughout, and every one of its files can be changed in the code editor.

Editing through MCP

MCP, the Model Context Protocol, is an open standard that lets AI assistants connect to tools and data in other applications. PapelShip's MCP server means an agent you already use, such as Claude Code or one you have built yourself, can edit your store from your own tools instead of through the browser. It suits developers who live in their editor and teams that want to script repetitive changes across many pages or products.

The same rule applies to agents as to the Copilot: review what they change. Saving a named snapshot before a longer agent session costs nothing and makes the whole session easy to undo.

Set up pages and store SEO before you launch

A store that looks finished can still be hard to find in search and awkward to share. The page switcher gives every page its own settings: title, URL, meta description and social image. These are the fields search engines and link previews actually read, so they deserve ten minutes per page.

• –Title. Lead with what the page sells, in the words buyers search for, and keep it short enough not to be cut off in results.
• –URL. Short, lowercase and descriptive. Settle it before you share links, because changing it later breaks the links already out there.
• –Meta description. One or two sentences that say what the visitor gets. It often appears under the title in search results.
• –Social image. The picture shown when the page is shared in Discord, on X or in a messenger. Without one, the preview is chosen for you.

Before launch day, work through the setup checklist, a guided list of what is left before your store is ready, so nothing obvious is missing when the first visitor arrives. The customer login and customer panel can also be adjusted from the builder in every theme, so the pages buyers see after they pay match the store they bought from. If you sell in more than one language, the same SEO fields belong in the translation table; our guide to store localization covers it step by step.

Publish safely with version history and preview links

Fear of breaking a live store is what stops most sellers from improving it. Version history takes that fear away, whether the change came from you, the Copilot or an agent.

• –Automatic snapshots record the state of your store as you work.
• –Named snapshots mark a known-good version before a big change, such as a new homepage layout.
• –One-click restore takes the store back to any snapshot.
• –Shareable preview links let a partner, a client or a community moderator see a change before it goes live.

A simple routine for larger changes: save a named snapshot, make the change in the editor, with the Copilot or in code, share a preview link and check it on a phone, then publish. If something looks wrong afterwards, restore the snapshot and try again. Once the storefront is live, you can also bring the same checkout to an existing site with an embedded checkout widget.

Build the store, keep the decisions

AI makes the slow parts of building a store faster, but the decisions that make a store trustworthy, what you sell, at what price and on what terms, stay with you. Start from a theme, edit on the page, let PapelAI handle the repetitive work under your approval, and keep code, MCP and version history within reach for everything else.

When the store looks right, the next job is selling from it. Our guide to selling digital products online covers pricing, payments and instant delivery.